|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 3260 (2002)
|
|
Title:
|
D. Grossman, "New Terminology and Clarifications for Diffserv", April 2002
|
|
|
2.
|
Status of approval:
|
|
|
Informational
|
|
3.
|
Justification for the specific reference:
|
|
|
Technical specifications that use the Internet Protocol will need to reference RFCs.
|
|
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=3260
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Informational
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Informational
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] 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./
/
[2] Blake, S., Black, D., Carlson, M., Davies, E., Wang, Z. and W./
Weiss, "An Architecture for Differentiated Services", RFC 2475,/
December 1998./
/
[3] Heinanen, J., Baker, F., Weiss, W. and J. Wrocklawski, "Assured/
Forwarding PHB Group", RFC 2597, June 1999./
/
[4] Ramakrishnan, K., Floyd, S. and D. Black "The Addition of/
Explicit Congestion Notification (ECN) to IP", RFC 3168,/
September 2001./
/
[5] Bradner, S. and V. Paxon, "IANA Allocation Guidelines for Values/
in the Internet Protocol and Related Headers", BCP 37, RFC2780,/
March 2000./
/
[6] Westerinen, A., Schnizlein, J., Strassner, J., Scherling, M.,/
Quinn, B., Herzog, S., Huynh, A., Carlson, M., Perry, J. and S./
Waldbusser, "Terminology for Policy-Based Management", RFC 3198,/
November 2001./
[7] Davie, B., Charny, A., Baker, F., Bennett, J.C.R., Benson, K.,/
Le Boudec, J., Chiu, A., Courtney, W., Cavari, S., Firoiu, V.,/
Kalmanek, C., Ramakrishnam, K. and D. Stiliadis, "An Expedited/
Forwarding PHB (Per-Hop Behavior)", RFC 3246, March 2002./
/
[8] Baker, F., "Requirements for IP Version 4 Routers", RFC 1812,/
June 1995./
/
[9] Braden, R., "Requirements for Internet Hosts -- Communications/
Layers", STD 3, RFC 1122, October 1989./
/
[10] Braden, R., "Requirements for Internet Hosts -- Application and/
Support", STD 3, RFC 1123, October 1989./
|
|
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.
|
|
