|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 7771 (2016)
|
|
Title:
|
Switching Provider Edge (S-PE) Protection for MPLS and MPLS Transport Profile (MPLS-TP) Static Multi-Segment Pseudowires
|
|
|
2.
|
Status of approval:
|
|
|
The referred RFC was approved by IESG (Internet Engineering Steering Group).
|
|
3.
|
Justification for the specific reference:
|
|
|
G.8131 Amd. 2 provides end-to-end protection for pseudowires (PWs) carried over MPLS-TP Label Switched Paths (LSPs) as defined in Appendix A (Optional Linear Protection Approach) of the referenced RFC.
|
|
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:
|
|
|
The referenced RFC is an Internet Standards Track document.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
The referenced RFC was approved by IESG and published.
|
|
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:
|
|
|
IETF RFC 2119 (1997), Key words for use in RFCs to Indicate Requirement Levels/
IETF RFC 5659 (2009) An Architecture for Multi-Segment Pseudowire Emulation Edge-to-Edge/
IETF RFC 6378 (2011), MPLS Transport Profile (MPLS-TP) Linear Protection/
IETF RFC 6478 (2012), Pseudowire Status for Static Pseudowires/
IETF RFC 6870 (2013), Pseudowire Preferential Forwarding Status Bit/
IETF RFC 6718 (2012), Pseudowire Redundancy/
IETF RFC 7271 (2014), MPLS Transport Profile (MPLS-TP) Linear Protection to Match the Operational Expectations of Synchronous Digital Hierarchy,Optical Transport Network, and Ethernet Transport Network Operators/
IETF RFC 7324 (2014), Updates to MPLS Transport Profile Linear Protection/
IETF Idraft-ietf-pals-redundancy-spe-02 (2015), Pseudowire Redundancy on S-PE
|
|
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):
|
|
|
The following URL contains additional information on the referenced RFC:
https://datatracker.ietf.org/doc/rfc7771/
|
