PCEP extensions for Circuit Style Policies Cisco Systems, Inc.
Eurovea Central 3. Pribinova 10 Bratislava 811 09 Slovakia ssidor@cisco.com
Cisco Systems, Inc.
zali@cisco.com
Airtel India
Praveen.Maheshwari@airtel.com
Ciena
rrokui@ciena.com
Nokia
andrew.stone@nokia.com
Verizon
luay.jalil@verizon.com
Huawei Technologies
pengshuping@huawei.com
Juniper Networks
tsaad@juniper.net
Bell Canada
daniel.voyer@bell.ca
PCE Working Group This document proposes a set of extensions for Path Computation Element Communication Protocol (PCEP) for Circuit Style Policies - Segment-Routing Policy designed to satisfy requirements for connection-oriented transport services. New TLV is introduced to control path recomputation triggers and new flag to add ability to request path with strict hops only. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.
Usage of Segment-routing and PCEP in connection-oriented transport services require path persistancy and hop-by-hop behavior for PCE computed paths. Circuit-Style Policy introduced in requires PCEP extensions, which are covered in this document. This document: Introduces possibility to request strict path from the PCE by extending LSP-EXTENDED-FLAG TLV Adding new TLV for encoding blocked path recomputation triggers to the PCE is introduced, to be carried inside the LSP object, which is defined in . Clarifies usage of existing O-flag from RP object in Segment-routing PCEP extensions described in this document are applicable to RSVP-TE and SR-TE.
The following terminologies are used in this document: Explicit Route Object Interior Gateway Protocol Label Switched Path. Label Switched Path Attributes. Optical Transport Network. Path Computation Client Path Computation Element Path Computation Element Protocol. Synchronous Digital Hierarchy Segment Identifier Synchronous Optical Network Segment Routing. Segment Routing Traffic Engineering.
O-flag is proposed in the LSP-EXTENDED-FLAG TLV, which was introduced in 5.1.2 of and extended with E-flag in The format of the LSP-EXTENDED-FLAG is as follows:
Type (16 bits): the value is TBD1 by IANA. Length (16 bits): multiple of 4 octets. O (Strict-Path): If set to 1, this indicates to the PCE that a path exclusively made of strict hops is required. Strict hop definition can be found in Section 4.1
This document defines new TLV for the LSP Object for encoding information about blocked path recomputation triggers.
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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type = TBD2 | Length = 4 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Reserved | Flags |T|P| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type (16 bits): the value is TBD2 by IANA. Length (16 bits): 4 octets MUST be set to zero by the sender and MUST be ignored by the receiver. This document defines the following flag bits. The other bits MUST be set to zero by the sender and MUST be ignored by the receiver. T (Topology-change): If set to 1, the PCE MUST NOT trigger recomputation as a result of received updated topology information. P (Periodic-timer): If set to 1, the PCE MUST NOT trigger recomputation based on any periodic timer.
PCC MAY set the O flag in LSP-EXTENDED-FLAG TLV in PCRpt message to the PCE to indicate that a path exclusively made of strict hops is required. O flag cleared or LSP-EXTENDED-FLAG TLV not included indicates that a loose path is acceptable. In PCUpdate or PCInitiate messages, when the O bit is set, this indicates that strict path is provided. The flag is applicable only for stateful messages. Existing O flag in RP object MAY be used to indicate similar behavior in PCReq and PCRep messages as described in as described in Section 7.4.1 of . If O flag is set to 1 for both stateful and stateless messages for SR paths introduced in , the PCE MUST use Adjacency SIDs only.
PCC MAY set flags in RECOMPUTATION-TRIGGERS-TLV to block specific triggers. If TLV is not included or all flags are set to 0, then the PCE MAY use any event to start path computation. Disabled recomputation triggered by topology event is not blocking path computation started based PCRpt or based on updated state of associated LSP. If trigger blocked by specific flag is not supported or allowed on the PCE, then PCE MAY ignore received flag value. The PCE SHOULD reflect blocked triggers in PCUpdate message. TLV MAY be included in PCInitiate and PCUpdate messages to indicate, which triggers will be disabled on the PCE. PCC should reflect flag values in PCRpt messages to forward requirement to other PCEs in the network.
No additional security measure is required.
defines the LSP-EXTENDED-FLAG TLV. IANA is requested to make the following assignment from the "LSP-EXTENDED-FLAG TLV Flag Field" registry: Bit Description Reference TBD1Strict-Path Flag (O)This document
IANA is requested to make the assignment of a new value for the existing "PCEP TLV Type Indicators" registry as follows: TLV Type TLV Name Reference TBD2RECOMPUTATION-TRIGGERS TLVThis document