Domain Subobjects for Resource Reservation Protocol - Traffic Engineering (RSVP-TE) (RFC7898)
Original Publication Date: 2016-Jun-01
Included in the Prior Art Database: 2016-Jun-29
Internet Society Requests For Comment (RFCs)
D. Dhody: AUTHOR [+4]
nodes (including domains).
Internet Engineering Task Force (IETF) D. Dhody Request for Comments: 7898 U. Palle Category: Experimental V. Kondreddy ISSN: 2070-1721 Huawei Technologies R. Casellas CTTC June 2016
Domain Subobjects for Resource Reservation Protocol - Traffic Engineering (RSVP-TE)
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.
Status of This Memo
This document is not an Internet Standards Track specification; it is published for examination, experimental implementation, and evaluation.
This document defines an Experimental Protocol for the Internet community. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 7841.
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7898.
al. Experimental [Page 1]
RFC 7898 Domain Subobjects for RSVP-TE June 2016
Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this docum...