@misc{rfc6291,
    series =    {Request for Comments},
    number =    6291,
    howpublished =  {RFC 6291},
    publisher = {RFC Editor},
    doi =       {10.17487/RFC6291},
    url =       {https://www.rfc-editor.org/info/rfc6291},
    author =    {Huub van Helvoort and Dan Romascanu and Ron Bonica and Scott Mansfield and Loa Andersson},
    title =     {{Guidelines for the Use of the "OAM" Acronym in the IETF}},
    pagetotal = 9,
    year =      2011,
    month =     jun,
    abstract =  {At first glance, the acronym "OAM" seems to be well-known and well-understood. Looking at the acronym a bit more closely reveals a set of recurring problems that are revisited time and again. This document provides a definition of the acronym "OAM" (Operations, Administration, and Maintenance) for use in all future IETF documents that refer to OAM. There are other definitions and acronyms that will be discussed while exploring the definition of the constituent parts of the "OAM" term. This memo documents an Internet Best Current Practice.},
}