{"draft":"draft-ietf-opsawg-mpls-tp-oam-def-10","doc_id":"RFC6291","title":"Guidelines for the Use of the \"OAM\" Acronym in the IETF","authors":["L. Andersson","H. van Helvoort","R. Bonica","D. Romascanu","S. Mansfield"],"format":["ASCII","HTML"],"page_count":"9","pub_status":"BEST CURRENT PRACTICE","status":"BEST CURRENT PRACTICE","source":"Operations and Management Area Working Group","abstract":"At first glance, the acronym \"OAM\" seems to be well-known and\r\nwell-understood.  Looking at the acronym a bit more closely reveals a\r\nset of recurring problems that are revisited time and again.\r\n\r\nThis document provides a definition of the acronym \"OAM\" (Operations,\r\nAdministration, and Maintenance) for use in all future IETF documents\r\nthat refer to OAM.  There are other definitions and acronyms that\r\nwill be discussed while exploring the definition of the constituent\r\nparts of the \"OAM\" term.  This memo documents an Internet Best Current \r\nPractice.","pub_date":"June 2011","keywords":["[--------]"],"obsoletes":[],"obsoleted_by":[],"updates":[],"updated_by":[],"see_also":["BCP0161"],"doi":"10.17487\/RFC6291","errata_url":null}