|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 2205 (1997)
|
|
Title:
|
Resource Reservation Protocol (RSVP) -- Version 1 Functional Specification, September 1997
|
|
|
2.
|
Status of approval:
|
|
|
Approved standards track document.
|
|
3.
|
Justification for the specific reference:
|
|
|
Draft Recommendation Y.NGN-ET-Tech refers to IETF RFC 2205 for Resource ReSerVation Protocol (RSVP).
|
|
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=2205
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This RFC has been in existence since September 1997. This text is a Proposed Standard.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC 2205 was published in September, 1997. It is a standards-track document and is currently in the "Proposed Standard" state. Updated by RFC 6437, RFC 5946, RFC 4495, RFC 3936, RFC 2750, RFC 6780.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
RFC 2205 is a resource reservation setup protocol designed for an integrated services Internet and is expected to be widely used.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[Baker96] Baker, F., "RSVP Cryptographic Authentication", Work in Progress./
[RFC 1633] Braden, R., Clark, D., and S. Shenker, "Integrated Services in the Internet Architecture: an Overview", RFC 1633, ISI, MIT, and PARC, June 1994./
[FJ94] Floyd, S. and V. Jacobson, "Synchronization of Periodic Routing Messages", IEEE/ACM Transactions on Networking, Vol. 2, No. 2, April, 1994./
[RFC 2207] Berger, L. and T. O'Malley, "RSVP Extensions for IPSEC Data Flows", RFC 2207, September 1997./
[RFC 2113] Katz, D., "IP Router Alert Option", RFC 2113, cisco Systems, February 1997./
[RFC 2210] Wroclawski, J., "The Use of RSVP with Integrated Services", RFC 2210, September 1997./
[PolArch96] Herzog, S., "Policy Control for RSVP: Architectural Overview". Work in Progress./
[OPWA95] Shenker, S. and L. Breslau, "Two Issues in Reservation Establishment", Proc. ACM SIGCOMM '95, Cambridge, MA, August 1995./
[RSVP93] Zhang, L., Deering, S., Estrin, D., Shenker, S., and D. Zappala, "RSVP: A New Resource ReSerVation Protocol", IEEE Network, September 1993.
|
|
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.
|
|
