RFC 2212: Specification of Guaranteed Quality of Service
In plain English — editorial summary, not part of the RFC
This memo describes the network element behavior required to deliver a guaranteed service (guaranteed delay and bandwidth) in the Internet. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2212
- Published
- September 1997
- Authors
- S. Shenker; C. Partridge; R. Guerin
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6660Encoding Three Pre-Congestion Notification (PCN) States in the IP Header Using a Single Diffserv Codepoint (DSCP)Current
July 2012
- RFC 2215General Characterization Parameters for Integrated Service Network ElementsCurrent
September 1997
- RFC 2996Format of the RSVP DCLASS ObjectCurrent
November 2000
- RFC 2997Specification of the Null Service TypeCurrent
November 2000
- RFC 2998A Framework for Integrated Services Operation over Diffserv NetworksCurrent
November 2000
- RFC 3086Definition of Differentiated Services Per Domain Behaviors and Rules for their SpecificationCurrent
April 2001
- RFC 3374Problem Description: Reasons For Performing Context Transfers Between Nodes in an IP Access NetworkCurrent
September 2002
- RFC 4094Analysis of Existing Quality-of-Service Signaling ProtocolsCurrent
May 2005
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?