Document Action: 'MPLS-TP Network Management Framework' to Informational RFC

The IESG <> Thu, 04 March 2010 16:06 UTC

Return-Path: <>
Received: by (Postfix, from userid 30) id EB39D3A8D3F; Thu, 4 Mar 2010 08:06:42 -0800 (PST)
X-idtracker: yes
From: The IESG <>
To: IETF-Announce <>
Subject: Document Action: 'MPLS-TP Network Management Framework' to Informational RFC
Message-Id: <>
Date: Thu, 04 Mar 2010 08:06:42 -0800
Cc: mpls mailing list <>, mpls chair <>, Internet Architecture Board <>, RFC Editor <>
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 04 Mar 2010 16:06:43 -0000

The IESG has approved the following document:

- 'MPLS-TP Network Management Framework '
   <draft-ietf-mpls-tp-nm-framework-05.txt> as an Informational RFC

This document is the product of the Multiprotocol Label Switching Working Group. 

The IESG contact persons are Adrian Farrel and Ross Callon.

A URL of this Internet-Draft is:

Technical Summary

  The document provides the network management framework for the
  Transport Profile of Multi-Protocol Label Switching (MPLS-TP). It
  relies on the management terminology from the ITU-T and describes
  a NM architecture for the Transport Profile of MPLS.

  Such management could be based on multi-tiered distributed management
  systems.  Thes document provides network and element management 
  architectures that could be applied.

Working Group Summary

  The document is part of the MPLS-TP project, the cooperation
  between IETF and ITU-T to specify an MPLS transport profile.
  There are no outstanding issues. It is put on the standards
  track to resolve issues around how the ITU-T references IETF

Document Quality

  The document is a framework document and will mainly be used 
  as input to the network management solutions specifications
  that will be published shortly.


   Loa Andersson ( is the Document Shepherd 
   Adrian Farrel ( is the Responsible AD

RFC Editor Note
 Section 2.2 last para on p7
 s/Element Management Function (EMF)/Equipment Management Function (EMF)/