datatracker.ietf.org
Sign in
Version 5.6.2.p2, 2014-07-24
Report a bug

p2mp pw protection for MPLS-TP network
draft-liu-pwe3-mpls-tp-p2mp-pw-protection-03

Document type: Expired Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2013-12-11 (latest revision 2013-06-09)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: Expired
Responsible AD: (None)
Send notices to: No addresses provided

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found here:
http://www.ietf.org/archive/id/draft-liu-pwe3-mpls-tp-p2mp-pw-protection-03.txt

Abstract

The requirements of MPLS-TP in RFC 5654 include a requirement(R63) that requires MPLS-TP MUST be possible to provide protection for MPLS-TP data plane without any IP forwarding capability and control plane.If applying 1:1 protection mechanism for the p2mp traffic in rfc6718 , it must have a return path to coordinate switch state to select the same path to receive and send traffic packet.For the above problem,this document describes a kind of protection solution to recovery and protect the p2mp traffic under the failure condition. This document is a product of a joint Internet Task Force(IETF) / International Telecommunications Union Telecommunications Standardization Sector (ITU-T) effort to include an MPLS Transport Profile within the IETF MPLS and PWE3 architectures to support the capabilities and functionalities of a packet transport network as defined by the ITU-T.

Authors

Guoman Liu <liu.guoman@zte.com.cn>

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