BCP 161, RFC 6291 on Guidelines for the Use of the "OAM" Acronym in the IETF
rfc-editor@rfc-editor.org Fri, 17 June 2011 16:53 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AB2A11E8202; Fri, 17 Jun 2011 09:53:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.48
X-Spam-Level:
X-Spam-Status: No, score=-102.48 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aphKFL+lepsl; Fri, 17 Jun 2011 09:53:13 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by ietfa.amsl.com (Postfix) with ESMTP id 8F3E411E8200; Fri, 17 Jun 2011 09:53:13 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 8379E98C516; Fri, 17 Jun 2011 09:53:13 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 161, RFC 6291 on Guidelines for the Use of the "OAM" Acronym in the IETF
From: rfc-editor@rfc-editor.org
Message-Id: <20110617165313.8379E98C516@rfc-editor.org>
Date: Fri, 17 Jun 2011 09:53:13 -0700
Cc: opsawg@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jun 2011 16:53:14 -0000
A new Request for Comments is now available in online RFC libraries.
BCP 161
RFC 6291
Title: Guidelines for the Use of
the "OAM" Acronym in the IETF
Author: L. Andersson, H. van Helvoort,
R. Bonica, D. Romascanu,
S. Mansfield
Status: Best Current Practice
Stream: IETF
Date: June 2011
Mailbox: loa.andersson@ericsson.com,
huub.van.helvoort@huawei.com,
rbonica@juniper.net, dromasca@avaya.com,
scott.mansfield@ericsson.com
Pages: 9
Characters: 16696
See Also: BCP0161
I-D Tag: draft-ietf-opsawg-mpls-tp-oam-def-10.txt
URL: http://www.rfc-editor.org/rfc/rfc6291.txt
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.
This document is a product of the Operations and Management Area Working Group Working Group of the IETF.
BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC