%% You should probably cite draft-liu-mpls-tp-interconnected-ring-protection-05 instead of this revision. @techreport{liu-mpls-tp-interconnected-ring-protection-01, number = {draft-liu-mpls-tp-interconnected-ring-protection-01}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-liu-mpls-tp-interconnected-ring-protection/01/}, author = {Guoman Liu and Yaacov Weingarten}, title = {{MPLS-TP protection for interconnected rings}}, pagetotal = 11, year = 2012, month = apr, day = 26, abstract = {According to the ring protection Requirements in RFC 5654, Requirement 93 : When a network is constructed from interconnected rings, MPLS-TP MUST support recovery mechanisms that protect user data that traverses more than one ring. This includes the possibility of failure of the ring-interconnect nodes and links,so this document will describle all kinds of interconnected ring Scenarios and several protection solutions for recovery the failure of the ring-interconnect nodes and Links. . 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.}, }