draft-ietf-pce-stateful-pce-20.txt   draft-ietf-pce-stateful-pce-21.txt 
skipping to change at page 1, line 14 skipping to change at page 1, line 14
Internet-Draft Oracle Internet-Draft Oracle
Intended status: Standards Track I. Minei Intended status: Standards Track I. Minei
Expires: December 21, 2017 Google, Inc. Expires: December 21, 2017 Google, Inc.
J. Medved J. Medved
Cisco Systems, Inc. Cisco Systems, Inc.
R. Varga R. Varga
Pantheon Technologies SRO Pantheon Technologies SRO
June 19, 2017 June 19, 2017
PCEP Extensions for Stateful PCE PCEP Extensions for Stateful PCE
draft-ietf-pce-stateful-pce-20 draft-ietf-pce-stateful-pce-21
Abstract Abstract
The Path Computation Element Communication Protocol (PCEP) provides The Path Computation Element Communication Protocol (PCEP) provides
mechanisms for Path Computation Elements (PCEs) to perform path mechanisms for Path Computation Elements (PCEs) to perform path
computations in response to Path Computation Clients (PCCs) requests. computations in response to Path Computation Clients (PCCs) requests.
Although PCEP explicitly makes no assumptions regarding the Although PCEP explicitly makes no assumptions regarding the
information available to the PCE, it also makes no provisions for PCE information available to the PCE, it also makes no provisions for PCE
control of timing and sequence of path computations within and across control of timing and sequence of path computations within and across
skipping to change at page 26, line 11 skipping to change at page 26, line 11
zero. Note that the intended-attribute-list is optional and thus may zero. Note that the intended-attribute-list is optional and thus may
be omitted. In this case, the PCE MAY use the values in the actual- be omitted. In this case, the PCE MAY use the values in the actual-
attribute-list as the requested parameters for the path. attribute-list as the requested parameters for the path.
The actual-attribute-list consists of the actual computed and The actual-attribute-list consists of the actual computed and
signaled values of the BANDWIDTH and METRIC objects defined in signaled values of the BANDWIDTH and METRIC objects defined in
[RFC5440]. When included as part of the actual-attribute-list, [RFC5440]. When included as part of the actual-attribute-list,
Object-Type 2 ([RFC5440]) SHOULD be used for the BANDWIDTH object and Object-Type 2 ([RFC5440]) SHOULD be used for the BANDWIDTH object and
the C flag SHOULD be set in the METRIC object ([RFC5440]). the C flag SHOULD be set in the METRIC object ([RFC5440]).
Note that the ordering of intended-path, actual-attribute-list,
actual-path and intended-attribute-list is chosen to retain
compatibility with implementations of an earlier version of this
standard.
A PCE may choose to implement a limit on the resources a single PCC A PCE may choose to implement a limit on the resources a single PCC
can occupy. If a PCRpt is received that causes the PCE to exceed can occupy. If a PCRpt is received that causes the PCE to exceed
this limit, the PCE MUST notify the PCC using a PCNtf message with this limit, the PCE MUST notify the PCC using a PCNtf message with
Notification Type 4 (Stateful PCE resource limit exceeded) and Notification Type 4 (Stateful PCE resource limit exceeded) and
Notification Value 1 (Entering resource limit exceeded state) and Notification Value 1 (Entering resource limit exceeded state) and
MUST terminate the session. MUST terminate the session.
6.2. The PCUpd Message 6.2. The PCUpd Message
A Path Computation LSP Update Request message (also referred to as A Path Computation LSP Update Request message (also referred to as
skipping to change at page 33, line 29 skipping to change at page 33, line 29
LSP Object-Class is 32. LSP Object-Class is 32.
LSP Object-Type is 1. LSP Object-Type is 1.
The format of the LSP object body is shown in Figure 11: The format of the LSP object body is shown in Figure 11:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PLSP-ID | Flag | O|A|R|S|D| | PLSP-ID | Flag | O |A|R|S|D|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
// TLVs // // TLVs //
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 11: The LSP Object format Figure 11: The LSP Object format
PLSP-ID (20 bits): A PCEP-specific identifier for the LSP. A PCC PLSP-ID (20 bits): A PCEP-specific identifier for the LSP. A PCC
creates a unique PLSP-ID for each LSP that is constant for the creates a unique PLSP-ID for each LSP that is constant for the
lifetime of a PCEP session. The PCC will advertise the same PLSP-ID lifetime of a PCEP session. The PCC will advertise the same PLSP-ID
 End of changes. 3 change blocks. 
2 lines changed or deleted 7 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/