|
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:
|
|
|
Draft Rec. X.cso refers to The COPS (Common Open Policy Service) Protocol, IETF RFC 2748, January 2000.
|
|
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=2748
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Proposed Standard
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Updated by: 4261
|
|
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:
|
|
|
[RSVP] Braden, R., Zhang, L., Berson, S., Herzog, S./
and S. Jamin, "Resource ReSerVation Protocol/
(RSVP) Version 1 - Functional Specification",/
RFC 2205, September 1997./
/
[WRK] Yavatkar, R., Pendarakis, D. and R. Guerin, "A/
Framework for Policy-Based Admission Control",/
RFC 2753, January 2000./
/
[SRVLOC] Guttman, E., Perkins, C., Veizades, J. and M./
Day, "Service Location Protocol , Version 2",/
RFC 2608, June 1999./
/
[INSCH] Shenker, S. and J. Wroclawski, "General/
Characterization Parameters for Integrated/
Service Network Elements", RFC 2215, September/
1997./
/
[IPSEC] Atkinson, R., "Security Architecture for the/
Internet Protocol", RFC 2401, August 1995./
/
[HMAC] Krawczyk, H., Bellare, M. and R. Canetti,/
"HMAC: Keyed-Hashing for Message/
Authentication", RFC 2104, February 1997./
/
[MD5] Rivest, R., "The MD5 Message-Digest Algorithm",/
RFC 1321, April 1992./
/
[RSVPPR] Braden, R. and L. Zhang, "Resource ReSerVation/
Protocol (RSVP) - Version 1 Message Processing/
Rules", RFC 2209, September 1997./
/
[TLS] Dierks T. and C. Allen, "The TLS Protocol/
Version 1.0", RFC 2246, January 1999./
/
[IANA] http://www.isi.edu/in-/
notes/iana/assignments/port-numbers/
/
[IANA-CONSIDERATIONS] Alvestrand, H. and T. Narten, "Guidelines for/
Writing an IANA Considerations Section in/
RFCs", BCP 26, RFC 2434, October 1998./
|
|
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):
|
|
|
None
|
|
