|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 7271 (2014)
|
|
Title:
|
MPLS Transport Profile (MPLS-TP) Linear Protection to Match the Operational Expectations of Synchronous Digital Hierarchy, Optical Transport Network, and Ethernet Transport Network Operators
|
|
|
2.
|
Status of approval:
|
|
|
The referred RFC was approved by IESG (Internet Engineering Steering Group).
|
|
3.
|
Justification for the specific reference:
|
|
|
G.8131 describes linear protection switching protocol and mechanism for MPLS-TP.
The referenced RFC specifies the priority order of various protection switching inputs and describes protection switching operation including priority evaluation and state machines.
[Note that the RFC number and URL will be updated before publication once they are available.]
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding document is available at: https://datatracker.ietf.org/ipr/search/.
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This is a standards track document as "Proposed Standard". It updates RFC 6378 and it was updated by RFC 8234. No errata exist.
NB - previous reference to this entry was [IETF RFC psc-itu]
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
The status of the referred RFC, is "Proposed Standard".
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
References within the referenced RFC are listed under item (8).
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[RFC2119] IETF RFC 2119 (1997), Key words for use in RFCs to Indicate Requirement Levels/
[RFC4427] IETF RFC 4427 (2006), Recovery (Protection and Restoration) Terminology for Generalized Multi-Protocol Label Switching (GMPLS)/
[RFC5226] IETF RFC 5226 (2008), Guidelines for Writing an IANA Considerations Section in RFCs/
[RFC5586] IETF RFC 5586 (2009), MPLS Generic Associated Channel/
[RFC5654] IETF RFC 5654 (2009), Requirements of an MPLS Transport Profile/
[RFC5920] IETF RFC 5920 (2010), Security Framework for MPLS and GMPLS Networks/
[RFC6372] IETF RFC 6372 (2011), MPLS Transport Profile (MPLS-TP) Survivability Framework/
[RFC6378] IETF RFC 6378 (2011), MPLS Transport Profile (MPLS-TP) Linear Protection/
[G841] ITU-T Recommendation G.841 (1998), Types and characteristics of SDH network protection architectures/
[G873.1] ITU-T Recommendation G.873.1 (2011), Optical Transport Network (OTN): Linear protection/
[G8031] ITU-T Recommendation G.8031/Y.1342 (2011), Ethernet Linear Protection Switching
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
Reference should always be made by RFC number (and not by other designations such as STD, BCP, etc.). References should not be made to documents referred to as "Internet Drafts" or to IETF RFCs categorized as Historic or Experimental. Normative references must only be made to IETF RFCs that are Standards Track or to Informational RFCs that have IETF consensus.
|
