--- 1/draft-ietf-teas-yang-te-topo-16.txt 2018-06-23 19:13:13.244527758 -0700 +++ 2/draft-ietf-teas-yang-te-topo-17.txt 2018-06-23 19:13:13.588535973 -0700 @@ -4,24 +4,24 @@ Huawei Technologies Vishnu Pavan Beeram Juniper Networks Tarek Saad Cisco Systems Inc Himanshu Shah Ciena Oscar Gonzalez De Dios Telefonica -Expires: December 4, 2018 June 4, 2018 +Expires: December 23, 2018 June 23, 2018 YANG Data Model for Traffic Engineering (TE) Topologies - draft-ietf-teas-yang-te-topo-16 + draft-ietf-teas-yang-te-topo-17 Status of this Memo 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), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. @@ -30,21 +30,21 @@ 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." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html - This Internet-Draft will expire on December 4, 2018. + This Internet-Draft will expire on December 23, 2018. Copyright Notice Copyright (c) 2018 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 (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -57,88 +57,91 @@ Abstract 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. Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", - "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this - document are to be interpreted as described in RFC-2119 [RFC2119]. + "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. Table of Contents 1. Introduction...................................................3 1.1. Terminology...............................................4 1.2. Tree Structure............................................4 1.3. Prefixes in Data Node Names...............................5 2. Characterizing TE Topologies...................................5 - 3. Modeling Abstractions and Transformations......................6 - 3.1. TE Topology...............................................6 + 3. Modeling Abstractions and Transformations......................7 + 3.1. TE Topology...............................................7 3.2. TE Node...................................................7 - 3.3. TE Link...................................................7 - 3.4. Transitional TE Link for Multi-Layer Topologies...........7 - 3.5. TE Link Termination Point (LTP)...........................9 - 3.6. TE Tunnel Termination Point (TTP).........................9 - 3.7. TE Node Connectivity Matrix..............................10 - 3.8. TTP Local Link Connectivity List (LLCL)..................10 - 3.9. TE Path..................................................10 - 3.10. TE Inter-Layer Lock.....................................10 - 3.11. Underlay TE topology....................................12 - 3.12. Overlay TE topology.....................................12 - 3.13. Abstract TE topology....................................12 - 4. Model Applicability...........................................13 - 4.1. Native TE Topologies.....................................13 - 4.2. Customized TE Topologies.................................15 - 4.3. Merging TE Topologies Provided by Multiple Providers.....18 + 3.3. TE Link...................................................8 + 3.4. Transitional TE Link for Multi-Layer Topologies...........8 + 3.5. TE Link Termination Point (LTP)..........................10 + 3.6. TE Tunnel Termination Point (TTP)........................10 + 3.7. TE Node Connectivity Matrix..............................11 + 3.8. TTP Local Link Connectivity List (LLCL)..................11 + 3.9. TE Path..................................................11 + 3.10. TE Inter-Layer Lock.....................................12 + 3.11. Underlay TE topology....................................13 + 3.12. Overlay TE topology.....................................13 + 3.13. Abstract TE topology....................................13 + + 4. Model Applicability...........................................14 + 4.1. Native TE Topologies.....................................14 + 4.2. Customized TE Topologies.................................16 + 4.3. Merging TE Topologies Provided by Multiple Providers.....19 4.4. Dealing with Multiple Abstract TE Topologies Provided by the - Same Provider.................................................21 - 5. Modeling Considerations.......................................24 - 5.1. Network topology building blocks.........................24 - 5.2. Technology agnostic TE Topology model....................24 - 5.3. Model Structure..........................................25 - 5.4. Topology Identifiers.....................................26 - 5.5. Generic TE Link Attributes...............................26 - 5.6. Generic TE Node Attributes...............................27 - 5.7. TED Information Sources..................................28 - 5.8. Overlay/Underlay Relationship............................29 - 5.9. Templates................................................30 - 5.10. Scheduling Parameters...................................31 - 5.11. Notifications...........................................31 + Same Provider.................................................22 + 5. Modeling Considerations.......................................25 + 5.1. Network topology building blocks.........................25 + 5.2. Technology agnostic TE Topology model....................25 + 5.3. Model Structure..........................................26 + 5.4. Topology Identifiers.....................................27 + 5.5. Generic TE Link Attributes...............................27 + 5.6. Generic TE Node Attributes...............................28 + 5.7. TED Information Sources..................................29 + 5.8. Overlay/Underlay Relationship............................30 + 5.9. Templates................................................31 + 5.10. Scheduling Parameters...................................32 + 5.11. Notifications...........................................32 6. Guidance for Writing Technology Specific TE Topology Augmentations - .................................................................32 - 7. TE Topology YANG Module.......................................44 + .................................................................33 + 7. TE Topology YANG Module.......................................45 8. Security Considerations.......................................92 9. IANA Considerations...........................................94 - 10. References...................................................94 - 10.1. Normative References....................................94 - 10.2. Informative References..................................95 - 11. Acknowledgments..............................................96 - Appendix A. Complete Model Tree Structure........................97 + 10. References...................................................95 + 10.1. Normative References....................................95 + 10.2. Informative References..................................96 + 11. Acknowledgments.............................................100 + Appendix A. Complete Model Tree Structure.......................101 Appendix B. Companion YANG Model for Non-NMDA Compliant - Implementations.................................................151 + Implementations.................................................150 Appendix C. Example: YANG Model for Technology Specific Augmentations - ................................................................159 - Contributors....................................................197 - Authors' Addresses..............................................197 + ................................................................158 + Contributors....................................................196 + Authors' Addresses..............................................196 1. Introduction The Traffic Engineering Database (TED) is an essential component of Traffic Engineered (TE) systems that are based on MPLS-TE [RFC2702] and GMPLS [RFC3945]. The TED is a collection of all TE information about all TE nodes and TE links in the network. The TE Topology is a schematic arrangement of TE nodes and TE links present in a given TED. There could be one or more TE Topologies present in a given - Traffic Engineered system. The TE Topology is the topology on which + Traffic Engineered system. A TE Topology is the topology on which path computational algorithms are run to compute Traffic Engineered Paths (TE Paths). This document defines a YANG [RFC7950] data model for representing and manipulating TE Topologies. This model contains technology agnostic TE Topology building blocks that can be augmented and used by other technology-specific TE Topology models. 1.1. Terminology @@ -162,96 +165,114 @@ and TE links in a given TED. It forms the basis for a graph suitable for TE path computations. Native TE Topology: Native TE Topology is a topology that is native to a given provider network. Native TE topology could be discovered via various routing protocols and/or subscribe/publish techniques. This is the topology on which path computational algorithms are run to compute TE Paths. Customized TE Topology: Customized TE Topology is a custom topology - that is produced by a provider for a given Client. This topology - typically augments the Client's Native TE Topology. Path - computational algorithms aren't typically run on the Customized TE - Topology; they are run on the Client's augmented Native TE Topology. + that is produced by a provider for a given client. This topology + typically makes abstractions on the provider's Native TE Topology, + and is provided to the client. The client receives the Customized TE + Topology, and merges it into the client's Native TE Topology. The + client's path computational algorithms aren't typically run on the + Customized TE Topology; they are run on the client's Native TE + Topology after the merge. 1.2. Tree Structure A simplified graphical representation of the data model is presented in Appendix A. of this document. The tree format defined in [RFC8340] is used for the YANG data model tree representation. 1.3. Prefixes in Data Node Names In this document, names of data nodes and other data model objects are prefixed using the standard prefix associated with the corresponding YANG imported modules, as shown in Table 1. - +--------+-----------------+-----------+ + +----------+-----------------------+-------------------------+ | Prefix | YANG module | Reference | - +--------+-----------------+-----------+ + +----------+-----------------------+-------------------------+ | yang | ietf-yang-types | [RFC6991] | | inet | ietf-inet-types | [RFC6991] | - +--------+-----------------+-----------+ + | nw | ietf-network | [RFC6991] | + | nt | ietf-network-topology | [RFC8345] | + | te-types | ietf-te-types | [I-D.ietf-teas-yang-te] | + +----------+-----------------------+-------------------------+ Table 1: Prefixes and corresponding YANG modules 2. Characterizing TE Topologies The data model proposed by this document takes the following characteristics of TE Topologies into account: - TE Topology is an abstract control-plane representation of the data-plane topology. Hence attributes specific to the data-plane must make their way into the corresponding TE Topology modeling. - The TE Topology comprises of dynamic auto-discovered data (data - that may change frequently - example: unreserved bandwidth - available on data-plane links) as well as fairly static data (data - that rarely changes- examples: layer network identification, - switching and adaptation capabilities and limitations, fate - sharing, administrative colors) associated with data-plane nodes - and links. It is possible for a single TE Topology to encompass TE - information at multiple switching layers. + The TE Topology comprises of dynamic auto-discovered data as well + as fairly static data associated with data-plane nodes and links. + The dynamic data may change frequently, such as unreserved + bandwidth available on data-plane links. The static data rarely + changes, such as layer network identification, switching and + adaptation capabilities and limitations, fate sharing, and + administrative colors. It is possible for a single TE Topology to + encompass TE information at multiple switching layers. - TE Topologies are protocol independent. Information about topological elements may be learnt via link-state protocols, but the topology can exist without being dependent on any particular protocol. - - TE Topology may not be congruent to the routing topology (topology - constructed based on routing adjacencies) in a given TE System. - There isn't always a one-to-one association between a TE-link and - a routing adjacency. For example, the presence of a TE link - between a pair of nodes doesn't necessarily imply the existence of - a routing-adjacency between these nodes. + - TE Topology may not be congruent to the routing topology in a + given TE System. The routing topology is constructed based on + routing adjacencies. There isn't always a one-to-one association + between a TE-link and a routing adjacency. For example, the + presence of a TE link between a pair of nodes doesn't necessarily + imply the existence of a routing-adjacency between these nodes. - - Each TE Topological element has an information source associated - with it. In some scenarios, there could be more than one - information source associated with each topological element. + - Each TE Topological element has at least one information source + associated with it. In some scenarios, there could be more than + one information source associated with any given topological + element. - TE Topologies can be hierarchical. Each node and link of a given TE Topology can be associated with respective underlay topology. This means that each node and link of a given TE Topology can be associated with an independent stack of supporting TE Topologies. - TE Topologies can be customized. TE topologies of a given network presented by the network provider to its client could be customized on per-client request basis. This customization could be performed by provider, by client or by provider/client - negotiation. The relationship between a customized topology (as - presented to the client) and provider's native topology (as known - in its entirety to the provider itself) could be captured as - hierarchical (overlay-underlay), but otherwise the two topologies - are decoupled from each other. + negotiation. The relationship between a customized topology and + provider's native topology could be captured as hierarchical + (overlay-underlay), but otherwise the two topologies are decoupled + from each other. A customized topology is presented to the client, + while provider's native topology is known in its entirety to the + provider itself. 3. Modeling Abstractions and Transformations + | +---+ __ + | | | TE Node \/ TTP o LTP + | +---+ + | + | ----- TE Link + | ***** Node Connectivity Matrix, + | TTP Local Link Connectivity + | @@@@@ TE Tunnel + o---------------------------------- + Node-1 Node-3 +------------+ +------------+ | TTP-1 | | TTP-1 | |LTP __ | TE-Tunel-1 | __ | |-6 \/@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@\/ | o * * oLTP-1 Node-2 LTP-6o * * o | * * | +------------+ | * * | | * TTP-2* | | | | * TTP-2* | | * __ * |LTP-2 LTP-6| |LTP-1 LTP-5| * __ * | o* \/ *o-----------o************o-----------o* \/ *o @@ -267,75 +288,79 @@ 3.1. TE Topology TE topology is a traffic engineering representation of one or more layers of network topologies. TE topology is comprised of TE nodes (TE graph vertices) interconnected via TE links (TE graph edges). A TE topology is mapped to a TE graph. 3.2. TE Node - TE node is an element of a TE topology (presented as a vertex on TE - graph). TE node represents one or several nodes (physical switches), - or a fraction of a node. TE node belongs to and is fully defined in - exactly one TE topology. TE node is assigned with the TE topology - scope unique ID. TE node attributes include information related to - the data plane aspects of the associated node(s) (e.g. connectivity - matrix), as well as configuration data (such as TE node name). A - given TE node can be reached on the TE graph over one of TE links - terminated by the TE node. + TE node is an element of a TE topology, presented as a vertex on TE + graph. TE node represents one or several nodes, or a fraction of a + node, which can be a switch or router that is physical or virtual. TE + node belongs to and is fully defined in exactly one TE topology. TE + node is assigned a unique ID within the TE topology scope. TE node + attributes include information related to the data plane aspects of + the associated node(s) (e.g. connectivity matrix), as well as + configuration data (such as TE node name). A given TE node can be + reached on the TE graph over one of TE links terminated by the TE + node. Multi-layer TE nodes providing switching functions at multiple network layers are an example where a physical node can be decomposed - into multiple logical TE nodes (fractions of a node). Some of these - (logical) TE nodes may reside in the client layer TE topology while - the remaining TE nodes belong to the server layer TE topology. + into multiple logical TE nodes, which are fractions of the physical + node. Some of these (logical) TE nodes may reside in the client layer + TE topology while the remaining TE nodes belong to the server layer + TE topology. In Figure 1, Node-1, Node-2, and Node-3 are TE nodes. 3.3. TE Link - TE link is an element of a TE topology (presented as an edge on TE - graph, arrows indicate one or both directions of the TE link). TE - link represents one or several (physical) links or a fraction of a - link. TE link belongs to and is fully defined in exactly one TE - topology. TE link is assigned with the TE topology scope unique ID. - TE link attributes include parameters related to the data plane - aspects of the associated link(s) (e.g. unreserved bandwidth, - resource maps/pools, etc.), as well as the configuration data (such - as remote node/link IDs, SRLGs, administrative colors, etc.). TE link - is connected to TE node, terminating the TE link via exactly one TE - link termination point (LTP). + TE link is an element of a TE topology, presented as an edge on TE + graph. The arrows on an edge indicate one or both directions of the + TE link. When there are a pair of parallel links of opposite + directions, an edge without arrows is also used. TE link represents + one or several (physical) links or a fraction of a link. TE link + belongs to and is fully defined in exactly one TE topology. TE link + is assigned a unique ID within the TE topology scope. TE link + attributes include parameters related to the data plane aspects of + the associated link(s) (e.g. unreserved bandwidth, resource + maps/pools, etc.), as well as the configuration data (such as remote + node/link IDs, SRLGs, administrative colors, etc.). TE link is + connected to TE node, terminating the TE link via exactly one TE link + termination point (LTP). In Figure 1, Link-12 and Link-23 are TE links. 3.4. Transitional TE Link for Multi-Layer Topologies Networks are typically composed of multiple network layers where one or multiple signals in the client layer network can be multiplexed and encapsulated into a server layer signal [RFC5212] [G.805]. The server layer signal can be carried in the server layer network across multiple nodes until the server layer signal is terminated and the client layer signals reappear in the node that terminates the server layer signal. Examples of multi-layer networks are: IP over MPLS over Ethernet, low order Optical Data Unit-k (ODUk) signals multiplexed into a high order ODUl (l>k) carried over an Optical Channel (OCh) signal in an optical transport network as defined in [G.872] and [G.709]. TE links as defined in 3.3. can be used to represent links within a network layer. In case of a multi-layer network, TE nodes and TE links only allow representation of each network layer as a separate - TE topology Each of these single layer TE topologies would be + TE topology. Each of these single layer TE topologies would be isolated from their client and their server layer TE topology, if - present (the highest and the lowest network layer in the hierarchy - only have a single adjacent layer below or above, respectively). + present. The highest and the lowest network layer in the hierarchy + only have a single adjacent layer below or above, respectively. Multiplexing of client layer signals and encapsulating them into a server layer signal requires a function that is provided inside a node (typically realized in hardware). This function is also called layer transition. One of the key requirements for path computation is to be able to calculate a path between two endpoints across a multi-layer network based on the TE topology representing this multi-layer network. This means that an additional TE construct is needed that represents potential layer transitions in the multi-layer TE-topology that @@ -344,27 +369,37 @@ represents the layer transition function residing inside a node that is decomposed into multiple logical nodes that are represented as TE nodes (see also the transitional link definition in [G.8080] for the optical transport network). Hence, a transitional TE link connects a client layer node with a server layer node. A TE link as defined in 3.3. has LTPs of exactly the same kind on each link end whereas the transitional TE link has client layer LTPs on the client side of the transitional link and in most cases a single server layer LTP on the server side. It should be noted that transitional links are a helper construct in the multi-layer TE topology and they only exist as long - as they are not in use (as they represent potential connectivity). + as they are not in use, as they represent potential connectivity. When the server layer trail has been established between the server layer LTP of two transitional links in the server layer network, the resulting client layer link in the data plane will be represented as a normal TE link in the client layer topology. The transitional TE links will re-appear when the server layer trail has been torn down. + | | + | +---+ --- + | | | TE Node \ / Transitional + | +---+ | Link + | + | ----- Client Layer Link + | ===== Server Layer Link + | ***** Layer Boundary + o---------------------------------- + +------------------+ | +------+ | +------+ -----|Client|------+ | Client -----|Client| | |Layer |---+ | | Layer |Layer | -----|Switch|-+ | | | Links -----|Node | | +------+ | | | | +------+ | | | | | Client | | | | | | ---_| Layer --- --- ***|**********|*| \ /*|***************************\ /*\ /**** | --- | | Server Transitional | | @@ -389,24 +424,24 @@ Cardinality between an LTP and the associated TE link is 1:0..1. In Figure 1, Node-2 has six LTPs: LTP-1 to LTP-6. 3.6. TE Tunnel Termination Point (TTP) TE tunnel termination point (TTP) is an element of TE topology representing one or several of potential transport service termination points (i.e. service client adaptation points such as WDM/OCh transponder). TTP is associated with (hosted by) exactly one - TE node. TTP is assigned with the TE node scope unique ID. Depending - on the TE node's internal constraints, a given TTP hosted by the TE - node could be accessed via one, several or all TE links terminated by - the TE node. + TE node. TTP is assigned a unique ID within the TE node scope. + Depending on the TE node's internal constraints, a given TTP hosted + by the TE node could be accessed via one, several or all TE links + terminated by the TE node. In Figure 1, Node-1 has two TTPs: TTP-1 and TTP-2. 3.7. TE Node Connectivity Matrix TE node connectivity matrix is a TE node's attribute describing the TE node's switching limitations in a form of valid switching combinations of the TE node's LTPs (see below). From the point of view of a potential TE path arriving at the TE node at a given inbound LTP, the node's connectivity matrix describes valid @@ -415,21 +450,21 @@ In Figure 1, the connectivity matrix on Node-2 is: {, , , , } 3.8. TTP Local Link Connectivity List (LLCL) TTP Local Link Connectivity List (LLCL) is a List of TE links terminated by the TTP hosting TE node (i.e. list of the TE link LTPs), which the TTP could be connected to. From the point of view of - a potential TE path LLCL provides a list of valid TE links the TE + a potential TE path, LLCL provides a list of valid TE links the TE path needs to start/stop on for the connection, taking the TE path, to be successfully terminated on the TTP in question. In Figure 1, the LLCL on Node-1 is: {, , , } 3.9. TE Path TE path is an ordered list of TE links and/or TE nodes on the TE topology graph, inter-connecting a pair of TTPs to be taken by a @@ -441,24 +476,32 @@ 3.10. TE Inter-Layer Lock TE inter-layer lock is a modeling concept describing client-server layer adaptation relationships and hence important for the multi- layer traffic engineering. It is an association of M client layer LTPs and N server layer TTPs, within which data arriving at any of the client layer LTPs could be adopted onto any of the server layer TTPs. TE inter-layer lock is identified by inter-layer lock ID, which is unique across all TE topologies provided by the same provider. The - client layer LIPs and the server layer TTPs associated within a given + client layer LTPs and the server layer TTPs associated within a given TE inter-layer lock are annotated with the same inter-layer lock ID attribute. + | +---+ __ + | | | TE Node \/ TTP o LTP + | +---+ + | + | ----- TE Link + | ***** TTP Local Link Connectivity + o---------------------------------- + (IL-1) C-LTP-1 +------------+ C-LTP-2 (IL-1) --------O (IL-1) O-------- (IL-1) C-LTP-3 | S-TTP-1 | C-LTP-4 (IL-1) --------O __ 0-------- (IL-1) C-LTP-5 | *\/* | C-LTP-5 (IL-1) --------O * * O-------- | *(IL-1)* | S-LTP-3 | * S-TTP-2* | S-LTP-4 --------o* __ *o-------- | *\/* | @@ -518,20 +562,26 @@ the provider's native TE topologies (underlay TE topologies), the provider's policies and the client's preferences. For example, a first level topology provider (such as Domain Controller) can create an abstract TE topology for its client (e.g. Multi-Domain Service Coordinator) based on the provider's one or more native TE topologies, local policies/profiles and the client's TE topology configuration requests Figure 4 shows an example of abstract TE topology. + | +---+ + | | | TE Node + | +---+ + | ----- TE Link + o---------------------------------- + +---+ +---+ |s31|--------------|S5 | +---+\ / +---+ \ / \ / \+---+/ +---+ /|AN1|\----------------|S8 | / +---+ \ +---+ +---+ / \ +---+ |S9 |-------------|S11| @@ -558,39 +608,45 @@ Figure 4: Abstract TE Topology 4. Model Applicability 4.1. Native TE Topologies The model discussed in this draft can be used to represent and retrieve native TE topologies on a given TE system. + | +---+ + | | | TE Node + | +---+ + | ----- TE Link + o---------------------------------- + +---+ +---+ +---+ +---+ +---+ | R1|-------| R2|--------| R3|---------| R4|---------| R5| +---+ +---+ +---+ +---+ +---+ | / \ / \ / | / \ / \ / | / \ / \ / | / \ / \ / | / \ / \ / +---+ +---+ +---+ +---+ | R6|-------------| R7| | R8|---------| R9| +---+ +---+ +---+ +---+ Figure 5a: Example Network Topology - Consider the network topology depicted in Figure 5a (R1 .. R9 are - nodes representing routers). An implementation MAY choose to - construct a native TE Topology using all nodes and links present in - the given TED as depicted in Figure 5b. The data model proposed in - this document can be used to retrieve/represent this TE topology. + Consider the network topology depicted in Figure 5a. R1 .. R9 are + nodes representing routers. An implementation MAY choose to construct + a native TE Topology using all nodes and links present in the given + TED as depicted in Figure 5b. The data model proposed in this + document can be used to retrieve/represent this TE topology. --------------- | Native | | [ ] TE Node | TE-Topology | | +++ TE Link --------------- o-------------- [R1] ++++ [R2] ++++ [R3] ++++ [R4] ++++ [R5] + + + + + + + + + + + + + + ++ ++ @@ -725,33 +781,33 @@ [R2] ++++++++ [B] ++++++++++++++++++++ [F] +++++++++ [R4] Figure 8c: Customized TE Topology merged with the Client's Native TE Topology The data model proposed in this document can be used to retrieve/represent/manipulate the customized TE Topology depicted in Figure 8b. A customized TE topology is not necessarily an abstract TE topology. - he provider may produce, for example, an abstract TE topology of + The provider may produce, for example, an abstract TE topology of certain type (e.g. single-abstract-node-with-connectivit-matrix topology, a border_nodes_connected_via_mesh_of_abstract_links topology, etc.) and expose it to all/some clients in expectation that the clients will use it without customization. On the other hand, a client may request a customized version of the provider's native TE topology (e.g. by requesting removal of TE links which belong to certain layers, are too slow, not protected and/or have a certain affinity). Note that the resulting TE topology will not be abstract (because it will not contain abstract elements), but customized (modified upon client's instructions). - The client ID field in the TE topology identifier (Section 5.4. + The client ID field in the TE topology identifier (Section 5.4. ) indicates which client the TE topology is customized for. Although a authorized client MAY receive a TE topology with the client ID field matching some other client, the client can customize only TE topologies with the client ID field either 0 or matching the ID of the client in question. If the client starts reconfiguration of a topology its client ID will be automatically set in the topology ID field for all future configurations and updates wrt. the topology in question. The provider MAY tell the client that a given TE topology cannot be @@ -837,28 +893,28 @@ remote nodeID/linkID attribute in the provided inter-domain TE links. This, however, may prove to be not flexible. For example, the providers may not know the respective remote nodeIDs/ linkIDs. More importantly, this option does not allow for the client to mix-n-match multiple (more than one) topologies catered by the same providers (see below). Another, more flexible, option to resolve the open-ended inter-domain TE links is by annotating them with the inter-domain plug ID attribute. Inter-domain plug ID is a network-wide unique number that identifies on the network a connectivity supporting a given inter-domain TE link. Instead of specifying remote node ID/link - ID, an inter-domain TE link may provide a non-zero inert-domain plug + ID, an inter-domain TE link may provide a non-zero inter-domain plug ID. It is expected that two neighboring domain TE topologies (provided by separate providers) will have each at least one open- ended inter-domain TE link with an inter-domain plug ID matching to one provided by its neighbor. For example, the inter-domain TE link - originating from node S5 of the Domain 1 TE topology (Figure 1) and - the inter-domain TE link coming from node S3 of Domain2 TE topology - may specify matching inter-domain plug ID (e.g. 175344) This allows + originating from node S15 of the Domain 1 TE topology (Figure 9) and + the inter-domain TE link coming from node S23 of Domain 2 TE topology + may specify matching inter-domain plug ID (e.g. 175344). This allows for the client to identify adjacent nodes in the separate neighboring TE topologies and resolve the inter-domain TE links connecting them regardless of their respective nodeIDs/linkIDs (which, as mentioned, could be allocated from independent name spaces). Inter-domain plug IDs may be assigned and managed by a central network authority. Alternatively, inter-domain plug IDs could be dynamically auto- discovered (e.g. via LMP protocol). Furthermore, the client renames the TE nodes, links and SRLGs offered in the abstract TE topologies by assigning to them IDs allocated from @@ -916,21 +972,21 @@ topologies. In any case, the client should be prepared for a provider to offer to the client more than one abstract TE topology. It should be up to the client (based on the client's local configuration and/or policies conveyed to the client by the client's clients) to decide how to mix-and-match multiple abstract TE topologies provided by each or some of the providers, as well as how to merge them into the client's native TE topologies. The client also decides how many such merged TE topologies it needs to produce and maintain. For example, in addition to the merged TE topology depicted - in the upper part of Figure 1, the client may merge the abstract TE + in the upper part of Figure 9, the client may merge the abstract TE topologies received from the two providers, as shown in Figure 10, into the client's additional native TE topologies, as shown in Figure 11. Note that allowing for the client mix-n-matching of multiple TE topologies assumes that inter-domain plug IDs (rather than remote nodeID/linkID) option is used for identifying neighboring domains and inter-domain TE link resolution. Client's Merged TE Topology 2 @@ -1070,24 +1126,25 @@ 5.4. Topology Identifiers The TE-Topology is uniquely identified by a key that has 3 constituents - te-topology-id, provider-id and client-id. The combination of provider-id and te-topology-id uniquely identifies a native TE Topology on a given provider. The client-id is used only when Customized TE Topologies come into play; a value of "0" is used as the client-id for native TE Topologies. augment /nw:networks/nw:network: + +--rw provider-id? te-types:te-global-id + +--rw client-id? te-types:te-global-id + +--rw te-topology-id? te-types:te-topology-id +--rw te! - +--rw provider-id te-global-id - +--rw client-id te-global-id - +--rw te-topology-id te-topology-id + | ............ 5.5. Generic TE Link Attributes The model covers the definitions for generic TE Link attributes - bandwidth, admin groups, SRLGs, switching capabilities, TE metric extensions etc. +--rw te-link-attributes ..................... +--rw admin-status? te-admin-status @@ -1112,54 +1168,52 @@ The definition of a generic connectivity matrix is shown below: +--rw te-node-attributes ........... +--rw connectivity-matrices ........... | +--rw connectivity-matrix* [id] | | +--rw id uint32 | | +--rw from | | | +--rw tp-ref? leafref - | | | +--rw label-restriction* [inclusive-exclusive label- - start] + | | | +--rw label-restrictions | | +--rw to | | | +--rw tp-ref? leafref - | | | +--rw label-restriction* [inclusive-exclusive label- - start] + | | | +--rw label-restrictions | | +--rw is-allowed? boolean ........... | | +--rw underlay! {te-topology-hierarchy}? ........... | | +--rw path-constraints ........... | | +--rw optimizations ........... | | +--ro path-properties ........... The definition of a TTP Local Link Connectivity List is shown below: +--rw tunnel-termination-point* [tunnel-tp-id] +--rw tunnel-tp-id binary +--rw admin-status? te-types:te-admin-status +--rw name? string +--rw switching-capability? identityref +--rw encoding? identityref - +--rw inter-layer-lock-id? uint32 + +--rw inter-layer-lock-id* uint32 +--rw protection-type? Identityref +--rw client-layer-adaptation ........... +--rw local-link-connectivities ........... | +--rw local-link-connectivity* [link-tp-ref] | +--rw link-tp-ref leafref - | +--rw label-restriction* [inclusive-exclusive label-start] + | +--rw label-restrictions ........... | +--rw is-allowed? boolean | +--rw underlay {te-topology-hierarchy}? ........... | +--rw path-constraints ........... | +--rw optimizations ........... | +--ro path-properties ........... @@ -1267,97 +1322,100 @@ | | +--rw tunnels | | | .................... 5.9. Templates The data model provides the users with the ability to define templates and apply them to link and node configurations. The use of "template" configuration is optional and this functionality is tagged as a "feature" ("template"). - +--rw topology* [provider-id client-id te-topology-id] - | ........... - | +--rw node* [te-node-id] - | | +--rw te-node-template? leafref {template}? - | | .......... - | +--rw link* [source-te-node-id source-te-link-id dest-te-node-id - dest-te-link-id] - | +--rw te-link-template? leafref {template}? - | .......... + augment /nw:networks/nw:network/nw:node: + +--rw te-node-id? te-types:te-node-id + +--rw te! + +--rw te-node-template* + | -> ../../../../te/templates/node-template/name + | {template}? + + augment /nw:networks/nw:network/nt:link: + +--rw te! + +--rw te-link-template* + | -> ../../../../te/templates/link-template/name + | {template}? augment /nw:networks: + +--rw te! +--rw templates +--rw node-template* [name] {template}? - | +--rw name te-types:te-template- - name + | +--rw name + | | te-types:te-template-name | +--rw priority? uint16 | +--rw reference-change-policy? enumeration | +--rw te-node-attributes .......... +--rw link-template* [name] {template}? - +--rw name te-types:te-template- - name + +--rw name + | te-types:te-template-name +--rw priority? uint16 +--rw reference-change-policy? enumeration +--rw te-link-attributes .......... Multiple templates can be specified to a configuration element. When two or more templates specify values for the same configuration field, the value from the template with the highest priority is used. The reference-change-policy specifies the action that needs to be taken when the template changes on a configuration element that has a reference to this template. The choices of action include taking no action, rejecting the change to the template and applying the change - to the corresponding configuration. [Editor's Note: The notion of - "templates" has wider applicability. It is possible for this to be - discussed in a separate document.] + to the corresponding configuration. 5.10. Scheduling Parameters The model allows time scheduling parameters to be specified for each topological element or for the topology as a whole. These parameters allow the provider to present different topological views to the client at different time slots. The use of "scheduling parameters" is optional. - The YANG data model for configuration scheduling is defined in [YANG- - SCHEDULE], which allows specifying configuration schedules without - altering this data model. + The YANG data model for configuration scheduling is defined in [I- + D.liu-netmod-yang-schedule], which allows specifying configuration + schedules without altering this data model. 5.11. Notifications Notifications are a key component of any topology data model. - [YANG-PUSH] and [NETCONF-NOTIF] define a subscription and push - mechanism for YANG datastores. This mechanism currently allows the - user to: + [I-D.ietf-netconf-subscribed-notifications] and [I-D.ietf-netconf- + yang-push] define a subscription and push mechanism for YANG + datastores. This mechanism currently allows the user to: - Subscribe notifications on a per client basis - Specify subtree filters or xpath filters so that only interested contents will be sent. - Specify either periodic or on-demand notifications. 6. Guidance for Writing Technology Specific TE Topology Augmentations The TE topology model defined in this document is technology agnostic as it defines concepts, abstractions and attributes that are common across multiple network technologies. It is envisioned that this base model will be widely used when defining technology specific TE - topology models for various layer networks. [YANG-TOPO-WSON], [YANG- - TOPO-OTN], and [YANG-TOPO-L3TE] are some examples of technology - specific TE Topology models. Writers of such models are encouraged to - augment the basic TE topology model's containers, such as TE - Topology, TE Node, TE Link, Link Termination Point (LTP), Tunnel - Termination Point (TTP), Bandwidth and Label with the layer specific - attributes instead of defining new containers. + topology models for various layer networks. [I-D.ietf-ccamp-wson- + yang], [I-D.ietf-ccamp-otn-topo-yang], and [I-D.ietf-teas-yang-l3-te- + topo] are some examples of technology specific TE Topology models. + Writers of such models are encouraged to augment the basic TE + topology model's containers, such as TE Topology, TE Node, TE Link, + Link Termination Point (LTP), Tunnel Termination Point (TTP), + Bandwidth and Label with the layer specific attributes instead of + defining new containers. Consider the following technology specific example-topology model: module: example-topology augment /nw:networks/nw:network/nw:network-types/tet:te-topology: +--rw example-topology! augment /nw:networks/nw:network/tet:te: +--rw attributes +--rw attribute-1? uint8 augment /nw:networks/nw:network/nw:node/tet:te @@ -1526,43 +1582,44 @@ +--rw example +--rw label-1? uint32 augment /nw:networks/tet:te/tet:templates/tet:link-template /tet:te-link-attributes/tet:underlay/tet:backup-path /tet:path-element/tet:type/tet:label/tet:label-hop /tet:te-label/tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/tet:te/tet:templates/tet:link-template - /tet:te-link-attributes/tet:label-restriction - /tet:label-start/tet:te-label/tet:technology: + /tet:te-link-attributes/tet:label-restrictions + /tet:label-restriction/tet:label-start/tet:te-label + /tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/tet:te/tet:templates/tet:link-template - /tet:te-link-attributes/tet:label-restriction - /tet:label-end/tet:te-label/tet:technology: - + /tet:te-link-attributes/tet:label-restrictions + /tet:label-restriction/tet:label-end/tet:te-label + /tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:te-node-attributes/tet:connectivity-matrices - /tet:label-restriction/tet:label-start/tet:te-label - /tet:technology: + /tet:label-restrictions/tet:label-restriction + /tet:label-start/tet:te-label/tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:te-node-attributes/tet:connectivity-matrices - /tet:label-restriction/tet:label-end/tet:te-label - /tet:technology: + /tet:label-restrictions/tet:label-restriction + /tet:label-end/tet:te-label/tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:te-node-attributes/tet:connectivity-matrices /tet:underlay/tet:primary-path/tet:path-element/tet:type /tet:label/tet:label-hop/tet:te-label/tet:technology: +--:(example) +--rw example +--rw label-1? uint32 @@ -1576,43 +1633,47 @@ augment /nw:networks/nw:network/nw:node/tet:te /tet:te-node-attributes/tet:connectivity-matrices /tet:path-properties/tet:path-route-objects /tet:path-route-object/tet:type/tet:label/tet:label-hop /tet:te-label/tet:technology: +--:(example) +--ro example +--ro label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:te-node-attributes/tet:connectivity-matrices - /tet:connectivity-matrix/tet:from/tet:label-restriction - /tet:label-start/tet:te-label/tet:technology: + /tet:connectivity-matrix/tet:from/tet:label-restrictions + /tet:label-restriction/tet:label-start/tet:te-label + /tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:te-node-attributes/tet:connectivity-matrices - /tet:connectivity-matrix/tet:from/tet:label-restriction - /tet:label-end/tet:te-label/tet:technology: + /tet:connectivity-matrix/tet:from/tet:label-restrictions + /tet:label-restriction/tet:label-end/tet:te-label + /tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:te-node-attributes/tet:connectivity-matrices - /tet:connectivity-matrix/tet:to/tet:label-restriction - /tet:label-start/tet:te-label/tet:technology: + /tet:connectivity-matrix/tet:to/tet:label-restrictions + /tet:label-restriction/tet:label-start/tet:te-label + /tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:te-node-attributes/tet:connectivity-matrices - /tet:connectivity-matrix/tet:to/tet:label-restriction - /tet:label-end/tet:te-label/tet:technology: + /tet:connectivity-matrix/tet:to/tet:label-restrictions + /tet:label-restriction/tet:label-end/tet:te-label + /tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:te-node-attributes/tet:connectivity-matrices /tet:connectivity-matrix/tet:underlay/tet:primary-path /tet:path-element/tet:type/tet:label/tet:label-hop /tet:te-label/tet:technology: +--:(example) +--rw example @@ -1628,29 +1690,29 @@ augment /nw:networks/nw:network/nw:node/tet:te /tet:te-node-attributes/tet:connectivity-matrices /tet:connectivity-matrix/tet:path-properties /tet:path-route-objects/tet:path-route-object/tet:type /tet:label/tet:label-hop/tet:te-label/tet:technology: +--:(example) +--ro example +--ro label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:information-source-entry/tet:connectivity-matrices - /tet:label-restriction/tet:label-start/tet:te-label - /tet:technology: + /tet:label-restrictions/tet:label-restriction + /tet:label-start/tet:te-label/tet:technology: +--:(example) +--ro example +--ro label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:information-source-entry/tet:connectivity-matrices - /tet:label-restriction/tet:label-end/tet:te-label - /tet:technology: + /tet:label-restrictions/tet:label-restriction + /tet:label-end/tet:te-label/tet:technology: +--:(example) +--ro example +--ro label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:information-source-entry/tet:connectivity-matrices /tet:underlay/tet:primary-path/tet:path-element/tet:type /tet:label/tet:label-hop/tet:te-label/tet:technology: +--:(example) +--ro example +--ro label-1? uint32 @@ -1664,43 +1727,47 @@ augment /nw:networks/nw:network/nw:node/tet:te /tet:information-source-entry/tet:connectivity-matrices /tet:path-properties/tet:path-route-objects /tet:path-route-object/tet:type/tet:label/tet:label-hop /tet:te-label/tet:technology: +--:(example) +--ro example +--ro label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:information-source-entry/tet:connectivity-matrices - /tet:connectivity-matrix/tet:from/tet:label-restriction - /tet:label-start/tet:te-label/tet:technology: + /tet:connectivity-matrix/tet:from/tet:label-restrictions + /tet:label-restriction/tet:label-start/tet:te-label + /tet:technology: +--:(example) +--ro example +--ro label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:information-source-entry/tet:connectivity-matrices - /tet:connectivity-matrix/tet:from/tet:label-restriction - /tet:label-end/tet:te-label/tet:technology: + /tet:connectivity-matrix/tet:from/tet:label-restrictions + /tet:label-restriction/tet:label-end/tet:te-label + /tet:technology: +--:(example) +--ro example +--ro label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:information-source-entry/tet:connectivity-matrices - /tet:connectivity-matrix/tet:to/tet:label-restriction - /tet:label-start/tet:te-label/tet:technology: + /tet:connectivity-matrix/tet:to/tet:label-restrictions + /tet:label-restriction/tet:label-start/tet:te-label + /tet:technology: +--:(example) +--ro example +--ro label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:information-source-entry/tet:connectivity-matrices - /tet:connectivity-matrix/tet:to/tet:label-restriction - /tet:label-end/tet:te-label/tet:technology: + /tet:connectivity-matrix/tet:to/tet:label-restrictions + /tet:label-restriction/tet:label-end/tet:te-label + /tet:technology: +--:(example) +--ro example +--ro label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:information-source-entry/tet:connectivity-matrices /tet:connectivity-matrix/tet:underlay/tet:primary-path /tet:path-element/tet:type/tet:label/tet:label-hop /tet:te-label/tet:technology: +--:(example) +--ro example @@ -1716,29 +1783,31 @@ augment /nw:networks/nw:network/nw:node/tet:te /tet:information-source-entry/tet:connectivity-matrices /tet:connectivity-matrix/tet:path-properties /tet:path-route-objects/tet:path-route-object/tet:type /tet:label/tet:label-hop/tet:te-label/tet:technology: +--:(example) +--ro example +--ro label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:tunnel-termination-point - /tet:local-link-connectivities/tet:label-restriction - /tet:label-start/tet:te-label/tet:technology: + /tet:local-link-connectivities/tet:label-restrictions + /tet:label-restriction/tet:label-start/tet:te-label + /tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:tunnel-termination-point - /tet:local-link-connectivities/tet:label-restriction - /tet:label-end/tet:te-label/tet:technology: + /tet:local-link-connectivities/tet:label-restrictions + /tet:label-restriction/tet:label-end/tet:te-label + /tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:tunnel-termination-point /tet:local-link-connectivities/tet:underlay /tet:primary-path/tet:path-element/tet:type/tet:label /tet:label-hop/tet:te-label/tet:technology: +--:(example) +--rw example @@ -1755,30 +1824,32 @@ /tet:tunnel-termination-point /tet:local-link-connectivities/tet:path-properties /tet:path-route-objects/tet:path-route-object/tet:type /tet:label/tet:label-hop/tet:te-label/tet:technology: +--:(example) +--ro example +--ro label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:tunnel-termination-point /tet:local-link-connectivities - /tet:local-link-connectivity/tet:label-restriction - /tet:label-start/tet:te-label/tet:technology: + /tet:local-link-connectivity/tet:label-restrictions + /tet:label-restriction/tet:label-start/tet:te-label + /tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:tunnel-termination-point /tet:local-link-connectivities - /tet:local-link-connectivity/tet:label-restriction - /tet:label-end/tet:te-label/tet:technology: + /tet:local-link-connectivity/tet:label-restrictions + /tet:label-restriction/tet:label-end/tet:te-label + /tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nw:node/tet:te /tet:tunnel-termination-point /tet:local-link-connectivities /tet:local-link-connectivity/tet:underlay /tet:primary-path/tet:path-element/tet:type/tet:label /tet:label-hop/tet:te-label/tet:technology: +--:(example) @@ -1796,97 +1867,114 @@ augment /nw:networks/nw:network/nw:node/tet:te /tet:tunnel-termination-point /tet:local-link-connectivities /tet:local-link-connectivity/tet:path-properties /tet:path-route-objects/tet:path-route-object/tet:type /tet:label/tet:label-hop/tet:te-label/tet:technology: +--:(example) +--ro example +--ro label-1? uint32 augment /nw:networks/nw:network/nt:link/tet:te - /tet:te-link-attributes/tet:label-restriction - /tet:label-start/tet:te-label/tet:technology: + /tet:te-link-attributes/tet:label-restrictions + /tet:label-restriction/tet:label-start/tet:te-label + /tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nt:link/tet:te - /tet:te-link-attributes/tet:label-restriction - /tet:label-end/tet:te-label/tet:technology: + /tet:te-link-attributes/tet:label-restrictions + /tet:label-restriction/tet:label-end/tet:te-label + /tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nt:link/tet:te /tet:te-link-attributes/tet:underlay/tet:primary-path /tet:path-element/tet:type/tet:label/tet:label-hop /tet:te-label/tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nt:link/tet:te /tet:te-link-attributes/tet:underlay/tet:backup-path /tet:path-element/tet:type/tet:label/tet:label-hop /tet:te-label/tet:technology: +--:(example) +--rw example +--rw label-1? uint32 augment /nw:networks/nw:network/nt:link/tet:te - /tet:information-source-entry/tet:label-restriction - /tet:label-start/tet:te-label/tet:technology: + /tet:information-source-entry/tet:label-restrictions + /tet:label-restriction/tet:label-start/tet:te-label + /tet:technology: +--:(example) +--ro example +--ro label-1? uint32 augment /nw:networks/nw:network/nt:link/tet:te - /tet:information-source-entry/tet:label-restriction - /tet:label-end/tet:te-label/tet:technology: + /tet:information-source-entry/tet:label-restrictions + /tet:label-restriction/tet:label-end/tet:te-label + /tet:technology: +--:(example) +--ro example +--ro label-1? uint32 The YANG module to implement the above example topology can be seen in Appendix C. 7. TE Topology YANG Module - file "ietf-te-topology@2018-06-02.yang" + This module references [RFC1195], [RFC3209], [RFC3272], [RFC3471], + [RFC3630], [RFC3785], [RFC4201], [RFC4202], [RFC4203], [RFC4206], + [RFC4872], [RFC5152], [RFC5212], [RFC5305], [RFC5316], [RFC5329], + [RFC5392], [RFC6001], [RFC6241], [RFC6991], [RFC7308], [RFC7471], + [RFC7579], [RFC7752], [RFC8345], and [I-D.ietf-teas-yang-te]. + + file "ietf-te-topology@2018-06-15.yang" module ietf-te-topology { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-te-topology"; prefix "tet"; import ietf-yang-types { prefix "yang"; + reference "RFC 6991: Common YANG Data Types"; } import ietf-inet-types { prefix "inet"; + reference "RFC 6991: Common YANG Data Types"; } import ietf-te-types { prefix "te-types"; + reference + "I-D.ietf-teas-yang-te: A YANG Data Model for Traffic + Engineering Tunnels and Interfaces"; } import ietf-network { prefix "nw"; + reference "RFC 8345: A YANG Data Model for Network Topologies"; } + import ietf-network-topology { prefix "nt"; + reference "RFC 8345: A YANG Data Model for Network Topologies"; } organization "IETF Traffic Engineering Architecture and Signaling (TEAS) Working Group"; contact "WG Web: WG List: - Editor: Xufeng Liu Editor: Igor Bryskin Editor: Vishnu Pavan Beeram Editor: Tarek Saad @@ -1908,21 +1996,21 @@ Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; - revision "2018-06-02" { + revision "2018-06-15" { description "Initial revision"; reference "RFC XXXX: YANG Data Model for TE Topologies"; // RFC Ed.: replace XXXX with actual RFC number and remove // this note } /* * Features */ feature nsrlg { @@ -1986,74 +2074,20 @@ } } description "Describining the type of source that has provided the related information, and the source credibility."; } // te-info-source /* * Groupings */ - grouping connectivity-label-restriction-list { - description - "List of abel restrictions specifying what labels may or may - not be used on a link connectivity."; - list label-restriction { - key "index"; - description - "List of abel restrictions specifying what labels may or may - not be used on a link connectivity."; - reference - "RFC7579: General Network Element Constraint Encoding - for GMPLS-Controlled Networks"; - leaf index { - type uint32; - description - "Then index of the label restriction list entry."; - } - leaf inclusive-exclusive { - type enumeration { - enum inclusive { - description "The label or label range is inclusive."; - } - enum exclusive { - description "The label or label range is exclusive."; - } - } - default inclusive; - description - "Whether the list item is inclusive or exclusive."; - } - container label-start { - description - "This is the starting lable if a lable range is specified. - This is the lable value if a single lable is specified, - in which case, attribute 'label-end' is not set."; - uses te-types:te-label; - } - container label-end { - description - "The ending lable if a lable range is specified; - This attribute is not set, If a single lable is - specified."; - uses te-types:te-label; - } - leaf range-bitmap { - type binary; - description - "When there are gaps between label-start and label-end, - this attribute is used to specified the possitions - of the used labels."; - } - } - } // connectivity-label-restriction-list - grouping connectivity-matrix-entry-path-attributes { description "Attributes of connectivity matrix entry."; leaf is-allowed { type boolean; description "true - switching is allowed, false - switching is disallowed."; } container underlay { @@ -2667,27 +2703,28 @@ description "The link identifier. If OSPF is used, this represents an ospfLsdbID. If IS-IS is used, this represents an isisLSPID. If a locally configured link is used, this object represents a unique value, which is locally defined in a router."; } leaf administrative-group { type te-types:admin-groups; description "Administrative group or color of the link. + This attribute covers both administrative group (defined in - RFC3630, RFC5329, and RFC5305), and extended administrative - group (defined in RFC7308)."; + RFC 3630, RFC 5305 and RFC 5329), and extended + administrative group (defined in RFC 7308)."; } uses interface-switching-capability-list; - uses connectivity-label-restriction-list; + uses te-types:label-set-info; leaf link-protection-type { type enumeration { enum "unprotected" { description "Unprotected."; } enum "extra-traffic" { description "Extra traffic."; } enum "shared" { @@ -3115,27 +3151,27 @@ grouping te-node-connectivity-matrices { description "Connectivity matrix on a TE node."; container connectivity-matrices { description "Containing connectivity matrix on a TE node."; leaf number-of-entries { type uint16; description "The number of connectivity matrix entries. - If this number is speficied in the configuration request, + If this number is specified in the configuration request, the number is requested number of entries, which may not all be listed in the list; if this number is reported in the state data, the number is the current number of operational entries."; } - uses connectivity-label-restriction-list; + uses te-types:label-set-info; uses connectivity-matrix-entry-path-attributes; list connectivity-matrix { key "id"; description "Represents node's switching limitations, i.e. limitations in interconnecting network TE links across the node."; reference "RFC7579: General Network Element Constraint Encoding for GMPLS-Controlled Networks."; leaf id { @@ -3151,33 +3188,33 @@ container from { description "Reference to source link termination point."; leaf tp-ref { type leafref { path "../../../../../../nt:termination-point/nt:tp-id"; } description "Relative reference to a termination point."; } - uses connectivity-label-restriction-list; + uses te-types:label-set-info; } container to { description "Reference to destination link termination point."; leaf tp-ref { type leafref { path "../../../../../../nt:termination-point/nt:tp-id"; } description "Relative reference to a termination point."; } - uses connectivity-label-restriction-list; + uses te-types:label-set-info; } uses connectivity-matrix-entry-path-attributes; } // te-node-connectivity-matrix-attributes grouping te-node-info-attributes { description "Advertised TE information attributes."; leaf domain-id { type uint32; description @@ -3255,28 +3292,27 @@ TE node."; uses te-node-tunnel-termination-point-config-attributes; container local-link-connectivities { description "Containing local link connectivity list for a tunnel termination point on a TE node."; leaf number-of-entries { type uint16; description "The number of local link connectivity list entries. - If this number is speficied in the configuration request, + If this number is specified in the configuration request, the number is requested number of entries, which may not all be listed in the list; if this number is reported in the state data, the number is the current number of operational entries."; - } - uses connectivity-label-restriction-list; + uses te-types:label-set-info; uses connectivity-matrix-entry-path-attributes; } // local-link-connectivities } // te-node-tunnel-termination-point-config grouping te-node-tunnel-termination-point-config-attributes { description "Configuration attributes of a tunnel termination point on a TE node."; leaf admin-status { type te-types:te-admin-status; @@ -3360,34 +3396,34 @@ "Local link connectivity list of a tunnel termination point on a TE node."; list local-link-connectivity { key "link-tp-ref"; description "The termination capabilities between tunnel-termination-point and link termination-point. The capability information can be used to compute the tunnel path. The Interface Adjustment Capability Descriptors (IACD) - [RFC6001] on each link-tp can be derived from this - local-link-connectivity list."; + (defined in RFC 6001) on each link-tp can be derived from + this local-link-connectivity list."; reference "RFC6001: Generalized MPLS (GMPLS) Protocol Extensions for Multi-Layer and Multi-Region Networks (MLN/MRN)."; leaf link-tp-ref { type leafref { path "../../../../../nt:termination-point/nt:tp-id"; } description "Link termination point."; } - uses connectivity-label-restriction-list; + uses te-types:label-set-info; uses connectivity-matrix-entry-path-attributes; } // local-link-connectivity } // te-node-tunnel-termination-point-config grouping te-path-element { description "A group of attributes defining an element in a TE path such as TE node, TE link, TE atomic resource or label."; uses te-types:explicit-route-hop; } // te-path-element @@ -3734,21 +3771,21 @@ leaf src-tp-ref { type leafref { path "../../../../../nw:node[nw:node-id = " + "current()/../../../../nt:source/" + "nt:source-node]/" + "nt:termination-point/nt:tp-id"; require-instance true; } description "Reference to another TE termination point on the - same souruce node."; + same source node."; } leaf des-tp-ref { type leafref { path "../../../../../nw:node[nw:node-id = " + "current()/../../../../nt:destination/" + "nt:dest-node]/" + "nt:termination-point/nt:tp-id"; require-instance true; } description @@ -3867,158 +3904,314 @@ o /nw:networks/nw:network/nw:network-types/tet:te-topology Unauthorized access to this subtree can disclose the TE topology type. o /nw:networks/tet:te Unauthorized access to this subtree can disclose the TE node templates and TE link templates. o /nw:networks/nw:network Unauthorized access to this subtree can disclose the topology-wide - configurations, including the TE topology ID and topology-wide - policies + configurations, including the TE topology ID, the topology-wide + policies, and the topology geolocation. o /nw:networks/nw:network/nw:node Unauthorized access to this subtree can disclose the operational state information of TE nodes. o /nw:networks/nw:network/nt:link/tet:te Unauthorized access to this subtree can disclose the operational state information of TE links. o /nw:networks/nw:network/nw:node/nt:termination-point Unauthorized access to this subtree can disclose the operational state information of TE link termination points. 9. IANA Considerations This document registers the following URIs in the IETF XML registry [RFC3688]. Following the format in [RFC3688], the following registration is requested to be made. URI: urn:ietf:params:xml:ns:yang:ietf-te-topology + Registrant Contact: The IESG. XML: N/A, the requested URI is an XML namespace. URI: urn:ietf:params:xml:ns:yang:ietf-te-topology-state + Registrant Contact: The IESG. XML: N/A, the requested URI is an XML namespace. This document registers a YANG module in the YANG Module Names registry [RFC7950]. name: ietf-te-topology namespace: urn:ietf:params:xml:ns:yang:ietf-te-topology prefix: tet + reference: RFC XXXX name: ietf-te-topology-state namespace: urn:ietf:params:xml:ns:yang:ietf-te-topology-state prefix: tet-s + reference: RFC XXXX 10. References 10.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate - Requirement Levels", BCP 14, RFC 2119, March 1997. + Requirement Levels", BCP 14, RFC 2119, + DOI 10.17487/RFC2119, March 1997, + . [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, - January 2004. + DOI 10.17487/RFC3688, January 2004, + . - [RFC3945] Mannie, E., "Generalized Multi-Protocol Label Switching - (GMPLS) Architecture", October 2004. + [RFC3945] Mannie, E., Ed., "Generalized Multi-Protocol Label + Switching (GMPLS) Architecture", RFC 3945, + DOI 10.17487/RFC3945, October 2004, + . [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security - (TLS) Protocol Version 1.2", RFC 5246, DOI - 10.17487/RFC5246, August 2008. + (TLS) Protocol Version 1.2", RFC 5246, + DOI 10.17487/RFC5246, August 2008, + . - [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., - Ed., and A. Bierman, Ed., "Network Configuration Protocol - (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011. + [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., + and A. Bierman, Ed., "Network Configuration Protocol + (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, + . [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure - Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011. + Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, + . [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration - Protocol (NETCONF) Access Control Model", RFC 6536, DOI - 10.17487/RFC6536, March 2012. + Protocol (NETCONF) Access Control Model", RFC 6536, + DOI 10.17487/RFC6536, March 2012, + . - [RFC6991] Schoenwaelder, J., "Common YANG Data Types", RFC 6991, - July 2013. + [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", + RFC 6991, DOI 10.17487/RFC6991, July 2013, + . [RFC7926] Farrel, A., Ed., Drake, J., Bitar, N., Swallow, G., Ceccarelli, D., and X. Zhang, "Problem Statement and Architecture for Information Exchange between - Interconnected Traffic-Engineered Networks", BCP 206, RFC - 7926, DOI 10.17487/RFC7926, July 2016. + Interconnected Traffic-Engineered Networks", BCP 206, + RFC 7926, DOI 10.17487/RFC7926, July 2016, + . - [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling - Language", RFC 7950, August 2016. + [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", + RFC 7950, DOI 10.17487/RFC7950, August 2016, + . [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF - Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017. + Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, + . [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, - May 2017. + May 2017, . [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., and R. Wilton, "Network Management Datastore Architecture - (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018. + (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, + . [RFC8345] Clemm, A., Medved, J., Varga, R., Bahadur, N., Ananthakrishnan, H., and X. Liu, "A YANG Data Model for - Network Topologies", RFC 8345, DOI 10.17487/RFC8345, - March 2018. - - [YANG-PUSH] Clemm, A., "Subscribing to YANG datastore push updates", - draft-ietf-netconf-yang-push (work in progress), October - 2017. + Network Topologies", RFC 8345, DOI 10.17487/RFC8345, March + 2018, . - [NETCONF-NOTIF] Voit, E., "Custom Subscription to Event - Notifications", draft-ietf-netconf-subscribed- - notifications-05 (work in progress), October 2017. + [I-D.ietf-teas-yang-te] + Saad, T., Gandhi, R., Liu, X., Beeram, V., Shah, H., and + I. Bryskin, "A YANG Data Model for Traffic Engineering + Tunnels and Interfaces", draft-ietf-teas-yang-te-15 (work + in progress), June 2018. 10.2. Informative References [G.709] ITU-T, "Interfaces for the optical transport network", ITU-T Recommendation G.709, June 2016. [G.805] ITU-T, "Generic functional architecture of transport networks", ITU-T Recommendation G.805, March 2000. - [G.872] ITU-T, "Architecture of optical transport networks", ITU- - T Recommendation G.872, January 2017. + [G.872] ITU-T, "Architecture of optical transport networks", ITU-T + Recommendation G.872, January 2017. [G.8080] ITU-T, "Architecture for the automatically switched optical network", ITU-T Recommendation G.8080, February 2012. - [RFC2702] Awduche, D., "Requirements for Traffic Engineering Over - MPLS", RFC 2702, September 1999. + [RFC1195] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and + dual environments", RFC 1195, DOI 10.17487/RFC1195, + December 1990, . + + [RFC2702] Awduche, D., Malcolm, J., Agogbua, J., O'Dell, M., and J. + McManus, "Requirements for Traffic Engineering Over MPLS", + RFC 2702, DOI 10.17487/RFC2702, September 1999, + . + + [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., + and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP + Tunnels", RFC 3209, DOI 10.17487/RFC3209, December 2001, + . + + [RFC3272] Awduche, D., Chiu, A., Elwalid, A., Widjaja, I., and X. + Xiao, "Overview and Principles of Internet Traffic + Engineering", RFC 3272, DOI 10.17487/RFC3272, May 2002, + . + + [RFC3471] Berger, L., Ed., "Generalized Multi-Protocol Label + Switching (GMPLS) Signaling Functional Description", + RFC 3471, DOI 10.17487/RFC3471, January 2003, + . + + [RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering + (TE) Extensions to OSPF Version 2", RFC 3630, + DOI 10.17487/RFC3630, September 2003, + . + + [RFC3785] Le Faucheur, F., Uppili, R., Vedrenne, A., Merckx, P., and + T. Telkamp, "Use of Interior Gateway Protocol (IGP) Metric + as a second MPLS Traffic Engineering (TE) Metric", BCP 87, + RFC 3785, DOI 10.17487/RFC3785, May 2004, + . + + [RFC4201] Kompella, K., Rekhter, Y., and L. Berger, "Link Bundling + in MPLS Traffic Engineering (TE)", RFC 4201, + DOI 10.17487/RFC4201, October 2005, + . + + [RFC4202] Kompella, K., Ed. and Y. Rekhter, Ed., "Routing Extensions + in Support of Generalized Multi-Protocol Label Switching + (GMPLS)", RFC 4202, DOI 10.17487/RFC4202, October 2005, + . + + [RFC4203] Kompella, K., Ed. and Y. Rekhter, Ed., "OSPF Extensions in + Support of Generalized Multi-Protocol Label Switching + (GMPLS)", RFC 4203, DOI 10.17487/RFC4203, October 2005, + . + + [RFC4206] Kompella, K. and Y. Rekhter, "Label Switched Paths (LSP) + Hierarchy with Generalized Multi-Protocol Label Switching + (GMPLS) Traffic Engineering (TE)", RFC 4206, + DOI 10.17487/RFC4206, October 2005, + . + + [RFC4872] Lang, J., Ed., Rekhter, Y., Ed., and D. Papadimitriou, + Ed., "RSVP-TE Extensions in Support of End-to-End + Generalized Multi-Protocol Label Switching (GMPLS) + Recovery", RFC 4872, DOI 10.17487/RFC4872, May 2007, + . + + [RFC5152] Vasseur, JP., Ed., Ayyangar, A., Ed., and R. Zhang, "A + Per-Domain Path Computation Method for Establishing Inter- + Domain Traffic Engineering (TE) Label Switched Paths + (LSPs)", RFC 5152, DOI 10.17487/RFC5152, February 2008, + . + + [RFC5212] Shiomoto, K., Papadimitriou, D., Le Roux, JL., Vigoureux, + M., and D. Brungard, "Requirements for GMPLS-Based Multi- + Region and Multi-Layer Networks (MRN/MLN)", RFC 5212, + DOI 10.17487/RFC5212, July 2008, + . + + [RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic + Engineering", RFC 5305, DOI 10.17487/RFC5305, October + 2008, . + + [RFC5316] Chen, M., Zhang, R., and X. Duan, "ISIS Extensions in + Support of Inter-Autonomous System (AS) MPLS and GMPLS + Traffic Engineering", RFC 5316, DOI 10.17487/RFC5316, + December 2008, . + + [RFC5329] Ishiguro, K., Manral, V., Davey, A., and A. Lindem, Ed., + "Traffic Engineering Extensions to OSPF Version 3", + RFC 5329, DOI 10.17487/RFC5329, September 2008, + . + + [RFC5392] Chen, M., Zhang, R., and X. Duan, "OSPF Extensions in + Support of Inter-Autonomous System (AS) MPLS and GMPLS + Traffic Engineering", RFC 5392, DOI 10.17487/RFC5392, + January 2009, . + + [RFC6001] Papadimitriou, D., Vigoureux, M., Shiomoto, K., Brungard, + D., and JL. Le Roux, "Generalized MPLS (GMPLS) Protocol + Extensions for Multi-Layer and Multi-Region Networks (MLN/ + MRN)", RFC 6001, DOI 10.17487/RFC6001, October 2010, + . + + [RFC7308] Osborne, E., "Extended Administrative Groups in MPLS + Traffic Engineering (MPLS-TE)", RFC 7308, + DOI 10.17487/RFC7308, July 2014, + . + + [RFC7471] Giacalone, S., Ward, D., Drake, J., Atlas, A., and S. + Previdi, "OSPF Traffic Engineering (TE) Metric + Extensions", RFC 7471, DOI 10.17487/RFC7471, March 2015, + . + + [RFC7579] Bernstein, G., Ed., Lee, Y., Ed., Li, D., Imajuku, W., and + J. Han, "General Network Element Constraint Encoding for + GMPLS-Controlled Networks", RFC 7579, + DOI 10.17487/RFC7579, June 2015, + . + + [RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and + S. Ray, "North-Bound Distribution of Link-State and + Traffic Engineering (TE) Information Using BGP", RFC 7752, + DOI 10.17487/RFC7752, March 2016, + . [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", - BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018. + BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, + . - [YANG-SCHEDULE] Liu, X., "A YANG Data Model for Configuration - Scheduling", draft-liu-netmod-yang-schedule (Work in - Progress), September 2017. + [I-D.ietf-netconf-subscribed-notifications] + Voit, E., Clemm, A., Prieto, A., Nilsen-Nygaard, E., and + A. Tripathy, "Customized Subscriptions to a Publisher's + Event Streams", draft-ietf-netconf-subscribed- + notifications-12 (work in progress), April 2018. - [YANG-TOPO-WSON] Lee, Y., "A YANG Data Model for WSON Optical - Networks", draft-ietf-ccamp-wson-yang, (work in - progress), October 2017. + [I-D.ietf-netconf-yang-push] + Clemm, A., Voit, E., Prieto, A., Tripathy, A., Nilsen- + Nygaard, E., Bierman, A., and B. Lengyel, "YANG Datastore + Subscription", draft-ietf-netconf-yang-push-16 (work in + progress), May 2018. - [YANG-TOPO-OTN] Zheng, H., "A YANG Data Model for Optical Transport - Network Topology", draft-ietf-ccamp-otn-topo-yang-01, - work in progress), September 2017. + [I-D.liu-netmod-yang-schedule] + Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and + O. Dios, "A YANG Data Model for Configuration Scheduling", + draft-liu-netmod-yang-schedule-05 (work in progress), + March 2018. - [YANG-TOPO-L3TE] Liu, X., "YANG Data Model for Layer 3 TE - Topologies", draft-liu-teas-yang-l3-te-topo, (work in - progress), July 2017. + [I-D.ietf-ccamp-wson-yang] + Lee, Y., Dhody, D., Zhang, X., Guo, A., Lopezalvarez, V., + King, D., Yoon, B., and R. Vilata, "A Yang Data Model for + WSON Optical Networks", draft-ietf-ccamp-wson-yang-10 + (work in progress), February 2018. + + [I-D.ietf-ccamp-otn-topo-yang] + zhenghaomian@huawei.com, z., Guo, A., Busi, I., Sharma, + A., Liu, X., Belotti, S., Xu, Y., Wang, L., and O. Dios, + "A YANG Data Model for Optical Transport Network + Topology", draft-ietf-ccamp-otn-topo-yang-03 (work in + progress), June 2018. + + [I-D.ietf-teas-yang-l3-te-topo] + Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and + O. Dios, "YANG Data Model for Layer 3 TE Topologies", + draft-ietf-teas-yang-l3-te-topo-01 (work in progress), + March 2018. 11. Acknowledgments The authors would like to thank Lou Berger, Sue Hares, Mazen Khaddam, Cyril Margaria and Zafar Ali for participating in design discussions and providing valuable insights. Appendix A. Complete Model Tree Structure module: ietf-te-topology @@ -4058,78 +4251,64 @@ +--rw name? string +--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 index? uint32 | | +--rw (type)? - | | +--:(numbered) - | | | +--rw numbered-hop - | | | +--rw address? + | | +--:(num-unnum-hop) + | | | +--rw num-unnum-hop + | | | +--rw node-id? + | | | | te-types:te-node-id + | | | +--rw link-tp-id? | | | | te-types:te-tp-id | | | +--rw hop-type? te-hop-type | | | +--rw direction? | | | te-link-direction | | +--:(as-number) | | | +--rw as-number-hop | | | +--rw as-number? binary | | | +--rw hop-type? te-hop-type - | | +--:(unnumbered) - | | | +--rw unnumbered-hop - | | | +--rw node-id? - | | | | te-types:te-node-id - | | | +--rw link-tp-id? - | | | | te-types:te-tp-id - | | | +--rw hop-type? te-hop-type - | | | +--rw direction? - | | | te-link-direction | | +--:(label) | | +--rw label-hop | | +--rw te-label | | +--rw (technology)? | | | +--:(generic) | | | +--rw generic? | | | rt- types:generalized-label | | +--rw direction? | | te-label-direction | +--rw backup-path* [index] | | +--rw index uint32 | | +--rw network-ref? | | | -> /nw:networks/network/network-id | | +--rw path-element* [path-element-id] | | +--rw path-element-id uint32 | | +--rw index? uint32 | | +--rw (type)? - | | +--:(numbered) - | | | +--rw numbered-hop - | | | +--rw address? + | | +--:(num-unnum-hop) + | | | +--rw num-unnum-hop + | | | +--rw node-id? + | | | | te-types:te-node-id + | | | +--rw link-tp-id? | | | | te-types:te-tp-id | | | +--rw hop-type? te-hop-type | | | +--rw direction? | | | te-link-direction | | +--:(as-number) | | | +--rw as-number-hop | | | +--rw as-number? binary | | | +--rw hop-type? te-hop-type - | | +--:(unnumbered) - | | | +--rw unnumbered-hop - | | | +--rw node-id? - | | | | te-types:te-node-id - | | | +--rw link-tp-id? - | | | | te-types:te-tp-id - | | | +--rw hop-type? te-hop-type - | | | +--rw direction? - | | | te-link-direction | | +--:(label) | | +--rw label-hop | | +--rw te-label | | +--rw (technology)? | | | +--:(generic) | | | +--rw generic? | | | rt- types:generalized-label | | +--rw direction? | | te-label-direction @@ -4150,23 +4329,24 @@ +--rw interface-switching-capability* | [switching-capability encoding] | +--rw switching-capability identityref | +--rw encoding identityref | +--rw max-lsp-bandwidth* [priority] | +--rw priority uint8 | +--rw te-bandwidth | +--rw (technology)? | +--:(generic) | +--rw generic? te-bandwidth - +--rw label-restriction* [index] + +--rw label-restrictions + | +--rw label-restriction* [index] + | +--rw restriction? enumeration | +--rw index uint32 - | +--rw inclusive-exclusive? enumeration | +--rw label-start | | +--rw te-label | | +--rw (technology)? | | | +--:(generic) | | | +--rw generic? | | | rt-types:generalized-label | | +--rw direction? te-label-direction | +--rw label-end | | +--rw te-label | | +--rw (technology)? @@ -4217,23 +4397,24 @@ augment /nw:networks/nw:network/nw:node: +--rw te-node-id? te-types:te-node-id +--rw te! +--rw te-node-template* | -> ../../../../te/templates/node-template/name | {template}? +--rw te-node-attributes | +--rw admin-status? te-types:te-admin-status | +--rw connectivity-matrices | | +--rw number-of-entries? uint16 - | | +--rw label-restriction* [index] + | | +--rw label-restrictions + | | | +--rw label-restriction* [index] + | | | +--rw restriction? enumeration | | | +--rw index uint32 - | | | +--rw inclusive-exclusive? enumeration | | | +--rw label-start | | | | +--rw te-label | | | | +--rw (technology)? | | | | | +--:(generic) | | | | | +--rw generic? | | | | | rt-types:generalized-label | | | | +--rw direction? te-label-direction | | | +--rw label-end | | | | +--rw te-label | | | | +--rw (technology)? @@ -4245,70 +4426,60 @@ | | +--rw is-allowed? boolean | | +--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 index? uint32 | | | | +--rw (type)? - | | | | +--:(numbered) - | | | | | +--rw numbered-hop - | | | | | +--rw address? te-types:te-tp-id + | | | | +--:(num-unnum-hop) + | | | | | +--rw num-unnum-hop + | | | | | +--rw node-id? + | | | | | | te-types:te-node-id + | | | | | +--rw link-tp-id? te-types:te-tp-id | | | | | +--rw hop-type? te-hop-type | | | | | +--rw direction? te-link-direction | | | | +--:(as-number) | | | | | +--rw as-number-hop | | | | | +--rw as-number? binary | | | | | +--rw hop-type? te-hop-type - | | | | +--:(unnumbered) - | | | | | +--rw unnumbered-hop - | | | | | +--rw node-id? - | | | | | | te-types:te-node-id - | | | | | +--rw link-tp-id? te-types:te-tp-id - | | | | | +--rw hop-type? te-hop-type - | | | | | +--rw direction? te-link-direction | | | | +--:(label) | | | | +--rw label-hop | | | | +--rw te-label | | | | +--rw (technology)? | | | | | +--:(generic) | | | | | +--rw generic? | | | | | rt-types:generalized- label | | | | +--rw direction? | | | | te-label-direction | | | +--rw backup-path* [index] | | | | +--rw index uint32 | | | | +--rw network-ref? | | | | | -> /nw:networks/network/network-id | | | | +--rw path-element* [path-element-id] | | | | +--rw path-element-id uint32 | | | | +--rw index? uint32 | | | | +--rw (type)? - | | | | +--:(numbered) - | | | | | +--rw numbered-hop - | | | | | +--rw address? te-types:te-tp-id + | | | | +--:(num-unnum-hop) + | | | | | +--rw num-unnum-hop + | | | | | +--rw node-id? + | | | | | | te-types:te-node-id + | | | | | +--rw link-tp-id? te-types:te-tp-id | | | | | +--rw hop-type? te-hop-type | | | | | +--rw direction? te-link-direction | | | | +--:(as-number) | | | | | +--rw as-number-hop | | | | | +--rw as-number? binary | | | | | +--rw hop-type? te-hop-type - | | | | +--:(unnumbered) - | | | | | +--rw unnumbered-hop - | | | | | +--rw node-id? - | | | | | | te-types:te-node-id - | | | | | +--rw link-tp-id? te-types:te-tp-id - | | | | | +--rw hop-type? te-hop-type - | | | | | +--rw direction? te-link-direction | | | | +--:(label) | | | | +--rw label-hop | | | | +--rw te-label | | | | +--rw (technology)? | | | | | +--:(generic) | | | | | +--rw generic? | | | | | rt-types:generalized- label | | | | +--rw direction? | | | | te-label-direction @@ -4322,22 +4493,20 @@ | | | +--rw tunnel-name string | | | +--rw sharing? boolean | | +--rw path-constraints | | | +--rw te-bandwidth | | | | +--rw (technology)? | | | | +--:(generic) | | | | +--rw generic? te-bandwidth | | | +--rw setup-priority? uint8 | | | +--rw hold-priority? uint8 | | | +--rw signaling-type? identityref - | | | +--rw disjointness? - | | | | te-types:te-path-disjointness | | | +--rw path-metric-bounds | | | | +--rw path-metric-bound* [metric-type] | | | | +--rw metric-type identityref | | | | +--rw upper-bound? uint64 | | | +--rw path-affinities | | | | +--rw constraint* [usage] | | | | +--rw usage identityref | | | | +--rw value? admin-groups | | | +--rw path-srlgs | | | +--rw usage? identityref @@ -4348,81 +4517,68 @@ | | | | +--rw optimization-metric* [metric-type] | | | | | +--rw metric-type | | | | | | identityref | | | | | +--rw weight? | | | | | | uint8 | | | | | +--rw explicit-route-exclude-objects | | | | | | +--rw route-object-exclude-object* | | | | | | [index] | | | | | | +--rw index uint32 | | | | | | +--rw (type)? - | | | | | | +--:(numbered) - | | | | | | | +--rw numbered-hop - | | | | | | | +--rw address? + | | | | | | +--:(num-unnum-hop) + | | | | | | | +--rw num-unnum-hop + | | | | | | | +--rw node-id? + | | | | | | | | te-types:te-node-id + | | | | | | | +--rw link-tp-id? | | | | | | | | te-types:te-tp-id | | | | | | | +--rw hop-type? | | | | | | | | te-hop-type | | | | | | | +--rw direction? | | | | | | | te-link-direction | | | | | | +--:(as-number) | | | | | | | +--rw as-number-hop | | | | | | | +--rw as-number? binary | | | | | | | +--rw hop-type? | | | | | | | te-hop-type - | | | | | | +--:(unnumbered) - | | | | | | | +--rw unnumbered-hop - | | | | | | | +--rw node-id? - | | | | | | | | te-types:te-node-id - | | | | | | | +--rw link-tp-id? - | | | | | | | | te-types:te-tp-id - | | | | | | | +--rw hop-type? - | | | | | | | | te-hop-type - | | | | | | | +--rw direction? - | | | | | | | te-link-direction | | | | | | +--:(label) - | | | | | | +--rw label-hop - | | | | | | +--rw te-label - | | | | | | +--rw (technology)? - | | | | | | | +--:(generic) - | | | | | | | +--rw generic? - | | | | | | | rt- + | | | | | | | +--rw label-hop + | | | | | | | +--rw te-label + | | | | | | | +--rw (technology)? + | | | | | | | | +--:(generic) + | | | | | | | | +--rw generic? + | | | | | | | | rt- types:generalized-label - | | | | | | +--rw direction? - | | | | | | te-label-direction + | | | | | | | +--rw direction? + | | | | | | | te-label-direction + | | | | | | +--:(srlg) + | | | | | | +--rw srlg + | | | | | | +--rw srlg? uint32 | | | | | +--rw explicit-route-include-objects | | | | | +--rw route-object-include-object* | | | | | [index] | | | | | +--rw index uint32 | | | | | +--rw (type)? - | | | | | +--:(numbered) - | | | | | | +--rw numbered-hop - | | | | | | +--rw address? + | | | | | +--:(num-unnum-hop) + | | | | | | +--rw num-unnum-hop + | | | | | | +--rw node-id? + | | | | | | | te-types:te-node-id + | | | | | | +--rw link-tp-id? | | | | | | | te-types:te-tp-id | | | | | | +--rw hop-type? | | | | | | | te-hop-type | | | | | | +--rw direction? | | | | | | te-link-direction | | | | | +--:(as-number) | | | | | | +--rw as-number-hop | | | | | | +--rw as-number? binary | | | | | | +--rw hop-type? | | | | | | te-hop-type - | | | | | +--:(unnumbered) - | | | | | | +--rw unnumbered-hop - | | | | | | +--rw node-id? - | | | | | | | te-types:te-node-id - | | | | | | +--rw link-tp-id? - | | | | | | | te-types:te-tp-id - | | | | | | +--rw hop-type? - | | | | | | | te-hop-type - | | | | | | +--rw direction? - | | | | | | te-link-direction | | | | | +--:(label) | | | | | +--rw label-hop | | | | | +--rw te-label | | | | | +--rw (technology)? | | | | | | +--:(generic) | | | | | | +--rw generic? | | | | | | rt- types:generalized-label | | | | | +--rw direction? | | | | | te-label-direction @@ -4441,156 +4597,147 @@ | | | | +--ro constraint* [usage] | | | | +--ro usage identityref | | | | +--ro value? admin-groups | | | +--ro path-srlgs | | | | +--ro usage? identityref | | | | +--ro values* srlg | | | +--ro path-route-objects | | | +--ro path-route-object* [index] | | | +--ro index uint32 | | | +--ro (type)? - | | | +--:(numbered) - | | | | +--ro numbered-hop - | | | | +--ro address? te-types:te-tp-id + | | | +--:(num-unnum-hop) + | | | | +--ro num-unnum-hop + | | | | +--ro node-id? + | | | | | te-types:te-node-id + | | | | +--ro link-tp-id? te-types:te-tp-id | | | | +--ro hop-type? te-hop-type | | | | +--ro direction? te-link-direction | | | +--:(as-number) | | | | +--ro as-number-hop | | | | +--ro as-number? binary | | | | +--ro hop-type? te-hop-type - | | | +--:(unnumbered) - | | | | +--ro unnumbered-hop - | | | | +--ro node-id? - | | | | | te-types:te-node-id - | | | | +--ro link-tp-id? te-types:te-tp-id - | | | | +--ro hop-type? te-hop-type - | | | | +--ro direction? te-link-direction | | | +--:(label) | | | +--ro label-hop | | | +--ro te-label | | | +--ro (technology)? | | | | +--:(generic) | | | | +--ro generic? | | | | rt-types:generalized- label | | | +--ro direction? | | | te-label-direction | | +--rw connectivity-matrix* [id] | | +--rw id uint32 | | +--rw from | | | +--rw tp-ref? leafref + | | | +--rw label-restrictions | | | +--rw label-restriction* [index] + | | | +--rw restriction? enumeration | | | +--rw index uint32 - | | | +--rw inclusive-exclusive? enumeration | | | +--rw label-start | | | | +--rw te-label | | | | +--rw (technology)? | | | | | +--:(generic) | | | | | +--rw generic? - | | | | | rt-types:generalized-label - | | | | +--rw direction? te-label-direction + | | | | | rt-types:generalized- + label + | | | | +--rw direction? + | | | | te-label-direction | | | +--rw label-end | | | | +--rw te-label | | | | +--rw (technology)? | | | | | +--:(generic) | | | | | +--rw generic? - | | | | | rt-types:generalized-label - | | | | +--rw direction? te-label-direction + | | | | | rt-types:generalized- + label + | | | | +--rw direction? + | | | | te-label-direction | | | +--rw range-bitmap? binary | | +--rw to | | | +--rw tp-ref? leafref + | | | +--rw label-restrictions | | | +--rw label-restriction* [index] + | | | +--rw restriction? enumeration | | | +--rw index uint32 - | | | +--rw inclusive-exclusive? enumeration | | | +--rw label-start | | | | +--rw te-label | | | | +--rw (technology)? | | | | | +--:(generic) | | | | | +--rw generic? - | | | | | rt-types:generalized-label - | | | | +--rw direction? te-label-direction + | | | | | rt-types:generalized- + label + | | | | +--rw direction? + | | | | te-label-direction | | | +--rw label-end | | | | +--rw te-label | | | | +--rw (technology)? | | | | | +--:(generic) | | | | | +--rw generic? - | | | | | rt-types:generalized-label - | | | | +--rw direction? te-label-direction + | | | | | rt-types:generalized- + label + | | | | +--rw direction? + | | | | te-label-direction | | | +--rw range-bitmap? binary | | +--rw is-allowed? boolean | | +--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 index? uint32 | | | | +--rw (type)? - | | | | +--:(numbered) - | | | | | +--rw numbered-hop - | | | | | +--rw address? + | | | | +--:(num-unnum-hop) + | | | | | +--rw num-unnum-hop + | | | | | +--rw node-id? + | | | | | | te-types:te-node-id + | | | | | +--rw link-tp-id? | | | | | | te-types:te-tp-id | | | | | +--rw hop-type? te-hop-type | | | | | +--rw direction? | | | | | te-link-direction | | | | +--:(as-number) | | | | | +--rw as-number-hop | | | | | +--rw as-number? binary | | | | | +--rw hop-type? te-hop-type - | | | | +--:(unnumbered) - | | | | | +--rw unnumbered-hop - | | | | | +--rw node-id? - | | | | | | te-types:te-node-id - | | | | | +--rw link-tp-id? - | | | | | | te-types:te-tp-id - | | | | | +--rw hop-type? te-hop-type - | | | | | +--rw direction? - | | | | | te-link-direction | | | | +--:(label) | | | | +--rw label-hop | | | | +--rw te-label | | | | +--rw (technology)? | | | | | +--:(generic) | | | | | +--rw generic? | | | | | rt- types:generalized-label | | | | +--rw direction? | | | | te-label-direction | | | +--rw backup-path* [index] | | | | +--rw index uint32 | | | | +--rw network-ref? | | | | | -> /nw:networks/network/network-id | | | | +--rw path-element* [path-element-id] | | | | +--rw path-element-id uint32 | | | | +--rw index? uint32 | | | | +--rw (type)? - | | | | +--:(numbered) - | | | | | +--rw numbered-hop - | | | | | +--rw address? + | | | | +--:(num-unnum-hop) + | | | | | +--rw num-unnum-hop + | | | | | +--rw node-id? + | | | | | | te-types:te-node-id + | | | | | +--rw link-tp-id? | | | | | | te-types:te-tp-id | | | | | +--rw hop-type? te-hop-type | | | | | +--rw direction? | | | | | te-link-direction | | | | +--:(as-number) | | | | | +--rw as-number-hop | | | | | +--rw as-number? binary | | | | | +--rw hop-type? te-hop-type - | | | | +--:(unnumbered) - | | | | | +--rw unnumbered-hop - | | | | | +--rw node-id? - | | | | | | te-types:te-node-id - | | | | | +--rw link-tp-id? - | | | | | | te-types:te-tp-id - | | | | | +--rw hop-type? te-hop-type - | | | | | +--rw direction? - | | | | | te-link-direction | | | | +--:(label) | | | | +--rw label-hop | | | | +--rw te-label | | | | +--rw (technology)? | | | | | +--:(generic) | | | | | +--rw generic? | | | | | rt- types:generalized-label | | | | +--rw direction? | | | | te-label-direction @@ -4604,22 +4751,20 @@ | | | +--rw tunnel-name string | | | +--rw sharing? boolean | | +--rw path-constraints | | | +--rw te-bandwidth | | | | +--rw (technology)? | | | | +--:(generic) | | | | +--rw generic? te-bandwidth | | | +--rw setup-priority? uint8 | | | +--rw hold-priority? uint8 | | | +--rw signaling-type? identityref - | | | +--rw disjointness? - | | | | te-types:te-path-disjointness | | | +--rw path-metric-bounds | | | | +--rw path-metric-bound* [metric-type] | | | | +--rw metric-type identityref | | | | +--rw upper-bound? uint64 | | | +--rw path-affinities | | | | +--rw constraint* [usage] | | | | +--rw usage identityref | | | | +--rw value? admin-groups | | | +--rw path-srlgs | | | +--rw usage? identityref @@ -4628,88 +4773,73 @@ | | | +--rw (algorithm)? | | | +--:(metric) {path-optimization-metric}? | | | | +--rw optimization-metric* [metric-type] | | | | | +--rw metric-type | | | | | | identityref | | | | | +--rw weight? | | | | | | uint8 | | | | | +--rw explicit-route-exclude-objects | | | | | | +--rw route-object-exclude-object* | | | | | | [index] - | | | | | | +--rw index - | | | | | | | uint32 + | | | | | | +--rw index uint32 | | | | | | +--rw (type)? - | | | | | | +--:(numbered) - | | | | | | | +--rw numbered-hop - | | | | | | | +--rw address? + | | | | | | +--:(num-unnum-hop) + | | | | | | | +--rw num-unnum-hop + | | | | | | | +--rw node-id? + | | | | | | | | te-types:te-node- + id + | | | | | | | +--rw link-tp-id? | | | | | | | | te-types:te-tp-id | | | | | | | +--rw hop-type? | | | | | | | | te-hop-type | | | | | | | +--rw direction? | | | | | | | te-link-direction | | | | | | +--:(as-number) | | | | | | | +--rw as-number-hop | | | | | | | +--rw as-number? binary | | | | | | | +--rw hop-type? | | | | | | | te-hop-type - | | | | | | +--:(unnumbered) - | | | | | | | +--rw unnumbered-hop - | | | | | | | +--rw node-id? - | | | | | | | | te-types:te-node- - id - | | | | | | | +--rw link-tp-id? - | | | | | | | | te-types:te-tp-id - | | | | | | | +--rw hop-type? - | | | | | | | | te-hop-type - | | | | | | | +--rw direction? - | | | | | | | te-link-direction | | | | | | +--:(label) - | | | | | | +--rw label-hop - | | | | | | +--rw te-label - | | | | | | +--rw (technology)? - | | | | | | | +--:(generic) - | | | | | | | +--rw generic? - | | | | | | | rt- + | | | | | | | +--rw label-hop + | | | | | | | +--rw te-label + | | | | | | | +--rw (technology)? + | | | | | | | | +--:(generic) + | | | | | | | | +--rw generic? + | | | | | | | | rt- types:generalized-label - | | | | | | +--rw direction? - | | | | | | te-label- + | | | | | | | +--rw direction? + | | | | | | | te-label- direction + | | | | | | +--:(srlg) + | | | | | | +--rw srlg + | | | | | | +--rw srlg? uint32 | | | | | +--rw explicit-route-include-objects | | | | | +--rw route-object-include-object* | | | | | [index] - | | | | | +--rw index - | | | | | | uint32 + | | | | | +--rw index uint32 | | | | | +--rw (type)? - | | | | | +--:(numbered) - | | | | | | +--rw numbered-hop - | | | | | | +--rw address? + | | | | | +--:(num-unnum-hop) + | | | | | | +--rw num-unnum-hop + | | | | | | +--rw node-id? + | | | | | | | te-types:te-node- + id + | | | | | | +--rw link-tp-id? | | | | | | | te-types:te-tp-id | | | | | | +--rw hop-type? | | | | | | | te-hop-type | | | | | | +--rw direction? | | | | | | te-link-direction | | | | | +--:(as-number) | | | | | | +--rw as-number-hop | | | | | | +--rw as-number? binary | | | | | | +--rw hop-type? | | | | | | te-hop-type - | | | | | +--:(unnumbered) - | | | | | | +--rw unnumbered-hop - | | | | | | +--rw node-id? - | | | | | | | te-types:te-node- - id - | | | | | | +--rw link-tp-id? - | | | | | | | te-types:te-tp-id - | | | | | | +--rw hop-type? - | | | | | | | te-hop-type - | | | | | | +--rw direction? - | | | | | | te-link-direction | | | | | +--:(label) | | | | | +--rw label-hop | | | | | +--rw te-label | | | | | +--rw (technology)? | | | | | | +--:(generic) | | | | | | +--rw generic? | | | | | | rt- types:generalized-label | | | | | +--rw direction? | | | | | te-label- @@ -4731,40 +4861,33 @@ | | | +--ro constraint* [usage] | | | +--ro usage identityref | | | +--ro value? admin-groups | | +--ro path-srlgs | | | +--ro usage? identityref | | | +--ro values* srlg | | +--ro path-route-objects | | +--ro path-route-object* [index] | | +--ro index uint32 | | +--ro (type)? - | | +--:(numbered) - | | | +--ro numbered-hop - | | | +--ro address? + | | +--:(num-unnum-hop) + | | | +--ro num-unnum-hop + | | | +--ro node-id? + | | | | te-types:te-node-id + | | | +--ro link-tp-id? | | | | te-types:te-tp-id | | | +--ro hop-type? te-hop-type | | | +--ro direction? | | | te-link-direction | | +--:(as-number) | | | +--ro as-number-hop | | | +--ro as-number? binary | | | +--ro hop-type? te-hop-type - | | +--:(unnumbered) - | | | +--ro unnumbered-hop - | | | +--ro node-id? - | | | | te-types:te-node-id - | | | +--ro link-tp-id? - | | | | te-types:te-tp-id - | | | +--ro hop-type? te-hop-type - | | | +--ro direction? - | | | te-link-direction | | +--:(label) | | +--ro label-hop | | +--ro te-label | | +--ro (technology)? | | | +--:(generic) | | | +--ro generic? | | | rt- types:generalized-label | | +--ro direction? | | te-label-direction @@ -4793,23 +4916,24 @@ | +--ro information-source-state | | +--ro credibility-preference? uint16 | | +--ro logical-network-element? string | | +--ro network-instance? string | | +--ro topology | | +--ro node-ref? leafref | | +--ro network-ref? | | -> /nw:networks/network/network-id | +--ro connectivity-matrices | | +--ro number-of-entries? uint16 - | | +--ro label-restriction* [index] + | | +--ro label-restrictions + | | | +--ro label-restriction* [index] + | | | +--ro restriction? enumeration | | | +--ro index uint32 - | | | +--ro inclusive-exclusive? enumeration | | | +--ro label-start | | | | +--ro te-label | | | | +--ro (technology)? | | | | | +--:(generic) | | | | | +--ro generic? | | | | | rt-types:generalized-label | | | | +--ro direction? te-label-direction | | | +--ro label-end | | | | +--ro te-label | | | | +--ro (technology)? @@ -4821,70 +4945,60 @@ | | +--ro is-allowed? boolean | | +--ro underlay {te-topology-hierarchy}? | | | +--ro enabled? boolean | | | +--ro primary-path | | | | +--ro network-ref? | | | | | -> /nw:networks/network/network-id | | | | +--ro path-element* [path-element-id] | | | | +--ro path-element-id uint32 | | | | +--ro index? uint32 | | | | +--ro (type)? - | | | | +--:(numbered) - | | | | | +--ro numbered-hop - | | | | | +--ro address? te-types:te-tp-id + | | | | +--:(num-unnum-hop) + | | | | | +--ro num-unnum-hop + | | | | | +--ro node-id? + | | | | | | te-types:te-node-id + | | | | | +--ro link-tp-id? te-types:te-tp-id | | | | | +--ro hop-type? te-hop-type | | | | | +--ro direction? te-link-direction | | | | +--:(as-number) | | | | | +--ro as-number-hop | | | | | +--ro as-number? binary | | | | | +--ro hop-type? te-hop-type - | | | | +--:(unnumbered) - | | | | | +--ro unnumbered-hop - | | | | | +--ro node-id? - | | | | | | te-types:te-node-id - | | | | | +--ro link-tp-id? te-types:te-tp-id - | | | | | +--ro hop-type? te-hop-type - | | | | | +--ro direction? te-link-direction | | | | +--:(label) | | | | +--ro label-hop | | | | +--ro te-label | | | | +--ro (technology)? | | | | | +--:(generic) | | | | | +--ro generic? | | | | | rt-types:generalized- label | | | | +--ro direction? | | | | te-label-direction | | | +--ro backup-path* [index] | | | | +--ro index uint32 | | | | +--ro network-ref? | | | | | -> /nw:networks/network/network-id | | | | +--ro path-element* [path-element-id] | | | | +--ro path-element-id uint32 | | | | +--ro index? uint32 | | | | +--ro (type)? - | | | | +--:(numbered) - | | | | | +--ro numbered-hop - | | | | | +--ro address? te-types:te-tp-id + | | | | +--:(num-unnum-hop) + | | | | | +--ro num-unnum-hop + | | | | | +--ro node-id? + | | | | | | te-types:te-node-id + | | | | | +--ro link-tp-id? te-types:te-tp-id | | | | | +--ro hop-type? te-hop-type | | | | | +--ro direction? te-link-direction | | | | +--:(as-number) | | | | | +--ro as-number-hop | | | | | +--ro as-number? binary | | | | | +--ro hop-type? te-hop-type - | | | | +--:(unnumbered) - | | | | | +--ro unnumbered-hop - | | | | | +--ro node-id? - | | | | | | te-types:te-node-id - | | | | | +--ro link-tp-id? te-types:te-tp-id - | | | | | +--ro hop-type? te-hop-type - | | | | | +--ro direction? te-link-direction | | | | +--:(label) | | | | +--ro label-hop | | | | +--ro te-label | | | | +--ro (technology)? | | | | | +--:(generic) | | | | | +--ro generic? | | | | | rt-types:generalized- label | | | | +--ro direction? | | | | te-label-direction @@ -4898,22 +5012,20 @@ | | | +--ro tunnel-name string | | | +--ro sharing? boolean | | +--ro path-constraints | | | +--ro te-bandwidth | | | | +--ro (technology)? | | | | +--:(generic) | | | | +--ro generic? te-bandwidth | | | +--ro setup-priority? uint8 | | | +--ro hold-priority? uint8 | | | +--ro signaling-type? identityref - | | | +--ro disjointness? - | | | | te-types:te-path-disjointness | | | +--ro path-metric-bounds | | | | +--ro path-metric-bound* [metric-type] | | | | +--ro metric-type identityref | | | | +--ro upper-bound? uint64 | | | +--ro path-affinities | | | | +--ro constraint* [usage] | | | | +--ro usage identityref | | | | +--ro value? admin-groups | | | +--ro path-srlgs | | | +--ro usage? identityref @@ -4924,81 +5036,68 @@ | | | | +--ro optimization-metric* [metric-type] | | | | | +--ro metric-type | | | | | | identityref | | | | | +--ro weight? | | | | | | uint8 | | | | | +--ro explicit-route-exclude-objects | | | | | | +--ro route-object-exclude-object* | | | | | | [index] | | | | | | +--ro index uint32 | | | | | | +--ro (type)? - | | | | | | +--:(numbered) - | | | | | | | +--ro numbered-hop - | | | | | | | +--ro address? + | | | | | | +--:(num-unnum-hop) + | | | | | | | +--ro num-unnum-hop + | | | | | | | +--ro node-id? + | | | | | | | | te-types:te-node-id + | | | | | | | +--ro link-tp-id? | | | | | | | | te-types:te-tp-id | | | | | | | +--ro hop-type? | | | | | | | | te-hop-type | | | | | | | +--ro direction? | | | | | | | te-link-direction | | | | | | +--:(as-number) | | | | | | | +--ro as-number-hop | | | | | | | +--ro as-number? binary | | | | | | | +--ro hop-type? | | | | | | | te-hop-type - | | | | | | +--:(unnumbered) - | | | | | | | +--ro unnumbered-hop - | | | | | | | +--ro node-id? - | | | | | | | | te-types:te-node-id - | | | | | | | +--ro link-tp-id? - | | | | | | | | te-types:te-tp-id - | | | | | | | +--ro hop-type? - | | | | | | | | te-hop-type - | | | | | | | +--ro direction? - | | | | | | | te-link-direction | | | | | | +--:(label) - | | | | | | +--ro label-hop - | | | | | | +--ro te-label - | | | | | | +--ro (technology)? - | | | | | | | +--:(generic) - | | | | | | | +--ro generic? - | | | | | | | rt- + | | | | | | | +--ro label-hop + | | | | | | | +--ro te-label + | | | | | | | +--ro (technology)? + | | | | | | | | +--:(generic) + | | | | | | | | +--ro generic? + | | | | | | | | rt- types:generalized-label - | | | | | | +--ro direction? - | | | | | | te-label-direction + | | | | | | | +--ro direction? + | | | | | | | te-label-direction + | | | | | | +--:(srlg) + | | | | | | +--ro srlg + | | | | | | +--ro srlg? uint32 | | | | | +--ro explicit-route-include-objects | | | | | +--ro route-object-include-object* | | | | | [index] | | | | | +--ro index uint32 | | | | | +--ro (type)? - | | | | | +--:(numbered) - | | | | | | +--ro numbered-hop - | | | | | | +--ro address? + | | | | | +--:(num-unnum-hop) + | | | | | | +--ro num-unnum-hop + | | | | | | +--ro node-id? + | | | | | | | te-types:te-node-id + | | | | | | +--ro link-tp-id? | | | | | | | te-types:te-tp-id | | | | | | +--ro hop-type? | | | | | | | te-hop-type | | | | | | +--ro direction? | | | | | | te-link-direction | | | | | +--:(as-number) | | | | | | +--ro as-number-hop | | | | | | +--ro as-number? binary | | | | | | +--ro hop-type? | | | | | | te-hop-type - | | | | | +--:(unnumbered) - | | | | | | +--ro unnumbered-hop - | | | | | | +--ro node-id? - | | | | | | | te-types:te-node-id - | | | | | | +--ro link-tp-id? - | | | | | | | te-types:te-tp-id - | | | | | | +--ro hop-type? - | | | | | | | te-hop-type - | | | | | | +--ro direction? - | | | | | | te-link-direction | | | | | +--:(label) | | | | | +--ro label-hop | | | | | +--ro te-label | | | | | +--ro (technology)? | | | | | | +--:(generic) | | | | | | +--ro generic? | | | | | | rt- types:generalized-label | | | | | +--ro direction? | | | | | te-label-direction @@ -5017,156 +5116,147 @@ | | | | +--ro constraint* [usage] | | | | +--ro usage identityref | | | | +--ro value? admin-groups | | | +--ro path-srlgs | | | | +--ro usage? identityref | | | | +--ro values* srlg | | | +--ro path-route-objects | | | +--ro path-route-object* [index] | | | +--ro index uint32 | | | +--ro (type)? - | | | +--:(numbered) - | | | | +--ro numbered-hop - | | | | +--ro address? te-types:te-tp-id + | | | +--:(num-unnum-hop) + | | | | +--ro num-unnum-hop + | | | | +--ro node-id? + | | | | | te-types:te-node-id + | | | | +--ro link-tp-id? te-types:te-tp-id | | | | +--ro hop-type? te-hop-type | | | | +--ro direction? te-link-direction | | | +--:(as-number) | | | | +--ro as-number-hop | | | | +--ro as-number? binary | | | | +--ro hop-type? te-hop-type - | | | +--:(unnumbered) - | | | | +--ro unnumbered-hop - | | | | +--ro node-id? - | | | | | te-types:te-node-id - | | | | +--ro link-tp-id? te-types:te-tp-id - | | | | +--ro hop-type? te-hop-type - | | | | +--ro direction? te-link-direction | | | +--:(label) | | | +--ro label-hop | | | +--ro te-label | | | +--ro (technology)? | | | | +--:(generic) | | | | +--ro generic? | | | | rt-types:generalized- label | | | +--ro direction? | | | te-label-direction | | +--ro connectivity-matrix* [id] | | +--ro id uint32 | | +--ro from | | | +--ro tp-ref? leafref + | | | +--ro label-restrictions | | | +--ro label-restriction* [index] + | | | +--ro restriction? enumeration | | | +--ro index uint32 - | | | +--ro inclusive-exclusive? enumeration | | | +--ro label-start | | | | +--ro te-label | | | | +--ro (technology)? | | | | | +--:(generic) | | | | | +--ro generic? - | | | | | rt-types:generalized-label - | | | | +--ro direction? te-label-direction + | | | | | rt-types:generalized- + label + | | | | +--ro direction? + | | | | te-label-direction | | | +--ro label-end | | | | +--ro te-label | | | | +--ro (technology)? | | | | | +--:(generic) | | | | | +--ro generic? - | | | | | rt-types:generalized-label - | | | | +--ro direction? te-label-direction + | | | | | rt-types:generalized- + label + | | | | +--ro direction? + | | | | te-label-direction | | | +--ro range-bitmap? binary | | +--ro to | | | +--ro tp-ref? leafref + | | | +--ro label-restrictions | | | +--ro label-restriction* [index] + | | | +--ro restriction? enumeration | | | +--ro index uint32 - | | | +--ro inclusive-exclusive? enumeration | | | +--ro label-start | | | | +--ro te-label | | | | +--ro (technology)? | | | | | +--:(generic) | | | | | +--ro generic? - | | | | | rt-types:generalized-label - | | | | +--ro direction? te-label-direction + | | | | | rt-types:generalized- + label + | | | | +--ro direction? + | | | | te-label-direction | | | +--ro label-end | | | | +--ro te-label | | | | +--ro (technology)? | | | | | +--:(generic) | | | | | +--ro generic? - | | | | | rt-types:generalized-label - | | | | +--ro direction? te-label-direction + | | | | | rt-types:generalized- + label + | | | | +--ro direction? + | | | | te-label-direction | | | +--ro range-bitmap? binary | | +--ro is-allowed? boolean | | +--ro underlay {te-topology-hierarchy}? | | | +--ro enabled? boolean | | | +--ro primary-path | | | | +--ro network-ref? | | | | | -> /nw:networks/network/network-id | | | | +--ro path-element* [path-element-id] | | | | +--ro path-element-id uint32 | | | | +--ro index? uint32 | | | | +--ro (type)? - | | | | +--:(numbered) - | | | | | +--ro numbered-hop - | | | | | +--ro address? + | | | | +--:(num-unnum-hop) + | | | | | +--ro num-unnum-hop + | | | | | +--ro node-id? + | | | | | | te-types:te-node-id + | | | | | +--ro link-tp-id? | | | | | | te-types:te-tp-id | | | | | +--ro hop-type? te-hop-type | | | | | +--ro direction? | | | | | te-link-direction | | | | +--:(as-number) | | | | | +--ro as-number-hop | | | | | +--ro as-number? binary | | | | | +--ro hop-type? te-hop-type - | | | | +--:(unnumbered) - | | | | | +--ro unnumbered-hop - | | | | | +--ro node-id? - | | | | | | te-types:te-node-id - | | | | | +--ro link-tp-id? - | | | | | | te-types:te-tp-id - | | | | | +--ro hop-type? te-hop-type - | | | | | +--ro direction? - | | | | | te-link-direction | | | | +--:(label) | | | | +--ro label-hop | | | | +--ro te-label | | | | +--ro (technology)? | | | | | +--:(generic) | | | | | +--ro generic? | | | | | rt- types:generalized-label | | | | +--ro direction? | | | | te-label-direction | | | +--ro backup-path* [index] | | | | +--ro index uint32 | | | | +--ro network-ref? | | | | | -> /nw:networks/network/network-id | | | | +--ro path-element* [path-element-id] | | | | +--ro path-element-id uint32 | | | | +--ro index? uint32 | | | | +--ro (type)? - | | | | +--:(numbered) - | | | | | +--ro numbered-hop - | | | | | +--ro address? + | | | | +--:(num-unnum-hop) + | | | | | +--ro num-unnum-hop + | | | | | +--ro node-id? + | | | | | | te-types:te-node-id + | | | | | +--ro link-tp-id? | | | | | | te-types:te-tp-id | | | | | +--ro hop-type? te-hop-type | | | | | +--ro direction? | | | | | te-link-direction | | | | +--:(as-number) | | | | | +--ro as-number-hop | | | | | +--ro as-number? binary | | | | | +--ro hop-type? te-hop-type - | | | | +--:(unnumbered) - | | | | | +--ro unnumbered-hop - | | | | | +--ro node-id? - | | | | | | te-types:te-node-id - | | | | | +--ro link-tp-id? - | | | | | | te-types:te-tp-id - | | | | | +--ro hop-type? te-hop-type - | | | | | +--ro direction? - | | | | | te-link-direction | | | | +--:(label) | | | | +--ro label-hop | | | | +--ro te-label | | | | +--ro (technology)? | | | | | +--:(generic) | | | | | +--ro generic? | | | | | rt- types:generalized-label | | | | +--ro direction? | | | | te-label-direction @@ -5180,22 +5270,20 @@ | | | +--ro tunnel-name string | | | +--ro sharing? boolean | | +--ro path-constraints | | | +--ro te-bandwidth | | | | +--ro (technology)? | | | | +--:(generic) | | | | +--ro generic? te-bandwidth | | | +--ro setup-priority? uint8 | | | +--ro hold-priority? uint8 | | | +--ro signaling-type? identityref - | | | +--ro disjointness? - | | | | te-types:te-path-disjointness | | | +--ro path-metric-bounds | | | | +--ro path-metric-bound* [metric-type] | | | | +--ro metric-type identityref | | | | +--ro upper-bound? uint64 | | | +--ro path-affinities | | | | +--ro constraint* [usage] | | | | +--ro usage identityref | | | | +--ro value? admin-groups | | | +--ro path-srlgs | | | +--ro usage? identityref @@ -5204,88 +5292,73 @@ | | | +--ro (algorithm)? | | | +--:(metric) {path-optimization-metric}? | | | | +--ro optimization-metric* [metric-type] | | | | | +--ro metric-type | | | | | | identityref | | | | | +--ro weight? | | | | | | uint8 | | | | | +--ro explicit-route-exclude-objects | | | | | | +--ro route-object-exclude-object* | | | | | | [index] - | | | | | | +--ro index - | | | | | | | uint32 + | | | | | | +--ro index uint32 | | | | | | +--ro (type)? - | | | | | | +--:(numbered) - | | | | | | | +--ro numbered-hop - | | | | | | | +--ro address? + | | | | | | +--:(num-unnum-hop) + | | | | | | | +--ro num-unnum-hop + | | | | | | | +--ro node-id? + | | | | | | | | te-types:te-node- + id + | | | | | | | +--ro link-tp-id? | | | | | | | | te-types:te-tp-id | | | | | | | +--ro hop-type? | | | | | | | | te-hop-type | | | | | | | +--ro direction? | | | | | | | te-link-direction | | | | | | +--:(as-number) | | | | | | | +--ro as-number-hop | | | | | | | +--ro as-number? binary | | | | | | | +--ro hop-type? | | | | | | | te-hop-type - | | | | | | +--:(unnumbered) - | | | | | | | +--ro unnumbered-hop - | | | | | | | +--ro node-id? - | | | | | | | | te-types:te-node- - id - | | | | | | | +--ro link-tp-id? - | | | | | | | | te-types:te-tp-id - | | | | | | | +--ro hop-type? - | | | | | | | | te-hop-type - | | | | | | | +--ro direction? - | | | | | | | te-link-direction | | | | | | +--:(label) - | | | | | | +--ro label-hop - | | | | | | +--ro te-label - | | | | | | +--ro (technology)? - | | | | | | | +--:(generic) - | | | | | | | +--ro generic? - | | | | | | | rt- + | | | | | | | +--ro label-hop + | | | | | | | +--ro te-label + | | | | | | | +--ro (technology)? + | | | | | | | | +--:(generic) + | | | | | | | | +--ro generic? + | | | | | | | | rt- types:generalized-label - | | | | | | +--ro direction? - | | | | | | te-label- + | | | | | | | +--ro direction? + | | | | | | | te-label- direction + | | | | | | +--:(srlg) + | | | | | | +--ro srlg + | | | | | | +--ro srlg? uint32 | | | | | +--ro explicit-route-include-objects | | | | | +--ro route-object-include-object* | | | | | [index] - | | | | | +--ro index - | | | | | | uint32 + | | | | | +--ro index uint32 | | | | | +--ro (type)? - | | | | | +--:(numbered) - | | | | | | +--ro numbered-hop - | | | | | | +--ro address? + | | | | | +--:(num-unnum-hop) + | | | | | | +--ro num-unnum-hop + | | | | | | +--ro node-id? + | | | | | | | te-types:te-node- + id + | | | | | | +--ro link-tp-id? | | | | | | | te-types:te-tp-id | | | | | | +--ro hop-type? | | | | | | | te-hop-type | | | | | | +--ro direction? | | | | | | te-link-direction | | | | | +--:(as-number) | | | | | | +--ro as-number-hop | | | | | | +--ro as-number? binary | | | | | | +--ro hop-type? | | | | | | te-hop-type - | | | | | +--:(unnumbered) - | | | | | | +--ro unnumbered-hop - | | | | | | +--ro node-id? - | | | | | | | te-types:te-node- - id - | | | | | | +--ro link-tp-id? - | | | | | | | te-types:te-tp-id - | | | | | | +--ro hop-type? - | | | | | | | te-hop-type - | | | | | | +--ro direction? - | | | | | | te-link-direction | | | | | +--:(label) | | | | | +--ro label-hop | | | | | +--ro te-label | | | | | +--ro (technology)? | | | | | | +--:(generic) | | | | | | +--ro generic? | | | | | | rt- types:generalized-label | | | | | +--ro direction? | | | | | te-label- @@ -5307,40 +5380,33 @@ | | | +--ro constraint* [usage] | | | +--ro usage identityref | | | +--ro value? admin-groups | | +--ro path-srlgs | | | +--ro usage? identityref | | | +--ro values* srlg | | +--ro path-route-objects | | +--ro path-route-object* [index] | | +--ro index uint32 | | +--ro (type)? - | | +--:(numbered) - | | | +--ro numbered-hop - | | | +--ro address? + | | +--:(num-unnum-hop) + | | | +--ro num-unnum-hop + | | | +--ro node-id? + | | | | te-types:te-node-id + | | | +--ro link-tp-id? | | | | te-types:te-tp-id | | | +--ro hop-type? te-hop-type | | | +--ro direction? | | | te-link-direction | | +--:(as-number) | | | +--ro as-number-hop | | | +--ro as-number? binary | | | +--ro hop-type? te-hop-type - | | +--:(unnumbered) - | | | +--ro unnumbered-hop - | | | +--ro node-id? - | | | | te-types:te-node-id - | | | +--ro link-tp-id? - | | | | te-types:te-tp-id - | | | +--ro hop-type? te-hop-type - | | | +--ro direction? - | | | te-link-direction | | +--:(label) | | +--ro label-hop | | +--ro te-label | | +--ro (technology)? | | | +--:(generic) | | | +--ro generic? | | | rt- types:generalized-label | | +--ro direction? | | te-label-direction @@ -5377,23 +5443,24 @@ | +--rw switching-capability* | [switching-capability encoding] | +--rw switching-capability identityref | +--rw encoding identityref | +--rw te-bandwidth | +--rw (technology)? | +--:(generic) | +--rw generic? te-bandwidth +--rw local-link-connectivities | +--rw number-of-entries? uint16 - | +--rw label-restriction* [index] + | +--rw label-restrictions + | | +--rw label-restriction* [index] + | | +--rw restriction? enumeration | | +--rw index uint32 - | | +--rw inclusive-exclusive? enumeration | | +--rw label-start | | | +--rw te-label | | | +--rw (technology)? | | | | +--:(generic) | | | | +--rw generic? | | | | rt-types:generalized-label | | | +--rw direction? te-label-direction | | +--rw label-end | | | +--rw te-label | | | +--rw (technology)? @@ -5405,70 +5472,60 @@ | +--rw is-allowed? boolean | +--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 index? uint32 | | | +--rw (type)? - | | | +--:(numbered) - | | | | +--rw numbered-hop - | | | | +--rw address? te-types:te-tp-id + | | | +--:(num-unnum-hop) + | | | | +--rw num-unnum-hop + | | | | +--rw node-id? + | | | | | te-types:te-node-id + | | | | +--rw link-tp-id? te-types:te-tp-id | | | | +--rw hop-type? te-hop-type | | | | +--rw direction? te-link-direction | | | +--:(as-number) | | | | +--rw as-number-hop | | | | +--rw as-number? binary | | | | +--rw hop-type? te-hop-type - | | | +--:(unnumbered) - | | | | +--rw unnumbered-hop - | | | | +--rw node-id? - | | | | | te-types:te-node-id - | | | | +--rw link-tp-id? te-types:te-tp-id - | | | | +--rw hop-type? te-hop-type - | | | | +--rw direction? te-link-direction | | | +--:(label) | | | +--rw label-hop | | | +--rw te-label | | | +--rw (technology)? | | | | +--:(generic) | | | | +--rw generic? | | | | rt-types:generalized- label | | | +--rw direction? | | | te-label-direction | | +--rw backup-path* [index] | | | +--rw index uint32 | | | +--rw network-ref? | | | | -> /nw:networks/network/network-id | | | +--rw path-element* [path-element-id] | | | +--rw path-element-id uint32 | | | +--rw index? uint32 | | | +--rw (type)? - | | | +--:(numbered) - | | | | +--rw numbered-hop - | | | | +--rw address? te-types:te-tp-id + | | | +--:(num-unnum-hop) + | | | | +--rw num-unnum-hop + | | | | +--rw node-id? + | | | | | te-types:te-node-id + | | | | +--rw link-tp-id? te-types:te-tp-id | | | | +--rw hop-type? te-hop-type | | | | +--rw direction? te-link-direction | | | +--:(as-number) | | | | +--rw as-number-hop | | | | +--rw as-number? binary | | | | +--rw hop-type? te-hop-type - | | | +--:(unnumbered) - | | | | +--rw unnumbered-hop - | | | | +--rw node-id? - | | | | | te-types:te-node-id - | | | | +--rw link-tp-id? te-types:te-tp-id - | | | | +--rw hop-type? te-hop-type - | | | | +--rw direction? te-link-direction | | | +--:(label) | | | +--rw label-hop | | | +--rw te-label | | | +--rw (technology)? | | | | +--:(generic) | | | | +--rw generic? | | | | rt-types:generalized- label | | | +--rw direction? | | | te-label-direction @@ -5482,22 +5539,20 @@ | | +--rw tunnel-name string | | +--rw sharing? boolean | +--rw path-constraints | | +--rw te-bandwidth | | | +--rw (technology)? | | | +--:(generic) | | | +--rw generic? te-bandwidth | | +--rw setup-priority? uint8 | | +--rw hold-priority? uint8 | | +--rw signaling-type? identityref - | | +--rw disjointness? - | | | te-types:te-path-disjointness | | +--rw path-metric-bounds | | | +--rw path-metric-bound* [metric-type] | | | +--rw metric-type identityref | | | +--rw upper-bound? uint64 | | +--rw path-affinities | | | +--rw constraint* [usage] | | | +--rw usage identityref | | | +--rw value? admin-groups | | +--rw path-srlgs | | +--rw usage? identityref @@ -5508,81 +5563,68 @@ | | | +--rw optimization-metric* [metric-type] | | | | +--rw metric-type | | | | | identityref | | | | +--rw weight? | | | | | uint8 | | | | +--rw explicit-route-exclude-objects | | | | | +--rw route-object-exclude-object* | | | | | [index] | | | | | +--rw index uint32 | | | | | +--rw (type)? - | | | | | +--:(numbered) - | | | | | | +--rw numbered-hop - | | | | | | +--rw address? + | | | | | +--:(num-unnum-hop) + | | | | | | +--rw num-unnum-hop + | | | | | | +--rw node-id? + | | | | | | | te-types:te-node-id + | | | | | | +--rw link-tp-id? | | | | | | | te-types:te-tp-id | | | | | | +--rw hop-type? | | | | | | | te-hop-type | | | | | | +--rw direction? | | | | | | te-link-direction | | | | | +--:(as-number) | | | | | | +--rw as-number-hop | | | | | | +--rw as-number? binary | | | | | | +--rw hop-type? | | | | | | te-hop-type - | | | | | +--:(unnumbered) - | | | | | | +--rw unnumbered-hop - | | | | | | +--rw node-id? - | | | | | | | te-types:te-node-id - | | | | | | +--rw link-tp-id? - | | | | | | | te-types:te-tp-id - | | | | | | +--rw hop-type? - | | | | | | | te-hop-type - | | | | | | +--rw direction? - | | | | | | te-link-direction | | | | | +--:(label) - | | | | | +--rw label-hop - | | | | | +--rw te-label - | | | | | +--rw (technology)? - | | | | | | +--:(generic) - | | | | | | +--rw generic? - | | | | | | rt- + | | | | | | +--rw label-hop + | | | | | | +--rw te-label + | | | | | | +--rw (technology)? + | | | | | | | +--:(generic) + | | | | | | | +--rw generic? + | | | | | | | rt- types:generalized-label - | | | | | +--rw direction? - | | | | | te-label-direction + | | | | | | +--rw direction? + | | | | | | te-label-direction + | | | | | +--:(srlg) + | | | | | +--rw srlg + | | | | | +--rw srlg? uint32 | | | | +--rw explicit-route-include-objects | | | | +--rw route-object-include-object* | | | | [index] | | | | +--rw index uint32 | | | | +--rw (type)? - | | | | +--:(numbered) - | | | | | +--rw numbered-hop - | | | | | +--rw address? + | | | | +--:(num-unnum-hop) + | | | | | +--rw num-unnum-hop + | | | | | +--rw node-id? + | | | | | | te-types:te-node-id + | | | | | +--rw link-tp-id? | | | | | | te-types:te-tp-id | | | | | +--rw hop-type? | | | | | | te-hop-type | | | | | +--rw direction? | | | | | te-link-direction | | | | +--:(as-number) | | | | | +--rw as-number-hop | | | | | +--rw as-number? binary | | | | | +--rw hop-type? | | | | | te-hop-type - | | | | +--:(unnumbered) - | | | | | +--rw unnumbered-hop - | | | | | +--rw node-id? - | | | | | | te-types:te-node-id - | | | | | +--rw link-tp-id? - | | | | | | te-types:te-tp-id - | | | | | +--rw hop-type? - | | | | | | te-hop-type - | | | | | +--rw direction? - | | | | | te-link-direction | | | | +--:(label) | | | | +--rw label-hop | | | | +--rw te-label | | | | +--rw (technology)? | | | | | +--:(generic) | | | | | +--rw generic? | | | | | rt- types:generalized-label | | | | +--rw direction? | | | | te-label-direction @@ -5601,52 +5643,48 @@ | | | +--ro constraint* [usage] | | | +--ro usage identityref | | | +--ro value? admin-groups | | +--ro path-srlgs | | | +--ro usage? identityref | | | +--ro values* srlg | | +--ro path-route-objects | | +--ro path-route-object* [index] | | +--ro index uint32 | | +--ro (type)? - | | +--:(numbered) - | | | +--ro numbered-hop - | | | +--ro address? te-types:te-tp-id + | | +--:(num-unnum-hop) + | | | +--ro num-unnum-hop + | | | +--ro node-id? + | | | | te-types:te-node-id + | | | +--ro link-tp-id? te-types:te-tp-id | | | +--ro hop-type? te-hop-type | | | +--ro direction? te-link-direction | | +--:(as-number) | | | +--ro as-number-hop | | | +--ro as-number? binary | | | +--ro hop-type? te-hop-type - | | +--:(unnumbered) - | | | +--ro unnumbered-hop - | | | +--ro node-id? - | | | | te-types:te-node-id - | | | +--ro link-tp-id? te-types:te-tp-id - | | | +--ro hop-type? te-hop-type - | | | +--ro direction? te-link-direction | | +--:(label) | | +--ro label-hop | | +--ro te-label | | +--ro (technology)? | | | +--:(generic) | | | +--ro generic? | | | rt-types:generalized- label | | +--ro direction? | | te-label-direction | +--rw local-link-connectivity* [link-tp-ref] | +--rw link-tp-ref | | -> ../../../../../nt:termination-point/tp-id - | +--rw label-restriction* [index] + | +--rw label-restrictions + | | +--rw label-restriction* [index] + | | +--rw restriction? enumeration | | +--rw index uint32 - | | +--rw inclusive-exclusive? enumeration | | +--rw label-start | | | +--rw te-label | | | +--rw (technology)? | | | | +--:(generic) | | | | +--rw generic? | | | | rt-types:generalized-label | | | +--rw direction? te-label-direction | | +--rw label-end | | | +--rw te-label | | | +--rw (technology)? @@ -5658,78 +5696,64 @@ | +--rw is-allowed? boolean | +--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 index? uint32 | | | +--rw (type)? - | | | +--:(numbered) - | | | | +--rw numbered-hop - | | | | +--rw address? + | | | +--:(num-unnum-hop) + | | | | +--rw num-unnum-hop + | | | | +--rw node-id? + | | | | | te-types:te-node-id + | | | | +--rw link-tp-id? | | | | | te-types:te-tp-id | | | | +--rw hop-type? te-hop-type | | | | +--rw direction? | | | | te-link-direction | | | +--:(as-number) | | | | +--rw as-number-hop | | | | +--rw as-number? binary | | | | +--rw hop-type? te-hop-type - | | | +--:(unnumbered) - | | | | +--rw unnumbered-hop - | | | | +--rw node-id? - | | | | | te-types:te-node-id - | | | | +--rw link-tp-id? - | | | | | te-types:te-tp-id - | | | | +--rw hop-type? te-hop-type - | | | | +--rw direction? - | | | | te-link-direction | | | +--:(label) | | | +--rw label-hop | | | +--rw te-label | | | +--rw (technology)? | | | | +--:(generic) | | | | +--rw generic? | | | | rt- types:generalized-label | | | +--rw direction? | | | te-label-direction | | +--rw backup-path* [index] | | | +--rw index uint32 | | | +--rw network-ref? | | | | -> /nw:networks/network/network-id | | | +--rw path-element* [path-element-id] | | | +--rw path-element-id uint32 | | | +--rw index? uint32 | | | +--rw (type)? - | | | +--:(numbered) - | | | | +--rw numbered-hop - | | | | +--rw address? + | | | +--:(num-unnum-hop) + | | | | +--rw num-unnum-hop + | | | | +--rw node-id? + | | | | | te-types:te-node-id + | | | | +--rw link-tp-id? | | | | | te-types:te-tp-id | | | | +--rw hop-type? te-hop-type | | | | +--rw direction? | | | | te-link-direction | | | +--:(as-number) | | | | +--rw as-number-hop | | | | +--rw as-number? binary | | | | +--rw hop-type? te-hop-type - | | | +--:(unnumbered) - | | | | +--rw unnumbered-hop - | | | | +--rw node-id? - | | | | | te-types:te-node-id - | | | | +--rw link-tp-id? - | | | | | te-types:te-tp-id - | | | | +--rw hop-type? te-hop-type - | | | | +--rw direction? - | | | | te-link-direction | | | +--:(label) | | | +--rw label-hop | | | +--rw te-label | | | +--rw (technology)? | | | | +--:(generic) | | | | +--rw generic? | | | | rt- types:generalized-label | | | +--rw direction? | | | te-label-direction @@ -5743,22 +5767,20 @@ | | +--rw tunnel-name string | | +--rw sharing? boolean | +--rw path-constraints | | +--rw te-bandwidth | | | +--rw (technology)? | | | +--:(generic) | | | +--rw generic? te-bandwidth | | +--rw setup-priority? uint8 | | +--rw hold-priority? uint8 | | +--rw signaling-type? identityref - | | +--rw disjointness? - | | | te-types:te-path-disjointness | | +--rw path-metric-bounds | | | +--rw path-metric-bound* [metric-type] | | | +--rw metric-type identityref | | | +--rw upper-bound? uint64 | | +--rw path-affinities | | | +--rw constraint* [usage] | | | +--rw usage identityref | | | +--rw value? admin-groups | | +--rw path-srlgs | | +--rw usage? identityref @@ -5767,88 +5789,73 @@ | | +--rw (algorithm)? | | +--:(metric) {path-optimization-metric}? | | | +--rw optimization-metric* [metric-type] | | | | +--rw metric-type | | | | | identityref | | | | +--rw weight? | | | | | uint8 | | | | +--rw explicit-route-exclude-objects | | | | | +--rw route-object-exclude-object* | | | | | [index] - | | | | | +--rw index - | | | | | | uint32 + | | | | | +--rw index uint32 | | | | | +--rw (type)? - | | | | | +--:(numbered) - | | | | | | +--rw numbered-hop - | | | | | | +--rw address? + | | | | | +--:(num-unnum-hop) + | | | | | | +--rw num-unnum-hop + | | | | | | +--rw node-id? + | | | | | | | te-types:te-node- + id + | | | | | | +--rw link-tp-id? | | | | | | | te-types:te-tp-id | | | | | | +--rw hop-type? | | | | | | | te-hop-type | | | | | | +--rw direction? | | | | | | te-link-direction | | | | | +--:(as-number) | | | | | | +--rw as-number-hop | | | | | | +--rw as-number? binary | | | | | | +--rw hop-type? | | | | | | te-hop-type - | | | | | +--:(unnumbered) - | | | | | | +--rw unnumbered-hop - | | | | | | +--rw node-id? - | | | | | | | te-types:te-node- - id - | | | | | | +--rw link-tp-id? - | | | | | | | te-types:te-tp-id - | | | | | | +--rw hop-type? - | | | | | | | te-hop-type - | | | | | | +--rw direction? - | | | | | | te-link-direction | | | | | +--:(label) - | | | | | +--rw label-hop - | | | | | +--rw te-label - | | | | | +--rw (technology)? - | | | | | | +--:(generic) - | | | | | | +--rw generic? - | | | | | | rt- + | | | | | | +--rw label-hop + | | | | | | +--rw te-label + | | | | | | +--rw (technology)? + | | | | | | | +--:(generic) + | | | | | | | +--rw generic? + | | | | | | | rt- types:generalized-label - | | | | | +--rw direction? - | | | | | te-label- + | | | | | | +--rw direction? + | | | | | | te-label- direction + | | | | | +--:(srlg) + | | | | | +--rw srlg + | | | | | +--rw srlg? uint32 | | | | +--rw explicit-route-include-objects | | | | +--rw route-object-include-object* | | | | [index] - | | | | +--rw index - | | | | | uint32 + | | | | +--rw index uint32 | | | | +--rw (type)? - | | | | +--:(numbered) - | | | | | +--rw numbered-hop - | | | | | +--rw address? + | | | | +--:(num-unnum-hop) + | | | | | +--rw num-unnum-hop + | | | | | +--rw node-id? + | | | | | | te-types:te-node- + id + | | | | | +--rw link-tp-id? | | | | | | te-types:te-tp-id | | | | | +--rw hop-type? | | | | | | te-hop-type | | | | | +--rw direction? | | | | | te-link-direction | | | | +--:(as-number) | | | | | +--rw as-number-hop | | | | | +--rw as-number? binary | | | | | +--rw hop-type? | | | | | te-hop-type - | | | | +--:(unnumbered) - | | | | | +--rw unnumbered-hop - | | | | | +--rw node-id? - | | | | | | te-types:te-node- - id - | | | | | +--rw link-tp-id? - | | | | | | te-types:te-tp-id - | | | | | +--rw hop-type? - | | | | | | te-hop-type - | | | | | +--rw direction? - | | | | | te-link-direction | | | | +--:(label) | | | | +--rw label-hop | | | | +--rw te-label | | | | +--rw (technology)? | | | | | +--:(generic) | | | | | +--rw generic? | | | | | rt- types:generalized-label | | | | +--rw direction? | | | | te-label- @@ -5870,40 +5877,33 @@ | | +--ro constraint* [usage] | | +--ro usage identityref | | +--ro value? admin-groups | +--ro path-srlgs | | +--ro usage? identityref | | +--ro values* srlg | +--ro path-route-objects | +--ro path-route-object* [index] | +--ro index uint32 | +--ro (type)? - | +--:(numbered) - | | +--ro numbered-hop - | | +--ro address? + | +--:(num-unnum-hop) + | | +--ro num-unnum-hop + | | +--ro node-id? + | | | te-types:te-node-id + | | +--ro link-tp-id? | | | te-types:te-tp-id | | +--ro hop-type? te-hop-type | | +--ro direction? | | te-link-direction | +--:(as-number) | | +--ro as-number-hop | | +--ro as-number? binary | | +--ro hop-type? te-hop-type - | +--:(unnumbered) - | | +--ro unnumbered-hop - | | +--ro node-id? - | | | te-types:te-node-id - | | +--ro link-tp-id? - | | | te-types:te-tp-id - | | +--ro hop-type? te-hop-type - | | +--ro direction? - | | te-link-direction | +--:(label) | +--ro label-hop | +--ro te-label | +--ro (technology)? | | +--:(generic) | | +--ro generic? | | rt- types:generalized-label | +--ro direction? | te-label-direction @@ -5965,68 +5966,58 @@ | +--rw name? string | +--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 index? uint32 | | | +--rw (type)? - | | | +--:(numbered) - | | | | +--rw numbered-hop - | | | | +--rw address? te-types:te-tp-id + | | | +--:(num-unnum-hop) + | | | | +--rw num-unnum-hop + | | | | +--rw node-id? te-types:te-node-id + | | | | +--rw link-tp-id? te-types:te-tp-id | | | | +--rw hop-type? te-hop-type | | | | +--rw direction? te-link-direction | | | +--:(as-number) | | | | +--rw as-number-hop | | | | +--rw as-number? binary | | | | +--rw hop-type? te-hop-type - | | | +--:(unnumbered) - | | | | +--rw unnumbered-hop - | | | | +--rw node-id? te-types:te-node-id - | | | | +--rw link-tp-id? te-types:te-tp-id - | | | | +--rw hop-type? te-hop-type - | | | | +--rw direction? te-link-direction | | | +--:(label) | | | +--rw label-hop | | | +--rw te-label | | | +--rw (technology)? | | | | +--:(generic) | | | | +--rw generic? | | | | rt-types:generalized- label | | | +--rw direction? | | | te-label-direction | | +--rw backup-path* [index] | | | +--rw index uint32 | | | +--rw network-ref? | | | | -> /nw:networks/network/network-id | | | +--rw path-element* [path-element-id] | | | +--rw path-element-id uint32 | | | +--rw index? uint32 | | | +--rw (type)? - | | | +--:(numbered) - | | | | +--rw numbered-hop - | | | | +--rw address? te-types:te-tp-id + | | | +--:(num-unnum-hop) + | | | | +--rw num-unnum-hop + | | | | +--rw node-id? te-types:te-node-id + | | | | +--rw link-tp-id? te-types:te-tp-id | | | | +--rw hop-type? te-hop-type | | | | +--rw direction? te-link-direction | | | +--:(as-number) | | | | +--rw as-number-hop | | | | +--rw as-number? binary | | | | +--rw hop-type? te-hop-type - | | | +--:(unnumbered) - | | | | +--rw unnumbered-hop - | | | | +--rw node-id? te-types:te-node-id - | | | | +--rw link-tp-id? te-types:te-tp-id - | | | | +--rw hop-type? te-hop-type - | | | | +--rw direction? te-link-direction | | | +--:(label) | | | +--rw label-hop | | | +--rw te-label | | | +--rw (technology)? | | | | +--:(generic) | | | | +--rw generic? | | | | rt-types:generalized- label | | | +--rw direction? | | | te-label-direction @@ -6047,34 +6038,37 @@ | +--rw interface-switching-capability* | | [switching-capability encoding] | | +--rw switching-capability identityref | | +--rw encoding identityref | | +--rw max-lsp-bandwidth* [priority] | | +--rw priority uint8 | | +--rw te-bandwidth | | +--rw (technology)? | | +--:(generic) | | +--rw generic? te-bandwidth - | +--rw label-restriction* [index] + | +--rw label-restrictions + | | +--rw label-restriction* [index] + | | +--rw restriction? enumeration | | +--rw index uint32 - | | +--rw inclusive-exclusive? enumeration | | +--rw label-start | | | +--rw te-label | | | +--rw (technology)? | | | | +--:(generic) - | | | | +--rw generic? rt-types:generalized-label + | | | | +--rw generic? + | | | | rt-types:generalized-label | | | +--rw direction? te-label-direction | | +--rw label-end | | | +--rw te-label | | | +--rw (technology)? | | | | +--:(generic) - | | | | +--rw generic? rt-types:generalized-label + | | | | +--rw generic? + | | | | rt-types:generalized-label | | | +--rw direction? te-label-direction | | +--rw range-bitmap? binary | +--rw link-protection-type? enumeration | +--rw max-link-bandwidth | | +--rw te-bandwidth | | +--rw (technology)? | | +--:(generic) | | +--rw generic? te-bandwidth | +--rw max-resv-link-bandwidth | | +--rw te-bandwidth @@ -6120,34 +6114,37 @@ | +--ro interface-switching-capability* | | [switching-capability encoding] | | +--ro switching-capability identityref | | +--ro encoding identityref | | +--ro max-lsp-bandwidth* [priority] | | +--ro priority uint8 | | +--ro te-bandwidth | | +--ro (technology)? | | +--:(generic) | | +--ro generic? te-bandwidth - | +--ro label-restriction* [index] + | +--ro label-restrictions + | | +--ro label-restriction* [index] + | | +--ro restriction? enumeration | | +--ro index uint32 - | | +--ro inclusive-exclusive? enumeration | | +--ro label-start | | | +--ro te-label | | | +--ro (technology)? | | | | +--:(generic) - | | | | +--ro generic? rt-types:generalized-label + | | | | +--ro generic? + | | | | rt-types:generalized-label | | | +--ro direction? te-label-direction | | +--ro label-end | | | +--ro te-label | | | +--ro (technology)? | | | | +--:(generic) - | | | | +--ro generic? rt-types:generalized-label + | | | | +--ro generic? + | | | | rt-types:generalized-label | | | +--ro direction? te-label-direction | | +--ro range-bitmap? binary | +--ro link-protection-type? enumeration | +--ro max-link-bandwidth | | +--ro te-bandwidth | | +--ro (technology)? | | +--:(generic) | | +--ro generic? te-bandwidth | +--ro max-resv-link-bandwidth | | +--ro te-bandwidth @@ -6232,42 +6229,51 @@ The companion module, ietf-te-topology-state, is redundant and SHOULD NOT be supported by implementations that support NMDA. As the structure of the module ietf-te-topology-state mirrors that of the module ietf-te-topology. The YANG tree of the module ietf-te- topology-state is not depicted separately. B.1. TE Topology State YANG Module - file "ietf-te-topology-state@2018-06-02.yang" + This module references [RFC6001], [RFC8345], and [I-D.ietf-teas-yang- + te]. + + file "ietf-te-topology-state@2018-06-15.yang" module ietf-te-topology-state { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-te-topology-state"; prefix "tet-s"; import ietf-te-types { prefix "te-types"; + reference + "I-D.ietf-teas-yang-te: A YANG Data Model for Traffic + Engineering Tunnels and Interfaces"; } import ietf-te-topology { prefix "tet"; } import ietf-network-state { prefix "nw-s"; + reference "RFC 8345: A YANG Data Model for Network Topologies"; } import ietf-network-topology-state { prefix "nt-s"; + reference "RFC 8345: A YANG Data Model for Network Topologies"; } + organization "IETF Traffic Engineering Architecture and Signaling (TEAS) Working Group"; contact "WG Web: WG List: Editor: Xufeng Liu @@ -6282,21 +6288,21 @@ Editor: Himanshu Shah Editor: Oscar Gonzalez De Dios "; description "TE topology state model"; - revision "2018-06-02" { + revision "2018-06-15" { description "Initial revision"; reference "RFC XXXX: YANG Data Model for TE Topologies"; // RFC Ed.: replace XXXX with actual RFC number and remove // this note } /* * Groupings */ grouping te-node-connectivity-matrix-attributes { @@ -6305,63 +6311,63 @@ container from { description "Reference to source link termination point."; leaf tp-ref { type leafref { path "../../../../../../nt-s:termination-point/nt-s:tp-id"; } description "Relative reference to a termination point."; } - uses tet:connectivity-label-restriction-list; + uses te-types:label-set-info; } container to { description "Reference to destination link termination point."; leaf tp-ref { type leafref { path "../../../../../../nt-s:termination-point/nt-s:tp-id"; } description "Relative reference to a termination point."; } - uses tet:connectivity-label-restriction-list; + uses te-types:label-set-info; } uses tet:connectivity-matrix-entry-path-attributes; } // te-node-connectivity-matrix-attributes grouping te-node-tunnel-termination-point-llc-list { description "Local link connectivity list of a tunnel termination point on a TE node."; list local-link-connectivity { key "link-tp-ref"; description "The termination capabilities between tunnel-termination-point and link termination-point. The capability information can be used to compute the tunnel path. The Interface Adjustment Capability Descriptors (IACD) - [RFC6001] on each link-tp can be derived from this - local-link-connectivity list."; + (defined in RFC 6001) on each link-tp can be derived from + this local-link-connectivity list."; reference "RFC6001: Generalized MPLS (GMPLS) Protocol Extensions for Multi-Layer and Multi-Region Networks (MLN/MRN)."; leaf link-tp-ref { type leafref { path "../../../../../nt-s:termination-point/nt-s:tp-id"; } description "Link termination point."; } - uses tet:connectivity-label-restriction-list; + uses te-types:label-set-info; uses tet:connectivity-matrix-entry-path-attributes; } // local-link-connectivity } // te-node-tunnel-termination-point-config /* * Data nodes */ augment "/nw-s:networks/nw-s:network/nw-s:network-types" { description "Introduce new network type for TE topology."; @@ -6470,21 +6475,21 @@ leaf src-tp-ref { type leafref { path "../../../../../nw-s:node[nw-s:node-id = " + "current()/../../../../nt-s:source/" + "nt-s:source-node]/" + "nt-s:termination-point/nt-s:tp-id"; require-instance true; } description "Reference to another TE termination point on the - same souruce node."; + same source node."; } leaf des-tp-ref { type leafref { path "../../../../../nw-s:node[nw-s:node-id = " + "current()/../../../../nt-s:destination/" + "nt-s:dest-node]/" + "nt-s:termination-point/nt-s:tp-id"; require-instance true; } description @@ -6562,21 +6567,21 @@ organization "Example Organization"; contact "Editor: Example Author"; description "This module defines a topology data model for the example technology."; - revision 2018-06-02 { + revision 2018-06-15 { description "Initial revision."; reference "Example reference."; } /* * Data nodes */ augment "/nw:networks/nw:network/nw:network-types/" @@ -6688,106 +6693,106 @@ + "ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } description "Augment link termination point."; container attributes { description "Attributes for example technology."; leaf attribute-5 { type uint8; - description "Attribute 4 for example technology."; + description "Attribute 5 for example technology."; } } } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:te-link-attributes" { when "../../../nw:network-types/tet:te-topology/" + "ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } description "Augment link attributes."; container attributes { description "Attributes for example technology."; leaf attribute-6 { type uint8; - description "Attribute 4 for example technology."; + description "Attribute 6 for example technology."; } } } /* * Augment TE bandwidth. */ augment "/nw:networks/tet:te/tet:templates/" + "tet:link-template/tet:te-link-attributes/" + "tet:interface-switching-capability/tet:max-lsp-bandwidth/" + "tet:te-bandwidth/tet:technology" { case "example" { container example { description "Attributes for example technology."; leaf bandwidth-1 { type uint32; - description "Attribute 11 for example technology."; + description "Bandwidth 1 for example technology."; } } } description "Augment TE bandwidth."; } augment "/nw:networks/tet:te/tet:templates/" + "tet:link-template/tet:te-link-attributes/" + "tet:max-link-bandwidth/" + "tet:te-bandwidth/tet:technology" { case "example" { container example { description "Attributes for example technology."; leaf bandwidth-1 { type uint32; - description "Attribute 11 for example technology."; + description "Bandwidth 1 for example technology."; } } } description "Augment TE bandwidth."; } augment "/nw:networks/tet:te/tet:templates/" + "tet:link-template/tet:te-link-attributes/" + "tet:max-resv-link-bandwidth/" + "tet:te-bandwidth/tet:technology" { case "example" { container example { description "Attributes for example technology."; leaf bandwidth-1 { type uint32; - description "Attribute 11 for example technology."; + description "Bandwidth 1 for example technology."; } } } description "Augment TE bandwidth."; } augment "/nw:networks/tet:te/tet:templates/" + "tet:link-template/tet:te-link-attributes/" + "tet:unreserved-bandwidth/" + "tet:te-bandwidth/tet:technology" { case "example" { container example { description "Attributes for example technology."; leaf bandwidth-1 { type uint32; - description "Attribute 11 for example technology."; + description "Bandwidth 1 for example technology."; } } } description "Augment TE bandwidth."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:path-constraints/tet:te-bandwidth/tet:technology" { @@ -6795,21 +6800,21 @@ + "ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf bandwidth-1 { type uint32; - description "Attribute 11 for example technology."; + description "Bandwidth 1 for example technology."; } } } description "Augment TE bandwidth."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:connectivity-matrix/" + "tet:path-constraints/tet:te-bandwidth/tet:technology" { @@ -6817,21 +6822,21 @@ + "ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf bandwidth-1 { type uint32; - description "Attribute 11 for example technology."; + description "Bandwidth 1 for example technology."; } } } description "Augment TE bandwidth."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:path-constraints/tet:te-bandwidth/tet:technology" { @@ -6839,21 +6844,21 @@ + "ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf bandwidth-1 { type uint32; - description "Attribute 11 for example technology."; + description "Bandwidth 1 for example technology."; } } } description "Augment TE bandwidth."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:connectivity-matrix/" + "tet:path-constraints/tet:te-bandwidth/tet:technology" { @@ -6861,21 +6866,21 @@ + "ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf bandwidth-1 { type uint32; - description "Attribute 11 for example technology."; + description "Bandwidth 1 for example technology."; } } } description "Augment TE bandwidth."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:tunnel-termination-point/tet:client-layer-adaptation/" + "tet:switching-capability/tet:te-bandwidth/tet:technology" { @@ -6883,42 +6888,42 @@ + "ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf bandwidth-1 { type uint32; - description "Attribute 11 for example technology."; + description "Bandwidth 1 for example technology."; } } } description "Augment TE bandwidth."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:tunnel-termination-point/tet:local-link-connectivities/" + "tet:path-constraints/tet:te-bandwidth/tet:technology" { when "../../../../../../../nw:network-types/tet:te-topology/" + "ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf bandwidth-1 { type uint32; - description "Attribute 11 for example technology."; + description "Bandwidth 1 for example technology."; } } } description "Augment TE bandwidth."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:tunnel-termination-point/tet:local-link-connectivities/" + "tet:local-link-connectivity/" + "tet:path-constraints/tet:te-bandwidth/tet:technology" { @@ -6926,21 +6931,21 @@ + "ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf bandwidth-1 { type uint32; - description "Attribute 11 for example technology."; + description "Bandwidth 1 for example technology."; } } } description "Augment TE bandwidth."; } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:te-link-attributes/" + "tet:interface-switching-capability/tet:max-lsp-bandwidth/" + "tet:te-bandwidth/tet:technology" { @@ -6948,21 +6953,21 @@ + "ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf bandwidth-1 { type uint32; - description "Attribute 11 for example technology."; + description "Bandwidth 1 for example technology."; } } } description "Augment TE bandwidth."; } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:te-link-attributes/" + "tet:max-link-bandwidth/" + "tet:te-bandwidth/tet:technology" { @@ -6970,21 +6975,21 @@ + "ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf bandwidth-1 { type uint32; - description "Attribute 11 for example technology."; + description "Bandwidth 1 for example technology."; } } } description "Augment TE bandwidth."; } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:te-link-attributes/" + "tet:max-resv-link-bandwidth/" + "tet:te-bandwidth/tet:technology" { @@ -6993,21 +6998,21 @@ description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf bandwidth-1 { type uint32; - description "Attribute 11 for example technology."; + description "Bandwidth 1 for example technology."; } } } description "Augment TE bandwidth."; } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:information-source-entry/" + "tet:interface-switching-capability/tet:max-lsp-bandwidth/" + "tet:te-bandwidth/tet:technology" { @@ -7015,21 +7020,21 @@ + "ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf bandwidth-1 { type uint32; - description "Attribute 11 for example technology."; + description "Bandwidth 1 for example technology."; } } } description "Augment TE bandwidth."; } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:information-source-entry/" + "tet:max-link-bandwidth/" + "tet:te-bandwidth/tet:technology" { @@ -7038,21 +7043,21 @@ description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf bandwidth-1 { type uint32; - description "Attribute 11 for example technology."; + description "Bandwidth 1 for example technology."; } } } description "Augment TE bandwidth."; } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:information-source-entry/" + "tet:max-resv-link-bandwidth/" + "tet:te-bandwidth/tet:technology" { @@ -7060,21 +7065,21 @@ + "ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf bandwidth-1 { type uint32; - description "Attribute 11 for example technology."; + description "Bandwidth 1 for example technology."; } } } description "Augment TE bandwidth."; } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:information-source-entry/" + "tet:unreserved-bandwidth/" + "tet:te-bandwidth/tet:technology" { @@ -7082,21 +7087,21 @@ + "ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf bandwidth-1 { type uint32; - description "Attribute 11 for example technology."; + description "Bandwidth 1 for example technology."; } } } description "Augment TE bandwidth."; } augment "/nw:networks/nw:network/nw:node/nt:termination-point/" + "tet:te/" + "tet:interface-switching-capability/tet:max-lsp-bandwidth/" + "tet:te-bandwidth/tet:technology" { @@ -7104,134 +7109,134 @@ + "ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf bandwidth-1 { type uint32; - description "Attribute 11 for example technology."; + description "Bandwidth 1 for example technology."; } } } description "Augment TE bandwidth."; } /* * Augment TE label. */ augment "/nw:networks/tet:te/tet:templates/" + "tet:link-template/tet:te-link-attributes/" + "tet:underlay/tet:primary-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } augment "/nw:networks/tet:te/tet:templates/" + "tet:link-template/tet:te-link-attributes/" + "tet:underlay/tet:backup-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } augment "/nw:networks/tet:te/tet:templates/" + "tet:link-template/tet:te-link-attributes/" - + "tet:label-restriction/tet:label-start/tet:te-label/" - + "tet:technology" { + + "tet:label-restrictions/tet:label-restriction/tet:label-start/" + + "tet:te-label/tet:technology" { case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } augment "/nw:networks/tet:te/tet:templates/" + "tet:link-template/tet:te-link-attributes/" - + "tet:label-restriction/tet:label-end/tet:te-label/" - + "tet:technology" { + + "tet:label-restrictions/tet:label-restriction/tet:label-end/" + + "tet:te-label/tet:technology" { case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } /* Under te-node-attributes/connectivity-matrices */ augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" - + "tet:label-restriction/tet:label-start/tet:te-label/" - + "tet:technology" { + + "tet:label-restrictions/tet:label-restriction/tet:label-start/" + + "tet:te-label/tet:technology" { when "../../../../../../../../nw:network-types/tet:te-topology/" + "ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" - + "tet:label-restriction/tet:label-end/tet:te-label/" - + "tet:technology" { + + "tet:label-restrictions/tet:label-restriction/tet:label-end/" + + "tet:te-label/tet:technology" { when "../../../../../../../../nw:network-types/tet:te-topology/" + "ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:underlay/tet:primary-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { @@ -7240,21 +7245,21 @@ description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:underlay/tet:backup-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { @@ -7262,21 +7267,21 @@ + "tet:te-topology/ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:path-properties/tet:path-route-objects/" + "tet:path-route-object/tet:type/" @@ -7285,115 +7290,115 @@ + "tet:te-topology/ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } /* Under te-node-attributes/.../connectivity-matrix */ augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:connectivity-matrix/tet:from/" - + "tet:label-restriction/tet:label-start/tet:te-label/" - + "tet:technology" { + + "tet:label-restrictions/tet:label-restriction/tet:label-start/" + + "tet:te-label/tet:technology" { when "../../../../../../../../../../nw:network-types/" + "tet:te-topology/ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:connectivity-matrix/tet:from/" - + "tet:label-restriction/tet:label-end/tet:te-label/" - + "tet:technology" { + + "tet:label-restrictions/tet:label-restriction/tet:label-end/" + + "tet:te-label/tet:technology" { when "../../../../../../../../../../nw:network-types/" + "tet:te-topology/ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:connectivity-matrix/tet:to/" - + "tet:label-restriction/tet:label-start/tet:te-label/" - + "tet:technology" { + + "tet:label-restrictions/tet:label-restriction/tet:label-start/" + + "tet:te-label/tet:technology" { when "../../../../../../../../../../nw:network-types/" + "tet:te-topology/ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:connectivity-matrix/tet:to/" - + "tet:label-restriction/tet:label-end/tet:te-label/" - + "tet:technology" { + + "tet:label-restrictions/tet:label-restriction/tet:label-end/" + + "tet:te-label/tet:technology" { when "../../../../../../../../../../nw:network-types/" + "tet:te-topology/ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:connectivity-matrix/" + "tet:underlay/tet:primary-path/tet:path-element/tet:type/" @@ -7402,21 +7407,21 @@ + "tet:te-topology/ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:connectivity-matrix/" + "tet:underlay/tet:backup-path/tet:path-element/tet:type/" @@ -7425,21 +7430,21 @@ + "tet:te-topology/ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:te-node-attributes/tet:connectivity-matrices/" + "tet:connectivity-matrix/" + "tet:path-properties/tet:path-route-objects/" @@ -7449,66 +7454,66 @@ + "tet:te-topology/ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } /* Under information-source-entry/connectivity-matrices */ augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" - + "tet:label-restriction/tet:label-start/tet:te-label/" - + "tet:technology" { + + "tet:label-restrictions/tet:label-restriction/tet:label-start/" + + "tet:te-label/tet:technology" { when "../../../../../../../../nw:network-types/tet:te-topology/" + "ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" - + "tet:label-restriction/tet:label-end/tet:te-label/" - + "tet:technology" { + + "tet:label-restrictions/tet:label-restriction/tet:label-end/" + + "tet:te-label/tet:technology" { when "../../../../../../../../nw:network-types/tet:te-topology/" + "ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:underlay/tet:primary-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { @@ -7516,21 +7521,21 @@ + "tet:te-topology/ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:underlay/tet:backup-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { @@ -7538,21 +7543,21 @@ + "tet:te-topology/ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:path-properties/tet:path-route-objects/" + "tet:path-route-object/tet:type/" @@ -7561,115 +7566,115 @@ + "tet:te-topology/ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } /* Under information-source-entry/.../connectivity-matrix */ augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:connectivity-matrix/tet:from/" - + "tet:label-restriction/tet:label-start/tet:te-label/" - + "tet:technology" { + + "tet:label-restrictions/tet:label-restriction/tet:label-start/" + + "tet:te-label/tet:technology" { when "../../../../../../../../../../nw:network-types/" + "tet:te-topology/ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:connectivity-matrix/tet:from/" - + "tet:label-restriction/tet:label-end/tet:te-label/" - + "tet:technology" { + + "tet:label-restrictions/tet:label-restriction/tet:label-end/" + + "tet:te-label/tet:technology" { when "../../../../../../../../../../nw:network-types/" + "tet:te-topology/ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:connectivity-matrix/tet:to/" - + "tet:label-restriction/tet:label-start/tet:te-label/" - + "tet:technology" { + + "tet:label-restrictions/tet:label-restriction/tet:label-start/" + + "tet:te-label/tet:technology" { when "../../../../../../../../../../nw:network-types/" + "tet:te-topology/ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:connectivity-matrix/tet:to/" - + "tet:label-restriction/tet:label-end/tet:te-label/" - + "tet:technology" { + + "tet:label-restrictions/tet:label-restriction/tet:label-end/" + + "tet:te-label/tet:technology" { when "../../../../../../../../../../nw:network-types/" + "tet:te-topology/ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:connectivity-matrix/" + "tet:underlay/tet:primary-path/tet:path-element/tet:type/" @@ -7678,21 +7683,21 @@ + "tet:te-topology/ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:connectivity-matrix/" + "tet:underlay/tet:backup-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { @@ -7700,21 +7705,21 @@ + "tet:te-topology/ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:information-source-entry/tet:connectivity-matrices/" + "tet:connectivity-matrix/" + "tet:path-properties/tet:path-route-objects/" @@ -7724,67 +7729,67 @@ + "tet:te-topology/ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } /* Under tunnel-termination-point/local-link-connectivities */ augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:tunnel-termination-point/tet:local-link-connectivities/" - + "tet:label-restriction/tet:label-start/tet:te-label/" - + "tet:technology" { + + "tet:label-restrictions/tet:label-restriction/tet:label-start/" + + "tet:te-label/tet:technology" { when "../../../../../../../../nw:network-types/tet:te-topology/" + "ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:tunnel-termination-point/tet:local-link-connectivities/" - + "tet:label-restriction/tet:label-end/tet:te-label/" - + "tet:technology" { + + "tet:label-restrictions/tet:label-restriction/tet:label-end/" + + "tet:te-label/tet:technology" { when "../../../../../../../../nw:network-types/tet:te-topology/" + "ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:tunnel-termination-point/tet:local-link-connectivities/" + "tet:underlay/tet:primary-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { @@ -7792,21 +7797,21 @@ + "tet:te-topology/ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:tunnel-termination-point/tet:local-link-connectivities/" + "tet:underlay/tet:backup-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { @@ -7814,21 +7819,21 @@ + "tet:te-topology/ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:tunnel-termination-point/tet:local-link-connectivities/" + "tet:path-properties/tet:path-route-objects/" + "tet:path-route-object/tet:type/" @@ -7837,69 +7842,69 @@ + "tet:te-topology/ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } /* Under tunnel-termination-point/.../local-link-connectivity */ augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:tunnel-termination-point/tet:local-link-connectivities/" + "tet:local-link-connectivity/" - + "tet:label-restriction/tet:label-start/tet:te-label/" - + "tet:technology" { + + "tet:label-restrictions/tet:label-restriction/tet:label-start/" + + "tet:te-label/tet:technology" { when "../../../../../../../../../nw:network-types/" + "tet:te-topology/ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:tunnel-termination-point/tet:local-link-connectivities/" + "tet:local-link-connectivity/" - + "tet:label-restriction/tet:label-end/tet:te-label/" - + "tet:technology" { + + "tet:label-restrictions/tet:label-restriction/tet:label-end/" + + "tet:te-label/tet:technology" { when "../../../../../../../../../nw:network-types/" + "tet:te-topology/ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:tunnel-termination-point/tet:local-link-connectivities/" + "tet:local-link-connectivity/" @@ -7909,21 +7914,21 @@ + "tet:te-topology/ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:tunnel-termination-point/tet:local-link-connectivities/" + "tet:local-link-connectivity/" + "tet:underlay/tet:backup-path/tet:path-element/tet:type/" @@ -7932,21 +7937,21 @@ + "tet:te-topology/ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } augment "/nw:networks/nw:network/nw:node/tet:te/" + "tet:tunnel-termination-point/tet:local-link-connectivities/" + "tet:local-link-connectivity/" + "tet:path-properties/tet:path-route-objects/" @@ -7956,67 +7961,67 @@ + "tet:te-topology/ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } /* Under te-link-attributes */ augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:te-link-attributes/" - + "tet:label-restriction/tet:label-start/tet:te-label/" - + "tet:technology" { + + "tet:label-restrictions/tet:label-restriction/tet:label-start/" + + "tet:te-label/tet:technology" { when "../../../../../../../nw:network-types/" + "tet:te-topology/ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:te-link-attributes/" - + "tet:label-restriction/tet:label-end/tet:te-label/" - + "tet:technology" { + + "tet:label-restrictions/tet:label-restriction/tet:label-end/" + + "tet:te-label/tet:technology" { when "../../../../../../../nw:network-types/" + "tet:te-topology/ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:te-link-attributes/" + "tet:underlay/tet:primary-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { @@ -8024,21 +8029,21 @@ + "tet:te-topology/ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:te-link-attributes/" + "tet:underlay/tet:backup-path/tet:path-element/tet:type/" + "tet:label/tet:label-hop/tet:te-label/tet:technology" { @@ -8046,66 +8051,66 @@ + "tet:te-topology/ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } /* Under te-link information-source-entry */ augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:information-source-entry/" - + "tet:label-restriction/tet:label-start/tet:te-label/" - + "tet:technology" { + + "tet:label-restrictions/tet:label-restriction/tet:label-start/" + + "tet:te-label/tet:technology" { when "../../../../../../../nw:network-types/" + "tet:te-topology/ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } augment "/nw:networks/nw:network/nt:link/tet:te/" + "tet:information-source-entry/" - + "tet:label-restriction/tet:label-end/tet:te-label/" - + "tet:technology" { + + "tet:label-restrictions/tet:label-restriction/tet:label-end/" + + "tet:te-label/tet:technology" { when "../../../../../../../nw:network-types/" + "tet:te-topology/ex-topo:example-topology" { description "Augmentation parameters apply only for networks with example topology type."; } case "example" { container example { description "Attributes for example technology."; leaf label-1 { type uint32; - description "Attribute 11 for example technology."; + description "Label 1 for example technology."; } } } description "Augment TE label."; } } Contributors