MPLS-TP protection for interconnected rings
draft-liu-mpls-tp-interconnected-ring-protection-05
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Guoman Liu , Masahiro Daikoku , Takeshi Maruyama | ||
Last updated | 2014-04-20 (Latest revision 2013-10-17) | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The requirements for MPLS Transport Profile include a requirement (R93) that requires MPLS-TP must support recovery mechanisms for a network constructed from interconnected rings that protect user data that traverses more than one ring. In particular, This includes protecting against cases of failure at the ring-interconnect nodes and links. This document presents different scenario of interconnected rings and special mechanism to address recovery of the failure of ring-interconnect nodes and links. . This document is a product of a joint Internet Engineering 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
Masahiro Daikoku
Takeshi Maruyama
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)