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

 
Document Type Expired Internet-Draft (individual)
Last updated 2013-12-11 (latest revision 2013-06-09)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

Email authors IPR References Referenced by Nits Search lists

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://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.)