|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Normative
|
|
3.
|
Justification for the specific reference:
|
|
|
G.8121 refers to the terminology defined in RFC 3031.
|
|
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=3031
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This RFC has been in existence since January, 2001.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC 3031 was published January, 2001. It is a standards-track document. Current standards status of this document can be found at http://www.rfc-editor.org/rfcxx00.html.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
RFC 3031 is the overall document for MPLS technology in general.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[MPLS-ATM] Davie, B., Lawrence, J., McCloghrie, K., Rekhter,/
Y., Rosen, E., Swallow, G. and P. Doolan, "MPLS/
using LDP and ATM VC Switching", RFC 3035,/
January 2001./
/
[MPLS-BGP] "Carrying Label Information in BGP-4", Rekhter,/
Rosen, Work in Progress./
/
[MPLS-CR-LDP] "Constraint-Based LSP Setup using LDP", Jamoussi,/
Editor, Work in Progress./
/
[MPLS-FRMRLY] Conta, A., Doolan, P. and A. Malis, "Use of Label/
Switching on Frame Relay Networks Specification",/
RFC 3034, January 2001./
/
[MPLS-LDP] Andersson, L., Doolan, P., Feldman, N., Fredette,/
A. and B. Thomas, "LDP Specification", RFC 3036,/
January 2001./
/
[MPLS-RSVP-TUNNELS] "Extensions to RSVP for LSP Tunnels", Awduche,/
Berger, Gan, Li, Swallow, Srinvasan, Work in/
Progress./
/
[MPLS-SHIM] Rosen, E., Rekhter, Y., Tappan, D., Fedorkow, G.,/
Farinacci, D. and A. Conta, "MPLS Label Stack/
Encoding", RFC 3032, January 2001./
/
[MPLS-TRFENG] Awduche, D., Malcolm, J., Agogbua, J., O'Dell, M./
and J. McManus, "Requirements for Traffic/
Engineering Over MPLS", RFC 2702, September 1999./
|
|
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):
|
|
|
References should always be made to RFC numbers (and not by other designations such as STD, BCP, etc.). References not to be made to documents referred to as "Internet Drafts" or RFCs categorized as "Historic". Normative references should not be made to RFCs that are not standards, for example, "Informational" and "Experimental" RFCs.
|
|
