RFC 2210: The Use of RSVP with IETF Integrated Services
In plain English — editorial summary, not part of the RFC
This note describes the use of the RSVP resource reservation protocol with the Controlled-Load and Guaranteed QoS control services. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2210
- Published
- September 1997
- Authors
- J. Wroclawski
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 33
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2207RSVP Extensions for IPSEC Data FlowsCurrent
September 1997
- RFC 2379RSVP over ATM Implementation GuidelinesCurrent
August 1998
- RFC 2688Integrated Services Mappings for Low Speed NetworksCurrent
September 1999
- RFC 2815Integrated Service Mappings on IEEE 802 NetworksCurrent
May 2000
- RFC 2751Signaled Preemption Priority Policy ElementObsoleted
January 2000
- RFC 2752Identity Representation for RSVPObsoleted
January 2000
- RFC 3210Applicability Statement for Extensions to RSVP for LSP-TunnelsCurrent
December 2001
- RFC 2211Specification of the Controlled-Load Network Element ServiceCurrent
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?