Skip to main content

Use of the Synchronization VECtor (SVEC) List for Synchronized Dependent Path Computations
RFC 6007

Revision differences

Document history

Date By Action
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'A Path Computation Element (PCE) may be required to perform dependent path computations. Dependent path computations …
Received changes through RFC Editor sync (changed abstract to 'A Path Computation Element (PCE) may be required to perform dependent path computations. Dependent path computations are requests that need to be synchronized in order to meet specific objectives. An example of a dependent request would be a PCE computing a set of services that are required to be diverse (disjointed) from each other. When a PCE computes sets of dependent path computation requests concurrently, use of the Synchronization VECtor (SVEC) list is required for association among the sets of dependent path computation requests. The SVEC object is optional and carried within the Path Computation Element Communication Protocol (PCEP) PCRequest (PCReq) message.

This document does not specify the PCEP SVEC object or procedure. This informational document clarifies the use of the SVEC list for synchronized path computations when computing dependent requests. The document also describes a number of usage scenarios for SVEC lists within single-domain and multi-domain environments. This document is not an Internet Standards Track specification; it is published for informational purposes.')
2015-10-14
(System) Notify list changed from pce-chairs@ietf.org, draft-ietf-pce-pcep-svec-list@ietf.org to (None)
2010-09-22
Cindy Morgan State changed to RFC Published from RFC Ed Queue by Cindy Morgan
2010-09-22
Cindy Morgan [Note]: changed to 'RFC 6007' by Cindy Morgan
2010-09-21
(System) RFC published