Network Management Requirements for MPLS-based Transport Networks
draft-ietf-mpls-tp-nm-req-06

Approval announcement
Draft of message to be sent after approval:

Announcement

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@ietf.org>, 
    mpls chair <mpls-chairs@tools.ietf.org>
Subject: Protocol Action: 'MPLS TP Network Management Requirements' to Proposed Standard

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:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-nm-req-06.txt

Ballot Text

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
  supports.

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
  documents.

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.

Personnel

   Loa Andersson (loa@pi.nu) is the Document Shepherd.
   Adrian Farrel (adrian.farrel@huawei.com) is the Responsible AD.

RFC Editor Note