RFC 4859: Codepoint Registry for the Flags Field in the Resource Reservation Protocol-Traffic Engineering (RSVP-TE) Session Attribute Object
In plain English — editorial summary, not part of the RFC
This document provides instructions to IANA for the creation of a new codepoint registry for the flags field in the Session Attribute object of the Resource Reservation Protocol Traffic Engineering (RSVP-TE) signaling messages used in Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) signaling. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4859
- Published
- April 2007
- Authors
- A. Farrel
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 5
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4863Wildcard Pseudowire TypeCurrent
May 2007
- RFC 4847Framework and Requirements for Layer 1 Virtual Private NetworksCurrent
April 2007
- RFC 4872RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) RecoveryUpdated
May 2007
- RFC 4873GMPLS Segment RecoveryUpdated
May 2007
- RFC 4874Exclude Routes - Extension to Resource ReserVation Protocol-Traffic Engineering (RSVP-TE)Updated
April 2007
- RFC 4875Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs)Updated
May 2007
- RFC 4842Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Circuit Emulation over Packet (CEP)Current
April 2007
- RFC 4834Requirements for Multicast in Layer 3 Provider-Provisioned Virtual Private Networks (PPVPNs)Current
April 2007
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?