Movatterモバイル変換


[0]ホーム

URL:


Search RFCs

Advanced Search

RFC Editor

BCP 161

RFC 6291

Guidelines for the Use of the "OAM" Acronym in the IETF,June 2011

File formats:
icon for text fileicon for PDFicon for HTML
Status:
BEST CURRENT PRACTICE
Authors:
L. Andersson
H. van Helvoort
R. Bonica
D. Romascanu
S. Mansfield
Stream:
IETF
Source:
opsawg (ops)

Cite this BCP:TXT  | XML

Discuss this RFC: Send questions or comments to the mailing listiesg@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC


Abstract

At first glance, the acronym "OAM" seems to be well-known andwell-understood. Looking at the acronym a bit more closely reveals aset 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 documentsthat refer to OAM. There are other definitions and acronyms thatwill be discussed while exploring the definition of the constituentparts of the "OAM" term. This memo documents an Internet Best Current Practice.


For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.




IABIANAIETFIRTFISEISOCIETF Trust
ReportsPrivacy StatementSite MapContact Us

Advanced Search

[8]ページ先頭

©2009-2026 Movatter.jp