]> Huawei

italo.busi@huawei.com

Alef Edge

xufeng.liu.ietf@gmail.com

Individual

i_bryskin@yahoo.com

Cisco Systems Inc

tsaad.net@gmail.com

Telefonica

oscar.gonzalezdedios@telefonica.com

TEAS Working Group This document describes how profiles of the Traffic Engineering (TE) Topology Model, defined in RFC8795, can be used to address applications beyond "Traffic Engineering".

Introduction There are many network scenarios being discussed in various IETF Working Groups (WGs) that are not classified as "Traffic Engineering" but can be addressed by a sub-set (profile) of the Traffic Engineering (TE) Topology YANG data model, defined in . Traffic Engineering (TE) is defined in as aspects of Internet network engineering that deal with the issues of performance evaluation and performance optimization of operational IP networks. TE encompasses the application of technology and scientific principles to the measurement, characterization, modeling, and control of Internet traffic. The TE Topology Model is augmenting the Network Topology Model defined in with generic and technology-agnostic features that some are strictly applicable to TE networks, while others applicable to both TE and non-TE networks. Examples of such features that are applicable to both TE and non-TE networks are: inter-domain link discovery (plug-id), geo- localization, and admin/operational status. It is also worth noting that the TE Topology Model is quite an extensive and comprehensive model in which most features are optional. Therefore, even though the full model appears to be complex, at the first glance, a sub-set of the model (profile) can be used to address specific scenarios, e.g. suitable also to non-TE use cases. The implementation of such TE Topology profiles can simplify and expedite adoption of the full TE topology YANG data model, and allow for its reuse even for non-TE use case. The key question being whether all or some of the attributes defined in the TE Topology Model are needed to address a given network scenario. provides examples where profiles of the TE Topology Model can be used to address some generic use cases applicable to both TE and non-TE technologies.

Examples of non-TE scenarios

UNI Topology Discovery UNI Topology Discovery is independent from whether the network is TE or non-TE. The TE Topology Model supports inter-domain link discovery (including but not being limited to UNI link discovery) using the plug-id attribute. This solution is quite generic and does not require the network to be a TE network. The following profile of the TE Topology model can be used for the UNI Topology Discovery:

The profile data model shown in can be used to discover TE and non TE UNIs as well as to discover UNIs for TE or non TE networks. Such a UNI TE Topology profile model can also be used with technology-specific UNI augmentations, as described in section 3. For example, in , the eth-svc container is defined to represent the capabilities of the Termination Point (TP) to be configured as an Ethernet client UNI, together with the Ethernet classification and VLAN operations supported by that TP. The provides another example, where: the client-svc container is defined to represent the capabilities of the TP to be configured as an transparent client UNI (e.g., STM-N, Fiber Channel or transparent Ethernet); the OTN technology-specific Link Termination Point (LTP) augmentations are defined to represent the capabilities of the TP to be configured as an OTN UNI, together with the information about OTN label and bandwidth availability at the OTN UNI. For example, the UNI TE Topology profile can be used to model features defined in : The inter-domain-plug-id attribute would provide the same information as the attachment-id attribute defined in ; The admin-status and oper-status that exists in this TE topology profile can provide the same information as the admin-status and oper-status attributes defined in . Following the same approach in and , the type and encapsulation-type attributes can be defined by technology- specific UNI augmentations to represent the capability of a TP to be configured as a L2VPN/L3VPN UNI Service Attachment Point (SAP). The advantages of using a TE Topology profile would be having common solutions for: discovering UNIs as well as inter-domain NNI links, which is applicable to any technology (TE or non TE) used at the UNI or within the network; modelling non TE UNIs such as Ethernet, and TE UNIs such as OTN, as well as UNIs which can configured as TE or non-TE (e.g., being configured as either Ethernet or OTN UNI).

Administrative and Operational status management The TE Topology Model supports the management of administrative and operational state, including also the possibility to associate some administrative names, for nodes, termination points and links. This solution is generic and also does not require the network to be a TE network. The following profile of the TE Topology Model can be used for administrative and operational state management:

The TE topology data model profile shown in is applicable to any technology (TE or non-TE) that requires management of the administrative and operational state and administrative names for nodes, termination points and links.

Overlay and Underlay non-TE Topologies The TE Topology model supports the management of overlay/underlay relationship for nodes and links, as described in section 5.8 of . This solution is generic and does not require the network to be a TE network. The following TE topology data model profile can be used to manage overlay/underlay network data:

/nw:networks/network/network-id augment /nw:networks/nw:network/nt:link: +--rw te! +--rw te-link-attributes +--rw underlay {te-topology-hierarchy}? +--rw enabled? boolean +--rw primary-path +--rw network-ref? | -> /nw:networks/network/network-id +--rw path-element* [path-element-id] +--rw path-element-id uint32 +--rw (type)? +--:(numbered-link-hop) | +--rw numbered-link-hop | +--rw link-tp-id te-tp-id | +--rw hop-type? te-hop-type | +--rw direction? te-link-direction +--:(unnumbered-link-hop) +--rw unnumbered-link-hop +--rw link-tp-id te-tp-id +--rw node-id te-node-id +--rw hop-type? te-hop-type +--rw direction? te-link-direction ]]>

This profile is applicable to any technology (TE or non-TE) when it is needed to manage the overlay/underlay information. It is also allows a TE underlay network to support a non-TE overlay network and, vice versa, a non-TE underlay network to support a TE overlay network.

Nodes with switching limitations A node can have some switching limitations where connectivity is not possible between all its TP pairs, for example when: the node represents a physical device with switching limitations; the node represents an abstraction of a network topology. This scenario is generic and applies to both TE and non-TE technologies. A connectivity TE Topology profile data model supports the management of the node connectivity matrix to represent feasible connections between termination points across the nodes. This solution is generic and does not necessarily require a TE enabled network. The following profile of the TE Topology model can be used for nodes with connectivity constraints:

The TE topology data model profile shown in is applicable to any technology (TE or non-TE) networks that requires managing nodes with certain connectivity constraints. When used with TE technologies, additional TE attributes, as defined in , can also be provided.

Technology-specific augmentations There are two main options to define technology-specific Topology Models which can use the attributes defined in the TE Topology Model . Both options are applicable to any possible profile of the TE Topology Model, such as those defined in . The first option is to define a technology-specific TE Topology Model which augments the TE Topology Model, as shown in :

This approach is more suitable for cases when the technology-specific TE topology model provides augmentations to the TE Topology constructs, such as bandwidth information (e.g., link bandwidth), tunnel termination points (TTPs) or connectivity matrices. It also allows providing augmentations to the Network Topology constructs, such as nodes, links, and termination points (TPs). This is the approach currently used in and . It is worth noting that a profile of the technology-specific TE Topology model not using any TE topology attribute or constructs can be used to address any use case that do not require these attributes. In this case, only the te-topology presence container of the TE Topology Model needs to be implemented. The second option is to define a technology-specific Network Topology Model which augments the Network Topology Model and to rely on the multiple inheritance capability, which is implicit in the network- types definition of , to allow using also the generic attributes defined in the TE Topology model:

This approach is more suitable in cases where the technology-specific Network Topology Model provides augmentation only to the constructs defined in the Network Topology Model, such as nodes, links, and termination points (TPs). Therefore, with this approach, only the generic attributes defined in the TE Topology Model could be used. It is also worth noting that in this case, technology-specific augmentations for the bandwidth information could not be defined. In principle, it would be also possible to define both a technology specific TE Topology Model which augments the TE Topology Model, and a technology-specific Network Topology Model which augments the Network Topology Model and to rely on the multiple inheritance capability, as shown in :

This option does not provide any technical advantage with respect to the first option, shown in , but could be useful to add augmentations to the TE Topology constructs and to re-use an already existing technology-specific Network Topology Model. It is worth noting that the technology-specific TE Topology model can reference constructs defined by the technology-specific Network Topology model but it could not augment constructs defined by the technology-specific Network Topology model.

Multi-inheritance As described in section 4.1 of , the network types should be defined using presence containers to allow the representation of network subtypes. The hierachy of netwok subtypes can be single hierarchy, as shown in . In this case, each presence container contains at most one child presence container, as shows in the JSON code below:

The hierachy of netwok subtypes can also be multi-hierarchy, as shown in and . In this case, one presence container can contain more than one child presence containers, as show in the JSON codes below:

Other examples of multi-hierarchy topologies are described in .

Example (Link augmentation) This section provides an example on how technology-specific attributes can be added to the Link construct:

../../../nw:node/node-id | +--rw source-tp? leafref +--rw destination | +--rw dest-node? -> ../../../nw:node/node-id | +--rw dest-tp? leafref +--rw supporting-link* [network-ref link-ref] | +--rw network-ref | | -> ../../../nw:supporting-network/network-ref | +--rw link-ref leafref +--rw example-link-attributes | <...> +--rw te! +--rw te-link-attributes +--rw name? string +--rw example-te-link-attributes | <...> +--rw max-link-bandwidth +--rw te-bandwidth +--rw (technology)? +--:(generic) | +--rw generic? te-bandwidth +--:(example) +--rw example? example-bandwidth ]]>

The technology-specific attributes within the example-link-attributes container can be defined either in the technology-specific TE Topology Model (Option 1) or in the technology-specific Network Topology Model (Option 2 or Option 3). These attributes can only be non-TE and do not require the implementation of the te container. The technology-specific attributes within the example-te-link-attributes container as well as the example max-link-bandwidth can only be defined in the technology-specific TE Topology Model (Option 1 or Option 3). These attributes can be TE or non-TE and require the implementation of the te container.

Implemented profiles When a server implements a profile of the TE topology model, it is not clear how the server can report to the client the subset of the model being implemented. It is also worth noting that the supported profile may also depend on other attributes (for example the network type). In case the TE topology profile is reported by the server to the client, the server will report in the operational datastore only the leaves which have been implemented, as described in section 5.3 of . More investigation is required in case the TE topology profile is configured by the client.

Security Considerations This document provides only information about how the TE Topology Model, as defined in , can be profiled to address some scenarios which are not considered as TE. As such, this document does not introduce any additional security considerations besides those already defined in .

IANA Considerations This document requires no IANA actions.

Acknowledgments The authors would like to thank Vishnu Pavan Beeram, Daniele Ceccarelli, Jonas Ahlberg and Scott Mansfield for providing useful suggestions for this draft. This document was prepared using kramdown. Initial versions of this document were prepared using 2-Word-v2.0.template.dot.

This document defines a YANG data model for representing, retrieving, and manipulating Traffic Engineering (TE) Topologies. The model serves as a base model that other technology-specific TE topology models can augment. This document defines an abstract (generic, or base) YANG data model for network/service topologies and inventories. The data model serves as a base model that is augmented with technology-specific details in other, more specific topology and inventory data models. Datastores are a fundamental concept binding the data models written in the YANG data modeling language to network management protocols such as the Network Configuration Protocol (NETCONF) and RESTCONF. This document defines an architectural framework for datastores based on the experience gained with the initial simpler model, addressing requirements that were not well supported in the initial model. This document updates RFC 7950. Old Dog Consulting This document describes the principles of traffic engineering (TE) in the Internet. The document is intended to promote better understanding of the issues surrounding traffic engineering in IP networks and the networks that support IP networking, and to provide a common basis for the development of traffic engineering capabilities for the Internet. The principles, architectures, and methodologies for performance evaluation and performance optimization of operational networks are also discussed. This work was first published as RFC 3272 in May 2002. This document obsoletes RFC 3272 by making a complete update to bring the text in line with best current practices for Internet traffic engineering and to include references to the latest relevant work in the IETF. Huawei Technologies Huawei Technologies Futurewei Huawei Technologies CAICT China Mobile Alef Edge This document describes a YANG data model for Ethernet networks when used either as a client-layer network of an underlay transport network (e.g., an Optical Transport Network (OTN)) or as a transport network itself. Huawei Technologies Huawei Technologies IBM Corporation Nokia Telefonica This document describes a YANG data model to describe the topologies of an Optical Transport Network (OTN). It is independent of control plane protocols and captures topological and resource-related information pertaining to OTN. This model enables clients, which interact with a transport domain controller, for OTN topology-related operations such as obtaining the relevant topology resource information. Telefonica Telefonica Huawei Orange This document defines a YANG data model for representing an abstract view of the Service Provider network topology containing the points from which its services can be attached (e.g., basic connectivity, VPN, SDWAN). The data model augments the 'ietf-network' data model by adding the concept of service-attachment-points. The service- attachment-points are an abstraction of the points to which network services (such as L3 VPN or L2 VPN) can be attached. Alef Edge Individual Juniper Networks Juniper Networks Ciena Cisco This document defines a YANG data model for Segment Routing (SR) topology and Segment Routing (SR) traffic engineering (TE) topology, using MPLS data plane.

Contributors Futurewei Inc.

aihuaguo.ietf@gmail.com

Huawei

zhenghaomian@huawei.com

Nokia

sergio.belotti@nokia.com