|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Approved by IESG (Internet Engineering Steering Group)
|
|
3.
|
Justification for the specific reference:
|
|
|
Draft Rec. Y.1453 refers to Intserv enabled IP network discussed in IETF RFC 2210 (1997).
|
|
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=2210
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
The status of all the referred RFCs, is "Proposed Standard".
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
The status of all the referred RFCs, is "Proposed Standard".
|
|
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] IETF RFC 2205 91997), Resource Reservation Protocol (RSVP) - Version 1 Functional Specification/
[2] IETF RFC 2216 (1997), Network Element QoS Control Service Specification Template /
[3] IETF RFC 2212 (1997), Specification of Guaranteed Quality of Service /
[4] IETF RFC 2211 (1997), Specification of the Controlled Load Quality of Service /
[5] IETF RFC 2215 (1997), General Characterization Parameters for Integrated Service Network Elements /
[6] Baker, F., "RSVP Cryptographic Authentication", Work in Progress/
[7] IETF RFC 1832 (1995), External Data Representation Standard
|
|
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
|
