TEAS Working GroupX.Xufeng LiuInternet-DraftInternet Draft Ericsson Intended status: Standards TrackI.Igor BryskinExpires: November 08, 2015ADVA Optical NetworkingV.Vishnu Pavan Beeram Juniper NetworksT.Tarek Saad Cisco SystemsInc. H.Inc Himanshu Shah CienaMay 08,Oscar Gonzalez De Dios Telefonica Expires: January 6, 2016 July 6, 2015 YANG Data Model for TE Topologiesdraft-ietf-teas-yang-te-topo-00 Abstract This document defines a YANG data model for representing and manipulating TE Topologies.draft-ietf-teas-yang-te-topo-01 Status ofThisthis 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).(IETF), its areas, and its working groups. Note that other groups may also distribute working documents asInternet-Drafts. The list of currentInternet-Drafts is at http://datatracker.ietf.org/drafts/current/.Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." 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 onNovember 08, 2015.January 6, 2016. Copyright Notice Copyright (c) 2015 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 carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Abstract This document defines a YANG data model for representing, retrieving and manipulating 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]. Table of Contents 1.Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2Introduction...................................................3 1.1. Terminology...............................................3 1.2. Tree Structure -Legend . . . . . . . . . . . . . . . . . 2 1.2.Legend...................................4 1.3. Prefixes in Data NodeNames . . . . . . . . . . . . . . . 3 1.3. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4Names...............................4 2.Design Considerations . . . . . . . . . . . . . . . . . . . . 4 2.1.Characterizing TE Topologies...................................5 3. Model Applicability............................................6 3.1. Native TE Topologies......................................6 3.2. Customized TE Topologies..................................8 4. Modeling Considerations.......................................10 4.1. Generic extensible Model.................................10 4.2. Model. . . . . . . . . . . . . . . . 4 2.1.1.Structure..........................................10 4.3. Topology Identifiers.....................................11 4.4. Generic TE LinkAttributes . . . . . . . . . . . . . 4 2.1.2.Attributes...............................12 4.5. Generic TE NodeAttributes . . . . . . . . . . . . . 4 2.1.3.Attributes...............................12 4.6. TED InformationSources . . . . . . . . . . . . . . . 4 2.2.Sources..................................13 4.7. Overlay/UnderlayRelationship . . . . . . . . . . . . . . 5 2.3.Relationship............................14 4.8. SchedulingParameters . . . . . . . . . . . . . . . . . . 5 2.4. Abstract TE Topologies . . . . . . . . . . . . . . . . . 5 2.5.Parameters....................................15 4.9. Templates................................................15 4.10. Notifications...........................................16 4.11. OpenItems . . . . . . . . . . . . . . . . . . . . . . . 6 3.Items..............................................17 5. TreeStructure . . . . . . . . . . . . . . . . . . . . . . . 6 3.1.Structure................................................17 6. TE Topology YangModule . . . . . . . . . . . . . . . . . 29 4.Module.......................................42 7. Security Considerations.......................................78 8. IANA Considerations...........................................78 9. References....................................................78 9.1. NormativeReferences . . . . . . . . . . . . . . . . . . . . 49 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 49References.....................................78 9.2. Informative References...................................79 10. Acknowledgments..............................................79 1. IntroductionYANG [RFC6020] a data definition language that was introduced to define the contentsThe Traffic Engineering Database (TED) is an essential component ofa conceptual data storeTraffic Engineered (TE) systems thatallows networked devices to be managed using NETCONF [RFC6241]. YANGare based on MPLS-TE [RFC2702] and GMPLS [RFC3945]. The TED isproving relevant beyond its initial confines, as bindings to other interfaces (e.g. ReST)a collection of all TE information about all TE nodes andencoding other than XML (e.g. JSON) are being defined. Furthermore, YANG data models can be used asTE links in thebasisnetwork. The TE Topology is a schematic arrangement ofimplementation for other interface, such as CLITE nodes andprogrammatic APIs.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 path computational algorithms are run to compute Traffic Engineered Paths (TE Paths). This document defines a YANG [RFC6020] 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.Tree Structure - Legend A simplified graphical representation ofTerminology TED: The Traffic Engineering Database is a collection of all TE information about all TE nodes and TE links in a given network. TE-Topology: The TE Topology is a schematic arrangement of TE nodes 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. 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. 1.2. Tree Structure - Legend A simplified graphical representation of the data model is presented in Section35 of this document. The following notations are used for the YANG model data tree representation. <status> <flags> <name> <opts> <type> <status> is one of: + for current x for deprecated o for obsolete <flags> is one of: rw for read-write configuration data ro for read-only non-configuration data -x for execution rpcs -n for notifications <name> is the name of the node If the node is augmented into the tree from another module, its name is printed as <prefix>:<name> <opts> is one of: ? for an optional leaf or node ! for a presence container * for a leaf-list or list Brackets [<keys>] for a list's keys Curly braces {<condition>} for optional feature that make node conditional Colon : for marking case nodes Ellipses ("...") subtree contents not shown Parentheses enclose choice and case nodes, and case nodes are also marked with a colon (":"). <type> is the name of the type for leafs and leaf-lists.1.2.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] | +--------+-----------------+-----------+ Table 1: Prefixes and corresponding YANG modules1.3. Terminology In this document, the key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted as described in BCP 14, RFC 2119 [RFC2119].2.Design Considerations 2.1. Generic extensible Model TheCharacterizing TETopologyTopologies The data model proposedinby this documentis meant to be technology agnostic. Other technology specifictakes the following characteristics of TE Topologies into account: - TE Topologymodels can augment and useis an abstract control-plane representation of thebuilding blocks provided bydata-plane topology. Hence attributes specific to theproposed model. 2.1.1. Genericdata-plane must make their way into the corresponding TELink AttributesTopology modeling. Themodel covers the definitions for genericTELink attributesTopology comprises of dynamic auto-discovered data (data that may change frequently -bandwidth, admin groups, SRLGs,example: unreserved bandwidth available on data-plane links) as well as fairly static data (data that rarely changes- examples: layer network identification, switchingcapabilities,and adaptation capabilities and limitations, fate sharing, administrative colors) associated with data-plane nodes and links. It is possible for a single TEmetric extensions etc. 2.1.2. GenericTopology to encompass TENode Attributes The model covers the definitions for genericinformation at multiple switching layers. - TENode attributes like connectivity matrix. +--rw connectivity-matrix* [id] +--rw id uint32 +--rw from-link +--rw topo-ref? leafref +--rw node-ref? leafref +--rw link-end-ref? leafref +--rw to-link +--rw topo-ref? leafref +--rw node-ref? leafref +--rw link-end-ref? leafref +--rw is-allowed? Boolean 2.1.3. TEDTopologies are protocol independent. InformationSources The model allows each TEabout topologicalelementelements 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 tohave multiplethe routing topology (topology constructed based on routing adjacencies) in a given TEinformation sources (OSPF-TE, ISIS-TE, BGP-LS, User-Configured, Other).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. - Each TE Topological element has an information sourceisassociated witha credibility preference to indicate precedence. The model captures overlayit. In some scenarios, there could be more than one information source associated with each topological element. - TE Topologies can be hierarchical. Each node and link of a given TE Topology can be associated with respective underlayrelationship fortopology. This means that each node and link of a given TEnodes/ links. For exampleTopology can be associated with an independent stack of supporting TE Topologies. -in networks where multipleTE Topologiesare built hierarchically, this model allowscan be customized. TE topologies of a given network presented by theusernetwork provider tostart fromits 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 aspecific topological element in the top mostcustomized topologyand traverse all the way down(as presented to thesupporting topological elementsclient) and provider's native topology (as known in its entirety to thebottom most topology. 2.2. Overlay/Underlay Relationship +--rw node* [te-node-id] : +--rw te-node-attributes : +--rw underlay-topology? leafref {te-topology-hierarchy}? +--rw link* [source-te-node-id source-te-link-id dest-te-node-id dest-te-link-id] : +--rw te-link-attributes +--rw underlay! {te-topology-hierarchy}? +--rw underlay-path : +--rw underlay-backup-path : +--rw underlay-protection-type? uint16 +--rw underlay-trail-src : +--rw underlay-trail-des : 2.3. Scheduling Parametersprovider itself) could be captured as hierarchical (overlay-underlay), but otherwise the two topologies are decoupled from each other. 3. Model Applicability 3.1. Native TE Topologies The modelallows time scheduling parameters todiscussed in this draft can bespecified for each topological element. These parameters allow the provider to present different topological viewsused tothe client at different time slots. +--rw schedules* [schedule-id]represent and retrieve native TE topologies on a given TE system. +---+ +---+ +---+ +---+ +---+ | R1|-------| R2|--------| R3|---------| R4|---------| R5| +---+ +---+ +---+ +---+ +---+ | / \ / \ / | / \ / \ / | / \ / \ / | / \ / \ / | / \ / \ / +---+ +---+ +---+ +---+ | R6|-------------| R7| | R8|---------| R9| +---+ +---+ +---+ +---+ Figure 1a: Example Network Topology --------------- |+--rw schedule-id uint32Native |+--rw start? yang:date-and-time|+--rw schedule-duration? string[ ] TE Node |+--rw repeat-interval? string 2.4. AbstractTE-Topology | | +++ TE Link --------------- o-------------- __________________ [R1] ++++ [R2] ++++ [R3] ++++ [R4] ++++ [R5] + + + + + + + + + + + + + + ++ ++ [R6] +++++++++ [R7] [R8] ++++ [R9] Figure 1b: Native TETopologies The model allows the provider to present the network in abstract terms on per client basis and facilitates the notion of "TETopology asa service". These topologies are typically decoupled fromseen on Node R3 Consider theactualnetwork topologyanddepicted in Figure 1a (R1 .. R9 aresupposed to be fully comprehensible by the clients and contain sufficient information for the client path computers to select service paths according to the client policies. The model also allows the client to request changesnodes representing routers). An implementation MAY choose tothe abstractconstruct a native TE Topologythat is presented to itusing all nodes andthus manipulate it. 2.5. Open Items o Relationship with "generic network topology" model: The generic network topology building blocks are discussedlinks present in[YANG-NET-TOPO]. This version of the document does not use any of those building blocks. The authors would like to explorethepossibility of doing thatgiven TED as depicted infuture revisions of this document. o Incremental notifications:Figure 1b. The data model proposed in thisversion does not cover incremental notifications. The authors intenddocument can be used toaddretrieve/represent thisin future revisions of the document. 3. Tree Structure module: ietf-te-topology +--rw te-topologies | +--rw topology* [te-topology-id] | | +--rw te-topology-id te-topology-id | | +--rw topology-types | | | +--rw te-topology!TE topology. : TE info distributed via ISIS-TE : TE info distributed via OSPF-TE : +---+ +---+ +---+ +---+ +---+ | R1|-------| R2|--------| R3|---------| R4|---------| R5| +---+ +---+ +---+ +---+ +---+ | / : \ / \ / |+--rw node* [te-node-id]/ : \ / \ / | / : \ / \ / | / : \ / \ / |+--rw te-node-id te-node-id/ : \ / \ / +---+ +---+ : +---+ +---+ | R6|-------------| R7| : | R8|---------| R9| +---+ +---+ : +---+ +---+ : Figure 2a: Example Network Topology ----------------------- : ----------------------- |Native TE Topology |+--rw te-node-template? leafref: |Native TE Topology | |Info-Source: ISIS-TE | : |Info-Source: OSPF-TE |+--rw te-node-attributes----------------------- : ----------------------- : [R1] ++++ [R2] ++++ [R3] : [R3'] ++++ [R4] ++++ [R5] + + : + + + + + + : + + + + + + : ++ ++ [R6] +++++++++ [R7] : [R8] ++++ [R9] Figure 2b: Native TE Topologies as seen on Node R3 Consider the case of the topology being split in a way that some nodes participate in OSPF-TE while others participate in ISIS-TE (Figure 2a). An implementation MAY choose to construct separate TE Topologies based on the information source. The native TE Topologies constructed using only nodes and links that were learnt via a specific information source are depicted in Figure 2b. The data model proposed in this document can be used to retrieve/represent these TE topologies. Similarly, the data model can be used to represent/retrieve a TE Topology that is constructed using only nodes and links that belong to a particular technology layer. The data model is flexible enough to retrieve and represent many such native TE Topologies. 3.2. Customized TE Topologies The model discussed in this draft can be used to represent, retrieve and manipulate customized TE Topologies. The model allows the provider to present the network in abstract TE Terms on a per client basis. These customized topologies contain sufficient information for the path computing client to select paths according to its policies. | +---+ /-\ | |+--rw schedules* [schedule-id]| Router ( ) WDM | +---+ Node \-/ node | o----------------------------_____ __ +---+ /-\ /-\ /-\ +---+ |+--rw schedule-id uint32R1|-------( A )--------( C )---------( E )---------| R3| +---+ \-/ \-/ \-/ +---+ / \ / \ / \ / \ / \ / \ / \ / \ / \ / \ +---+ /-\ /-\ /-\ +---+ | R2|---------( B )---------( D )---------( F )---------| R4| +---+ \-/ \-/ \-/ +---+ Figure 3: Example packet optical topology Consider the network topology depicted in Figure 3. This is a typical packet optical transport deployment scenario where the WDM layer network domain serves as a Server Network Domain providing transport connectivity to the packet layer network Domain (Client Network Domain). Nodes R1, R2, R3 and R4 are IP routers that are connected to an Optical WDM transport network. A, B, C, D, E and F are WDM nodes that constitute the Server Network Domain. | ***** B-F WDM Path | @@@@@ B-E WDM Path | $$$$$ A-E WDM Path o--------------------_ +---+ /-\ $$$$$$$$ /-\ $$$$$$$$$ /-\ +---+ | R1|-------( A )--------( C )---------( E )---------| R3| +---+ \-/ @\-/ @@@@@@@@@ \-/ +---+ @/ \ / \ @/ \ / \ @/ \ / \ @/ \ / \ @/ \ / \ +---+ /-\ ********* /-\ ********* /-\ +---+ | R2|---------( B )---------( D )---------( F )---------| R4| +---+ \-/ \-/ \-/ +---+ Figure 4a: Paths within the provider domain ++++++++ [A] ++++++++++++++++++++ [E] +++++++++ +++++ ++++ ++++ ++++ ++++ ++++++++ [B] ++++++++++++++++++++ [F] +++++++++ Figure 4b: Customized TE Topology provided to the Client [R1] ++++++++ [A] ++++++++++++++++++++ [E] +++++++++ [R3] +++++ ++++ ++++ ++++ ++++ [R2] ++++++++ [B] ++++++++++++++++++++ [F] +++++++++ [R4] Figure 4c: Customized TE Topology merged with the Client's Native TE Topology The goal here is to augment the Client TE Topology with a customized TE Topology provided by the WDM network. Given the availability of the paths A-E, B-F and B-E (Figure 4a), a customized TE Topology as depicted in Figure 4b is provided to the Client. This customized TE Topology is merged with the Client's Native TE Topology and the resulting topology is depicted in Figure 4c. The data model proposed in this document can be used to retrieve/represent/manipulate the customized TE Topology depicted in Figure 4b. 4. Modeling Considerations 4.1. Generic extensible Model The TE Topology model proposed in this document is meant to be technology agnostic. Other technology specific TE Topology models can augment and use the building blocks provided by the proposed model. +-------------------+ || +--rw start? yang:date-and-time |Generic | | TE Topology Model |+--rw schedule-duration? string+-------------------+ | +-------------+-------------+-------------+ | | |+--rw repeat-interval? string| V V V V +------------+ +------------+ | Technology |+--rw name? inet:domain-name| Technology | |+--rw signaling-address* inet:ip-addressSpecific | ...................... | Specific |+--rw flag* flag-type| TE Topology| | TE Topology| |+--rw is-abstract? booleanModel 1 | | Model n | +------------+ +------------+ Figure 5: Extending the generic model 4.2. Model Structure The high-level model structure proposed by this document is as shown below: +--rwunderlay-topology? leafref {te-topology-hierarchy}? | |te-topologies | +--rwte-link* [te-link-id]topology* [provider-id client-id te-topology-id] | | .......... | | +--rwte-link-id te-link-id | |node* [te-node-id] | |+--rw (stack-level)?| .......... | | |+--:(bundle)+--rw te-link* [te-link-id] | | | .......... | | +--rwbundled-links |link* [source-te-node-id source-te-link-id dest-te- node-id dest-te-link-id] | | | .......... | +--rwbundled-link* [sequence] | |node-template* [name] {template}? | | .......... | +--rwsequence uint32 |link-template* [name] {template}? | | .......... +--ro te-topologies-state +--ro topology* [provider-id client-id te-topology-id] | .......... +--ro node* [te-node-id] |+--rw te-link-ref? leafref| .......... | +--ro te-node-state | .......... +--ro link* [source-te-node-id source-te-link-id dest-te- node-id dest-te-link-id] |+--:(component)| .......... | +--ro te-link-state | .......... notifications: +---n te-node-event | .......... +---n te-link-event .......... 4.3. 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. +--rwcomponent-links |topology* [provider-id client-id te-topology-id] | +--rw provider-id te-global-id | +--rw client-id te-global-id | +--rwcomponent-link* [sequence]te-topology-id te-topology-id 4.4. 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 performance-metric-throttle {te-performance-metric}? | |+--rw sequence uint32.......... | +--rw administrative-group? te-types:admin-groups | +--rw max-link-bandwidth? decimal64 | +--rw max-resv-link-bandwidth? decimal64 | +--rwcomponent-link-ref? leafrefunreserved-bandwidth* [priority] | | .......... | +--rwconnectivity-matrix* [id]te-default-metric? uint32 | +--rw performance-metric {te-performance-metric}? | | .......... | +--rwid uint32link-protection-type? enumeration | +--rw interface-switching-capabilities* [switching-capability] | | .......... | +--rwfrom-linkte-srlgs | | .......... 4.5. Generic TE Node Attributes The model covers the definitions for generic TE Node attributes. The definition of a generic connectivity matrix is shown below: +--rw te-node-attributes | .......... | +--rw connectivity-matrix* [id] | +--rwtopo-ref? leafrefid uint32 | +--rw from-link | | +--rw provider-id-ref? leafref | | +--rwnode-ref?client-id-ref? leafref | ||+--rw topology-id-ref? leafref | | +--rwlink-end-ref?node-ref? leafref | ||+--rw link-end-ref? leafref | +--rw to-link | ||+--rw provider-id-ref? leafref | | +--rwtopo-ref?client-id-ref? leafref | ||+--rw topology-id-ref? leafref | | +--rw node-ref? leafref | || | |+--rw link-end-ref? leafref || | |+--rw is-allowed?boolean | |Boolean 4.6. TED Information Sources The model allows each TE topological element to have multiple TE information sources (OSPF-TE, ISIS-TE, BGP-LS, User-Configured, System-Processed, Other). Each information source is associated with a credibility preference to indicate precedence. In scenarios where a customized TE Topology is merged into a Client's native TE Topology, the merged topological elements would point to the corresponding customized TE Topology as its information source. +--ro te-topologies-state +--ro topology* [provider-id client-id te-topology-id] |+--rw ted.......... +--ro node* [te-node-id] | .......... | +--ro te-node-state |+--rw te-router-id-ipv4? inet:ipv4-address+--ro information-source? enumeration | +--ro information-source-state | +--ro credibility-preference? uint16 |+--rw te-router-id-ipv6? inet:ipv6-address+--ro topology | | +--ro provider-id-ref? leafref |+--rw ipv4-local-address* [ipv4-prefix]| +--ro client-id-ref? leafref | | +--ro topology-id-ref? leafref |+--rw ipv4-prefix inet:ipv4-prefix+--ro routing-instance? string +--ro te-topologies-state +--ro topology* [provider-id client-id te-topology-id] | .......... +--ro link* [source-te-node-id source-te-link-id dest-te- node-id dest-te-link-id] | .......... |+--rw ipv6-local-address* [ipv6-prefix]+--ro te-link-state | +--ro information-source? enumeration | +--ro information-source-state | |+--rw ipv6-prefix inet:ipv6-prefix+--ro credibility-preference? uint16 | | +--ro topology | |+--rw prefix-option? uint8| +--ro provider-id-ref? leafref | |+--rw pcc-capabilities? pcc-capabilities| +--ro client-id-ref? leafref |+--rw link* [source-te-node-id source-te-link-id dest-te-node-id dest-te-link-id]| |+--rw source-te-node-id+--ro topology-id-ref? leafref | |+--rw source-te-link-id leafref+--ro routing-instance? string | +--ro alt-information-sources* [information-source] |+--rw dest-te-node-id leafref | | +--rw dest-te-link-id leafref | | +--rw te-link-template? leafref+--ro information-source enumeration | +--ro information-source-state |+--rw te-link-attributes| +--ro credibility-preference? uint16 |+--rw schedules* [schedule-id]| +--ro topology | |+--rw schedule-id uint32| +--ro provider-id-ref? leafref | |+--rw start? yang:date-and-time| +--ro client-id-ref? leafref | |+--rw schedule-duration? string| +--ro topology-id-ref? leafref | |+--rw repeat-interval?+--ro routing-instance? string | | .......... 4.7. Overlay/Underlay Relationship The model captures overlay and underlay relationship for TE nodes/links. For example - in networks where multiple TE Topologies are built hierarchically, this model allows the user to start from a specific topological element in the top most topology and traverse all the way down to the supporting topological elements in the bottom most topology. This relationship is captured via the "underlay-topology" field for the node and via the "underlay" field for the link. The use of these fields is optional and this functionality is tagged as a "feature" ("te-topology-hierarchy"). +--rwname? stringnode* [te-node-id] | .......... | +--rwflag* flag-typete-node-attributes | |+--rw is-abstract? boolean.......... | | +--rwunderlay!underlay-topology {te-topology-hierarchy}? | | | +--rwunderlay-path | | | | +--rw topology-id?provider-id-ref? leafref | | || +--rw path-element* [path-element-id] | | | |+--rwpath-element-id uint32 |client-id-ref? leafref | | | +--rwloose? boolean | | | |topology-id-ref? leafref +--rw(element-type)? | | | | +--:(numbered-link) | | |link* [source-te-node-id source-te-link-id dest-te-node-id dest-te-link-id] | .......... | +--rwlink-ip-address? inet:ip-address | | | | +--:(unnumbered-link) |te-link-attributes | | ....... | | +--rwlink-node-id? uint32 | |underlay! {te-topology-hierarchy}? | | | +--rwte-link-id? uint32 | | | | +--:(node) |underlay-primary-path | | | | +--rwte-node-id? uint32 | | | | +--:(label) | | |provider-id-ref? leafref |+--rw label? uint32| | | +--rwunderlay-backup-pathclient-id-ref? leafref | | | | +--rwtopology-id?topology-id-ref? leafref | | | | +--rw path-element* [path-element-id] | | | |+--rw path-element-id uint32 |.......... | | | +--rwloose? booleanunderlay-backup-path* [index] | | | | +--rw(element-type)? | | | | +--:(numbered-link) |index uint32 | | | | +--rwlink-ip-address? inet:ip-address | | | | +--:(unnumbered-link) |provider-id-ref? leafref | | | | +--rwlink-node-id? uint32 |client-id-ref? leafref | | | | +--rwte-link-id? uint32 | | | | +--:(node) |topology-id-ref? leafref | | | | +--rwte-node-id? uint32 | | | | +--:(label)path-element* [path-element-id] | | | |+--rw label? uint32.......... | | | +--rw underlay-protection-type? uint16 | | | +--rw underlay-trail-src | | || +--rw topo-ref? leafref |.......... | | | +--rwnode-ref? leafref | |underlay-trail-des | |+--rw link-end-ref? leafref | | | +--rw underlay-trail-des | | | +--rw topo-ref? leafref | | | +--rw node-ref? leafref | | | +--rw link-end-ref? leafref | | +--rw ted | | +--rw admin-status? enumeration | | +--rw oper-status? enumeration | | +--rw area-id? binary || .......... 4.8. 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 and this functionality is tagged as a "feature" ("configuration-schedule"). [Editor's Note: The notion of "scheduling parameters" has wider applicability. The expectation is that this will eventually be discussed in a separate document.] +--rwperformance-metric-throttle {te-performance-metric}? | |schedules* [schedule-id] {configuration-schedule}? | +--rwunidirectional-delay-offset?schedule-id uint32 || |+--rwmeasure-interval? uint32 | |start? yang:date-and-time | +--rwadvertisement-interval? uint32 | |schedule-duration? string | +--rwsuppression-interval? uint32 | | |repeat-interval? string 4.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"). +--rwthreshold-out | |topology* [provider-id client-id te-topology-id] | ........... | +--rwunidirectional-delay? uint32 | |node* [te-node-id] | | +--rwunidirectional-min-delay? uint32 |te-node-template? leafref {template}? | | .......... | +--rwunidirectional-max-delay? uint32 | | |link* [source-te-node-id source-te-link-id dest-te-node- id dest-te-link-id] | +--rwunidirectional-delay-variation? uint32 | |te-link-template? leafref {template}? | .......... | +--rwunidirectional-packet-loss? decimal64 | | |node-template* [name] {template}? | +--rwunidirectional-residual-bandwidth? decimal64 | | |name te-template-name | +--rwunidirectional-available-bandwidth? decimal64 | | |priority? uint16 | +--rwunidirectional-utilized-bandwidth? decimal64 | |reference-change-policy? enumeration | +--rwthreshold-in | | |te-node-template* leafref | +--rwunidirectional-delay? uint32 | | |te-node-attributes | .......... +--rwunidirectional-min-delay? uint32 | | | |link-template* [name] {template}? +--rwunidirectional-max-delay? uint32 | | | |name te-template-name +--rwunidirectional-delay-variation? uint32 | | | |priority? uint16 +--rwunidirectional-packet-loss? decimal64 | | | |reference-change-policy? enumeration +--rwunidirectional-residual-bandwidth? decimal64 |te-link-template* leafref +--rw te-link-attributes .......... A template can be constructed using multiple other templates. 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 node 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.] 4.10. Notifications Notifications are a key component of any topology data model. [YANG-PUSH] defines 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. The authors would like to recommend the use of this mechanism for the TE-Topology notifications. They would also like to suggest the following extensions to [YANG-PUSH] - Specify specific entities that will trigger the push notifications. These entities can be specified by xpath, like the way a filter is specified. - Specify or limit the triggering event type, e.g. "add", "delete", "modify", or "all". The system sends the push notifications only when such events happen on the triggering entities. - Have an option to request either "incremental" or "full" notifications for an entity. For "incremental", the notification will contain only the changed attributes. 4.11. Open Items - Augmenting [YANG-NET-TOPO]: The generic network topology building blocks are discussed in [YANG-NET-TOPO]. This version of the document does not use any of those constructs. The next revision of this document should augment these constructs. - Coordinating changes to [YANG-PUSH]: The changes to [YANG-PUSH] discussed in Section 4.10 will need to be coordinated with the authors of that draft. 5. Tree Structure module: ietf-te-topology +--rw te-topologies | +--rw topology* [provider-id client-id te-topology-id] | | +--rwunidirectional-available-bandwidth? decimal64provider-id te-global-id | | +--rw client-id te-global-id | | +--rwunidirectional-utilized-bandwidth? decimal64 |te-topology-id te-topology-id | | +--rwthreshold-accelerated-advertisementschedules* [schedule-id] {configuration-schedule}? | | | +--rwunidirectional-delay?schedule-id uint32 | | | +--rwunidirectional-min-delay? uint32start? yang:date-and-time | | | +--rwunidirectional-max-delay? uint32schedule-duration? string | | | +--rwunidirectional-delay-variation? uint32 |repeat-interval? string | | +--rwunidirectional-packet-loss? decimal64topology-types | | | +--rwunidirectional-residual-bandwidth? decimal64 |te-topology! | | +--rwunidirectional-available-bandwidth? decimal64node* [te-node-id] | | | +--rwunidirectional-utilized-bandwidth? decimal64te-node-id te-node-id | | | +--rwinformation-source? enumerationte-node-template? leafref {template}? | | | +--rwcredibility-preference? uint16te-node-attributes | |+--rw link-index? uint64| | +--rwadministrative-group* [sequence] |schedules* [schedule-id] {configuration- schedule}? | |+--rw sequence uint32| | | +--rwag-element?schedule-id uint32 | |+--rw max-link-bandwidth? decimal64| | | +--rwmax-resv-link-bandwidth? decimal64start? yang:date-and-time | |+--rw unreserved-bandwidth* [priority]| | | +--rwpriority uint8schedule-duration? string | | |+--rw bandwidth? decimal64| | +--rwte-default-metric? uint32 |repeat-interval? string |+--rw performance-metric {te-performance-metric}?| | | +--rwmeasurementname? inet:domain-name | | | | +--rwunidirectional-delay? uint32signaling-address* inet:ip-address | | | | +--rwunidirectional-min-delay? uint32flag* flag-type | | | | +--rwunidirectional-max-delay? uint32is-abstract? boolean | | | | +--rwunidirectional-delay-variation? uint32underlay-topology {te-topology-hierarchy}? | | | | | +--rwunidirectional-packet-loss? decimal64provider-id-ref? leafref | | | | | +--rwunidirectional-residual-bandwidth? decimal64client-id-ref? leafref | | | | | +--rwunidirectional-available-bandwidth? decimal64topology-id-ref? leafref | | | | +--rwunidirectional-utilized-bandwidth? decimal64connectivity-matrix* [id] | | | | +--rwnormalityid uint32 | | |+--rw unidirectional-delay? performance-metric-normality| +--rw from-link | |+--rw unidirectional-min-delay? performance-metric-normality| | | +--rwunidirectional-max-delay? performance-metric-normality |provider-id-ref? leafref | |+--rw unidirectional-delay-variation? performance-metric-normality| | | +--rwunidirectional-packet-loss? performance-metric-normality |client-id-ref? leafref | |+--rw unidirectional-residual-bandwidth? performance-metric-normality| | | +--rwunidirectional-available-bandwidth? performance-metric-normalitytopology-id-ref? leafref | | |+--rw unidirectional-utilized-bandwidth? performance-metric-normality| | +--rwlink-protection-type? enumerationnode-ref? leafref | |+--rw interface-switching-capabilities* [switching-capability]| | | +--rwswitching-capability ted:switching-capabilitieslink-end-ref? leafref | | | | +--rwencoding? ted:encoding-typeto-link | | | | | +--rwmax-lsp-bandwidth* [priority]provider-id-ref? leafref | | | | | +--rwpriority uint8client-id-ref? leafref | | | | | +--rwbandwidth? decimal64topology-id-ref? leafref | | | | | +--rwpacket-switch-capablenode-ref? leafref | | | | | +--rwminimum-lsp-bandwidth? decimal64link-end-ref? leafref | | | | +--rwinterface-mtu? uint16is-allowed? boolean | | | +--rwtime-division-multiplex-capablete-link* [te-link-id] | | | +--rwminimum-lsp-bandwidth? decimal64te-link-id te-link-id | | | +--rwindication? enumeration(stack-level)? | | | +--:(bundle) | | | | +--rwsrlgbundled-links | | | | +--rwsrlg-values* [srlg-value]bundled-link* [sequence] | | | | +--rwsrlg-valuesequence uint32 | |+--rw alt-information-sources* [information-source]| | +--rwinformation-source enumerationte-link-ref? leafref | |+--rw credibility-preference? uint16| +--:(component) | | | +--rwlink-index? uint64component-links | | | +--rwadministrative-group*component-link* [sequence] | | | +--rw sequence uint32 | | | +--rwag-element? uint32component-link-ref? leafref | | +--rwmax-link-bandwidth? decimal64link* [source-te-node-id source-te-link-id dest-te- node-id dest-te-link-id] | | +--rwmax-resv-link-bandwidth? decimal64source-te-node-id leafref | | +--rwunreserved-bandwidth* [priority] |source-te-link-id leafref | | +--rwpriority uint8 |dest-te-node-id leafref | | +--rwbandwidth? decimal64dest-te-link-id leafref | | +--rwte-default-metric? uint32te-link-template? leafref {template}? | | +--rwperformance-metric {te-performance-metric}? |te-link-attributes | | +--rwmeasurement |schedules* [schedule-id] {configuration- schedule}? | | | +--rwunidirectional-delay?schedule-id uint32 | | ||+--rwunidirectional-min-delay? uint32 |start? yang:date-and-time | | | +--rwunidirectional-max-delay? uint32 |schedule-duration? string | | | +--rwunidirectional-delay-variation? uint32repeat-interval? string | | +--rw name? string | | +--rwunidirectional-packet-loss? decimal64flag* flag-type | | +--rw is-abstract? boolean | | +--rwunidirectional-residual-bandwidth? decimal64 |underlay! {te-topology-hierarchy}? | | | +--rwunidirectional-available-bandwidth? decimal64underlay-primary-path | | | | +--rwunidirectional-utilized-bandwidth? decimal64provider-id-ref? leafref | | | | +--rwnormalityclient-id-ref? leafref | | | | +--rwunidirectional-delay? performance-metric-normalitytopology-id-ref? leafref | | | | +--rwunidirectional-min-delay? performance-metric-normalitypath-element* [path-element-id] | | | | +--rwunidirectional-max-delay? performance-metric-normalitypath-element-id uint32 | | | | +--rwunidirectional-delay-variation? performance-metric-normality(type)? | | |+--rw unidirectional-packet-loss? performance-metric-normality| +--:(ipv4-address) | |+--rw unidirectional-residual-bandwidth? performance-metric-normality| | | +--rwunidirectional-available-bandwidth? performance-metric-normalityv4-address? inet:ipv4- address | | |+--rw unidirectional-utilized-bandwidth? performance-metric-normality| | +--rwlink-protection-type? enumerationv4-prefix-length? uint8 | |+--rw interface-switching-capabilities* [switching-capability]| | | +--rwswitching-capability ted:switching-capabilitiesv4-loose? boolean | | |+--rw encoding? ted:encoding-type| +--:(ipv6-address) | | | | | +--rwmax-lsp-bandwidth* [priority]v6-address? inet:ipv6- address | | | | | +--rwpriorityv6-prefix-length? uint8 | | | | | +--rwbandwidth? decimal64v6-loose? boolean | | |+--rw packet-switch-capable| +--:(as-number) | | | | | +--rwminimum-lsp-bandwidth? decimal64as-number? uint16 | | | |+--rw interface-mtu? uint16+--:(unnumbered-link) | | | | | +--rwtime-division-multiplex-capablerouter-id? inet:ip- address | | | | | +--rwminimum-lsp-bandwidth? decimal64interface-id? uint32 | | |+--rw indication? enumeration| +--:(label) | | | | +--rwsrlgvalue? uint32 | | | +--rwsrlg-values* [srlg-value]underlay-backup-path* [index] | | | | +--rwsrlg-valueindex uint32 | | | | +--rwnode-template* [name]provider-id-ref? leafref | | | | +--rwname te-template-nameclient-id-ref? leafref | | | | +--rwte-node-attributestopology-id-ref? leafref | | | | +--rwschedules* [schedule-id]path-element* [path-element-id] | | | | +--rwschedule-idpath-element-id uint32 | | | | +--rwstart? yang:date-and-time(type)? | | |+--rw schedule-duration? string| +--:(ipv4-address) | | |+--rw repeat-interval? string| | +--rwname? inet:domain-namev4-address? inet:ipv4- address | | |+--rw signaling-address* inet:ip-address| | +--rwflag* flag-typev4-prefix-length? uint8 | | | | | +--rwis-abstract?v4-loose? boolean | |+--rw underlay-topology? leafref {te-topology-hierarchy}?| |+--rw te-link* [te-link-id]+--:(ipv6-address) | | | | | +--rwte-link-id te-link-idv6-address? inet:ipv6- address | | |+--rw (stack-level)?| | +--rw v6-prefix-length? uint8 |+--:(bundle)| | | | +--rwbundled-linksv6-loose? boolean | | | |+--rw bundled-link* [sequence]+--:(as-number) | | | |+--rw sequence uint32| +--rw as-number? uint16 | | |+--rw te-link-ref? leafref| +--:(unnumbered-link) | |+--:(component)| | | +--rwcomponent-linksrouter-id? inet:ip- address | | | | | +--rwcomponent-link* [sequence]interface-id? uint32 | | | | +--:(label) | | | | +--rwsequencevalue? uint32 | | | +--rwcomponent-link-ref? leafrefunderlay-protection-type? uint16 | | | +--rwconnectivity-matrix* [id]underlay-trail-src | | | | +--rwid uint32provider-id-ref? leafref | | | | +--rwfrom-linkclient-id-ref? leafref | | | | +--rwtopo-ref?topology-id-ref? leafref | | | | +--rw node-ref? leafref | | | | +--rw link-end-ref? leafref | | | +--rwto-link |underlay-trail-des | | | +--rwtopo-ref?provider-id-ref? leafref | | ||+--rwnode-ref?client-id-ref? leafref | | ||+--rwlink-end-ref?topology-id-ref? leafref | | | +--rwis-allowed? booleannode-ref? leafref | | | +--rwtedlink-end-ref? leafref | | +--rwte-router-id-ipv4? inet:ipv4-addressadmin-status? enumeration | | +--rwte-router-id-ipv6? inet:ipv6-addressperformance-metric-throttle {te-performance- metric}? | | | +--rwipv4-local-address* [ipv4-prefix]unidirectional-delay-offset? uint32 | | | +--rwipv4-prefix inet:ipv4-prefixmeasure-interval? uint32 | | | +--rwipv6-local-address* [ipv6-prefix]advertisement-interval? uint32 | | | +--rwipv6-prefix inet:ipv6-prefixsuppression-interval? uint32 | | | +--rwprefix-option? uint8threshold-out | | |+--rw pcc-capabilities? pcc-capabilities| +--rwlink-template* [name] | +--rw name te-template-nameunidirectional-delay? uint32 |+--rw te-link-attributes|+--rw schedules* [schedule-id]| | +--rwschedule-idunidirectional-min-delay? uint32 | |+--rw start? yang:date-and-time | | +--rw schedule-duration? string| | +--rwrepeat-interval? stringunidirectional-max-delay? uint32 |+--rw name? string|+--rw flag* flag-type|+--rw is-abstract? boolean| +--rwunderlay! {te-topology-hierarchy}? |unidirectional-delay-variation? uint32 |+--rw underlay-path| | | +--rwtopology-id? leafref | |unidirectional-packet-loss? decimal64 |+--rw path-element* [path-element-id]| | | +--rwpath-element-id uint32 | |unidirectional-residual-bandwidth? decimal64 |+--rw loose? boolean| | | +--rw(element-type)? | | | +--:(numbered-link)unidirectional-available-bandwidth? decimal64 | | | | +--rwlink-ip-address? inet:ip-addressunidirectional-utilized-bandwidth? decimal64 | | |+--:(unnumbered-link)+--rw threshold-in | | | | +--rwlink-node-id?unidirectional-delay? uint32 | | | | +--rwte-link-id?unidirectional-min-delay? uint32 | | |+--:(node) | | || +--rwte-node-id?unidirectional-max-delay? uint32 | | |+--:(label) | || +--rwlabel?unidirectional-delay-variation? uint32 | |+--rw underlay-backup-path || | +--rwtopology-id? leafref | |unidirectional-packet-loss? decimal64 |+--rw path-element* [path-element-id]| | | +--rwpath-element-id uint32 | |unidirectional-residual-bandwidth? decimal64 |+--rw loose? boolean| | | +--rw(element-type)? | | | +--:(numbered-link)unidirectional-available-bandwidth? decimal64 | | | | +--rwlink-ip-address? inet:ip-address |unidirectional-utilized-bandwidth? decimal64 | |+--:(unnumbered-link)| +--rw threshold-accelerated-advertisement | | | +--rwlink-node-id?unidirectional-delay? uint32 | | ||+--rwte-link-id?unidirectional-min-delay? uint32 | | |+--:(node) | | | |+--rwte-node-id?unidirectional-max-delay? uint32 | | |+--:(label) | | |+--rwlabel?unidirectional-delay-variation? uint32 | |+--rw underlay-protection-type? uint16 || +--rwunderlay-trail-srcunidirectional-packet-loss? decimal64 | | | +--rwtopo-ref? leafrefunidirectional-residual-bandwidth? decimal64 | | | +--rwnode-ref? leafrefunidirectional-available-bandwidth? decimal64 | | | +--rwlink-end-ref? leafrefunidirectional-utilized-bandwidth? decimal64 | | +--rwunderlay-trail-deslink-index? uint64 | | +--rwtopo-ref? leafrefadministrative-group? te- types:admin-groups | | +--rwnode-ref? leafrefmax-link-bandwidth? decimal64 | | +--rwlink-end-ref? leafrefmax-resv-link-bandwidth? decimal64 |+--rw ted| +--rwadmin-status? enumerationunreserved-bandwidth* [priority] |+--rw oper-status? enumeration|+--rw area-id? binary| +--rwperformance-metric-throttle {te-performance-metric}? |priority uint8 |+--rw unidirectional-delay-offset? uint32| | +--rwmeasure-interval? uint32bandwidth? decimal64 | | +--rwadvertisement-interval?te-default-metric? uint32 | | +--rwsuppression-interval? uint32performance-metric {te-performance-metric}? | | | +--rwthreshold-outmeasurement | | | | +--rw unidirectional-delay? uint32 | | | | +--rw unidirectional-min-delay? uint32 | | | | +--rw unidirectional-max-delay? uint32 | | | | +--rw unidirectional-delay-variation? uint32 | | | | +--rw unidirectional-packet-loss? decimal64 | | | | +--rw unidirectional-residual-bandwidth? decimal64 | | | | +--rw unidirectional-available-bandwidth? decimal64 | | | | +--rw unidirectional-utilized-bandwidth? decimal64 | | | +--rwthreshold-innormality | | | +--rw unidirectional-delay?uint32performance-metric-normality | | | +--rw unidirectional-min-delay?uint32performance-metric-normality | | | +--rw unidirectional-max-delay?uint32performance-metric-normality | | | +--rw unidirectional-delay-variation?uint32performance-metric-normality | | | +--rw unidirectional-packet-loss?decimal64performance-metric-normality | | | +--rw unidirectional-residual-bandwidth?decimal64performance-metric-normality | | | +--rw unidirectional-available-bandwidth?decimal64performance-metric-normality | | | +--rw unidirectional-utilized-bandwidth?decimal64performance-metric-normality | | +--rwthreshold-accelerated-advertisementlink-protection-type? enumeration | | +--rwunidirectional-delay? uint32interface-switching-capabilities* [switching- capability] | | | +--rwunidirectional-min-delay? uint32switching-capability identityref | | | +--rwunidirectional-max-delay? uint32encoding? identityref | | | +--rwunidirectional-delay-variation? uint32max-lsp-bandwidth* [priority] | |+--rw unidirectional-packet-loss? decimal64| | +--rwunidirectional-residual-bandwidth? decimal64priority uint8 | |+--rw unidirectional-available-bandwidth? decimal64| | +--rwunidirectional-utilized-bandwidth?bandwidth? decimal64 |+--rw information-source? enumeration|+--rw credibility-preference? uint16| +--rwlink-index? uint64packet-switch-capable |+--rw administrative-group* [sequence]| |+--rw sequence uint32 | | +--rw ag-element? uint32| +--rwmax-link-bandwidth?minimum-lsp-bandwidth? decimal64 |+--rw max-resv-link-bandwidth? decimal64|+--rw unreserved-bandwidth* [priority]| | +--rwpriority uint8interface-mtu? uint16 | |+--rw bandwidth? decimal64| +--rwte-default-metric? uint32time-division-multiplex-capable |+--rw performance-metric {te-performance-metric}?| | +--rwmeasurementminimum-lsp-bandwidth? decimal64 | | | +--rwunidirectional-delay? uint32 |indication? enumeration | | +--rwunidirectional-min-delay? uint32 |te-srlgs | | +--rwunidirectional-max-delay? uint32values* te-types:srlg | +--rw node-template* [name] {template}? | | +--rwunidirectional-delay-variation? uint32 |name te-template-name | | +--rwunidirectional-packet-loss? decimal64 |priority? uint16 | | +--rwunidirectional-residual-bandwidth? decimal64reference-change-policy? enumeration | | +--rw te-node-template* leafref | | +--rwunidirectional-available-bandwidth? decimal64te-node-attributes | | | +--rwunidirectional-utilized-bandwidth? decimal64schedules* [schedule-id] {configuration-schedule}? | |+--rw normality| | +--rwunidirectional-delay? performance-metric-normalityschedule-id uint32 | |+--rw unidirectional-min-delay? performance-metric-normality| | +--rwunidirectional-max-delay? performance-metric-normalitystart? yang:date-and-time | |+--rw unidirectional-delay-variation? performance-metric-normality| | +--rwunidirectional-packet-loss? performance-metric-normalityschedule-duration? string | |+--rw unidirectional-residual-bandwidth? performance-metric-normality| | +--rwunidirectional-available-bandwidth? performance-metric-normalityrepeat-interval? string | |+--rw unidirectional-utilized-bandwidth? performance-metric-normality| +--rwlink-protection-type? enumerationname? inet:domain-name |+--rw interface-switching-capabilities* [switching-capability]| | +--rwswitching-capability ted:switching-capabilities |signaling-address* inet:ip-address |+--rw encoding? ted:encoding-type| | +--rwmax-lsp-bandwidth* [priority]flag* flag-type | | | +--rwpriority uint8is-abstract? boolean | | | +--rwbandwidth? decimal64 |underlay-topology {te-topology-hierarchy}? |+--rw packet-switch-capable| | | +--rwminimum-lsp-bandwidth? decimal64 |provider-id-ref? leafref | |+--rw interface-mtu? uint16| | +--rwtime-division-multiplex-capableclient-id-ref? leafref | |+--rw minimum-lsp-bandwidth? decimal64| | +--rwindication? enumerationtopology-id-ref? leafref |+--rw srlg| | +--rwsrlg-values* [srlg-value]connectivity-matrix* [id] | | | +--rwsrlg-valueid uint32 |+--rw alt-information-sources* [information-source]|+--rw information-source enumeration| +--rwcredibility-preference? uint16from-link |+--rw link-index? uint64|+--rw administrative-group* [sequence]| | +--rwsequence uint32 |provider-id-ref? leafref |+--rw ag-element? uint32|+--rw max-link-bandwidth? decimal64|+--rw max-resv-link-bandwidth? decimal64| +--rwunreserved-bandwidth* [priority]client-id-ref? leafref | |+--rw priority uint8| | +--rwbandwidth? decimal64topology-id-ref? leafref |+--rw te-default-metric? uint32|+--rw performance-metric {te-performance-metric}?| | +--rwmeasurementnode-ref? leafref | | | | +--rwunidirectional-delay? uint32link-end-ref? leafref | | | +--rwunidirectional-min-delay? uint32to-link | | | | +--rwunidirectional-max-delay? uint32provider-id-ref? leafref | | | | +--rwunidirectional-delay-variation? uint32client-id-ref? leafref | | | | +--rwunidirectional-packet-loss? decimal64topology-id-ref? leafref | | | | +--rwunidirectional-residual-bandwidth? decimal64node-ref? leafref | | | | +--rwunidirectional-available-bandwidth? decimal64link-end-ref? leafref | | | +--rwunidirectional-utilized-bandwidth? decimal64is-allowed? boolean | | +--rwnormalityte-link* [te-link-id] | | +--rwunidirectional-delay? performance-metric-normalityte-link-id te-link-id | | +--rwunidirectional-min-delay? performance-metric-normality(stack-level)? | |+--rw unidirectional-max-delay? performance-metric-normality+--:(bundle) | | | +--rwunidirectional-delay-variation? performance-metric-normalitybundled-links | | | +--rwunidirectional-packet-loss? performance-metric-normalitybundled-link* [sequence] | | | +--rwunidirectional-residual-bandwidth? performance-metric-normalitysequence uint32 | | | +--rwunidirectional-available-bandwidth? performance-metric-normalityte-link-ref? leafref | |+--rw unidirectional-utilized-bandwidth? performance-metric-normality+--:(component) |+--rw link-protection-type? enumeration| +--rwinterface-switching-capabilities* [switching-capability]component-links | | +--rwswitching-capability ted:switching-capabilitiescomponent-link* [sequence] | | +--rwencoding? ted:encoding-typesequence uint32 | | +--rwmax-lsp-bandwidth* [priority] | |component-link-ref? leafref | +--rwpriority uint8 | |link-template* [name] {template}? | +--rwbandwidth? decimal64 |name te-template-name | +--rwpacket-switch-capablepriority? uint16 | +--rw reference-change-policy? enumeration | +--rw te-link-template* leafref | +--rwminimum-lsp-bandwidth? decimal64te-link-attributes | +--rw schedules* [schedule-id] {configuration-schedule}? | | +--rwinterface-mtu? uint16schedule-id uint32 | | +--rwtime-division-multiplex-capablestart? yang:date-and-time | | +--rwminimum-lsp-bandwidth? decimal64schedule-duration? string | | +--rwindication? enumerationrepeat-interval? string | +--rwsrlgname? string | +--rwsrlg-values* [srlg-value]flag* flag-type | +--rwsrlg-value uint32 +--ro te-topologies-state +--ro topology* [te-topology-id] +--ro te-topology-id te-topology-id +--ro server-provided?is-abstract? boolean+--ro topology-types|+--ro te-topology! +--ro node* [te-node-id]+--rw underlay! {te-topology-hierarchy}? |+--ro te-node-id te-node-id|+--ro te-node-template? leafref+--rw underlay-primary-path |+--ro te-node-attributes| |+--ro schedules* [schedule-id]+--rw provider-id-ref? leafref | | |+--ro schedule-id uint32+--rw client-id-ref? leafref | | |+--ro start? yang:date-and-time+--rw topology-id-ref? leafref | | |+--ro schedule-duration? string+--rw path-element* [path-element-id] | | |+--ro repeat-interval? string+--rw path-element-id uint32 | |+--ro name? inet:domain-name| +--rw (type)? |+--ro signaling-address* inet:ip-address| |+--ro flag* flag-type+--:(ipv4-address) | |+--ro is-abstract? boolean| |+--ro underlay-topology? leafref {te-topology-hierarchy}?+--rw v4-address? inet:ipv4- address | |+--ro te-link* [te-link-id]| | +--rw v4-prefix-length? uint8 |+--ro te-link-id te-link-id| | |+--ro (stack-level)?+--rw v4-loose? boolean | | |+--:(bundle)+--:(ipv6-address) | | | |+--ro bundled-links+--rw v6-address? inet:ipv6- address | | | |+--ro bundled-link* [sequence]+--rw v6-prefix-length? uint8 | | | |+--ro sequence uint32+--rw v6-loose? boolean | | | +--:(as-number) |+--ro te-link-ref? leafref| | |+--:(component)+--rw as-number? uint16 | | |+--ro component-links+--:(unnumbered-link) | | |+--ro component-link* [sequence]| +--rw router-id? inet:ip-address | |+--ro sequence uint32| | +--rw interface-id? uint32 |+--ro component-link-ref? leafref| |+--ro connectivity-matrix* [id]+--:(label) | | |+--ro id+--rw value? uint32 | | +--rw underlay-backup-path* [index] | |+--ro from-link| +--rw index uint32 | | |+--ro topo-ref?+--rw provider-id-ref? leafref | | || +--ro node-ref?+--rw client-id-ref? leafref | | || +--ro link-end-ref?+--rw topology-id-ref? leafref | | |+--ro to-link+--rw path-element* [path-element-id] | | | +--rw path-element-id uint32 |+--ro topo-ref? leafref| | +--rw (type)? | |+--ro node-ref? leafref| +--:(ipv4-address) | | |+--ro link-end-ref? leafref| +--rw v4-address? inet:ipv4- address | |+--ro is-allowed? boolean| |+--ro ted+--rw v4-prefix-length? uint8 | |+--ro te-router-id-ipv4? inet:ipv4-address| |+--ro te-router-id-ipv6? inet:ipv6-address+--rw v4-loose? boolean | |+--ro ipv4-local-address* [ipv4-prefix]| +--:(ipv6-address) | |+--ro ipv4-prefix inet:ipv4-prefix| |+--ro ipv6-local-address* [ipv6-prefix]+--rw v6-address? inet:ipv6- address | | |+--ro ipv6-prefix inet:ipv6-prefix| +--rw v6-prefix-length? uint8 | |+--ro prefix-option? uint8| |+--ro pcc-capabilities? pcc-capabilities+--rw v6-loose? boolean |+--ro te-node-state-attributes|+--ro information-source? enumeration|+--ro credibility-preference? uint16 +--ro link* [source-te-node-id source-te-link-id dest-te-node-id dest-te-link-id] +--ro source-te-node-id leafref +--ro source-te-link-id leafref +--ro dest-te-node-id leafref +--ro dest-te-link-id leafref +--ro te-link-template? leafref +--ro te-link-attributes+--:(as-number) |+--ro schedules* [schedule-id]| |+--ro schedule-id uint32| +--rw as-number? uint16 |+--ro start? yang:date-and-time| |+--ro schedule-duration? string+--:(unnumbered-link) | |+--ro repeat-interval? string|+--ro name? string|+--ro flag* flag-type+--rw router-id? inet:ip-address |+--ro is-abstract? boolean|+--ro underlay! {te-topology-hierarchy}?| |+--ro underlay-path+--rw interface-id? uint32 | | |+--ro topology-id? leafref+--:(label) | | |+--ro path-element* [path-element-id]+--rw value? uint32 | | +--rw underlay-protection-type? uint16 | |+--ro path-element-id uint32+--rw underlay-trail-src | | |+--ro loose? boolean+--rw provider-id-ref? leafref | | |+--ro (element-type)?+--rw client-id-ref? leafref | | |+--:(numbered-link)+--rw topology-id-ref? leafref | | | +--rw node-ref? leafref |+--ro link-ip-address? inet:ip-address| | +--rw link-end-ref? leafref |+--:(unnumbered-link)| +--rw underlay-trail-des | | +--rw provider-id-ref? leafref |+--ro link-node-id? uint32| +--rw client-id-ref? leafref | | +--rw topology-id-ref? leafref |+--ro te-link-id? uint32| +--rw node-ref? leafref | |+--:(node)+--rw link-end-ref? leafref | +--rw admin-status? enumeration | +--rw performance-metric-throttle {te-performance- metric}? | |+--ro te-node-id?+--rw unidirectional-delay-offset? uint32 | | +--rw measure-interval? uint32 |+--:(label)| +--rw advertisement-interval? uint32 | |+--ro label?+--rw suppression-interval? uint32 | |+--ro underlay-backup-path+--rw threshold-out | | |+--ro topology-id? leafref+--rw unidirectional-delay? uint32 | | |+--ro path-element* [path-element-id]+--rw unidirectional-min-delay? uint32 | | |+--ro path-element-id+--rw unidirectional-max-delay? uint32 | | |+--ro loose? boolean+--rw unidirectional-delay-variation? uint32 | | |+--ro (element-type)?+--rw unidirectional-packet-loss? decimal64 | | |+--:(numbered-link)+--rw unidirectional-residual-bandwidth? decimal64 | | | +--rw unidirectional-available-bandwidth? decimal64 |+--ro link-ip-address? inet:ip-address| | +--rw unidirectional-utilized-bandwidth? decimal64 |+--:(unnumbered-link)| +--rw threshold-in | | |+--ro link-node-id?+--rw unidirectional-delay? uint32 | | || +--ro te-link-id?+--rw unidirectional-min-delay? uint32 | | |+--:(node) |+--rw unidirectional-max-delay? uint32 | | |+--ro te-node-id?+--rw unidirectional-delay-variation? uint32 | | |+--:(label)+--rw unidirectional-packet-loss? decimal64 | | |+--ro label? uint32+--rw unidirectional-residual-bandwidth? decimal64 | |+--ro underlay-protection-type? uint16| +--rw unidirectional-available-bandwidth? decimal64 |+--ro underlay-trail-src| | +--rw unidirectional-utilized-bandwidth? decimal64 |+--ro topo-ref? leafref| +--rw threshold-accelerated-advertisement | |+--ro node-ref? leafref+--rw unidirectional-delay? uint32 | | +--rw unidirectional-min-delay? uint32 |+--ro link-end-ref? leafref| +--rw unidirectional-max-delay? uint32 |+--ro underlay-trail-des| +--rw unidirectional-delay-variation? uint32 | |+--ro topo-ref? leafref+--rw unidirectional-packet-loss? decimal64 | | +--rw unidirectional-residual-bandwidth? decimal64 |+--ro node-ref? leafref| +--rw unidirectional-available-bandwidth? decimal64 | |+--ro link-end-ref? leafref+--rw unidirectional-utilized-bandwidth? decimal64 | +--rw link-index? uint64 |+--ro dynamic? boolean | | +--ro committed? boolean | +--ro ted | +--ro admin-status? enumeration | +--ro oper-status? enumeration+--rw administrative-group? te- types:admin-groups |+--ro area-id? binary+--rw max-link-bandwidth? decimal64 |+--ro performance-metric-throttle {te-performance-metric}?+--rw max-resv-link-bandwidth? decimal64 | +--rw unreserved-bandwidth* [priority] |+--ro unidirectional-delay-offset? uint32| +--rw priority uint8 |+--ro measure-interval? uint32| +--rw bandwidth? decimal64 |+--ro advertisement-interval?+--rw te-default-metric? uint32 || +--ro suppression-interval? uint32+--rw performance-metric {te-performance-metric}? | |+--ro threshold-out+--rw measurement | | |+--ro+--rw unidirectional-delay? uint32 | | |+--ro+--rw unidirectional-min-delay? uint32 | | |+--ro+--rw unidirectional-max-delay? uint32 | | |+--ro+--rw unidirectional-delay-variation? uint32 | | |+--ro+--rw unidirectional-packet-loss? decimal64 | | |+--ro+--rw unidirectional-residual-bandwidth? decimal64 | | |+--ro+--rw unidirectional-available-bandwidth? decimal64 | | |+--ro+--rw unidirectional-utilized-bandwidth? decimal64 | |+--ro threshold-in |+--rw normality | |+--ro+--rw unidirectional-delay?uint32 |performance-metric-normality | |+--ro+--rw unidirectional-min-delay?uint32 |performance-metric-normality | |+--ro+--rw unidirectional-max-delay?uint32 |performance-metric-normality | |+--ro+--rw unidirectional-delay-variation?uint32 |performance-metric-normality | |+--ro+--rw unidirectional-packet-loss?decimal64 |performance-metric-normality | |+--ro+--rw unidirectional-residual-bandwidth?decimal64 |performance-metric-normality | |+--ro+--rw unidirectional-available-bandwidth?decimal64 |performance-metric-normality | |+--ro+--rw unidirectional-utilized-bandwidth?decimal64performance-metric-normality | +--rw link-protection-type? enumeration |+--ro threshold-accelerated-advertisement+--rw interface-switching-capabilities* [switching- capability] | |+--ro unidirectional-delay? uint32+--rw switching-capability identityref | |+--ro unidirectional-min-delay? uint32+--rw encoding? identityref | |+--ro unidirectional-max-delay? uint32+--rw max-lsp-bandwidth* [priority] | |+--ro unidirectional-delay-variation? uint32| +--rw priority uint8 |+--ro unidirectional-packet-loss? decimal64| |+--ro unidirectional-residual-bandwidth?+--rw bandwidth? decimal64 | |+--ro unidirectional-available-bandwidth? decimal64+--rw packet-switch-capable | |+--ro unidirectional-utilized-bandwidth?| +--rw minimum-lsp-bandwidth? decimal64 |+--ro information-source? enumeration|+--ro credibility-preference?| +--rw interface-mtu? uint16 |+--ro link-index? uint64|+--ro administrative-group* [sequence]+--rw time-division-multiplex-capable | |+--ro sequence uint32+--rw minimum-lsp-bandwidth? decimal64 | |+--ro ag-element? uint32+--rw indication? enumeration |+--ro max-link-bandwidth? decimal64+--rw te-srlgs | +--rw values* te-types:srlg +--romax-resv-link-bandwidth? decimal64 |te-topologies-state +--rounreserved-bandwidth* [priority] | |topology* [provider-id client-id te-topology-id] +--ropriority uint8provider-id te-global-id +--ro client-id te-global-id +--ro te-topology-id te-topology-id +--ro server-provided? boolean +--ro topology-types | +--ro te-topology! +--ro node* [te-node-id] | +--robandwidth? decimal64te-node-id te-node-id | +--rote-default-metric? uint32te-node-template? leafref {template}? | +--roperformance-metric {te-performance-metric}?te-node-attributes | | +--romeasurementschedules* [schedule-id] {configuration- schedule}? | | | +--rounidirectional-delay?schedule-id uint32 | | | +--rounidirectional-min-delay? uint32start? yang:date-and-time | | | +--rounidirectional-max-delay? uint32schedule-duration? string | | | +--rounidirectional-delay-variation? uint32 |repeat-interval? string | | +--rounidirectional-packet-loss? decimal64 |name? inet:domain-name | | +--rounidirectional-residual-bandwidth? decimal64signaling-address* inet:ip-address | | +--ro flag* flag-type | | +--ro is-abstract? boolean | | +--rounidirectional-available-bandwidth? decimal64underlay-topology {te-topology-hierarchy}? | | | +--rounidirectional-utilized-bandwidth? decimal64provider-id-ref? leafref | | | +--ronormalityclient-id-ref? leafref | | | +--rounidirectional-delay? performance-metric-normalitytopology-id-ref? leafref | | +--rounidirectional-min-delay? performance-metric-normalityconnectivity-matrix* [id] | | +--rounidirectional-max-delay? performance-metric-normalityid uint32 | | +--rounidirectional-delay-variation? performance-metric-normalityfrom-link | | | +--rounidirectional-packet-loss? performance-metric-normalityprovider-id-ref? leafref | | | +--rounidirectional-residual-bandwidth? performance-metric-normalityclient-id-ref? leafref | | | +--rounidirectional-available-bandwidth? performance-metric-normalitytopology-id-ref? leafref | | | +--rounidirectional-utilized-bandwidth? performance-metric-normalitynode-ref? leafref | | | +--rolink-protection-type? enumerationlink-end-ref? leafref | | +--rointerface-switching-capabilities* [switching-capability]to-link | | | +--roswitching-capability ted:switching-capabilitiesprovider-id-ref? leafref | | | +--roencoding? ted:encoding-typeclient-id-ref? leafref | | | +--romax-lsp-bandwidth* [priority]topology-id-ref? leafref | | | +--ropriority uint8node-ref? leafref | | | +--robandwidth? decimal64link-end-ref? leafref | | +--ropacket-switch-capableis-allowed? boolean | +--ro te-link* [te-link-id] | | +--ro te-link-id te-link-id | | +--rominimum-lsp-bandwidth? decimal64(stack-level)? | | +--:(bundle) | | | +--rointerface-mtu? uint16bundled-links | | | +--rotime-division-multiplex-capablebundled-link* [sequence] | | | +--rominimum-lsp-bandwidth? decimal64sequence uint32 | | | +--roindication? enumerationte-link-ref? leafref | | +--:(component) | | +--rosrlgcomponent-links | | +--rosrlg-values* [srlg-value]component-link* [sequence] | | +--rosrlg-valuesequence uint32 | | +--roalt-information-sources* [information-source]component-link-ref? leafref | +--roinformation-sourcete-node-state | +--ro information-source? enumeration | +--ro information-source-state | +--ro credibility-preference? uint16 | +--rolink-index? uint64topology | | +--roadministrative-group* [sequence]provider-id-ref? leafref | | +--rosequence uint32client-id-ref? leafref | | +--roag-element? uint32topology-id-ref? leafref | +--romax-link-bandwidth? decimal64routing-instance? string +--ro link* [source-te-node-id source-te-link-id dest-te- node-id dest-te-link-id] +--ro source-te-node-id leafref +--ro source-te-link-id leafref +--ro dest-te-node-id leafref +--ro dest-te-link-id leafref +--ro te-link-template? leafref {template}? +--ro te-link-attributes | +--romax-resv-link-bandwidth? decimal64schedules* [schedule-id] {configuration- schedule}? | | +--rounreserved-bandwidth* [priority]schedule-id uint32 | | +--ropriority uint8start? yang:date-and-time | | +--robandwidth? decimal64schedule-duration? string | | +--rote-default-metric? uint32repeat-interval? string | +--roperformance-metric {te-performance-metric}?name? string | +--ro flag* flag-type | +--romeasurementis-abstract? boolean | +--ro underlay! {te-topology-hierarchy}? | | +--rounidirectional-delay? uint32underlay-primary-path | | | +--rounidirectional-min-delay? uint32provider-id-ref? leafref | | | +--rounidirectional-max-delay? uint32client-id-ref? leafref | | | +--rounidirectional-delay-variation? uint32topology-id-ref? leafref | | | +--rounidirectional-packet-loss? decimal64path-element* [path-element-id] | | | +--rounidirectional-residual-bandwidth? decimal64path-element-id uint32 | | | +--rounidirectional-available-bandwidth? decimal64(type)? | | |+--ro unidirectional-utilized-bandwidth? decimal64+--:(ipv4-address) | |+--ro normality| | +--rounidirectional-delay? performance-metric-normalityv4-address? inet:ipv4- address | |+--ro unidirectional-min-delay? performance-metric-normality| | +--rounidirectional-max-delay? performance-metric-normalityv4-prefix-length? uint8 | |+--ro unidirectional-delay-variation? performance-metric-normality| | +--rounidirectional-packet-loss? performance-metric-normalityv4-loose? boolean | |+--ro unidirectional-residual-bandwidth? performance-metric-normality| +--:(ipv6-address) | |+--ro unidirectional-available-bandwidth? performance-metric-normality| | +--rounidirectional-utilized-bandwidth? performance-metric-normalityv6-address? inet:ipv6- address |+--ro link-protection-type? enumeration|+--ro interface-switching-capabilities* [switching-capability]| | +--roswitching-capability ted:switching-capabilitiesv6-prefix-length? uint8 | |+--ro encoding? ted:encoding-type| | +--romax-lsp-bandwidth* [priority]v6-loose? boolean | | |+--ro priority uint8+--:(as-number) | | | | +--robandwidth? decimal64as-number? uint16 | |+--ro packet-switch-capable| +--:(unnumbered-link) | | | | +--rominimum-lsp-bandwidth? decimal64router-id? inet:ip- address | | | | +--rointerface-mtu? uint16interface-id? uint32 | |+--ro time-division-multiplex-capable| +--:(label) |+--ro minimum-lsp-bandwidth? decimal64| | +--roindication? enumerationvalue? uint32 |+--ro srlg| +--rosrlg-values* [srlg-value]underlay-backup-path* [index] | | | +--rosrlg-valueindex uint32+--ro te-link-state-attributes +--ro information-source? enumeration +--ro credibility-preference? uint16 notifications: +---n te-node-event|+--ro event-type? te-topology-event-type| | +--rotopo-ref?provider-id-ref? leafref | | | +--ronode-ref?client-id-ref? leafref |+--ro te-topology!| | +--rote-node-attributestopology-id-ref? leafref | | | +--roschedules* [schedule-id]path-element* [path-element-id] | | | +--roschedule-idpath-element-id uint32 | | | +--rostart? yang:date-and-time(type)? | |+--ro schedule-duration? string| +--:(ipv4-address) |+--ro repeat-interval? string|+--ro name? inet:domain-name|+--ro signaling-address* inet:ip-address| +--roflag* flag-typev4-address? inet:ipv4- address | |+--ro is-abstract? boolean|+--ro underlay-topology? leafref {te-topology-hierarchy}?| +--rote-link* [te-link-id]v4-prefix-length? uint8 | |+--ro te-link-id te-link-id| | +--ro(stack-level)?v4-loose? boolean | |+--:(bundle)| +--:(ipv6-address) | | | | +--robundled-linksv6-address? inet:ipv6- address | | | | +--robundled-link* [sequence]v6-prefix-length? uint8 | | | | +--rosequence uint32v6-loose? boolean | | |+--ro te-link-ref? leafref+--:(as-number) | |+--:(component)| | +--rocomponent-linksas-number? uint16 | |+--ro component-link* [sequence]| +--:(unnumbered-link) |+--ro sequence uint32| |+--ro component-link-ref? leafref| +--roconnectivity-matrix* [id]router-id? inet:ip- address | | | | +--roidinterface-id? uint32 | |+--ro from-link| +--:(label) | | | +--rotopo-ref? leafrefvalue? uint32 | | +--ro underlay-protection-type? uint16 | | +--ronode-ref? leafrefunderlay-trail-src | | | +--rolink-end-ref?provider-id-ref? leafref | | | +--roto-linkclient-id-ref? leafref | | | +--rotopo-ref?topology-id-ref? leafref | | | +--ro node-ref? leafref | | | +--ro link-end-ref? leafref | | +--rois-allowed? booleanunderlay-trail-des |+--ro ted|+--ro te-router-id-ipv4? inet:ipv4-address| +--rote-router-id-ipv6? inet:ipv6-addressprovider-id-ref? leafref |+--ro ipv4-local-address* [ipv4-prefix]| | +--roipv4-prefix inet:ipv4-prefixclient-id-ref? leafref |+--ro ipv6-local-address* [ipv6-prefix]| | +--roipv6-prefix inet:ipv6-prefixtopology-id-ref? leafref | |+--ro prefix-option? uint8| +--ropcc-capabilities? pcc-capabilities +---n te-link-event +--ro event-type? te-topology-event-type +--ro topo-ref? leafref +--ro source-te-node-id-ref? leafref +--ro source-te-link-id-ref? leafref +--ro dest-te-node-id-ref?node-ref? leafref | | | +--rodest-te-link-id-ref?link-end-ref? leafref+--ro te-topology! +--ro te-link-attributes +--ro schedules* [schedule-id]|+--ro schedule-id uint32| +--rostart? yang:date-and-timedynamic? boolean |+--ro schedule-duration? string| +--rorepeat-interval? string +--ro name? string +--ro flag* flag-type +--ro is-abstract?committed? boolean+--ro underlay! {te-topology-hierarchy}?| +--rounderlay-path |admin-status? enumeration | +--rotopology-id? leafrefperformance-metric-throttle {te-performance- metric}? | | +--ropath-element* [path-element-id]unidirectional-delay-offset? uint32 | | +--ropath-element-idmeasure-interval? uint32 | | +--roloose? booleanadvertisement-interval? uint32 | | +--ro(element-type)?suppression-interval? uint32 | |+--:(numbered-link)+--ro threshold-out | | | +--rolink-ip-address? inet:ip-address | | +--:(unnumbered-link)unidirectional-delay? uint32 | | | +--rolink-node-id?unidirectional-min-delay? uint32 | | | +--rote-link-id?unidirectional-max-delay? uint32 | |+--:(node) | | | +--ro te-node-id? uint32 | | +--:(label) | | +--ro label? uint32 | +--ro underlay-backup-path | | +--ro topology-id? leafref | | +--ro path-element* [path-element-id] | | +--ro path-element-id uint32 | | +--ro loose? boolean | | +--ro (element-type)? | | +--:(numbered-link) | | | +--ro link-ip-address? inet:ip-address | | +--:(unnumbered-link) | | | +--ro link-node-id? uint32 | | | +--ro te-link-id? uint32 | | +--:(node) | | | +--ro te-node-id? uint32 | | +--:(label) || +--rolabel?unidirectional-delay-variation? uint32 |+--ro underlay-protection-type? uint16 | +--ro underlay-trail-src | | +--ro topo-ref? leafref | | +--ro node-ref? leafref ||+--ro link-end-ref? leafref| +--rounderlay-trail-des |unidirectional-packet-loss? decimal64 |+--ro topo-ref? leafref| | +--ronode-ref? leafrefunidirectional-residual-bandwidth? decimal64 | |+--ro link-end-ref? leafref| +--rodynamic? booleanunidirectional-available-bandwidth? decimal64 |+--ro committed? boolean +--ro ted +--ro admin-status? enumeration +--ro oper-status? enumeration +--ro area-id? binary +--ro performance-metric-throttle{te-performance-metric}?|+--ro unidirectional-delay-offset? uint32| +--romeasure-interval? uint32unidirectional-utilized-bandwidth? decimal64 |+--ro advertisement-interval? uint32| +--rosuppression-interval? uint32threshold-in |+--ro threshold-out| | +--ro unidirectional-delay? uint32 | | | +--ro unidirectional-min-delay? uint32 | | | +--ro unidirectional-max-delay? uint32 | | | +--ro unidirectional-delay-variation? uint32 | | | +--ro unidirectional-packet-loss? decimal64 | | | +--ro unidirectional-residual-bandwidth? decimal64 | | | +--ro unidirectional-available-bandwidth? decimal64 | | | +--ro unidirectional-utilized-bandwidth? decimal64 | | +--rothreshold-inthreshold-accelerated-advertisement | | +--ro unidirectional-delay? uint32 | | +--ro unidirectional-min-delay? uint32 | | +--ro unidirectional-max-delay? uint32 | | +--ro unidirectional-delay-variation? uint32 | | +--ro unidirectional-packet-loss? decimal64 | | +--ro unidirectional-residual-bandwidth? decimal64 | | +--ro unidirectional-available-bandwidth? decimal64 | | +--ro unidirectional-utilized-bandwidth? decimal64 | +--rothreshold-accelerated-advertisement | +--ro unidirectional-delay? uint32 | +--ro unidirectional-min-delay? uint32 | +--ro unidirectional-max-delay? uint32 | +--ro unidirectional-delay-variation? uint32 | +--ro unidirectional-packet-loss? decimal64 | +--ro unidirectional-residual-bandwidth? decimal64 | +--ro unidirectional-available-bandwidth? decimal64 | +--ro unidirectional-utilized-bandwidth? decimal64 +--ro information-source? enumeration +--ro credibility-preference? uint16 +--rolink-index? uint64+--ro administrative-group* [sequence]| +--rosequence uint32administrative-group? te- types:admin-groups | +--roag-element? uint32 +--romax-link-bandwidth? decimal64 | +--ro max-resv-link-bandwidth? decimal64 | +--ro unreserved-bandwidth* [priority] | | +--ro priority uint8 | | +--ro bandwidth? decimal64 | +--ro te-default-metric? uint32 | +--ro performance-metric {te-performance-metric}? | | +--ro measurement | | | +--ro unidirectional-delay? uint32 | | | +--ro unidirectional-min-delay? uint32 | | | +--ro unidirectional-max-delay? uint32 | | | +--ro unidirectional-delay-variation? uint32 | | | +--ro unidirectional-packet-loss? decimal64 | | | +--ro unidirectional-residual-bandwidth? decimal64 | | | +--ro unidirectional-available-bandwidth? decimal64 | | | +--ro unidirectional-utilized-bandwidth? decimal64 | | +--ro normality | | +--ro unidirectional-delay? performance-metric-normality | | +--ro unidirectional-min-delay? performance-metric-normality | | +--ro unidirectional-max-delay? performance-metric-normality | | +--ro unidirectional-delay-variation? performance-metric-normality | | +--ro unidirectional-packet-loss? performance-metric-normality | | +--ro unidirectional-residual-bandwidth? performance-metric-normality | | +--ro unidirectional-available-bandwidth? performance-metric-normality | | +--ro unidirectional-utilized-bandwidth? performance-metric-normality | +--ro link-protection-type? enumeration | +--ro interface-switching-capabilities*[switching-capability][switching- capability] | | +--ro switching-capabilityted:switching-capabilitiesidentityref | | +--ro encoding?ted:encoding-typeidentityref | | +--ro max-lsp-bandwidth* [priority] | | | +--ro priority uint8 | | | +--ro bandwidth? decimal64 | | +--ro packet-switch-capable | | | +--ro minimum-lsp-bandwidth? decimal64 | | | +--ro interface-mtu? uint16 | | +--ro time-division-multiplex-capable | | +--ro minimum-lsp-bandwidth? decimal64 | | +--ro indication? enumeration+--ro srlg| +--rosrlg-values* [srlg-value]te-srlgs | +--rosrlg-value uint32values* te-types:srlg +--roalt-information-sources* [information-source]te-link-state +--roinformation-sourceoper-status? enumeration +--ro information-source? enumeration +--ro information-source-state | +--ro credibility-preference? uint16 | +--rolink-index? uint64topology | | +--roadministrative-group* [sequence]provider-id-ref? leafref | | +--rosequence uint32client-id-ref? leafref | | +--roag-element? uint32topology-id-ref? leafref | +--romax-link-bandwidth? decimal64routing-instance? string +--ro alt-information-sources* [information-source] +--ro information-source enumeration +--ro information-source-state | +--ro credibility-preference? uint16 | +--ro topology | | +--ro provider-id-ref? leafref | | +--ro client-id-ref? leafref | | +--ro topology-id-ref? leafref | +--ro routing-instance? string +--ro link-index? uint64 +--ro administrative-group? te- types:admin-groups +--ro max-link-bandwidth? decimal64 +--ro max-resv-link-bandwidth? decimal64 +--ro unreserved-bandwidth* [priority] | +--ro priority uint8 | +--ro bandwidth? decimal64 +--ro te-default-metric? uint32 +--ro performance-metric {te-performance-metric}? | +--ro measurement | | +--ro unidirectional-delay? uint32 | | +--ro unidirectional-min-delay? uint32 | | +--ro unidirectional-max-delay? uint32 | | +--ro unidirectional-delay-variation? uint32 | | +--ro unidirectional-packet-loss? decimal64 | | +--ro unidirectional-residual-bandwidth? decimal64 | | +--ro unidirectional-available-bandwidth? decimal64 | | +--ro unidirectional-utilized-bandwidth? decimal64 | +--ro normality | +--ro unidirectional-delay? performance-metric-normality | +--ro unidirectional-min-delay? performance-metric-normality | +--ro unidirectional-max-delay? performance-metric-normality | +--ro unidirectional-delay-variation? performance-metric-normality | +--ro unidirectional-packet-loss? performance-metric-normality | +--ro unidirectional-residual-bandwidth? performance-metric-normality | +--ro unidirectional-available-bandwidth? performance-metric-normality | +--ro unidirectional-utilized-bandwidth? performance-metric-normality +--ro link-protection-type? enumeration +--ro interface-switching-capabilities* [switching-capability] | +--ro switching-capabilityted:switching-capabilitiesidentityref | +--ro encoding?ted:encoding-typeidentityref | +--ro max-lsp-bandwidth* [priority] | | +--ro priority uint8 | | +--ro bandwidth? decimal64 | +--ro packet-switch-capable | | +--ro minimum-lsp-bandwidth? decimal64 | | +--ro interface-mtu? uint16 | +--ro time-division-multiplex-capable | +--ro minimum-lsp-bandwidth? decimal64 | +--ro indication? enumeration +--rosrlgte-srlgs +--ro values* te-types:srlg notifications: +---n te-node-event | +--ro event-type? te-topology-event-type | +--ro provider-id-ref? leafref | +--ro client-id-ref? leafref | +--ro topology-id-ref? leafref | +--ro node-ref? leafref | +--ro te-topology! | +--ro te-node-attributes | | +--rosrlg-values* [srlg-value]schedules* [schedule-id] {configuration-schedule}? | | | +--rosrlg-valueschedule-id uint323.1. TE Topology Yang Module <CODE BEGINS> file "ietf-te-topology@2015-03-23.yang" module ietf-te-topology| | | +--ro start? yang:date-and-time | | | +--ro schedule-duration? string | | | +--ro repeat-interval? string | | +--ro name? inet:domain-name | | +--ro signaling-address* inet:ip-address | | +--ro flag* flag-type | | +--ro is-abstract? boolean | | +--ro underlay-topology {te-topology-hierarchy}? | | | +--ro provider-id-ref? leafref | | | +--ro client-id-ref? leafref | | | +--ro topology-id-ref? leafref | | +--ro connectivity-matrix* [id] | | +--ro id uint32 | | +--ro from-link | | | +--ro provider-id-ref? leafref | | | +--ro client-id-ref? leafref | | | +--ro topology-id-ref? leafref | | | +--ro node-ref? leafref | | | +--ro link-end-ref? leafref | | +--ro to-link | | | +--ro provider-id-ref? leafref | | | +--ro client-id-ref? leafref | | | +--ro topology-id-ref? leafref | | | +--ro node-ref? leafref | | | +--ro link-end-ref? leafref | | +--ro is-allowed? boolean | +--ro te-link* [te-link-id] | | +--ro te-link-id te-link-id | | +--ro (stack-level)? | | +--:(bundle) | | | +--ro bundled-links | | | +--ro bundled-link* [sequence] | | | +--ro sequence uint32 | | | +--ro te-link-ref? leafref | | +--:(component) | | +--ro component-links | | +--ro component-link* [sequence] | | +--ro sequence uint32 | | +--ro component-link-ref? leafref | +--ro te-node-state | +--ro information-source? enumeration | +--ro information-source-state | +--ro credibility-preference? uint16 | +--ro topology | | +--ro provider-id-ref? leafref | | +--ro client-id-ref? leafref | | +--ro topology-id-ref? leafref | +--ro routing-instance? string +---n te-link-event +--ro event-type? te-topology-event-type +--ro provider-id-ref? leafref +--ro client-id-ref? leafref +--ro topology-id-ref? leafref +--ro source-te-node-id-ref? leafref +--ro source-te-link-id-ref? leafref +--ro dest-te-node-id-ref? leafref +--ro dest-te-link-id-ref? leafref +--ro te-topology! +--ro te-link-attributes | +--ro schedules* [schedule-id] {configuration-schedule}? | | +--ro schedule-id uint32 | | +--ro start? yang:date-and-time | | +--ro schedule-duration? string | | +--ro repeat-interval? string | +--ro name? string | +--ro flag* flag-type | +--ro is-abstract? boolean | +--ro underlay! {te-topology-hierarchy}? | | +--ro underlay-primary-path | | | +--ro provider-id-ref? leafref | | | +--ro client-id-ref? leafref | | | +--ro topology-id-ref? leafref | | | +--ro path-element* [path-element-id] | | | +--ro path-element-id uint32 | | | +--ro (type)? | | | +--:(ipv4-address) | | | | +--ro v4-address? inet:ipv4-address | | | | +--ro v4-prefix-length? uint8 | | | | +--ro v4-loose? boolean | | | +--:(ipv6-address) | | | | +--ro v6-address? inet:ipv6-address | | | | +--ro v6-prefix-length? uint8 | | | | +--ro v6-loose? boolean | | | +--:(as-number) | | | | +--ro as-number? uint16 | | | +--:(unnumbered-link) | | | | +--ro router-id? inet:ip-address | | | | +--ro interface-id? uint32 | | | +--:(label) | | | +--ro value? uint32 | | +--ro underlay-backup-path* [index] | | | +--ro index uint32 | | | +--ro provider-id-ref? leafref | | | +--ro client-id-ref? leafref | | | +--ro topology-id-ref? leafref | | | +--ro path-element* [path-element-id] | | | +--ro path-element-id uint32 | | | +--ro (type)? | | | +--:(ipv4-address) | | | | +--ro v4-address? inet:ipv4-address | | | | +--ro v4-prefix-length? uint8 | | | | +--ro v4-loose? boolean | | | +--:(ipv6-address) | | | | +--ro v6-address? inet:ipv6-address | | | | +--ro v6-prefix-length? uint8 | | | | +--ro v6-loose? boolean | | | +--:(as-number) | | | | +--ro as-number? uint16 | | | +--:(unnumbered-link) | | | | +--ro router-id? inet:ip-address | | | | +--ro interface-id? uint32 | | | +--:(label) | | | +--ro value? uint32 | | +--ro underlay-protection-type? uint16 | | +--ro underlay-trail-src | | | +--ro provider-id-ref? leafref | | | +--ro client-id-ref? leafref | | | +--ro topology-id-ref? leafref | | | +--ro node-ref? leafref | | | +--ro link-end-ref? leafref | | +--ro underlay-trail-des | | | +--ro provider-id-ref? leafref | | | +--ro client-id-ref? leafref | | | +--ro topology-id-ref? leafref | | | +--ro node-ref? leafref | | | +--ro link-end-ref? leafref | | +--ro dynamic? boolean | | +--ro committed? boolean | +--ro admin-status? enumeration | +--ro performance-metric-throttle {te-performance-metric}? | | +--ro unidirectional-delay-offset? uint32 | | +--ro measure-interval? uint32 | | +--ro advertisement-interval? uint32 | | +--ro suppression-interval? uint32 | | +--ro threshold-out | | | +--ro unidirectional-delay? uint32 | | | +--ro unidirectional-min-delay? uint32 | | | +--ro unidirectional-max-delay? uint32 | | | +--ro unidirectional-delay-variation? uint32 | | | +--ro unidirectional-packet-loss? decimal64 | | | +--ro unidirectional-residual-bandwidth? decimal64 | | | +--ro unidirectional-available-bandwidth? decimal64 | | | +--ro unidirectional-utilized-bandwidth? decimal64 | | +--ro threshold-in | | | +--ro unidirectional-delay? uint32 | | | +--ro unidirectional-min-delay? uint32 | | | +--ro unidirectional-max-delay? uint32 | | | +--ro unidirectional-delay-variation? uint32 | | | +--ro unidirectional-packet-loss? decimal64 | | | +--ro unidirectional-residual-bandwidth? decimal64 | | | +--ro unidirectional-available-bandwidth? decimal64 | | | +--ro unidirectional-utilized-bandwidth? decimal64 | | +--ro threshold-accelerated-advertisement | | +--ro unidirectional-delay? uint32 | | +--ro unidirectional-min-delay? uint32 | | +--ro unidirectional-max-delay? uint32 | | +--ro unidirectional-delay-variation? uint32 | | +--ro unidirectional-packet-loss? decimal64 | | +--ro unidirectional-residual-bandwidth? decimal64 | | +--ro unidirectional-available-bandwidth? decimal64 | | +--ro unidirectional-utilized-bandwidth? decimal64 | +--ro link-index? uint64 | +--ro administrative-group? te-types:admin- groups | +--ro max-link-bandwidth? decimal64 | +--ro max-resv-link-bandwidth? decimal64 | +--ro unreserved-bandwidth* [priority] | | +--ro priority uint8 | | +--ro bandwidth? decimal64 | +--ro te-default-metric? uint32 | +--ro performance-metric {te-performance-metric}? | | +--ro measurement | | | +--ro unidirectional-delay? uint32 | | | +--ro unidirectional-min-delay? uint32 | | | +--ro unidirectional-max-delay? uint32 | | | +--ro unidirectional-delay-variation? uint32 | | | +--ro unidirectional-packet-loss? decimal64 | | | +--ro unidirectional-residual-bandwidth? decimal64 | | | +--ro unidirectional-available-bandwidth? decimal64 | | | +--ro unidirectional-utilized-bandwidth? decimal64 | | +--ro normality | | +--ro unidirectional-delay? performance-metric-normality | | +--ro unidirectional-min-delay? performance-metric-normality | | +--ro unidirectional-max-delay? performance-metric-normality | | +--ro unidirectional-delay-variation? performance-metric-normality | | +--ro unidirectional-packet-loss? performance-metric-normality | | +--ro unidirectional-residual-bandwidth? performance-metric-normality | | +--ro unidirectional-available-bandwidth? performance-metric-normality | | +--ro unidirectional-utilized-bandwidth? performance-metric-normality | +--ro link-protection-type? enumeration | +--ro interface-switching-capabilities* [switching- capability] | | +--ro switching-capability identityref | | +--ro encoding? identityref | | +--ro max-lsp-bandwidth* [priority] | | | +--ro priority uint8 | | | +--ro bandwidth? decimal64 | | +--ro packet-switch-capable | | | +--ro minimum-lsp-bandwidth? decimal64 | | | +--ro interface-mtu? uint16 | | +--ro time-division-multiplex-capable | | +--ro minimum-lsp-bandwidth? decimal64 | | +--ro indication? enumeration | +--ro te-srlgs | +--ro values* te-types:srlg +--ro te-link-state +--ro oper-status? enumeration +--ro information-source? enumeration +--ro information-source-state | +--ro credibility-preference? uint16 | +--ro topology | | +--ro provider-id-ref? leafref | | +--ro client-id-ref? leafref | | +--ro topology-id-ref? leafref | +--ro routing-instance? string +--ro alt-information-sources* [information-source] +--ro information-source enumeration +--ro information-source-state | +--ro credibility-preference? uint16 | +--ro topology | | +--ro provider-id-ref? leafref | | +--ro client-id-ref? leafref | | +--ro topology-id-ref? leafref | +--ro routing-instance? string +--ro link-index? uint64 +--ro administrative-group? te- types:admin-groups +--ro max-link-bandwidth? decimal64 +--ro max-resv-link-bandwidth? decimal64 +--ro unreserved-bandwidth* [priority] | +--ro priority uint8 | +--ro bandwidth? decimal64 +--ro te-default-metric? uint32 +--ro performance-metric {te-performance-metric}? | +--ro measurement | | +--ro unidirectional-delay? uint32 | | +--ro unidirectional-min-delay? uint32 | | +--ro unidirectional-max-delay? uint32 | | +--ro unidirectional-delay-variation? uint32 | | +--ro unidirectional-packet-loss? decimal64 | | +--ro unidirectional-residual-bandwidth? decimal64 | | +--ro unidirectional-available-bandwidth? decimal64 | | +--ro unidirectional-utilized-bandwidth? decimal64 | +--ro normality | +--ro unidirectional-delay? performance-metric-normality | +--ro unidirectional-min-delay? performance-metric-normality | +--ro unidirectional-max-delay? performance-metric-normality | +--ro unidirectional-delay-variation? performance-metric-normality | +--ro unidirectional-packet-loss? performance-metric-normality | +--ro unidirectional-residual-bandwidth? performance-metric-normality | +--ro unidirectional-available-bandwidth? performance-metric-normality | +--ro unidirectional-utilized-bandwidth? performance-metric-normality +--ro link-protection-type? enumeration +--ro interface-switching-capabilities* [switching- capability] | +--ro switching-capability identityref | +--ro encoding? identityref | +--ro max-lsp-bandwidth* [priority] | | +--ro priority uint8 | | +--ro bandwidth? decimal64 | +--ro packet-switch-capable | | +--ro minimum-lsp-bandwidth? decimal64 | | +--ro interface-mtu? uint16 | +--ro time-division-multiplex-capable | +--ro minimum-lsp-bandwidth? decimal64 | +--ro indication? enumeration +--ro te-srlgs +--ro values* te-types:srlg 6. TE Topology Yang Module <CODE BEGINS> module ietf-te-topology { yang-version 1; namespace "urn:ietf:params:xml:ns:yang:ietf-te-topology"; // replace with IANA namespace when assigned prefix "tet"; import ietf-yang-types { prefix "yang"; } import ietf-inet-types { prefix "inet"; } import ietf-interfaces { prefix "if"; } import ietf-te-types { prefix "te-types"; } organization "TBD"; contact "TBD"; description "TE topology model"; revision "2015-07-02" { description "Initial revision"; reference "TBD"; } /* * Features */ feature te-topology-hierarchy { description "This feature indicates that the system allows underlay and/or overlay TE topology hierarchy."; } feature te-performance-metric { description "This feature indicates that the system supports TE performance metric defined in draft-ietf-ospf-te-metric-extensions."; } feature configuration-schedule { description "This feature indicates that the system supports configuration scheduling."; } feature template { description "This feature indicates that the system supports template configuration."; } /* * Typedefs */ typedef te-global-id { type uint32; description "An identifier to uniquely identify an operator, which can be either a provider or a client. The definition of this type is taken from RFC6370 and RFC503. This attribute type is used solely to provide a globally unique context for TE topologies."; } typedef te-topology-id { type string { pattern '/?([a-zA-Z0-9\-_.]+)(/[a-zA-Z0-9\-_.]+)*'; } description "An identifier for a topology."; } typedef te-template-name { type string { pattern '/?([a-zA-Z0-9\-_.]+)(/[a-zA-Z0-9\-_.]+)*'; } description "A type for the name of a TE node template or TE link template."; } typedef te-node-id { type inet:ip-address; description "An identifier for a node in a topology. The identifier is represented as an IPv4 or IPv6 address. The identifier SHOULD be chosen such that the same node in a real network topology will always be identified through the same identifier, even if the model is instantiated in separate datastores. An implementation MAY choose to capture semantics in the identifier, for example to indicate the type of node and/or the type of topology that the node is a part of."; } typedef te-link-id { type union { type uint32; // Unnumbered type inet:ip-address; // IPv4 or IPv6 address } description "An identifier for a TE link on a node. The identifier may be opaque. The identifier SHOULD be chosen such that the same TP in a real network topology will always be identified through the same identifier, even if the model is instantiated in separate datastores. An implementation MAY choose to capture semantics in the identifier, for example to indicate the type of TP and/or the type of node and topology that the TP is a part of."; } typedef te-topology-event-type { type enumeration { enum "add" { value 0; description "A TE node or te-link has been added"; } enum "remove" { value 1; description "A TE node or te-link has been removed"; } enum "update" { value 2; description "A TE node or te-link has been updated"; } } description "TE Event type for notifications"; } // te-topology-event-type typedef performance-metric-normality { type enumeration { enum "unknown" { value 0; description "Unknown"; } enum "normal" { value 1; description "Normal"; } enum "abnormal" { value 2; description "Abnormal. The anomalous bit is set."; } } description "Indicates whether a performance metric is normal, abnormal, or unknown."; } /* * Identities */ identity flag-identity { description "Base type for flags"; } identity undefined-flag { base "flag-identity"; description "Undefined flag"; } typedef flag-type { type identityref { base "flag-identity"; } description "Type for flags"; } /* * Groupings */ grouping topo-ref { description "Grouping for an absolute reference to a topology instance."; leaf provider-id-ref { type leafref { path "/tet:te-topologies/tet:topology/tet:provider-id"; } description "An absolute reference to a provider-id."; } leaf client-id-ref { type leafref { path "/tet:te-topologies/tet:topology/tet:client-id"; } description "An absolute reference to a client-id."; } leaf topology-id-ref { type leafref { path "/tet:te-topologies/tet:topology/tet:te-topology-id"; } description "An absolute reference to a te-topology-id."; } } // topo-ref grouping link-ref { description "Grouping for an absolute reference to a link instance."; uses topo-ref; leaf source-te-node-id-ref { type leafref { path "/tet:te-topologies/tet:topology" +"[tet:provider-id = current()/../provider-id-ref]" +"[tet:client-id = current()/../client-id-ref]" +"[tet:te-topology-id = current()/../topology-id-ref]" +"/tet:link/tet:source-te-node-id"; } description "An absolute reference to a link instance."; } leaf source-te-link-id-ref { type leafref { path "/tet:te-topologies/tet:topology" +"[tet:provider-id = current()/../provider-id-ref]" +"[tet:client-id = current()/../client-id-ref]" +"[tet:te-topology-id = current()/../topology-id-ref]" +"/tet:link/tet:source-te-link-id"; } description "An absolute reference to a link instance."; } leaf dest-te-node-id-ref { type leafref { path "/tet:te-topologies/tet:topology" +"[tet:provider-id = current()/../provider-id-ref]" +"[tet:client-id = current()/../client-id-ref]" +"[tet:te-topology-id = current()/../topology-id-ref]" +"/tet:link/tet:dest-te-node-id"; } description "An absolute reference to a link instance."; } leaf dest-te-link-id-ref { type leafref { path "/tet:te-topologies/tet:topology" +"[tet:provider-id = current()/../provider-id-ref]" +"[tet:client-id = current()/../client-id-ref]" +"[tet:te-topology-id = current()/../topology-id-ref]" +"/tet:link/tet:dest-te-link-id"; } description "An absolute reference to a link instance."; } } // link-ref grouping node-ref { description "Grouping for an absolute reference to a node instance."; uses topo-ref; leaf node-ref { type leafref { path "/tet:te-topologies/tet:topology" +"[tet:provider-id = current()/../provider-id-ref]" +"[tet:client-id = current()/../client-id-ref]" +"[tet:te-topology-id = current()/../topology-id-ref]" +"/tet:node/tet:te-node-id"; } description "An absolute reference to a node instance."; } } // node-ref grouping link-end-ref { description "Grouping for an absolute reference to a TE link end, which is the local representation of a TE link on a node."; uses node-ref; leaf link-end-ref { type leafref { path "/tet:te-topologies/tet:topology" +"[tet:provider-id = current()/../provider-id-ref]" +"[tet:client-id = current()/../client-id-ref]" +"[tet:te-topology-id = current()/../topology-id-ref]" +"/tet:node[tet:te-node-id = current()/../node-ref]" +"/tet:te-link/tet:te-link-id"; } description "Grouping for an absolute reference to a TE link end."; } } // link-end-ref grouping te-topology-type { description "Identifies the TE topology type."; container te-topology { presence "indicates TE topology"; description "Its presence identifies the TE topology type."; } } // te-topology-type 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-subobject; } // te-path-element grouping config-schedule-attributes { description "A list of schedules defining when a particular configuration takes effect."; list schedules { if-feature configuration-schedule; key "schedule-id"; description "A list of schedule elements."; leaf schedule-id { type uint32; description "Identifies the schedule element."; } leaf start { type yang:date-and-time; description "Start time."; } leaf schedule-duration { type string { pattern 'P(\d+Y)?(\d+M)?(\d+W)?(\d+D)?T(\d+H)?(\d+M)?(\d+S)?'; } description "Schedule duration in ISO 8601 format."; } leaf repeat-interval { type string { pattern 'R\d*/P(\d+Y)?(\d+M)?(\d+W)?(\d+D)?T(\d+H)?(\d+M)?' + '(\d+S)?'; } description "Repeat interval in ISO 8601 format."; } } } // config-schedule-attributes grouping information-source-attributes { description "The attributes identifying source that has provided the related information, and the source credibility."; leaf information-source { type enumeration { enum "unknown" { description "The source is unknown"; } enum "locally-configured" { description "Configured entity"; } enum "ospfv2" { description "OSPFv2"; } enum "ospfv3" { description "OSPFv3"; } enum "isis" { description "ISIS"; } enum "system-processed" { description "System processed entity."; } enum "other" { description "Other source"; } } description "Indicates the source of the information."; } container information-source-state { description "The container contains state attributes related to the information source."; leaf credibility-preference { type uint16; description "The preference value to calculate the traffic engineering database credibility value used for tie-break selection between different information-source values. Higher value is more preferable."; } container topology { description "When the information is processed by the system, the attributes in this container indicate which topology is used to process to generate the result information."; leaf provider-id-ref { type leafref { path "/tet:te-topologies/tet:topology/tet:provider-id"; } description "A reference to a provider-id."; } leaf client-id-ref { type leafref { path "/tet:te-topologies/tet:topology/tet:client-id"; } description "A reference to a client-id."; } leaf topology-id-ref { type leafref { path "/tet:te-topologies/tet:topology" +"/tet:te-topology-id"; } description "A reference to a te-topology-id."; } } // topology leaf routing-instance { type string; description "When applicable, this is the name of a routing instance from which the information is learned."; } // routing-information } } // information-source-attributes grouping te-node-attributes { description "Node attributes in a TE topology."; container te-node-attributes {yang-version 1; namespace "urn:ietf:params:xml:ns:yang:ietf-te-topology"; // replace with IANA namespace when assigned prefix "tet"; import ietf-yang-typesdescription "Node attributes in a TE topology."; uses config-schedule-attributes; leaf name {prefix "yang";type inet:domain-name; description "Node name."; }import ietf-inet-typesleaf-list signaling-address {prefix "inet";type inet:ip-address; description "Node signaling address."; }import tedleaf-list flag {prefix "ted";type flag-type; description "Node operational flags."; }import ietf-interfacesleaf is-abstract {prefix "if";type boolean; description "true if the node is abstract, false when the node is actual."; }organization "TBD"; contact "TBD";container underlay-topology { if-feature te-topology-hierarchy; description"TE topology model"; revision "2015-03-23""When an abstract node encapsulates a topology, the attributes in this container point to said topology."; leaf provider-id-ref { type leafref { path "/tet:te-topologies/tet:topology/tet:provider-id"; } description"Initial revision";"A reference"TBD";to a provider-id."; }/* * Features */ feature te-topology-hierarchyleaf client-id-ref { type leafref { path "/tet:te-topologies/tet:topology/tet:client-id"; } description"This feature indicates that the system allows underlay and/or overlay TE topology hierarchy.";"A reference to a client-id."; }/* * Typedefs */ typedef te-topology-idleaf topology-id-ref { typestringleafref {pattern '/?([a-zA-Z0-9\-_.]+)(/[a-zA-Z0-9\-_.]+)*';path "/tet:te-topologies/tet:topology" +"/tet:te-topology-id"; } description"An identifier for"A reference to atopology.";te-topology-id."; }typedef te-template-name} list connectivity-matrix { key "id"; description "Represents node's switching limitations, i.e. limitations in interconnecting network TE links across the node."; leaf id { typestringuint32; description "Identifies the connectivity-matrix entry."; } container from-link {pattern '/?([a-zA-Z0-9\-_.]+)(/[a-zA-Z0-9\-_.]+)*';uses tet:link-end-ref; description "Reference to source NTP."; } container to-link { uses tet:link-end-ref; description"A"Reference to destination NTP."; } leaf is-allowed { typefor the nameboolean; description "true - switching is allowed, false - switching is disallowed."; } } } list te-link { key "te-link-id"; description "The local representation of a TEnode template orlink, which interconnect TE nodes."; leaf te-link-id { type te-link-id; description "TE linktemplate.";identifier."; }typedef te-node-idchoice stack-level {type inet:ip-address;description"An identifier for a node in a topology. The identifier is represented as an IPv4 or IPv6 address. The identifier SHOULD"The TE link can bechosen such that the same node inpartitioned into bundled links, or component links."; case bundle { container bundled-links { description "A set of bundled links"; list bundled-link { key "sequence"; description "Specify areal network topology will always be identified through the same identifier, even if the modelbundled interface that isinstantiated in separate datastores. An implementation MAY choose to capture semantics in the identifier, for example to indicate thefurther partitioned."; leaf sequence { typeof node and/oruint32; description "Identify thetype of topology thatsequence in thenode is a part of.";bundle."; }typedef te-link-idleaf te-link-ref { typeunionleafref {type uint32; // Unnumbered type inet:ip-address; // IPv4 or IPv6 addresspath "../../../te-link-id"; require-instance true; } description"An identifier for a"Reference to TE link on this node."; } } } } case component { container component-links { description "A set of component links"; list component-link { key "sequence"; description "Specify anode. The identifier may be opaque. The identifier SHOULD be chosen suchcomponent interface thatthe same TP in a real network topology will always be identified through the same identifier, even if the modelisinstantiated in separate datastores. An implementation MAY choose to capture semantics in the identifier, for examplesufficient toindicateunambiguously identify the appropriate resources"; leaf sequence { typeof TP and/oruint32; description "Identify thetype of node and topology thatsequence in theTP is a part of.";bundle."; }typedef te-topology-event-typeleaf component-link-ref { typeenumeration { enum "add"leafref {value 0;path "/if:interfaces/if:interface/if:name"; require-instance false; } description"A TE node or te-link has been added";"Reference to component link on this node."; }enum "remove"} } } } } } // te-node-attributes grouping te-node-state-attributes {value 1;description"A"Node state attributes in a TEnode or te-link has been removed"; } enum "update"topology."; container te-node-state {value 2;description"A"Node state attributes in a TEnode or te-link has been updated"; }topology."; uses information-source-attributes; }description "TE Event type for notifications";} //te-topology-event-type /* * Identities */ identity flag-identityte-node-state-attributes grouping te-link-underlay-attributes { description"Base type"Attributes forflags"; } identity undefined-flagte-link underlay."; container underlay-primary-path {base "flag-identity";description"Undefined flag"; } typedef flag-type"The service path on the underlay topology that supports this link."; leaf provider-id-ref { typeidentityrefleafref {base "flag-identity";path "/tet:te-topologies/tet:topology/tet:provider-id"; require-instance false; } description"Type for flags";"A reference to a provider-id."; }/* * Groupings */ grouping topo-refleaf client-id-ref { type leafref { path "/tet:te-topologies/tet:topology/tet:client-id"; require-instance false; } description"Grouping for an absolute"A reference to atopology instance.";client-id."; } leaftopo-reftopology-id-ref { type leafref { path "/tet:te-topologies/tet:topology/tet:te-topology-id"; require-instance false; } description"An absolute reference to a"Identifies the topologyinstance."; }where the path belongs."; }grouping link-reflist path-element { key "path-element-id"; description"Grouping for an absolute reference to"A list of path elements describing the service path"; leaf path-element-id { type uint32; description "To identify the element in alink instance.";path."; } usestopo-ref;te-path-element; } } // underlay-primary-path list underlay-backup-path { key "index"; description "A list of backup service paths on the underlay topology that protect the underlay primary path. If the primary path is not protected, the list contains zero elements. If the primary path is protected, the list contains one or more elements."; leafsource-te-node-id-refindex { typeleafref { path "/tet:te-topologies/tet:topology" +"[tet:te-topology-id = current()/../topo-ref]" +"/tet:link/tet:source-te-node-id"; }uint32; description"An absolute reference"A sequence number to identify alink instance.";backup path."; } leafsource-te-link-id-refprovider-id-ref { type leafref { path"/tet:te-topologies/tet:topology" +"[tet:te-topology-id = current()/../topo-ref]" +"/tet:link/tet:source-te-link-id";"/tet:te-topologies/tet:topology/tet:provider-id"; require-instance false; } description"An absolute"A reference to alink instance.";provider-id."; } leafdest-te-node-id-refclient-id-ref { type leafref { path"/tet:te-topologies/tet:topology" +"[tet:te-topology-id = current()/../topo-ref]" +"/tet:link/tet:dest-te-node-id";"/tet:te-topologies/tet:topology/tet:client-id"; require-instance false; } description"An absolute"A reference to alink instance.";client-id."; } leafdest-te-link-id-reftopology-id-ref { type leafref { path"/tet:te-topologies/tet:topology" +"[tet:te-topology-id = current()/../topo-ref]" +"/tet:link/tet:dest-te-link-id";"/tet:te-topologies/tet:topology/tet:te-topology-id"; require-instance false; } description"An absolute reference to a link instance."; }"Identifies the topology where the path belongs."; }grouping node-reflist path-element { key "path-element-id"; description"Grouping for an absolute reference to a node instance."; uses topo-ref;"A list of path elements describing the backup service path"; leafnode-refpath-element-id { typeleafref { path "/tet:te-topologies/tet:topology" +"[tet:te-topology-id = current()/../topo-ref]" +"/tet:node/tet:te-node-id"; } description "An absolute reference to a node instance."; } } grouping link-end-ref {uint32; description"Grouping for an absolute reference to a TE link end, which is"To identify thelocal representation of a TE link onelement in anode.";path."; } usesnode-ref;te-path-element; } } // underlay-backup-path leaflink-end-refunderlay-protection-type { typeleafref { path "/tet:te-topologies/tet:topology" +"[tet:te-topology-id = current()/../topo-ref]" +"/tet:node[tet:te-node-id = current()/../node-ref]" +"/tet:te-node-attributes/tet:te-link/tet:te-link-id"; }uint16; description"Grouping"Underlay protection type desired foran absolute reference to a TE link end."; }this link"; }grouping te-topology-type { description "Identifies the TE topology type.";containerte-topologyunderlay-trail-src {presence "indicates TE topology";uses tet:link-end-ref; description"Its presence identifies the"Source TEtopology type."; }link of the underlay trail."; }grouping te-path-elementcontainer underlay-trail-des { uses tet:link-end-ref; description"A group of attributes defining an element in a TE path such as TE node, TE link,"Destination TEaotomic resource or label.";link of the underlay trail."; } } // te-link-underlay-attributes grouping te-link-state-underlay-attributes { description "State attributes for te-link underlay."; leafloosedynamic { type boolean; description "true if theelementunderlay isloose.";dynamically created."; }choice element-type { description "Attributes for various element types."; case numbered-link {leaflink-ip-addresscommitted { typeinet:ip-address;boolean; description"IPv4 or IPv6 address.";"true if the underlay is committed."; } }case unnumbered-link { leaf link-node-id// te-link-state-underlay-attributes grouping performance-metric-attributes {type uint32;description"Node ID of the node where the link end point resides."; }"Link performance information in real time."; reference "draft-ietf-ospf-te-metric-extensions."; leafte-link-idunidirectional-delay { typeuint32; description "Identifies the link end point.";uint32 { range 0..16777215; } description "Delay or latency in micro seconds."; }case node {leafte-node-idunidirectional-min-delay { typeuint32; description "Identifies the node.";uint32 { range 0..16777215; } description "Minimum delay or latency in micro seconds."; }case label {leaflabelunidirectional-max-delay { typeuint32;uint32 { range 0..16777215; } description"Identifies atomic TE resource"Maximum delay orlabel."; } } }latency in micro seconds."; }// te-path-element grouping config-schedule-attributesleaf unidirectional-delay-variation {description "A list of schedules defining when a particular configuration takes effect."; list schedulestype uint32 {key "schedule-id";range 0..16777215; } description"A list of schedule elements.";"Delay variation in micro seconds."; } leafschedule-idunidirectional-packet-loss { typeuint32;decimal64 { fraction-digits 6; range "0 .. 50.331642"; } description"Identifies"Packet loss as a percentage of theschedule element.";total traffic sent over a configurable interval. The finest precision is 0.000003%."; } leafstartunidirectional-residual-bandwidth { typeyang:date-and-time;decimal64 { fraction-digits 2; } description"Start time.";"Residual bandwidth that subtracts tunnel reservations from Maximum Bandwidth (or link capacity) [RFC3630] and provides an aggregated remainder across QoS classes."; } leafschedule-durationunidirectional-available-bandwidth { typestringdecimal64 {pattern 'P(\d+Y)?(\d+M)?(\d+W)?(\d+D)?T(\d+H)?(\d+M)?(\d+S)?';fraction-digits 2; } description"Schedule duration in ISO 8601 format.";"Available bandwidth that is defined to be residual bandwidth minus the measured bandwidth used for the actual forwarding of non-RSVP-TE LSP packets. For a bundled link, available bandwidth is defined to be the sum of the component link available bandwidths."; } leafrepeat-intervalunidirectional-utilized-bandwidth { typestringdecimal64 {pattern 'R\d*/P(\d+Y)?(\d+M)?(\d+W)?(\d+D)?T(\d+H)?(\d+M)?' + '(\d+S)?';fraction-digits 2; } description"Repeat interval"Bandwidth utilization that represents the actual utilization of the link (i.e. as measured inISO 8601 format."; }the router). For a bundled link, bandwidth utilization is defined to be the sum of the component link bandwidth utilizations."; } } // performance-metric-attributes groupinginformation-source-attributesperformance-metric-normality-attributes { description"The attributes identifying source that has provided the related information, and the source credibility.";"Link performance metric normality attributes."; reference "draft-ietf-ospf-te-metric-extensions."; leafinformation-sourceunidirectional-delay { typeenumeration { enum "unknown" {performance-metric-normality; description"The source is unknown";"Delay normality."; }enum "locally-configured"leaf unidirectional-min-delay { type performance-metric-normality; description"Configured TE link";"Minimum delay or latency normality."; }enum "ospfv2"leaf unidirectional-max-delay { type performance-metric-normality; description"OSPFv2";"Maximum delay or latency normality."; }enum "ospfv3"leaf unidirectional-delay-variation { type performance-metric-normality; description"OSPFv3";"Delay variation normality."; }enum "isis"leaf unidirectional-packet-loss { type performance-metric-normality; description"ISIS";"Packet loss normality."; }enum "other"leaf unidirectional-residual-bandwidth { type performance-metric-normality; description"Other source"; }"Residual bandwidth normality."; } leaf unidirectional-available-bandwidth { type performance-metric-normality; description"Indicates the source of the information.";"Available bandwidth normality."; } leafcredibility-preferenceunidirectional-utilized-bandwidth { typeuint16;performance-metric-normality; description"The preference value to calculate the traffic engineering database credibility value used for tie-break selection between different information-source values. Higher value is more preferable.";"Bandwidth utilization normality."; } } // performance-metric-normality-attributes groupingte-node-attributesperformance-metric-throttle-container { description"Node attributes in a TE topology.";"A containerte-node-attributescontrolling performance metric throttle."; container performance-metric-throttle { if-feature te-performance-metric; must "suppression-interval >= measure-interval" { error-message "suppression-interval cannot be less then measure-interval"; description"Node attributes"Constraint on suppression-interval and measure-interval."; } description "Link performance information ina TE topology."; uses config-schedule-attributes;real time."; reference "draft-ietf-ospf-te-metric-extensions."; leafnameunidirectional-delay-offset { typeinet:domain-name; description "Node name."; } leaf-list signaling-addressuint32 {type inet:ip-address;range 0..16777215; } description"Node signaling address.";"Offset value to be added to the measured delay value."; }leaf-list flagleaf measure-interval { typeflag-type;uint32; default 30; description"Node operational flags.";"Interval in seconds to measure the extended metric values."; } leafis-abstractadvertisement-interval { typeboolean;uint32; description"true if the node is abstract, false when"Interval in seconds to advertise thenode is actual.";extended metric values."; } leafunderlay-topologysuppression-interval {if-feature te-topology-hierarchy;typeleafrefuint32 {path "/tet:te-topologies/tet:topology/tet:te-topology-id";range "1 .. max"; } default 120; description"When an abstract node encapsulates a topology, this reference points"Interval in seconds tosaid topology.";suppress advertising the extended metric values."; }list te-linkcontainer threshold-out {key "te-link-id";uses performance-metric-attributes; description"The local representation of a TE link, which interconnect TE nodes."; leaf te-link-id"If the measured parameter falls outside an upper bound for all but the min delay metric (or lower bound for min-delay metric only) and the advertised value is not already outside that bound, anomalous announcement will be triggered."; } container threshold-in {type te-link-id;uses performance-metric-attributes; description"TE link identifier.";"If the measured parameter falls inside an upper bound for all but the min delay metric (or lower bound for min-delay metric only) and the advertised value is not already inside that bound, normal (anomalous-flag cleared) announcement will be triggered."; }choice stack-levelcontainer threshold-accelerated-advertisement { description"The TE link can"When the difference between the last advertised value and current measured value exceed this threshold, anomalous announcement will bepartitioned into bundled links, or component links."; case bundle { container bundled-linkstriggered."; uses performance-metric-attributes; } } } // performance-metric-throttle-container grouping te-link-info-attributes { description"A set of bundled links"; list bundled-link"Advertised TE information attributes."; leaf link-index {key "sequence";type uint64; description"Specify"The link identifier. If OSPF is used, this represents an ospfLsdbID. If IS-IS is used, this represents an isisLSPID. If abundled interfface thatlocally configured link isfurther partitioned.";used, this object represents a unique value, which is locally defined in a router."; } leafsequenceadministrative-group { typeuint32;te-types:admin-groups; description"Identify"Administrative group or color of thesequencelink. This attribute covers both administrative group (defined inthe bundle.";RFC3630, RFC5329, and RFC5305), and extended administrative group (defined in RFC7308)."; } leafte-link-refmax-link-bandwidth { typeleafrefdecimal64 {path "../../../te-link-id"; require-instance "true";fraction-digits 2; } description"Reference to TE link"Maximum bandwidth that can be seen on thisnode."; } } }link in this direction. Units in bytes per second"; }case componentleaf max-resv-link-bandwidth {container component-linkstype decimal64 { fraction-digits 2; } description"A set"Maximum amount ofcomponent links";bandwidth that can be reserved in this direction in this link. Units in bytes per second"; } listcomponent-linkunreserved-bandwidth { key"sequence";"priority"; max-elements "8"; description"Specify a component interfface that is sufficient to unambiguously identify the appropriate resources";"Unreserved bandwidth for 0-7 priority levels. Units in bytes per second"; leafsequencepriority { typeuint32;uint8 { range "0..7"; } description"Identify the sequence in the bundle.";"Priority"; } leafcomponent-link-refbandwidth { typeleafrefdecimal64 {path "/if:interfaces/if:interface/if:name"; require-instance "false";fraction-digits 2; } description"Reference to component link on"Unreserved bandwidth for thisnode."; } } }level"; } }} list connectivity-matrix { key "id"; description "Represents node's switching limitations, i.e. limitations in interconnecting network TE links across the node.";leafidte-default-metric { type uint32; description"Identifies the connectivity-matrix entry.";"Traffic Engineering Metric"; } containerfrom-linkperformance-metric {uses tet:link-end-ref;if-feature te-performance-metric; description"Reference to source NTP."; }"Link performance information in real time."; reference "draft-ietf-ospf-te-metric-extensions."; containerto-linkmeasurement { description "Measured performance metric values. Static configuration and manual overrides of these measurements are also allowed."; usestet:link-end-ref;performance-metric-attributes; } container normality { description"Reference to destination NTP.";"Performance metric normality values."; uses performance-metric-normality-attributes; } } leafis-allowedlink-protection-type { typeboolean; description "true - switching is allowed, false - switching is disallowed."; }enumeration { enum "unprotected" { description "unprotected"; }container tedenum "extra-traffic" { description"Includes TE node attributes."; uses ted:ted-node-attributes;"Extra traffic"; } enum "shared" { description "Shared"; } enum "1-for-1" { description "One for one protection"; }// te-node-attributes grouping te-node-state-attributesenum "1-plus-1" { description"Node state attributes in a TE topology."; container te-node-state-attributes"One plus one protection"; } enum "enhanced" { description"Node state attributes in a TE topology."; uses information-source-attributes;"Enhanced protection"; } }// te-node-state-attributes grouping te-link-underlay-attributesdescription "Link Protection Type desired for this link"; } list interface-switching-capabilities { key "switching-capability"; description"Attributes"List of interface capabilities forte-link underlay."; container underlay-paththis interface"; leaf switching-capability { type identityref { base te-types:switching-capabilities; } description"The service path on the underlay topology that supports"Switching Capability for thislink.";interface"; } leaftopology-idencoding { typeleafrefidentityref {path "/tet:te-topologies/tet:topology/tet:te-topology-id"; require-instance false;base te-types:lsp-encoding-types; } description"Identifies the topology where the path belongs.";"Encoding supported by this interface"; } listpath-elementmax-lsp-bandwidth { key"path-element-id"; description "A list of path elements describing the service path";"priority"; max-elements "8"; description "Maximum LSP Bandwidth at priorities 0-7"; leafpath-element-idpriority { typeuint32;uint8 { range "0..7"; } description"To identify the element in a path.";"Priority"; }uses te-path-element;leaf bandwidth { type decimal64 { fraction-digits 2; } description "Max LSP Bandwidth for this level"; } }// underlay-pathcontainerunderlay-backup-pathpacket-switch-capable { when "../switching-capability = 'PSC-1' or " +"../switching-capability = 'PSC-2' or " +"../switching-capability = 'PSC-3' or " +"../switching-capability = 'PSC-4'" { description"The backup service path on the underlay topology that supports this link.";"Valid only for PSC"; } description "Interface has packet-switching capabilities"; leaftopology-idminimum-lsp-bandwidth { typeleafrefdecimal64 {path "/tet:te-topologies/tet:topology/tet:te-topology-id"; require-instance false;fraction-digits 2; } description"Identifies the topology where the path belongs.";"Minimum LSP Bandwidth. Units in bytes per second"; }list path-element { key "path-element-id"; description "A list of path elements describing the backup service path";leafpath-element-idinterface-mtu { typeuint32;uint16; description"To identify the element in a path.";"Interface MTU"; }uses te-path-element;} container time-division-multiplex-capable { when "../switching-capability = 'TDM'" { description "Valid only for TDM"; }// underlay-backup-pathdescription "Interface has time-division multiplex capabilities"; leafunderlay-protection-typeminimum-lsp-bandwidth { typeuint16;decimal64 { fraction-digits 2; } description"Underlay protection type desired for this link";"Minimum LSP Bandwidth. Units in bytes per second"; }container underlay-trail-srcleaf indication { type enumeration { enum "standard" {uses tet:link-end-ref;description"Source TE link of the underlay trail.";"Indicates support of standard SONET/SDH"; }container underlay-trail-desenum "arbitrary" {uses tet:link-end-ref;description"Destination TE link"Indicates support of arbitrary SONET/SDH"; } } description "Indication whether theunderlay trail.";interface supports Standard or Arbitrary SONET/SDH"; } }// te-link-underlay-attributes grouping te-link-state-underlay-attributes} container te-srlgs { description"State attributes for te-link underlay."; leaf dynamic"A list of SLRGs."; leaf-list values { typeboolean;te-types:srlg; description"true if the underlay is dynamically created.";"SRLG value"; }leaf committed { type boolean; description "true if the underlay is committed.";} } //te-link-state-underlay-attributeste-link-info-attributes grouping te-link-attributes { description "Link attributes in a TE topology."; container te-link-attributes { description "Link attributes in a TE topology."; uses config-schedule-attributes; leaf name { type string; description "Link Name"; } leaf-list flag { type flag-type; description "Link flags"; } leaf is-abstract { type boolean; description "true if the link is abstract."; } container underlay { if-feature te-topology-hierarchy; presence "Indicates the underlay exists for thislink."; description "State of the underlay oflink."; description "State of the underlay of this link."; uses te-link-underlay-attributes; } // underlay leaf admin-status { type enumeration { enum up { value 1; description "Enabled."; } enum down { value 2; description "Disabled."; } enum testing { value 3; description "In some test mode."; } } description "The desired state of the link."; } uses performance-metric-throttle-container; uses te-link-info-attributes; } } // te-link-attributes grouping te-link-state-attributes { description "Link state attributes in a TE topology."; container te-link-state { description "Link state attributes in a TE topology."; leaf oper-status { type enumeration { enum up { value 1; description "Operational up"; } enum down { value 2; description "Operational down."; } enum testing { value 3; description "In some test mode"; } enum unknown { value 4; description "Status cannot be determined for some reason."; } } description "The current operational state of the link."; } uses information-source-attributes; list alt-information-sources { key "information-source"; description "A list of information sources learned but not used."; uses information-source-attributes; uses te-link-info-attributes; } } } // te-link-state-attributes grouping template-attributes { description "Common attributes for all templates."; leaf priority { type uint16; description "The preference value to resolve conflicts between different templates. When two or more templates specify values for one configuration attribute, the value from the template with the highest priority is used."; } leaf reference-change-policy { type enumeration { enum no-action { description "When an attribute changes in this template, the configuration node referring to this template does not take any action."; } enum not-allowed { description "When any configuration object has a reference to this template, changing thislink."; uses te-link-underlay-attributes;template is not allowed."; }// underlay container tedenum cascade { description"Includes TE link attributes."; uses ted:ted-link-attributes; }"When an attribute changes in this template, the configuration object referring to this template applies the new attribute value to the corresponding configuration."; } }// te-link-attributes grouping te-link-state-attributes {description"Link state attributes in"This attribute specifies the action taken to aTE topology."; container te-link-state-attributes { description "Link state attributes inconfiguration node that has aTE topology."; uses information-source-attributes;reference to this template."; } } //te-link-state-attributestemplate-attributes /* * Configuration data nodes */ container te-topologies { description "This container acts as the top-level data element of configuration data."; list topology { key"te-topology-id";"provider-id client-id te-topology-id"; description "This is the model of an abstract topology. A topology contains nodes and links. Each topology MUST be identified by a unique te-topology-id for reason that a network could contain many topologies."; leaf provider-id { type te-global-id; description "An identifier to uniquely identify a provider."; } leaf client-id { type te-global-id; description "An identifier to uniquely identify a client."; } leaf te-topology-id { type te-topology-id; description "It is presumed that a datastore will contain many topologies. To distinguish between topologies it is vital to have UNIQUE topology identifiers."; } uses config-schedule-attributes; container topology-types { description "This container is used to identify the type, or types (as a topology can support several types simultaneously), of the topology. Topology types are the subject of several integrity constraints that an implementing server can validate in order to maintain integrity of the datastore. Topology types are indicated through separate data nodes; the set of topology types is expected to increase over time. To add support for a new topology, an augmenting module needs to augment this container with a new empty optional container to indicate the new topology type. The use of a container allows to indicate a subcategorization of topology types. The container SHALL NOT be augmented with any data nodes that serve a purpose other than identifying a particular topology type."; uses te-topology-type; // Defines the TE topology type. } list node { key "te-node-id"; leaf te-node-id { type te-node-id; description "The identifier of a node in the topology. A node is specific to a topology to which it belongs."; } description "The list of network nodes defined for the topology."; leaf te-node-template { if-feature template; type leafref { path "/te-topologies/node-template/name"; } description "The reference to a TE node template."; } uses te-node-attributes; } list link { key "source-te-node-id source-te-link-id " + "dest-te-node-id dest-te-link-id"; leaf source-te-node-id { type leafref { path "../../node/te-node-id"; } mandatory true; description "Source node identifier, must be in same topology."; } leaf source-te-link-id { type leafref { path "../../node[te-node-id = " + "current()/../source-te-node-id]/" +"te-node-attributes/te-link/te-link-id";"te-link/te-link-id"; } mandatory true; description "Source TE link identifier, must be in same topology."; } leaf dest-te-node-id { type leafref { path "../../node/te-node-id"; } mandatory true; description "Destination node identifier, must be in the same topology."; } leaf dest-te-link-id { type leafref { path "../../node[te-node-id = " + "current()/../dest-te-node-id]/" +"te-node-attributes/te-link/te-link-id";"te-link/te-link-id"; } mandatory true; description "Destination TE link identifier, must be in same topology."; } description "TE link is a logical construct that represents a way to group/map information about certain physical resources (and their properties) that interconnect TE nodes. A Network Link connects a by Local (Source) node and a Remote (Destination) Network Nodes via a set of the nodes' TE links. As it is possible to have several links between the same source and destination nodes, and as a link could potentially be re-homed, to ensure that we would always know to distinguish between links, every link is identified by a dedicated link identifier. Note that a link models a point-to-point link, not a multipoint link."; leaf te-link-template { if-feature template; type leafref { path "/te-topologies/link-template/name"; } description "The reference to a TE link template."; } uses te-link-attributes; } // link } // topology list node-template { if-feature template; key "name"; leaf name { type te-template-name; description "The name to identify a TE node template."; } description "The list of TE node templates used to define sharable and reusable TE node attributes."; uses template-attributes; leaf-list te-node-template { type leafref { path "/te-topologies/node-template/name"; } description "The reference to a TE node template."; } uses te-node-attributes; } // node list link-template { if-feature template; key "name"; leaf name { type te-template-name; description "The name to identify a TE link template."; } description "The list of TE link templates used to define sharable and reusable TE link attributes."; uses template-attributes; leaf-list te-link-template { type leafref { path "/te-topologies/link-template/name"; } description "The reference to a TE link template."; } uses te-link-attributes; } // link } // te-topologies /* * Operational state data nodes */ container te-topologies-state { config"false";false; description "This container acts as the top-level state data element of operational data."; list topology { key"te-topology-id";"provider-id client-id te-topology-id"; description "This is the model of an abstract topology. A topology contains nodes and links. Each topology MUST be identified by a unique te-topology-id for reason that a network could contain many topologies."; leaf provider-id { type te-global-id; description "An identifier to uniquely identify a provider."; } leaf client-id { type te-global-id; description "An identifier to uniquely identify a client."; } leaf te-topology-id { type te-topology-id; description "It is presumed that a datastore will contain many topologies. To distinguish between topologies it is vital to have UNIQUE topology identifiers."; } leaf server-provided { type boolean; config false; description "Indicates whether the topology is configurable by clients, or whether it is provided by the server. This leaf is populated by the server implementing the model. It is set to false for topologies that are created by a client; it is set to true otherwise. If it is set to true, any attempt to edit the topology MUST be rejected."; } container topology-types { description "This container is used to identify the type, or types (as a topology can support several types simultaneously), of the topology. Topology types are the subject of several integrity constraints that an implementing server can validate in order to maintain integrity of the datastore. Topology types are indicated through separate data nodes; the set of topology types is expected to increase over time. To add support for a new topology, an augmenting module needs to augment this container with a new empty optional container to indicate the new topology type. The use of a container allows to indicate a subcategorization of topology types. The container SHALL NOT be augmented with any data nodes that serve a purpose other than identifying a particular topology type."; uses te-topology-type; // Defines the TE topology type. } list node { key "te-node-id"; leaf te-node-id { type te-node-id; description "The identifier of a node in the topology. A node is specific to a topology to which it belongs."; } description "The list of network nodes defined for the topology."; leaf te-node-template { if-feature template; type leafref { path "/te-topologies/node-template/name"; } description "The reference to a TE node template."; } uses te-node-attributes; uses te-node-state-attributes; } list link { key "source-te-node-id source-te-link-id " + "dest-te-node-id dest-te-link-id"; leaf source-te-node-id { type leafref { path "../../node/te-node-id"; } mandatory true; description "Source node identifier, must be in same topology."; } leaf source-te-link-id { type leafref { path "../../node[te-node-id = " + "current()/../source-te-node-id]/" +"te-node-attributes/te-link/te-link-id";"te-link/te-link-id"; } mandatory true; description "Source TE link identifier, must be in same topology."; } leaf dest-te-node-id { type leafref { path "../../node/te-node-id"; } mandatory true; description "Destination node identifier, must be in the same topology."; } leaf dest-te-link-id { type leafref { path "../../node[te-node-id = " + "current()/../dest-te-node-id]/" +"te-node-attributes/te-link/te-link-id";"te-link/te-link-id"; } mandatory true; description "Destination TE link identifier, must be in same topology."; } description "TE link is a logical construct that represents a way to group/map information about certain physical resources (and their properties) that interconnect TE nodes. A Network Link connects a by Local (Source) node and a Remote (Destination) Network Nodes via a set of the nodes' TE links. As it is possible to have several links between the same source and destination nodes, and as a link could potentially be re-homed, to ensure that we would always know to distinguish between links, every link is identified by a dedicated link identifier. Note that a link models a point-to-point link, not a multipoint link."; leaf te-link-template { if-feature template; type leafref { path "/te-topologies/link-template/name"; } description "The reference to a TE link template."; } uses te-link-attributes; uses te-link-state-attributes; } // link } // topology } // te-topologies augment "/te-topologies-state/topology/link/te-link-attributes/" + "underlay" { description "Add state attributes to te-link underlay."; uses te-link-state-underlay-attributes; } /* * Notifications */ notification te-node-event { description "Notification event for TE node"; leaf event-type { type te-topology-event-type; description "Event type"; } uses node-ref; uses te-topology-type; uses tet:te-node-attributes; uses tet:te-node-state-attributes; } notification te-link-event { description "Notification event for TE link"; leaf event-type { type te-topology-event-type; description "Event type"; } uses link-ref; uses te-topology-type; uses tet:te-link-attributes; uses tet:te-link-state-attributes; } augment "/te-link-event/te-link-attributes/underlay" { description "Add state attributes to te-link underlay."; uses te-link-state-underlay-attributes; } } <CODE ENDS>4.7. Security Considerations The transport protocol used for retrieving/manipulating the TE topology data MUST support authentication and SHOULD support encryption. The data-model by itself does not create any security implications. 8. 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 XML: N/A, the requested URI is an XML namespace. This document registers a YANG module in the YANG Module Names registry [RFC6020]. name: ietf-te-topology namespace: urn:ietf:params:xml:ns:yang:ietf-te-topology prefix: tet 9. References 9.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004. [RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)", RFC 6020, October 2010.[RFC6241] Enns, R., Bjorklund, M.,[RFC6991] Schoenwaelder, J.,and A. Bierman, "Network Configuration Protocol (NETCONF)","Common YANG Data Types", RFC 6991, July 2013. [RFC3945] Mannie, E., "Generalized Multi-Protocol Label Switching (GMPLS) Architecture", October 2004. [YANG-NET-TOPO] Clemm, A., "A Data Model for Network Topologies", draft-ietf-i2rs-yang-network-topo (Work in Progress). [YANG-PUSH] Clemm, A., "Subscribing to YANG datastore push updates", draft-clemm-netconf-yang-push (Work in Progress). 9.2. Informative References [RFC2702] Awduche, D., "Requirements for Traffic Engineering Over MPLS", RFC6241, June 2011.2702, September 1999. 10. 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. Authors' Addresses Xufeng Liu Ericsson Email: xufeng.liu@ericsson.com Igor Bryskin ADVA Optical Networking Email: ibryskin@advaoptical.com Vishnu Pavan Beeram Juniper Networks Email: vbeeram@juniper.net Tarek Saad Cisco SystemsInc.Inc Email: tsaad@cisco.com Himanshu Shah Ciena Email:tsaad@cisco.comhshah@ciena.com Oscar Gonzalez De Dios Telefonica Email: oscar.gonzalezdedios@telefonica.com