RFC 2206: RSVP Management Information Base using SMIv2
In plain English — editorial summary, not part of the RFC
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the Resource Reservation Protocol (RSVP) within the interface attributes defined in the Integrated Services Model. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2206
- Published
- September 1997
- Authors
- F. Baker; J. Krawczyk; A. Sastry
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 64
- 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 2205Resource ReSerVation Protocol (RSVP) -- Version 1 Functional SpecificationUpdated
September 1997
- RFC 2208Resource ReSerVation Protocol (RSVP) -- Version 1 Applicability Statement Some Guidelines on DeploymentCurrent
September 1997
- RFC 2209Resource ReSerVation Protocol (RSVP) -- Version 1 Message Processing RulesCurrent
September 1997
- RFC 2203RPCSEC_GSS Protocol SpecificationUpdated
September 1997
- RFC 2210The Use of RSVP with IETF Integrated ServicesCurrent
September 1997
- RFC 2211Specification of the Controlled-Load Network Element ServiceCurrent
September 1997
- RFC 2212Specification of Guaranteed Quality of 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?