|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 3443 (2003)
|
|
Title:
|
Time To Live (TTL) processing in Multi-Protocol Label Switching (MPLS) networks.
|
|
|
2.
|
Status of approval:
|
|
|
Approved by IESG (Internet Engineering Steering Group).
|
|
3.
|
Justification for the specific reference:
|
|
|
Draft Rec. G.8121/Y.1741 uses the MPLS TTL processing as specified in IETF RFC 3443 (2003).
|
|
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=3443
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
The status of RFC 3443 is "Standards Track".
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
The status of RFC 3443 is "Standards Track".
|
|
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:
|
|
|
[1] Bradner, S. “Key words for use in RFC's to Indicate Requirement Levels”, BCP 14, RFC 2119, March 1997./
[2] Rosen, E., Viswanathan, A. and R. Callon, “Multiprotocol Label Switching Architecture”, RFC 3031, January 2001./
[3] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., Farinacci, D., Li, T. and A. Conta, “MPLS Label Stack Encoding”, RFC 3032, January 2001./
[4] Le Faucheur, F., Wu, L., Davie, B., Davari, S., Vaananen, P., Krishnan, R., Cheval, P. and J. Heinanen, “Multi-Protocol Label Switching (MPLS) Support of Differentiated Services”, RFC 3270, May 2002./
Informative References/
[5] Andersson, L., Doolan, P., Feldman, N., Fredette, A. and B. Thomas, “LDP Specification”, RFC 3036, January 2001./
[6] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V. and G. Swallow, “RSVP-TE: Extensions to RSVP for LSP Tunnels”, RFC 3209, December 2001.
|
|
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.
|
|
