|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Approved by the IETF IESG (Internet Engineering Steering Group)
|
|
3.
|
Justification for the specific reference:
|
|
|
Draft Recommendation Y.NGN-ET-Tech refers to IETF RFC 4594 for mapping between DiffServ Service Classes and differentiated services code points (DSCP).
|
|
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=4594
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
The status of IETF RFC 4594 is "Informational". Current status of these documents can be found at http://www.ietf.org/iesg/1rfc_index.txt.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
The status of IETF RFC 4594 is "Informational". Current status of these documents can be found at http://www.ietf.org/iesg/1rfc_index.txt.
|
|
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:
|
|
|
Normative References/
/
[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, September/
1981./
/
[RFC0793] Postel, J., "Transmission Control Protocol", STD 7, RFC/
793, September 1981./
/
[RFC1349] Almquist, P., "Type of Service in the Internet Protocol/
Suite", RFC 1349, July 1992./
/
[RFC1812] Baker, F., "Requirements for IP Version 4 Routers", RFC/
1812, June 1995./
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[RFC2309] Braden, B., Clark, D., Crowcroft, J., Davie, B., Deering,/
S., Estrin, D., Floyd, S., Jacobson, V., Minshall, G.,/
Partridge, C., Peterson, L., Ramakrishnan, K., Shenker,/
S., Wroclawski, J., and L. Zhang, "Recommendations on/
Queue Management and Congestion Avoidance in the/
Internet", RFC 2309, April 1998./
/
[RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black,/
"Definition of the Differentiated Services Field (DS/
Field) in the IPv4 and IPv6 Headers", RFC 2474, December/
1998./
/
[RFC2475] Blake, S., Black, D., Carlson, M., Davies, E., Wang, Z.,/
and W. Weiss, "An Architecture for Differentiated/
Service", RFC 2475, December 1998./
/
[RFC2597] Heinanen, J., Baker, F., Weiss, W., and J. Wroclawski,/
"Assured Forwarding PHB Group", RFC 2597, June 1999./
/
[RFC3246] Davie, B., Charny, A., Bennet, J.C., Benson, K., Le/
Boudec, J., Courtney, W., Davari, S., Firoiu, V., and D./
Stiliadis, "An Expedited Forwarding PHB (Per-Hop/
Behavior)", RFC 3246, March 2002./
/
[RFC3662] Bless, R., Nichols, K., and K. Wehrle, "A Lower Effort/
Per-Domain Behavior (PDB) for Differentiated Services",/
RFC 3662, December 2003./
/
Informative References/
/
[AUTHMECH] Rescorla, E., "A Survey of Authentication Mechanisms",/
Work in Progress, September 2005./
/
[QBSS] "QBone Scavenger Service (QBSS) Definition", Internet2/
Technical Report Proposed Service Definition, March 2001./
/
[RFC1633] Braden, R., Clark, D., and S. Shenker, "Integrated/
Services in the Internet Architecture: an Overview", RFC/
1633, June 1994./
/
[RFC2205] Braden, R., Zhang, L., Berson, S., Herzog, S., and S./
Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1/
Functional Specification", RFC 2205, September 1997./
/
[RFC2581] Allman, M., Paxson, V., and W. Stevens, "TCP Congestion/
Control", RFC 2581, April 1999./
/
[RFC2697] Heinanen, J. and R. Guerin, "A Single Rate Three Color/
Marker", RFC 2697, September 1999./
/
[RFC2698] Heinanen, J. and R. Guerin, "A Two Rate Three Color/
Marker", RFC 2698, September 1999./
/
[RFC2963] Bonaventure, O. and S. De Cnodder, "A Rate Adaptive Shaper/
for Differentiated Services", RFC 2963, October 2000./
/
[RFC2983] Black, D., "Differentiated Services and Tunnels", RFC/
2983, October 2000./
/
[RFC2996] Bernet, Y., "Format of the RSVP DCLASS Object", RFC 2996,/
November 2000./
/
[RFC3086] Nichols, K. and B. Carpenter, "Definition of/
Differentiated Services Per Domain Behaviors and Rules for/
their Specification", RFC 3086, April 2001./
/
[RFC3168] Ramakrishnan, K., Floyd, S., and D. Black, "The Addition/
of Explicit Congestion Notification (ECN) to IP", RFC/
3168, September 2001./
/
[RFC3175] Baker, F., Iturralde, C., Le Faucheur, F., and B. Davie,/
"Aggregation of RSVP for IPv4 and IPv6 Reservations", RFC/
3175, September 2001./
/
[RFC3290] Bernet, Y., Blake, S., Grossman, D., and A. Smith, "An/
Informal Management Model for Diffserv Routers", RFC 3290,/
May 2002./
/
[RFC3782] Floyd, S., Henderson, T., and A. Gurtov, "The NewReno/
Modification to TCP's Fast Recovery Algorithm", RFC 3782,/
April 2004.
|
|
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.
|
|
