Supporting Shared Mesh Protection in MPLS-TP Networks
draft-pan-shared-mesh-protection-05

Document Type Expired Internet-Draft (individual)
Last updated 2013-04-22 (latest revision 2012-10-19)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

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-pan-shared-mesh-protection-05.txt

Abstract

Shared mesh protection is a common protection and recovery mechanism in transport networks, where multiple paths can share the same set of network resources for protection purposes. In the context of MPLS-TP, it has been explicitly requested as a part of the overall solution (Req. 67, 68 and 69 in RFC5654 [RFC5654]). It's important to note that each MPLS-TP LSP may be associated with transport network resources. In event of network failure, it may require explicit activation on the protecting paths before switching user traffic over. In this memo, we define a lightweight signaling mechanism for protecting path activation in shared mesh protection-enabled MPLS-TP networks.

Authors

Ping Pan (ppan@infinera.com)
Rajan Rao (rrao@infinera.com)
Biao Lu (blu@infinera.com)
Luyuan Fang (lufang@cisco.com)
Andrew Malis (andrew.g.malis@verizon.com)
Fei Zhang (zhang.fei3@zte.com.cn)
Sam Aldrin (sam.aldrin@huawei.com)
Fatai Zhang (zhangfatai@huawei.com)
Mohana Singamsetty (srsingam@cisco.com)

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