|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 2474 (1998)
|
|
Title:
|
Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers, December 1998
|
|
|
2.
|
Status of approval:
|
|
|
Approved standards track document.
|
|
3.
|
Justification for the specific reference:
|
|
|
This document deals with the management of home networks. This reference is needed to manage external technology not specified in ITU-T.
|
|
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=2474
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This RFC has been in existence since December 1998. This text is a Proposed Standard.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC 2474 was published in December, 1998. It is a standards-track document and is currently in the "Proposed Standard" state. Current standards status of this document can be found at ftp://ftp.isi.edu/in-notes/std/std1.txt
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
RFC 2474 defines the IP header field, called the DS (for differentiated services) field and is expected to be widely used.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] IETF RFC 2402 (1998), IP Authentication Header/
[2] IETF RFC 2475 (1998), An Architecture for Differentiated Services/
[3] S. Floyd and V. Jacobson, "Link-sharing and Resource Management Models for Packet Networks", IEEE/ACM Transactions on Networking, Vol. 3 no. 4, pp. 365-386, August 1995./
[4] IETF RFC 2434 (1998), Guidelines for Writing an IANA Considerations Section in RFCs/
[5] M. Shreedhar and G. Varghese, “Efficient Fair Queuing using Deficit Round Robin", Proc. ACM SIGCOMM 95, 1995/
[6] IETF RFC 2406 (1998), IP Encapsulating Security Payload (ESP)/
[7] J. Bennett and Hui Zhang, "Hierarchical Packet Fair Queuing Algorithms", Proc. ACM SIGCOMM 96, August 1996./
[8] IETF RFC 2460 (1998), Internet Protocol, Version 6 (IPv6) Specification/
[9] IETF STD 5, RFC 791(1980), Internet Protocol/
[10] IETF STD 3, RFC 1122 (1989), Requirements for Internet hosts -communication layers/
[11] IETF RFC 1812 (1995), Requirements for IP Version 4 Routers/
[12] IETF BCP 14, RFC 2119 (1997), Key words for use in RFCs to Indicate Requirement Levels/
[13] D. Stiliadis and A. Varma, "Rate-Proportional Servers: A Design Methodology for Fair Queuing Algorithms", IEEE/ACM Trans. on Networking, April 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):
|
|
|
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.
|
