Protocol Action: 'Requirements for OAM in MPLS Transport Networks' to Proposed Standard

The IESG <> Fri, 12 March 2010 14:47 UTC

Return-Path: <>
Received: by (Postfix, from userid 30) id D4B953A6D24; Fri, 12 Mar 2010 06:47:31 -0800 (PST)
X-idtracker: yes
From: The IESG <>
To: IETF-Announce <>
Subject: Protocol Action: 'Requirements for OAM in MPLS Transport Networks' to Proposed Standard
Message-Id: <>
Date: Fri, 12 Mar 2010 06:47:31 -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: Fri, 12 Mar 2010 14:47:32 -0000

The IESG has approved the following document:

- 'Requirements for OAM in MPLS Transport Networks '
   <draft-ietf-mpls-tp-oam-requirements-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 lists architectural and functional requirements for the
  Operations, Administration and Maintenance of the MPLS Transport
  Profile. These requirements apply to pseudowires, Label Switched
  Paths, and MPLS-TP Sections.

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.
  The working group has consensus on the document, and the ITU-T
  has indicated that it supports the publication

  The ITU-T has one outstanding issue on which they could not reach
  consensus: there will a continued discussion on the requirements
  for OAM interworking/translation, and further requirements may be
  subsequently brought to the IETF in a new I-D.

  The document has been 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 OAM solutions specifications that will be
  published shortly.


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