UNLIMITED FREE
ACCESS
TO THE WORLD'S BEST IDEAS

SUBMIT
Already a GlobalSpec user? Log in.

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

Customize Your GlobalSpec Experience

Finish!
Privacy Policy

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

IETF RFC 7150

Conveying Vendor-Specific Constraints in the Path Computation Element Communication Protocol

active, Most Current
Buy Now
Organization: IETF
Publication Date: 1 March 2014
Status: active
Page Count: 12
scope:

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-Variable that can be carried in any existing PCEP object.

Document History

IETF RFC 7150
March 1, 2014
Conveying Vendor-Specific Constraints in the Path Computation Element Communication Protocol
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)...

References

Advertisement