MPLS Guide PCEP
3HE 18686 AAAB TQZZA © 2022 Nokia.
Use subject to Terms available at: www.nokia.com
311
Note:
1. Nokia proprietary
The behavior and limitations of the implementation of the objects in Table 32 are as
follows.
• The PCE treats all supported objects received in a PCReq message as
mandatory, regardless of whether the P-flag in the object’s common header is
set (mandatory object) or not (optional object).
• The PCC implementation will always set the B-flag (B=1) in the metric object
containing the hop metric value, which means that a bound value must be
included in PCReq message. The PCE returns the computed value in the
PCRep message with flags set identically to the PCReq message.
• The PCC implementation will always set flags B=0 and C=1 in the metric object
for the IGP or TE metric values in the PCReq message. This means that the
request is to optimize (minimize) the metric without providing a bound value. The
PCE returns the computed value in the PCRep message with flags set
identically to the PCReq message.
• The IRO and LOAD-BALANCING objects are not part of the NSP PCE feature.
If the PCE receives a PCReq message with one or more of these objects, it will
ignore them regardless of the setting of the P-flag, and will process the path
computations normally.
• The LSPA, metric, and bandwidth objects are also included in the PCRpt
message. The inclusion of these objects in the PCRpt message is proprietary to
Nokia.
The following features are not supported on the 7705 SAR:
• PCE discovery using IS-IS, per RFC 5089, and OSPF, per RFC 5088, along with
corresponding extensions for discovering stateful PCE, per draft-sivabalan-pce-
disco-stateful
• security of the PCEP session using MD5 or TLS between PCEP peers
• PCEP synchronization optimization as per draft-ietf-pce-stateful-sync-
optimizations
PCEP-ERROR Object N/A PCErr
LOAD-BALANCING Object N/A PCReq
CLOSE Object N/A CLOSE
Table 32 Base PCEP TLVs, Objects, and Messages (Continued)
TLV, Object, or Message Contained in
Object
Contained in Message