RFC 7898: Domain Subobjects for Resource Reservation Protocol - Traffic Engineering (RSVP-TE)
In plain English — editorial summary, not part of the RFC
The Resource Reservation Protocol - Traffic Engineering (RSVP-TE) specification and the Generalized Multiprotocol Label Switching (GMPLS) extensions to RSVP-TE allow abstract nodes and resources to be explicitly included in a path setup. Further, Exclude Route extensions to RSVP-TE allow abstract nodes and resources to be explicitly excluded in a path setup. This document specifies new subobjects to include or exclude Autonomous Systems (ASes), which are identified by a 4-byte AS number, and Interior Gateway Protocol (IGP) areas during path setup.
Document record
- Document ID
- RFC7898
- Published
- June 2016
- Authors
- D. Dhody; U. Palle; V. Kondreddy; R. Casellas
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- rtg
- Pages
- 18
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7897Domain Subobjects for the Path Computation Element Communication Protocol (PCEP)Current
June 2016
- RFC 7699Generalized Labels for the Flexi-Grid in Lambda Switch Capable (LSC) Label Switching RoutersCurrent
November 2015
- RFC 7570Label Switched Path (LSP) Attribute in the Explicit Route Object (ERO)Current
July 2015
- RFC 7487Configuration of Proactive Operations, Administration, and Maintenance (OAM) Functions for MPLS-Based Transport Networks Using RSVP-TECurrent
March 2015
- RFC 8625Ethernet Traffic Parameters with Availability InformationCurrent
August 2019
- RFC 8779Path Computation Element Communication Protocol (PCEP) Extensions for GMPLSUpdated
July 2020
- RFC 6517Mandatory Features in a Layer 3 Multicast BGP/MPLS VPN SolutionCurrent
February 2012
- RFC 9306Vendor-Specific LISP Canonical Address Format (LCAF)Current
October 2022
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?