RFC 2211: Specification of the Controlled-Load Network Element Service
In plain English — editorial summary, not part of the RFC
This memo specifies the network element behavior required to deliver Controlled-Load service in the Internet. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2211
- Published
- September 1997
- Authors
- J. Wroclawski
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2212Specification of Guaranteed Quality of ServiceCurrent
September 1997
- RFC 2210The Use of RSVP with IETF Integrated ServicesCurrent
September 1997
- RFC 6660Encoding Three Pre-Congestion Notification (PCN) States in the IP Header Using a Single Diffserv Codepoint (DSCP)Current
July 2012
- RFC 4883Benchmarking Terminology for Resource Reservation Capable RoutersCurrent
July 2007
- RFC 4923Quality of Service (QoS) Signaling in a Nested Virtual Private NetworkCurrent
August 2007
- RFC 2209Resource ReSerVation Protocol (RSVP) -- Version 1 Message Processing RulesCurrent
September 1997
- RFC 2213Integrated Services Management Information Base using SMIv2Current
September 1997
- RFC 2208Resource ReSerVation Protocol (RSVP) -- Version 1 Applicability Statement Some Guidelines on DeploymentCurrent
September 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?