|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
The referred RFCs were approved by IESG (Internet Engineering Steering Group).
|
|
3.
|
Justification for the specific reference:
|
|
|
G.8121 refers to the terminology defined in RFC 3032.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=3032
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
The status of all the referred RFCs is "Proposed Standard".
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
The status of all the referred RFCs is "Proposed Standard".
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
References within the referenced RFCs are listed under item (8).
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] IETF RFC 3031 (2001), Multiprotocol Label Switching Architecture/
[2] IETF BCP 14, RFC 2119 (1997), Key words for use in RFCs to Indicate Requirement Levels/
[3] IETF STD 5, RFC 792 (1981), Internet Control Message Protocol/
[4] IETF RFC 1191 (1990), Path MTU Discovery/
[5] IETF RFC 2113 (1997), IP Router Alert Option/
[6] IETF STD 51, RFC 1661 (1994), The Point-to-Point Protocol (PPP)/
[7] IETF RFC 1885 (1995), Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification/
[8] IETF RFC 1981 (1996), Path MTU Discovery for IP version 6/
[9] IETF RFC 3035 (2001), MPLS Using LDP and ATM VC 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):
|
|
|
All RFCs are 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
|
