This page will soon be deactivated—explore our new, faster, mobile-friendly site, now centralized in MyWorkspace!

Committed to connecting the world

  •  
ITU GSR 2024

ITU-T work programme

Home : ITU-T Home : ITU-T Work Programme : X.1205     
  ITU-T A.5 justification information for referenced document IETF RFC 2749 (2000) in draft X.1205
1. Clear description of the referenced document:
Name: IETF RFC 2749 (2000)
Title: COPS usage for RSVP, January 2000.
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 COPS usage for RSVP, January 2000, IETF RFC 2749.
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=2749
5. Other useful information describing the "Quality" of the document:
Proposed Standard
6. The degree of stability or maturity of the document:
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:
[RSVP-EXT] Herzog, S., "RSVP Extensions for Policy Control", RFC/
2750, January 2000./
/
[RAP] Yavatkar, R., Pendarakis, D. and R. Guerin, "A Framework/
for Policy Based Admission Control", RFC 2753, January/
2000./
/
[COPS] Boyle, J., Cohen, R., Durham, D., Herzog, S., Raja, R. and/
A. Sastry, "The COPS (Common Open Policy Service)/
Protocol", RFC 2748, January 2000./
/
[RSVP] Braden, R., Zhang, L., Berson, S., Herzog, S. and S./
Jamin, "Resource ReSerVation Protocol (RSVP) - Functional/
Specification", RFC 2205, September 1997./
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
Note: This form is based on Recommendation ITU-T A.5