RFC 2474: Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers
In plain English — editorial summary, not part of the RFC
This document defines the IP header field, called the DS (for differentiated services) field. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2474
- Published
- December 1998
- Authors
- K. Nichols; S. Blake; F. Baker; D. Black
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 20
- Also known as
- —
- Updates:
- RFC 791
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 1349 (1992)
- RFC 1455 (1993)
- RFC 2474 (1998)
Referenced by
3 later RFCs formally update or obsolete part of this document.
- RFC 3168The Addition of Explicit Congestion Notification (ECN) to IPUpdated
September 2001
- RFC 3260New Terminology and Clarifications for DiffservCurrent
April 2002
- RFC 8436Update to IANA Registration Procedures for Pool 3 Values in the Differentiated Services Field Codepoints (DSCP) RegistryCurrent
August 2018
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3027Protocol Complications with the IP Network Address TranslatorCurrent
January 2001
- RFC 2432Terminology for IP Multicast BenchmarkingCurrent
October 1998
- RFC 2338Virtual Router Redundancy ProtocolObsoleted
April 1998
- RFC 3768Virtual Router Redundancy Protocol (VRRP)Obsoleted
April 2004
- RFC 2488Enhancing TCP Over Satellite Channels using Standard MechanismsCurrent
January 1999
- RFC 2214Integrated Services Management Information Base Guaranteed Service Extensions using SMIv2Current
September 1997
- RFC 2760Ongoing TCP Research Related to SatellitesCurrent
February 2000
- RFC 2962An SNMP Application Level Gateway for Payload Address TranslationCurrent
October 2000
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?