datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

The Reasons for Selecting a Single Solution for MPLS Transport Profile (MPLS-TP) Operations, Administration, and Maintenance (OAM)
draft-sprecher-mpls-tp-oam-considerations-03

RFC
Document Stream: IETF
Last updated: 2012-04-30
Intended RFC status: Informational
Other versions: (expired, archived): plain text, pdf, html

Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: RFC 6670
IANA Action State: No IC 
On agenda of 2012-05-10 IESG telechat
Responsible AD: Adrian Farrel
IESG Note: Ross Callon (rcallon@juniper.net) is the document shepherd.
Send notices to: nurit.sprecher@nsn.com, hongk@cisco.com, draft-sprecher-mpls-tp-oam-considerations@tools.ietf.org, rcallon@juniper.net

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-sprecher-mpls-tp-oam-considerations.

Abstract:
The MPLS Transport Profile (MPLS-TP) is a profile of the MPLS technology for use in transport network deployments. The work on MPLS-TP has extended the MPLS technology with additional architectural elements and functions that can be used in any MPLS deployment. MPLS-TP is a set of functions and features selected from the extended MPLS toolset and applied in a consistent way to meet the needs and requirements of operators of packet transport networks.

Authors:
Nurit Sprecher <nurit.sprecher@nsn.com>
Kyung-Yeop Hong <hongk@cisco.com>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)