| Internet-Draft | PCEP-LS | May 2024 |
| Dhody, et al. | Expires 17 November 2024 | [Page] |
In order to compute and provide optimal paths, Path Computation Elements (PCEs) require an accurate and timely Traffic Engineering Database (TED). Traditionally, this TED has been obtained from a link state (LS) routing protocol supporting the traffic engineering extensions.¶
This document extends the Path Computation Element Communication Protocol (PCEP) with Link-State and TE Information as an experimental extension.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 17 November 2024.¶
Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
In Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS), a Traffic Engineering Database (TED) is used in computing paths for connection-oriented packet services and for circuits. The TED contains all relevant information that a Path Computation Element (PCE) needs to perform its computations. The TED must be 'complete and accurate' each time the PCE performs a path computation.¶
In MPLS and GMPLS, Interior Gateway Protocols (IGPs) have been used to create and maintain a copy of the TED at each node running the IGP. One of the benefits of the PCE architecture [RFC4655] is the use of computationally more sophisticated path computation algorithms and the realization that these may need enhanced processing power (not necessarily available at each node).¶
Section 4.3 of [RFC4655] describes the potential load of the TED on a network node and proposes an architecture where the TED is maintained by the PCE rather than the network nodes. However, it does not describe how a PCE would obtain the information needed to populate its TED. PCE may construct its TED by participating in the IGP ([RFC3630] and [RFC5305] for MPLS-TE; [RFC4203] and [RFC5307] for GMPLS). An alternative mechanism is offered by BGP-LS [I-D.ietf-idr-rfc7752bis] .¶
[RFC8231] describes a set of extensions to PCEP to provide stateful control. A stateful PCE has access to not only the information carried by the network's IGP, but also the set of active paths and their reserved resources for its computations. Path Computation Client (PCC) can delegate the rights to modify the LSP parameters to an Active Stateful PCE. This requires PCE to quickly be updated on any changes in the topology/TED, so that PCE can meet the need for updating LSPs effectively and in a timely manner. The fastest way for a PCE to be updated on TED changes is via a direct session with each network node and with an incremental update from each network node with only the attributes that gets modified.¶
[RFC8281] describes the setup, maintenance, and teardown of PCE-initiated LSPs under the stateful PCE model, without the need for local configuration on the PCC, thus allowing for a dynamic network that is centrally controlled and deployed. This model requires timely topology and TED updates at the PCE.¶
[RFC5440] describes the specifications for the Path Computation Element Communication Protocol (PCEP). PCEP specifies the communication between a PCC and a PCE, or between two PCEs based on the PCE architecture [RFC4655].¶
This document describes how link-state and TE information can be collected from networks and shared with PCE using the PCEP itself. This is achieved using a new PCEP message format. The mechanism is applicable to physical and virtual links as well as further subjected to various policies.¶
A network node maintains one or more databases for storing link-state and TE information about nodes and links in any given area. Link attributes stored in these databases include: local/remote IP addresses, local/remote interface identifiers, link metric, and TE metric, link bandwidth, reservable bandwidth, per CoS class reservation state, preemption, and Shared Risk Link Groups (SRLG). The node's PCEP process can retrieve topology from these databases and distribute it to a PCE, either directly or via another PCEP Speaker, using the encoding specified in this document.¶
Further [RFC6805] describes Hierarchical-PCE architecture, where a Parent PCE maintains a domain topology map. To build this domain topology map, the Child PCE can carry the border nodes and inter-domain link information to the Parent PCE using the mechanism described in this document. Further, as described in [RFC8637], the Child PCE can also transport abstract Link-State and TE information from a Child PCE to a Parent PCE using the mechanism described in this document to build an abstract topology at the Parent PCE.¶
[RFC8231] describes LSP state synchronization between PCCs and PCEs in the case of stateful PCE. This document does not make any changes to the LSP state synchronization process. The mechanism described in this document are on top of the existing LSP state synchronization.¶
The procedures described in this document are experimental. The experiment is intended to enable research on the usage of PCEP to populate the Link-State and TE Information from a PCC to the PCE. For this purpose, this document specifies a new PCEP message, a new PCEP object, and new TLVs.¶
The new message introduced by this document will not be understood by legacy implementations. On receiving the message, a legacy implementation will behave according to the rules for an unknown message as per [RFC5440]. It is assumed that this experiment will be conducted only when both the PCE and PCC form part of the experiment. It is possible that a PCC or PCE can operate with peers, some of which form part of the experiment and some that do not. In this case, the capability exchange required before using this extension would take care of the mismatch. A PCEP speaker that offers this feature to its peer that does not support or does not wish to support the feature will not receive the indication of support in the Open message, and so is expected to not use the feature. Thus this experimentation would not clash with or cause harm to existing deployments. Further, since a PCEP speaker would use the new message only after capability exchange, there is no danger of this experimentation "escaping" to the wider Internet. A PCEP speaker that receives the new message (that is part of the feature when the use of the feature has not been agreed) will send an error message as described in Section 6.9 of [RFC5440]. A PCEP speaker that receives the new object that is part of the feature when the use of the feature has not been agreed, it will send an error message as described in Section 7.2 of [RFC5440].¶
The experiment will end three years after the RFC is published. At that point, the RFC authors will attempt to determine how widely this has been implemented and deployed. When the results of implementation and deployment are available, this document (or part thereof) will be updated and refined, and then it could be moved from Experimental to Standards Track.¶
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 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
The mechanism specified in this draft is applicable to deployments:¶
Where there is IGP or BGP-LS running but with a need for a faster and direct TE and link-state population and convergence at the PCE.¶
Based on the local policy and deployment scenario, a PCC chooses to send only local information or both local and remote learned information. How a PCE manages the link-state (and TE) information is implementation-specific and thus out of the scope of this document.¶
The prefix information in PCEP-LS can also help in determining the domain of the tunnel destination in the H-PCE (and ACTN) scenario. Section 4.5 of [RFC6805] describes various mechanisms and procedures that might be used, PCEP-LS provides a simple mechanism to exchange this information within PCEP.¶
[RFC8453] defines three types of topology abstraction - (1) Native/White Topology; (2) Black Topology; and (3) Grey Topology. Based on the local policy, the PNC (or Child PCE) would share the domain topology with the MDSC (or Parent PCE) based on the abstraction type. The protocol extensions defined in this document can carry any type of topology abstraction.¶
The following key requirements associated with link-state (and TE) distribution are identified for PCEP:¶
Several new functions are required in PCEP to support distribution of link-state (and TE) information. A function can be initiated either from a PCC towards a PCE (C-E) or from a PCE towards a PCC (E-C). The new functions are:¶
In this document, we define a new PCEP message called LS Report (LSRpt), a PCEP message sent by a PCC to a PCE to report link-state (and TE) information. Each LS Report in an LSRpt message can contain the node or link properties. A unique PCEP-specific LS identifier (LS-ID) is also carried in the message to identify a node or a link that remains constant for the lifetime of a PCEP session. This identifier on its own is sufficient when no IGP or BGP-LS running in the network for PCE to learn link-state (and TE) information. In case PCE learns some information from PCEP and some from the existing mechanism, the PCC SHOULD include the mapping of IGP or BGP-LS identifier to map the information populated via PCEP with IGP/BGP-LS. See Section 8.1 for details.¶
During the PCEP Initialization Phase, PCEP Speakers (PCE or PCC) advertise their support of LS (and TE) distribution via PCEP extensions. A PCEP Speaker includes the "LS Capability" TLV, described in Section 9.2.1, in the OPEN Object to advertise its support for PCEP-LS extensions. The presence of the LS Capability TLV in PCC's OPEN Object indicates that the PCC is willing to send LS Reports with local link-state (and TE) information. The presence of the LS Capability TLV in PCE's Open message indicates that the PCE is interested in receiving LS Reports with local link-state (and TE) information.¶
The PCEP extensions for LS (and TE) distribution MUST NOT be used if one or both PCEP Speakers have not included the LS Capability TLV in their respective OPEN message. If the PCE supports the extensions defined in this document but does not advertise this capability, then upon receipt of an LSRpt message from the PCC, it SHOULD generate a PCErr with error-type 19 (Invalid Operation), error-value TBD1 (Attempted LS Report if LS capability was not advertised) and it will terminate the PCEP session.¶
The LS reports sent by PCC MAY carry the remote link-state (and TE) information learned via existing means like IGP and BGP-LS only if both PCEP Speakers set the R (remote) Flag in the "LS Capability" TLV to 'Remote Allowed (R Flag = 1)'. If this is not the case and LS reports carry remote link-state (and TE) information, then a PCErr with error-type 19 (Invalid Operation) and error-value TBD1 (Attempted LS Report if LS remote capability was not advertised) and it will terminate the PCEP session.¶
The purpose of LS Synchronization is to provide a checkpoint-in-time state replica of a PCC's link-state (and TE) database in a PCE. State Synchronization is performed immediately after the Initialization phase (see [RFC5440]). In the case of stateful PCE ([RFC8231]) it is RECOMMENDED that the LS synchronization should be done before LSP state synchronization.¶
During LS Synchronization, a PCC first takes a snapshot of the state of its database, then sends the snapshot to a PCE in a sequence of LS Reports. Each LS Report sent during LS Synchronization has the SYNC Flag in the LS Object set to 1. The end of synchronization marker is an LSRpt message with the SYNC Flag set to 0 for an LS Object with LS-ID equal to the reserved value 0. If the PCC has no link-state to synchronize, it will only send the end of synchronization marker.¶
Either the PCE or the PCC MAY terminate the session using the PCEP session termination procedures during the synchronization phase. If the session is terminated, the PCE MUST clean up the state it received from this PCC. The session re-establishment MUST be re-attempted per the procedures defined in [RFC5440], including the use of a back-off timer.¶
If the PCC encounters a problem which prevents it from completing the LS synchronization, it MUST send a PCErr message with error-type TBD2 (LS Synchronization Error) and error-value 2 (indicating an internal PCC error) to the PCE and terminate the session.¶
The PCE does not send positive acknowledgements for properly received LS synchronization messages. It MUST respond with a PCErr message with error-type TBD2 (LS Synchronization Error) and error-value 1 (indicating an error in processing the LSRpt) if it encounters a problem with the LS Report it received from the PCC and it MUST terminate the session.¶
The LS reports can carry local as well as remote link-state (and TE) information depending on the R flag in the LS capability TLV.¶
The successful LS Synchronization sequence is shown in Figure 1.¶
+-+-+ +-+-+
|PCC| |PCE|
+-+-+ +-+-+
| |
|-----LSRpt, SYNC=1----->| (Sync start)
| |
|-----LSRpt, SYNC=1----->|
| . |
| . |
| . |
|-----LSRpt, SYNC=1----->|
| . |
| . |
| . |
| |
|-----LSRpt, SYNC=0----->| (End of sync marker
| | LS Report
| | for LS-ID=0)
| | (Sync done)
The sequence where the PCE fails during the LS Synchronization phase is shown in Figure 2.¶
+-+-+ +-+-+
|PCC| |PCE|
+-+-+ +-+-+
| |
|-----LSRpt, SYNC=1----->|
| |
|-----LSRpt, SYNC=1----->|
| . |
| . |
| . |
|-----LSRpt, SYNC=1----->|
| |
|---LSRpt,SYNC=1 |
| \ ,-PCErr---|
| \ / |
| \/ |
| /\ |
| / `-------->| (Ignored)
|<--------` |
The sequence where the PCC fails during the LS Synchronization phase is shown in Figure 3.¶
+-+-+ +-+-+
|PCC| |PCE|
+-+-+ +-+-+
| |
|-----LSRpt, SYNC=1----->|
| |
|-----LSRpt, SYNC=1----->|
| . |
| . |
| . |
|-------- PCErr--------->|
| |
These optimizations are described in [I-D.kondreddy-pce-pcep-ls-sync-optimizations].¶
The PCC MUST report any changes in the link-state (and TE) information to the PCE by sending an LS Report carried on an LSRpt message to the PCE. Each node and Link would be uniquely identified by a PCEP LS identifier (LS-ID). The LS reports may carry local as well as remote link-state (and TE) information depending on the R flag in LS capability TLV. It MAY also include the mapping of IGP or BGP-LS identifier to map the information populated via PCEP with IGP/BGP-LS identifiers.¶
More details about the LSRpt message are in Section 8.1.¶
A permanent PCEP session (section 4.2.8 of [RFC5440]) MUST be established between a PCE and PCC supporting link-state (and TE) distribution via PCEP. In the case of session failure, session re-establishment is re-attempted as per the procedures defined in [RFC5440].¶
As defined in [RFC5440], a PCEP message consists of a common header followed by a variable-length body made of a set of objects that can be either mandatory or optional. An object is said to be mandatory in a PCEP message when the object must be included for the message to be considered valid. For each PCEP message type, a set of rules is defined that specify the set of objects that the message can carry. An implementation MUST form the PCEP messages using the object ordering specified in this document.¶
A PCEP LS Report message (also referred to as LSRpt message) is a PCEP message sent by a PCC to a PCE to report the link-state (and TE) information. An LSRpt message can carry more than one LS Reports (LS object). The Message-Type field of the PCEP common header for the LSRpt message is set to [TBD3].¶
The format of the LSRpt message is as follows:¶
<LSRpt Message> ::= <Common Header>
<ls-report-list>
Where:
<ls-report-list> ::= <LS>[<ls-report-list>]
¶
The LS object is a mandatory object which carries LS information of a node/prefix or a link. Each LS object has a unique LS-ID as described in Section 9.3. If the LS object is missing, the receiving PCE MUST send a PCErr message with Error-type=6 (Mandatory Object missing) and Error-value=[TBD4] (LS object missing).¶
A PCE may choose to implement a limit on the LS information a single PCC can populate. If an LSRpt is received that causes the PCE to exceed this limit, it MUST send a PCErr message with error-type 19 (invalid operation) and error-value 4 (indicating resource limit exceeded) in response to the LSRpt message triggering this condition and SHOULD terminate the session.¶
If a PCEP speaker has advertised the LS capability on the PCEP session, the PCErr message MAY include the LS object. If the error reported is the result of an LS report, then the LS-ID number MUST be the one from the LSRpt that triggered the error.¶
The format of a PCErr message from [RFC5440] is extended as follows:¶
<PCErr Message> ::= <Common Header>
( <error-obj-list> [<Open>] ) | <error>
[<error-list>]
<error-obj-list>::=<PCEP-ERROR>[<error-obj-list>]
<error>::=[<request-id-list> | <ls-id-list>]
<error-obj-list>
<request-id-list>::=<RP>[<request-id-list>]
<ls-id-list>::=<LS>[<ls-id-list>]
<error-list>::=<error>[<error-list>]
¶
The PCEP objects defined in this document are compliant with the PCEP object format defined in [RFC5440]. The P flag and the I flag of the PCEP objects defined in this document MUST always be set to 0 on transmission and MUST be ignored on receipt since these flags are exclusively related to path computation requests.¶
The TLV and the sub-TLV format (and padding) in this document, is as per section 7.1 of [RFC5440].¶
This document defines a new optional TLV for use in the OPEN Object.¶
The LS-CAPABILITY TLV is an optional TLV for use in the OPEN Object for link-state (and TE) distribution via PCEP capability advertisement. Its format is shown in the following figure:¶
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=[TBD5] | Length=4 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Flags |R| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+¶
The type of the TLV is [TBD5] and it has a fixed length of 4 octets.¶
The value comprises a single field - Flags (32 bits):¶
Unassigned bits are considered reserved. They MUST be set to 0 on transmission and MUST be ignored on receipt.¶
Advertisement of the LS capability implies support of local link-state (and TE) distribution, as well as the objects, TLVs and procedures defined in this document.¶
The LS (link-state) object MUST be carried within LSRpt messages and MAY be carried within PCErr messages. The LS object contains a set of fields used to specify the target node or link. It also contains a flag indicating to a PCE that the LS synchronization is in progress. The TLVs used with the LS object correlate with the IGP/BGP-LS encodings.¶
LS Object-Class is TBD6.¶
Four Object-Type values are defined for the LS object so far:¶
The format of all types of LS objects are as follows:¶
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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Protocol-ID | Flag |R|S| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | LS-ID | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ // TLVs // | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+¶
Protocol-ID (8-bit): The field provides the source information. The protocol could be an IGP, BGP-LS, or an abstraction algorithm. In case the PCC only provides local information of the PCC, it MUST use Protocol-ID as Direct. The following values are defined (some of the initial values are the same as [I-D.ietf-idr-rfc7752bis]):¶
+-------------+----------------------------------+ | Protocol-ID | Source protocol | +-------------+----------------------------------+ | 1 | IS-IS Level 1 | | 2 | IS-IS Level 2 | | 3 | OSPFv2 | | 4 | Direct | | 5 | Static configuration | | 6 | OSPFv3 | | 7 | BGP | | 8 | RSVP-TE | | 9 | Segment Routing | | 10 | PCEP | | 11 | Abstraction | +-------------+----------------------------------+¶
Flags (24-bit):¶
LS-ID(64-bit): A PCEP-specific identifier for the node, link, or prefix information. A PCC creates a unique LS-ID for each node/link/prefix that is constant for the lifetime of a PCEP session. The PCC will advertise the same LS-ID on all PCEP sessions it maintains at a given time. All subsequent PCEP messages then address the node/link/prefix by the LS-ID. The values of 0 and 0xFFFFFFFFFFFFFFFF are reserved.¶
Unassigned bits are considered reserved. They MUST be set to 0 on transmission and MUST be ignored on receipt.¶
TLVs that may be included in the LS Object are described in the following sections.¶
In the case of remote link-state (and TE) population when existing IGP/BGP-LS are also used, OSPF and IS-IS may run multiple routing protocol instances over the same link as described in [I-D.ietf-idr-rfc7752bis]. See [RFC8202] and [RFC6549] for more information. These instances define an independent "routing universe". The 64-bit 'Identifier' field is used to identify the "routing universe" where the LS object belongs. The LS objects representing IGP objects (nodes, links, or prefix) from the same routing universe MUST have the same 'Identifier' value; LS objects with different 'Identifier' values MUST be considered to be from different routing universes.¶
The format of the optional ROUTING-UNIVERSE TLV is shown in the following figure:¶
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=[TBD7] | Length=8 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Identifier | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+¶
The below table lists the 'Identifier' values that are defined as well-known in this draft (same as [I-D.ietf-idr-rfc7752bis]).¶
+------------+-----------------------------------+ | Identifier | Routing Universe | +------------+-----------------------------------+ | 0 | Default Layer 3 Routing topology | +------------+-----------------------------------+¶
If this TLV is not present the default value 0 is assumed.¶
To allow identification of VPN link, node, and prefix information in PCEP-LS, a Route Distinguisher (RD) [RFC4364] is used. The LS objects from the same VPN MUST have the same RD; LS objects with different RD values MUST be considered to be from different VPNs.¶
The ROUTE-DISTINGUISHER TLV is defined in [RFC9168] as a Flow Specification TLVs with a separate registry. This document also adds the ROUTE-DISTINGUISHER TLV with TBD15 in the PCEP TLV registry to be used inside the LS object.¶
To realize ACTN, the MDSC needs to build a multi-domain topology. This topology is best served if this is an abstract view of the underlying network resources of each domain. It is also important to provide a customer view of the network slice for each customer. There is a need to control the level of abstraction based on the deployment scenario and business relationship between the controllers.¶
Virtual service coordination function in ACTN incorporates customer service-related knowledge into the virtual network operations in order to seamlessly operate virtual networks while meeting customer's service requirements. [I-D.ietf-teas-actn-requirements] describes various VN operations initiated by a customer/application. In this context, there is a need for associating the abstracted link-state and TE topology with a VN "construct" to facilitate VN operations in PCE architecture.¶
VIRTUAL-NETWORK-TLV as per [RFC9358] can be included in the LS object to identify the link, node, and prefix information belongs to a particular VN.¶
As described in [I-D.ietf-idr-rfc7752bis], each link is anchored by a pair of Router-IDs that are used by the underlying IGP, namely, 48-bit ISO System-ID for IS-IS and 32-bit Router-ID for OSPFv2 and OSPFv3. In case of additional auxiliary Router-IDs used for TE, these MUST also be included in the link attribute TLV (see Section 9.3.9.2).¶
It is desirable that the Router-ID assignments inside the Node Descriptors TLV are globally unique. Some considerations for globally unique Node/Link/Prefix identifiers are described in [I-D.ietf-idr-rfc7752bis].¶
The Local Node Descriptors TLV contains Node Descriptors for the node anchoring the local end of the link. This TLV MUST be included in the LS Report when during a given PCEP session a node/link/prefix is first reported to a PCE. A PCC sends to a PCE the first LS Report either during the State Synchronization, or when a new node/link/prefix is learned at the PCC. The value contains one or more Node Descriptor Sub-TLVs, which allows the specification of a flexible key for any given node/link/prefix information such that the global uniqueness of the node/link/prefix is ensured.¶
This TLV is applicable for all LS Object-Type.¶
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=[TBD8] | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | // Node Descriptor Sub-TLVs (variable) // | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+¶
The value contains one or more Node Descriptor Sub-TLVs defined in Section 9.3.6.¶
The Remote Node Descriptors contain Node Descriptors for the node anchoring the remote end of the link. This TLV MUST be included in the LS Report when during a given PCEP session a link is first reported to a PCE. A PCC sends to a PCE the first LS Report either during the State Synchronization, or when a new link is learned at the PCC. The length of this TLV is variable. The value contains one or more Node Descriptor Sub-TLVs defined in Section 9.3.6.¶
This TLV is applicable for LS Link Object-Type.¶
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=[TBD9] | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | // Node Descriptor Sub-TLVs (variable) // | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+¶
The Node Descriptors TLV (Local and Remote) carries one or more Node Descriptor Sub-TLV follows the format of all PCEP TLVs as defined in [RFC5440], however, the Type values are selected from a new PCEP-LS sub-TLV IANA registry (see Section 13.6).¶
Type values are chosen so that there can be commonality with BGP-LS [I-D.ietf-idr-rfc7752bis]. This is possible because the "BGP-LS Node Descriptor, Link Descriptor, Prefix Descriptor, and Attribute TLVs" registry marks 0-255 as reserved. Thus the space of the sub-TLV values for the Type field can be partitioned as shown below -¶
Range |
---------------+---------------------------------------------
0 | Reserved - must not be allocated.
|
1 .. 255 | New PCEP sub-TLV allocated according to the
| registry defined in this document.
|
256 .. 65535 | Per BGP registry defined by
| [I-D.ietf-idr-rfc7752bis].
| Not to be allocated in this registry.
¶
All Node Descriptors TLVs defined for BGP-LS can then be used with PCEP-LS as well. One new PCEP sub-TLVs for Node Descriptor are defined in this document.¶
+----------+-------------------+----------+----------------+ | Sub-TLV | Description | Length |Value defined in| +----------+-------------------+----------+----------------+ | 24 | SPEAKER-ENTITY-ID | Variable | [RFC8232] | +----------+-------------------+----------+----------------+¶
A new sub-TLV type (24) is allocated for SPEAKER-ENTITY-ID sub-TLV. The length and value fields are as per [RFC8232].¶
The Link Descriptors TLV contains Link Descriptors for each link. This TLV MUST be included in the LS Report when during a given PCEP session a link is first reported to a PCE. A PCC sends to a PCE the first LS Report either during State Synchronization, or when a new link is learned at the PCC. The length of this TLV is variable. The value contains one or more Link Descriptor Sub-TLVs.¶
The 'Link descriptor' TLVs uniquely identify a link among multiple parallel links between a pair of anchor routers similar to [I-D.ietf-idr-rfc7752bis].¶
This TLV is applicable for LS Link Object-Type.¶
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=[TBD10] | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | // Link Descriptor Sub-TLVs (variable) // | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+¶
All Link Descriptors TLVs defined for BGP-LS can then be used with PCEP-LS as well. No new PCEP sub-TLVs for Link Descriptor are defined in this document.¶
The format and semantics of the 'value' fields in most 'Link Descriptor' sub-TLVs correspond to the format and semantics of the value fields in IS-IS Extended IS Reachability sub-TLVs, defined in [RFC5305], [RFC5307] and [RFC6119]. Although the encodings for 'Link Descriptor' TLVs were originally defined for IS-IS, the TLVs can carry data sourced by IS-IS, OSPF, or direct.¶
The information about a link present in the LSA/LSP originated by the local node of the link determines the set of sub-TLVs in the Link Descriptor of the link as described in [I-D.ietf-idr-rfc7752bis].¶
The Prefix Descriptors TLV contains Prefix Descriptors that uniquely identify an IPv4 or IPv6 Prefix originated by a Node. This TLV MUST be included in the LS Report when during a given PCEP session a prefix is first reported to a PCE. A PCC sends to a PCE the first LS Report either during the State Synchronization, or when a new prefix is learned at the PCC. The length of this TLV is variable.¶
This TLV is applicable for LS Prefix Object-Types for both IPv4 and IPv6.¶
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=[TBD11] | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | // Prefix Descriptor Sub-TLVs (variable) // | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+¶
All Prefix Descriptors TLVs defined for BGP-LS can then be used with PCEP-LS as well. No new PCEP sub-TLVs for Prefix Descriptor are defined in this document.¶
This is an optional attribute that is used to carry node attributes. This TLV is applicable for LS Node Object-Type.¶
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=[TBD12] | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | // Node Attributes Sub-TLVs (variable) // | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+¶
All Node Attributes TLVs defined for BGP-LS can then be used with PCEP-LS as well. No new PCEP sub-TLVs for Node Attributes are defined in this document.¶
This TLV is applicable for LS Link Object-Type. The format and semantics of the 'value' fields in some 'Link Attribute' sub-TLVs correspond to the format and semantics of the 'value' fields in IS-IS Extended IS Reachability sub-TLVs, defined in [RFC5305], [RFC5307] and [I-D.ietf-idr-rfc7752bis]. Although the encodings for 'Link Attribute' TLVs were originally defined for IS-IS, the TLVs can carry data sourced by IS-IS, OSPF, or direct.¶
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=[TBD13] | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | // Link Attributes Sub-TLVs (variable) // | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+¶
All Link Attributes TLVs defined for BGP-LS can then be used with PCEP-LS as well. No new PCEP sub-TLVs for Link Attributes are defined in this document.¶
This TLV is applicable for LS Prefix Object-Types for both IPv4 and IPv6. Prefixes are learned from the IGP (IS-IS or OSPF) or BGP topology with a set of IGP attributes (such as metrics, route tags, etc.). This section describes the different attributes related to the IPv4/IPv6 prefixes. Prefix Attributes TLVs SHOULD be encoded in the LS Prefix Object.¶
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=[TBD14] | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | // Prefix Attributes Sub-TLVs (variable) // | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+¶
All Prefix Attributes TLVs defined for BGP-LS can then be used with PCEP-LS as well. No new PCEP sub-TLVs for Prefix Attributes are defined in this document.¶
One of the key objectives of PCEP-LS is to encode and carry only the impacted attributes of a Node, a Link, or a Prefix. To accommodate this requirement, in case of a removal of an attribute, the sub-TLV MUST be included with no 'value' field and length=0 to indicate that the attribute is removed. On receiving a sub-TLV with zero length, the receiver removes the attribute from the database. An absence of a sub-TLV that was included earlier MUST be interpreted as no change.¶
The main source of LS (and TE) information is the IGP, which is not active on inter-AS links. In some cases, the IGP may have information of inter-AS links ([RFC5392], [RFC9346]). In other cases, an implementation SHOULD provide a means to inject inter-AS links into PCEP. The exact mechanism used to provision the inter-AS links is outside the scope of this document.¶
This document extends PCEP for LS (and TE) distribution including a new LSRpt message with a new object and TLVs. Procedures and protocol extensions defined in this document do not affect the overall PCEP security model. See [RFC5440], [RFC8253]. Tampering with the LSRpt message may have an effect on path computations at PCE. It also provides adversaries an opportunity to eavesdrop and learn sensitive information and plan sophisticated attacks on the network infrastructure. The PCE implementation SHOULD provide mechanisms to prevent strains created by network flaps and amount of LS (and TE) information. Thus it is suggested that any mechanism used for securing the transmission of other PCEP message be applied here as well. As a general precaution, it is RECOMMENDED that these PCEP extensions only are activated on authenticated and encrypted sessions belonging to the same administrative authority.¶
Further, as stated in [RFC6952], PCEP implementations SHOULD support the TCP-AO [RFC5925] and not use TCP MD5 because of TCP MD5's known vulnerabilities and weaknesses. PCEP also support Transport Layer Security (TLS) [RFC8253] as per the recommendations and best current practices in [RFC9325].¶
All manageability requirements and considerations listed in [RFC5440] apply to PCEP protocol extensions defined in this document. In addition, requirements, and considerations listed in this section apply.¶
A PCE or PCC implementation MUST allow configuring the PCEP-LS capabilities as described in this document.¶
A PCC implementation SHOULD allow configuration to suggest if remote information learned via routing protocols should be reported or not.¶
An implementation SHOULD allow the operator to specify the maximum number of LS data to be reported.¶
An implementation SHOULD also allow the operator to create abstracted topologies that are reported to the peers and create different abstractions for different peers.¶
An implementation SHOULD allow the operator to configure a 64-bit identifier for Routing Universe TLV.¶
An implementation SHOULD allow the operator to view the LS capabilities advertised by each peer. To serve this purpose, the PCEP YANG module [I-D.ietf-pce-pcep-yang] can be extended to include advertised capabilities.¶
An implementation SHOULD also provide the following statistics:¶
These statistics should be recorded as absolute counts since the system or session start time. An implementation MAY also enhance this information by recording peak per-second counts in each case.¶
An operator SHOULD define an import policy to limit inbound LSRpt to "drop all LSRpt from a particular peer" as well as provide means to limit inbound LSRpts.¶
Mechanisms defined in this document do not imply any new liveness detection and monitoring requirements in addition to those already listed in [RFC5440]".¶
Mechanisms defined in this document do not imply any new operation verification requirements in addition to those already listed in [RFC5440].¶
Mechanisms defined in this document do not imply any new requirements on other protocols.¶
Mechanisms defined in this document do not have any impact on the network operations in addition to those already listed in [RFC5440].¶
This document requests IANA actions to allocate code points for the protocol elements defined in this document.¶
IANA created a registry for "PCEP Messages". Each PCEP message has a message type value. This document defines a new PCEP message value.¶
Value Meaning Reference TBD3 LSRpt [This I-D]¶
This document defines the following new PCEP Object-classes and Object-values:¶
Object-Class Value Name Reference
TBD6 LS Object [This I-D]
Object-Type=1
(LS Node)
Object-Type=2
(LS Link)
Object-Type=3
(LS IPv4 Prefix)
Object-Type=4
(LS IPv6 Prefix)
¶
This document requests that a new sub-registry, named "LS Object Protocol-ID Field", is created within the "Path Computation Element Protocol (PCEP) Numbers" registry to manage the Flag field of the LSP object. New values are to be assigned by "IETF Review" [RFC8126].¶
Value Meaning Reference 0 Reserved [This I-D] 1 IS-IS Level 1 [This I-D] 2 IS-IS Level 2 [This I-D] 3 OSPFv2 [This I-D] 4 Direct [This I-D] 5 Static configuration [This I-D] 6 OSPFv3 [This I-D] 7 BGP [This I-D] 8 RSVP-TE [This I-D] 9 Segment Routing [This I-D] 10 PCEP [This I-D] 11 Abstraction [This I-D] 12-255 Unassigned¶
Further, this document also requests that a new sub-registry, named "LS Object Flag Field", is created within the "Path Computation Element Protocol (PCEP) Numbers" registry to manage the Flag field of the LSP object. New values are to be assigned by "IETF Review" [RFC8126]. Each bit should be tracked with the following qualities:¶
The following values are defined in this document:¶
Bit Description Reference 0-21 Unassigned 22 R (Remove bit) [This I-D] 23 S (Sync bit) [This I-D]¶
IANA is requested to make the following allocation in the "PCEP-ERROR Object Error Types and Values" registry.¶
Error-Type Meaning Reference
6 Mandatory Object missing [RFC5440]
Error-Value=TBD4 [This I-D]
(LS object missing)
19 Invalid Operation [RFC8231]
Error-Value=TBD1 [This I-D]
(Attempted LS Report if LS
remote capability was not
advertised)
TBD2 LS Synchronization Error [This I-D]
Error-Value=1
(An error in processing the
LSRpt)
Error-Value=2
(An internal PCC error)
¶
IANA is requested to make the following allocation in the "PCEP TLV Type Indicators" registry.¶
Value Meaning Reference TBD5 LS-CAPABILITY TLV [This I-D] TBD7 ROUTING-UNIVERSE TLV [This I-D] TBD15 ROUTE-DISTINGUISHER TLV [This I-D] TBD8 Local Node Descriptors TLV [This I-D] TBD9 Remote Node Descriptors TLV [This I-D] TBD10 Link Descriptors TLV [This I-D] TBD11 Prefix Descriptors TLV [This I-D] TBD12 Node Attributes TLV [This I-D] TBD13 Link Attributes TLV [This I-D] TBD14 Prefix Attributes TLV [This I-D]¶
This document specifies the PCEP-LS Sub-TLVs. IANA is requested to create a "PCEP-LS Sub-TLV Types" sub-registry for the sub-TLVs carried in the PCEP-LS TLV (Local and Remote Node Descriptors TLV, Link Descriptors TLV, Prefix Descriptors TLV, Node Attributes TLV, Link Attributes TLV and Prefix Attributes TLV.¶
Allocations from this registry are to be made according to the following assignment policies [RFC8126]:¶
Range | Assignment policy
---------------+---------------------------------------------------
0 | Reserved - must not be allocated.
|
1 .. 251 | Specification Required
|
252 .. 255 | Experimental Use
|
256 .. 65535 | Reserved - must not be allocated.
| Usage mirrors the BGP-LS TLV registry
| [I-D.ietf-idr-rfc7752bis]
|
¶
IANA is requested to pre-populate this registry with values defined in this document as follows, taking the new values from the range 1 to 251:¶
Value | Meaning -------+------------------------ 24 | SPEAKER-ENTITY-ID¶
This section contains the global table of all TLVs in the LS object, defined in this document.¶
+-----------+---------------------+---------------+-----------------+ | TLV | Description | Ref TLV | Value defined | | | | | in: | +-----------+---------------------+---------------+-----------------+ | TBD7 | Routing Universe | -- | Sec 9.2.1 | | TBD15 | Route | -- | Sec 9.2.2 | | | Distinguisher | | | | * | Virtual Network | -- | [ietf-pce- | | | | | vn-association] | | TBD8 | Local Node | 256 | [I-D.ietf-idr- | | | | | rfc7752bis] | | | Descriptors | | /3.2.1.2 | | TBD9 | Remote Node | 257 | [I-D.ietf-idr- | | | | | rfc7752bis] | | | Descriptors | | /3.2.1.3 | | TBD10 | Link Descriptors | -- | Sec 9.2.8 | | TBD11 | Prefix Descriptors | -- | Sec 9.2.9 | | TBD12 | Node Attributes | -- | Sec 9.2.10.1 | | TBD13 | Link Attributes | -- | Sec 9.2.10.2 | | TBD14 | Prefix Attributes | -- | Sec 9.2.10.3 | +-----------+---------------------+---------------+-----------------+ * this TLV is defined in a different PCEP document
[Note to RFC Editor: Please remove this section.]¶
This section records the status of known implementations of the protocol defined by this specification at the time of posting of this Internet-Draft, and is based on a proposal described in RFC 7942. The description of implementations in this section is intended to assist the IETF in its decision processes in progressing drafts to RFCs. Please note that the listing of any individual implementation here does not imply endorsement by the IETF. Furthermore, no effort has been spent to verify the information presented here that was supplied by IETF contributors. This is not intended as, and must not be construed to be, a catalog of available implementations or their features. Readers are advised to note that other implementations may exist.¶
According to RFC 7942, "this will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature. It is up to the individual working groups to use this information as they see fit".¶
The PCEP-LS protocol extensions as described in this I-D were implemented and tested for a variety of applications. Apart from the below implementation, there exist other experimental implementations done for optical networks.¶
The PCEP-LS has been implemented as part of the IETF97 Hackathon and Bits-N-Bites demonstration. The use-case demonstrated was the DCI use-case of ACTN architecture in which to show the following scenarios:¶
Huawei (PNC, MDSC) and SKT (MDSC) implemented PCEP-LS during the Hackathon and IETF97 Bits-N-Bites demonstration. The demonstration was ONOS-based ACTN architecture in which to show the following capabilities:¶
Further description can be found at ONOS-PCEP and the code at ONOS-PCEP-GITHUB.¶
This document borrows some of the structure and text from the [I-D.ietf-idr-rfc7752bis].¶
Thanks to Eric Wu, Venugopal Kondreddy, Mahendra Singh Negi, Avantika, Zhengbin Li, Daniel King, and Adrian Farrel for the reviews.¶
Thanks to Ramon Casellas for his comments and suggestions based on his implementation experience.¶
These examples are for illustration purposes only to show how the new PCEP-LS message could be encoded. They are not meant to be an exhaustive list of all possible use cases and combinations.¶
Each node (PCC) in the network chooses to provide its own local node and link information, and in this way PCE can build the full link-state and TE information.¶
+--------------------+ +--------------------+
| | | |
| RTA |192.0.2.0/24 | RTB |
| 11.11.11.11 |--------------------| 33.33.33.34 |
| Area 0 | 192.0.2.0/24 | Area 0 |
| | | |
+--------------------+ +--------------------+
RTA
---
LS Node
TLV - Local Node Descriptors
Sub-TLV - 514: OSPF Area-ID: 0.0.0.0
Sub-TLV - 515: IGP Router-ID: 11.11.11.11
TLV - Node Attributes TLV
Sub-TLV(s)
LS Link
TLV - Local Node Descriptors
Sub-TLV - 514: OSPF Area-ID: 0.0.0.0
Sub-TLV - 515: IGP Router-ID: 11.11.11.11
TLV - Remote Node Descriptors
Sub-TLV - 514: OSPF Area-ID: 0.0.0.0
Sub-TLV - 515: IGP Router-ID: 22.22.22.22
TLV - Link Descriptors
Sub-TLV - 259: IPv4 interface: 192.0.2.1
Sub-TLV - 260: IPv4 neighbor: 192.0.2.2
TLV - Link Attributes TLV
Sub-TLV(s)
RTB
---
LS Node
TLV - Local Node Descriptors
Sub-TLV - 514: OSPF Area-ID: 0.0.0.0
Sub-TLV - 515: IGP Router-ID: 22.22.22.22
TLV - Node Attributes TLV
Sub-TLV(s)
LS Link
TLV - Local Node Descriptors
Sub-TLV - 514: OSPF Area-ID: 0.0.0.0
Sub-TLV - 515: IGP Router-ID: 22.22.22.22
TLV - Remote Node Descriptors
Sub-TLV - 514: OSPF Area-ID: 0.0.0.0
Sub-TLV - 515: IGP Router-ID: 11.11.11.11
TLV - Link Descriptors
Sub-TLV - 259: IPv4 interface: 192.0.2.2
Sub-TLV - 260: IPv4 neighbor: 192.0.2.1
TLV - Link Attributes TLV
Sub-TLV(s)
¶
A similar example with IPv6 address (say 2001:db8::1 and 2001:db8::2) for the links could be imagined with all other information as same and just IPv6 interface and neighbour TLVs.¶
A designated node(s) in the network will provide its own local node as well as all learned remote information, and in this way, PCE can build the full link-state and TE information.¶
As described in Appendix A.1, the same LS Node and Link objects will be generated with a difference that it would be a designated router say RTA that generates all this information.¶
As per Hierarchical-PCE [RFC6805], Parent PCE builds an abstract domain topology map with each domain as an abstract node and inter-domain links as an abstract link. Each Child PCE may provide this information to the Parent PCE. Considering the example in figure 1 of [RFC6805], following LS object will be generated:¶
PCE1
----
LS Node
TLV - Local Node Descriptors
Sub-TLV - 512: Autonomous System: 100 (Domain 1)
Sub-TLV - 515: IGP Router-ID: 11.11.11.11 (abstract)
LS Link
TLV - Local Node Descriptors
Sub-TLV - 512: Autonomous System: 100
Sub-TLV - 515: IGP Router-ID: 11.11.11.11 (abstract)
TLV - Remote Node Descriptors
Sub-TLV - 512: Autonomous System: 200 (Domain 2)
Sub-TLV - 515: IGP Router-ID: 22.22.22.22 (abstract)
TLV - Link Descriptors
Sub-TLV - 259: IPv4 interface: 192.0.2.1
Sub-TLV - 260: IPv4 neighbor: 192.0.2.2
TLV - Link Attributes TLV
Sub-TLV(s)
LS Link
TLV - Local Node Descriptors
Sub-TLV - 512: Autonomous System: 100
Sub-TLV - 515: IGP Router-ID: 11.11.11.11 (abstract)
TLV - Remote Node Descriptors
Sub-TLV - 512: Autonomous System: 200
Sub-TLV - 515: IGP Router-ID: 22.22.22.22 (abstract)
TLV - Link Descriptors
Sub-TLV - 259: IPv4 interface: 198.51.100.1
Sub-TLV - 260: IPv4 neighbor: 198.51.100.2
TLV - Link Attributes TLV
Sub-TLV(s)
LS Link
TLV - Local Node Descriptors
Sub-TLV - 512: Autonomous System: 100
Sub-TLV - 515: IGP Router-ID: 11.11.11.11 (abstract)
TLV - Remote Node Descriptors
Sub-TLV - 512: Autonomous System: 400 (Domain 4)
Sub-TLV - 515: IGP Router-ID: 44.44.44.44 (abstract)
TLV - Link Descriptors
Sub-TLV - 259: IPv4 interface: 203.0.113.1
Sub-TLV - 260: IPv4 neighbor: 203.0.113.2
TLV - Link Attributes TLV
Sub-TLV(s)
* similar information will be generated by other PCE
to help form the abstract domain topology.
¶
Further the exact border nodes and the abstract internal path between the border nodes may also be transported to the Parent PCE to enable ACTN as described in [RFC8637] using the similar LS node and link objects encodings.¶
Gyan Mishra Verizon Inc. Email: gyan.s.mishra@verizon.com Siva Sivabalan Ciena Corporation Email: ssivabal@ciena.com Udayasree Palle EMail: udayasreereddy@gmail.com Sergio Belotti Nokia EMail: sergio.belotti@nokia.com Satish Karunanithi India Email: satish.karunanithi@gmail.com Cheng Li Huawei Technologies Huawei Campus, No. 156 Beiqing Rd. Beijing 100095 China Email: c.l@huawei.com¶