Conveying Vendor-Specific Constraints in the Path Computation Element Communication Protocol
RFC 7470
Document | Type |
RFC - Proposed Standard
(March 2015; No errata)
Obsoletes RFC 7150
|
|
---|---|---|---|
Authors | Fatai Zhang , Adrian Farrel | ||
Last updated | 2018-12-20 | ||
Replaces | draft-farrel-pce-rfc7150bis | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Julien Meuric | ||
Shepherd write-up | Show (last changed 2014-09-12) | ||
IESG | IESG state | RFC 7470 (Proposed Standard) | |
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Alia Atlas | ||
Send notices to | (None) | ||
IANA | IANA review state | IANA OK - Actions Needed | |
IANA action state | RFC-Ed-Ack |
Internet Engineering Task Force (IETF) F. Zhang Request for Comments: 7470 Huawei Obsoletes: 7150 A. Farrel Category: Standards Track Juniper Networks ISSN: 2070-1721 March 2015 Conveying Vendor-Specific Constraints in the Path Computation Element Communication Protocol Abstract The Path Computation Element Communication Protocol (PCEP) is used to convey path computation requests and responses both between Path Computation Clients (PCCs) and Path Computation Elements (PCEs) and between cooperating PCEs. In PCEP, the path computation requests carry details of the constraints and objective functions that the PCC wishes the PCE to apply in its computation. This document defines a facility to carry vendor-specific information in PCEP using a dedicated object and a new Type-Length-Value (TLV) that can be carried in any PCEP object that supports TLVs. This document obsoletes RFC 7150. The only changes from that document are a clarification of the use of the new Type-Length-Value and the allocation of a different code point for the VENDOR- INFORMATION object. Status of This Memo This is an Internet Standards Track document. 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). Further information on Internet Standards is available in Section 2 of RFC 5741. 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/rfc7470. Zhang & Farrel Standards Track [Page 1] RFC 7470 Vendor-Specific Constraints in PCE March 2015 Copyright Notice Copyright (c) 2015 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 document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction ....................................................3 1.1. Conventions Used in This Document ..........................4 2. Procedures for the Vendor Information Object ....................5 2.1. Backward Compatibility for the Vendor Information Object ...7 3. Procedures for the Vendor Information TLV .......................7 3.1. Backward Compatibility .....................................8 4. Protocol Elements ...............................................8 5. IANA Considerations .............................................9 5.1. New PCEP Object ............................................9 5.2. New PCEP TLV ...............................................9 6. Management Considerations ......................................10 6.1. Control of Function and Policy ............................10 6.2. Information and Data Models ...............................10 6.3. Liveness Detection and Monitoring .........................10 6.4. Verifying Correct Operation ...............................10 6.5. Requirements on Other Protocols and Functional Components .11 6.6. Impact on Network Operation ...............................11 7. Security Considerations ........................................11 8. References .....................................................12 8.1. Normative References ......................................12 8.2. Informative References ....................................12 Acknowledgements ..................................................14 Contributors ......................................................14 Authors' Addresses ................................................14 Zhang & Farrel Standards Track [Page 2] RFC 7470 Vendor-Specific Constraints in PCE March 2015 1. Introduction A Path Computation Element (PCE) is an entity (component, application, or network node) that is capable of computing a network path or route based on a network graph and applying computational constraints. An architecture for the use of PCEs is defined in [RFC4655].Show full document text