A Framework for Multi-Protocol Label Switching (MPLS) Operations and Management (OAM)
RFC 4378

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>,
    RFC Editor <rfc-editor@rfc-editor.org>, 
    mpls mailing list <mpls@lists.ietf.org>, 
    mpls chair <mpls-chairs@tools.ietf.org>
Subject: Document Action: 'Operations and Management 
         Requirements for Multi-Protocol Label Switched Networks' to 
         Informational RFC 

The IESG has approved the following documents:

- 'Operations and Management Requirements for Multi-Protocol Label 
   Switched Networks '
   <draft-ietf-mpls-oam-requirements-08.txt> as an Informational RFC
- 'A Framework for MPLS Operations and Management (OAM) '
   <draft-ietf-mpls-oam-frmwk-06.txt> as an Informational RFC

These documents are products of the Multiprotocol Label Switching Working 
Group. 

The IESG contact persons are Alex Zinin and Ross Callon.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-oam-requirements-08.txt

Technical Summary
 
 The OAM requirements document describes requirements for user and data plane
 operations and management for MPLS. These requirements have been gathered
 from network operators who have extensive experience deploying MPLS networks,
 similarly some of these requirements have appeared in other documents. This
 draft specifies Operations and Management requirements for Multi-Protocol 
 Label Switching, as well as for applications of Multi-Protocol Label
 Switching such as pseudowire voice and virtual private network services.

 The OAM framework document desribes how data plane protocols can
 be applied to operations and maintenance procedures for
 Multi-Protocol Label Switching. The document is structured to 
 outline how Operations and Management functionality can be used to 
 assist in fault management, configuration, accounting, performance 
 management and security, commonly known by the acronym FCAPS.
 
Working Group Summary
 
 The WG had a consensus on progressing this document.
 
Protocol Quality
 
 The documents have been reviewed by Alex Zinin for the IESG and
 by Dimitri Papadimitriou for the Routing Area directorat.