Guidelines for the Use of the "OAM" Acronym in the IETF
RFC 6291
also known as BCP 161
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2023-12-12
|
(System) | Imported membership of rfc6291 in bcp161 via sync to the rfc-index |
|
2023-12-12
|
(System) | No history of BCP161 is currently available in the datatracker before this point |
|
2018-12-20
|
(System) | Received changes through RFC Editor sync (changed abstract to 'At first glance, the acronym "OAM" seems to be well-known and well-understood. Looking at the acronym … Received changes through RFC Editor sync (changed abstract to '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.') |
|
2015-10-14
|
(System) | Notify list changed from opsawg-chairs@ietf.org, draft-ietf-opsawg-mpls-tp-oam-def@ietf.org to (None) |
|
2011-06-20
|
Cindy Morgan | [Note]: changed to 'BCP 161; RFC 6291' |
|
2011-06-20
|
Cindy Morgan | State changed to RFC Published from RFC Ed Queue. |
|
2011-06-17
|
(System) | RFC published |