%% You should probably cite rfc6974 instead of this I-D. @techreport{ietf-mpls-tp-ring-protection-03, number = {draft-ietf-mpls-tp-ring-protection-03}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-mpls-tp-ring-protection/03/}, author = {Yaacov Weingarten and Stewart Bryant and Daniele Ceccarelli and Diego Caviglia and Francesco Fondelli and Marco Corsi and Bo Wu and Xuehui Dai}, title = {{Applicability of MPLS-TP Linear Protection for Ring Topologies}}, pagetotal = 29, year = 2012, month = nov, day = 5, abstract = {This document presents an applicability of linear protection mechanisms for Multi-Protocol Label Switching Transport Profile (MPLS-TP) in ring topologies. Protection on rings offers a number of opportunities for optimization as the protection choices are starkly limited (all traffic traveling one way around a ring can only be switched to travel the other way on the ring), but also suffers from some complications caused by the limitations of the topology. Requirements for MPLS-TP protection and specifically for protection in ring topologies are discussed in "Requirements of an MPLS Transport Profile" (RFC 5654) and "MPLS Transport Profile (MPLS-TP) Survivability Framework" (RFC 6372). This document shows how MPLS-TP linear protection as defined in RFC 6378 can be applied to ring topologies, discusses how most of the requirements are met, and describes scenarios in which the function provided by applying linear protection in a ring topology falls short of some of the requirements. 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.}, }