RFC 2996: Format of the RSVP DCLASS Object
In plain English — editorial summary, not part of the RFC
This document specifies the format of the DCLASS object and briefly discusses its use. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2996
- Published
- November 2000
- Authors
- Y. Bernet
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2997Specification of the Null Service TypeCurrent
November 2000
- RFC 4094Analysis of Existing Quality-of-Service Signaling ProtocolsCurrent
May 2005
- RFC 2998A Framework for Integrated Services Operation over Diffserv NetworksCurrent
November 2000
- RFC 2961RSVP Refresh Overhead Reduction ExtensionsUpdated
April 2001
- RFC 3086Definition of Differentiated Services Per Domain Behaviors and Rules for their SpecificationCurrent
April 2001
- RFC 3097RSVP Cryptographic Authentication -- Updated Message Type ValueCurrent
April 2001
- RFC 3175Aggregation of RSVP for IPv4 and IPv6 ReservationsUpdated
September 2001
- RFC 2814SBM (Subnet Bandwidth Manager): A Protocol for RSVP-based Admission Control over IEEE 802-style networksCurrent
May 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?