Protocol Action: 'MPLS TP Network Management Requirements' to Proposed Standard

The IESG <> Mon, 09 November 2009 17:36 UTC

Return-Path: <>
Received: by (Postfix, from userid 30) id 4B8773A6891; Mon, 9 Nov 2009 09:36:11 -0800 (PST)
X-idtracker: yes
From: The IESG <>
To: IETF-Announce <>
Subject: Protocol Action: 'MPLS TP Network Management Requirements' to Proposed Standard
Message-Id: <>
Date: Mon, 09 Nov 2009 09:36:11 -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: Mon, 09 Nov 2009 17:36:11 -0000

The IESG has approved the following document:

- 'MPLS TP Network Management Requirements '
   <draft-ietf-mpls-tp-nm-req-06.txt> as a Proposed Standard

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

  This document specifies the requirements for the management of
  equipment used in networks supporting an MPLS Transport Profile
  (MPLS-TP). The requirements are defined for specification of
  network management aspects of protocol mechanisms and procedures
  that constitute the building blocks out of which the MPLS
  transport profile is constructed. That is, these requirements
  indicate what management capabilities need to be available in
  MPLS for use in managing the MPLS-TP. This document is intended
  to identify essential network management capabilities, not to
  specify what functions any particular MPLS implementation

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 requirements specification 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.