RFC 3260: New Terminology and Clarifications for Diffserv
In plain English — editorial summary, not part of the RFC
This memo captures Diffserv working group agreements concerning new and improved terminology, and provides minor technical clarifications. It is intended to update RFC 2474, RFC 2475 and RFC 2597. When RFCs 2474 and 2597 advance on the standards track, and RFC 2475 is updated, it is intended that the revisions in this memo will be incorporated, and that this memo will be obsoleted by the new RFCs. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3260
- Published
- April 2002
- Authors
- D. Grossman
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 10
- Also known as
- —
Topics
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 2966Domain-wide Prefix Distribution with Two-Level IS-ISObsoleted
October 2000
- RFC 3768Virtual Router Redundancy Protocol (VRRP)Obsoleted
April 2004
- RFC 2583Guidelines for Next Hop Client (NHC) DevelopersCurrent
May 1999
- RFC 2519A Framework for Inter-Domain Route AggregationCurrent
February 1999
- RFC 2338Virtual Router Redundancy ProtocolObsoleted
April 1998
- RFC 2269Using the MARS Model in non-ATM NBMA NetworksCurrent
January 1998
- RFC 2236Internet Group Management Protocol, Version 2Updated
November 1997
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?