Domain Subobjects for the Path Computation Element Communication Protocol (PCEP) (RFC7897)
Original Publication Date: 2016-Jun-01
Included in the Prior Art Database: 2016-Jun-29
Internet Society Requests For Comment (RFCs)
D. Dhody: AUTHOR [+3]
node representing a domain is defined in [RFC3209]. In the current document, we specify new subobjects to include or exclude domains including an IGP area or an AS (4 bytes as per [RFC6793]).
Internet Engineering Task Force (IETF) D. Dhody Request for Comments: 7897 U. Palle Category: Experimental Huawei Technologies ISSN: 2070-1721 R. Casellas CTTC June 2016
Domain Subobjects for the Path Computation Element Communication Protocol (PCEP)
The ability to compute shortest constrained Traffic Engineering Label Switched Paths (TE LSPs) in Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) networks across multiple domains has been identified as a key requirement. In this context, a domain is a collection of network elements within a common sphere of address management or path computational responsibility such as an Interior Gateway Protocol (IGP) area or an Autonomous System (AS). This document specifies a representation and encoding of a domain sequence, which is defined as an ordered sequence of domains traversed to reach the destination domain to be used by Path Computation Elements (PCEs) to compute inter-domain constrained shortest paths across a predetermined sequence of domains. This document also defines new subobjects to be used to encode domain identifiers.
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/rfc7897.
Dhody, et al. Experimental [Page 1]
RFC 7897 Domain Subobjects for PCEP June 2016
Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved....