YANG Data Model for Layer 3 TE Topologies
draft-ietf-teas-yang-l3-te-topo-07

Network Working Group                                             X. Liu
Internet-Draft                                            Volta Networks
Intended status: Standards Track                              I. Bryskin
Expires: November 7, 2020                                     Individual
                                                               V. Beeram
                                                                 T. Saad
                                                        Juniper Networks
                                                                 H. Shah
                                                                   Ciena
                                                     O. Gonzalez de Dios
                                                              Telefonica
                                                             May 6, 2020


               YANG Data Model for Layer 3 TE Topologies
                   draft-ietf-teas-yang-l3-te-topo-07

Abstract

   This document defines a YANG data model for layer 3 traffic
   engineering topologies.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on November 7, 2020.

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents



Liu, et al.             Expires November 7, 2020                [Page 1]


Internet-Draft             YANG L3 TE Topology                  May 2020


   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Tree Diagrams . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Modeling Considerations for L3 TE Topologies  . . . . . . . .   3
     2.1.  Relationship Between Layer 3 Topology and TE topology . .   4
     2.2.  Relationship Modeling . . . . . . . . . . . . . . . . . .   5
       2.2.1.  Topology Referencing  . . . . . . . . . . . . . . . .   5
       2.2.2.  Node Referencing  . . . . . . . . . . . . . . . . . .   5
       2.2.3.  Link Termination Point Referencing  . . . . . . . . .   6
       2.2.4.  Link Referencing  . . . . . . . . . . . . . . . . . .   6
     2.3.  Topology Type Modeling  . . . . . . . . . . . . . . . . .   6
   3.  Packet Switching Technology Extensions  . . . . . . . . . . .   6
     3.1.  Technology Specific Link Attributes . . . . . . . . . . .   7
     3.2.  Performance Metric  . . . . . . . . . . . . . . . . . . .   7
   4.  Complete Model Tree Structure . . . . . . . . . . . . . . . .   8
     4.1.  Layer 3 TE Topology Module  . . . . . . . . . . . . . . .   8
     4.2.  Packet Switching TE Topology Module . . . . . . . . . . .   8
   5.  YANG Modules  . . . . . . . . . . . . . . . . . . . . . . . .  28
     5.1.  Layer 3 TE Topology Module  . . . . . . . . . . . . . . .  28
     5.2.  Packet Switching TE Topology Module . . . . . . . . . . .  33
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  40
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  42
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  44
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  44
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  46
   Appendix A.  Companion YANG Model for Non-NMDA Compliant
                Implementations  . . . . . . . . . . . . . . . . . .  47
     A.1.  Layer 3 TE Topology State Module  . . . . . . . . . . . .  47
     A.2.  Packet Switching TE Topology State Module . . . . . . . .  50
   Appendix B.  Data Tree Example  . . . . . . . . . . . . . . . . .  56
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  66

1.  Introduction

   This document defines a YANG [RFC7950] data model for describing the
   relationship between a layer 3 topology [RFC8346] and a Traffic
   Engineering (TE) topology [I-D.ietf-teas-yang-te-topo].

   When traffic engineering is enabled on a layer 3 topology, there will
   be a corresponding TE topology.  The TE topology may or may not be



Liu, et al.             Expires November 7, 2020                [Page 2]


Internet-Draft             YANG L3 TE Topology                  May 2020


   congruent to the layer 3 topology.  When such a congruent TE topology
   exists, there will be a one-to-one association between the one
   modeling element in the layer 3 topology to another element in the TE
   topology.  When such a congruent TE topology does not exist, the
   association will not be one-to-one.  This YANG data model allows both
   cases.

1.1.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14, [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

   The following terms are defined in [RFC7950] and are not redefined
   here:

   o  augment

   o  data model

   o  data node

1.2.  Tree Diagrams

   Tree diagrams used in this document follow the notation defined in
   [RFC8340].

2.  Modeling Considerations for L3 TE Topologies

   A layer 3 TE topology is a layer 3 topology with additional TE
   capabilities enabled.  [RFC8346] defines a YANG data model for layer
   3 topologies, consisting of two modules: ietf-l3-unicast-topology and
   ietf-l3-unicast-topology-state.  The YANG data model defined in this
   document augments the YANG data model defined in [RFC8346].  This
   document specifies two YANG modules ietf-l3-te-topology and ietf-l3-
   te-topology-state, augmenting ietf-l3-unicast-topology and ietf-l3-
   unicast-topology-state respectively, to add additional TE
   capabilities.











Liu, et al.             Expires November 7, 2020                [Page 3]


Internet-Draft             YANG L3 TE Topology                  May 2020


          +------------------------+
          |    Network Topology    |
          |  ietf-network-topology | Defined in RFC 8345
          +------------^-----------+
                       |
                       | augments
                       | (A "inheritance" relation)
                       |
        +----------------------------+
        |      Layer 3 Topology      |
        |  ietf-l3-unicast-topology  | Defined in RFC 8346
        +--------------^-------------+
                       |
                       | augments
                       | (A "inheritance" relation)
                       |
          +------------^-----------+
          |  Layer 3 TE Topology   |
          |  ietf-l3-te-topology   | Defined in this document
          +------------------------+

                       Figure 1: Model Augmentations

2.1.  Relationship Between Layer 3 Topology and TE topology

   In general, the layer 3 topology model specified in [RFC8346] and the
   TE topology model specified in [I-D.ietf-teas-yang-te-topo] can be
   used independently.  When traffic engineering is enabled on a layer 3
   topology, there will be associations between the objects in the layer
   3 topology and the objects in the TE topology.  Such associations are
   supported by the module ietf-l3-te-topology defined in this document.

        +----------------------------+  +----------------------+
        |      Layer 3 Topology      |  |     TE Topology      |
        |  ietf-l3-unicast-topology  |  |   ietf-te-topology   |
        +--------------^-------------+  +----------------------+
                       |                  A
                       | augments         |
                       |                 /
                       |                / references by "leafref"
          +------------^-----------+   /  (An "association" relation)
          |  Layer 3 TE Topology   |__/
          |  ietf-l3-te-topology   |
          +------------------------+

                        Figure 2: Model References





Liu, et al.             Expires November 7, 2020                [Page 4]


Internet-Draft             YANG L3 TE Topology                  May 2020


   The properties of the relations between the objects in a layer 3
   topology and the objects in the corresponding TE topology are:

   o  The associations are between objects of the same class, i.e. node
      to node or link to link.

   o  The multiplicity of such an association is: 0..1 to 0..1.  An
      object in a layer 3 topology augmented by ietf-l3-te-topology may
      be associated with zero or one object in the corresponding TE
      topology.

2.2.  Relationship Modeling

   YANG data type leafref is used to model the association relationship
   between a layer 3 topology and a TE topology.  YANG "must" statements
   are used to enforce that the referenced objects are in a topology of
   the proper type.

2.2.1.  Topology Referencing

   When TE is enabled on a layer 3 topology, if the TE topology is not
   congruent to the layer 3 topology, the layer 3 topology will have a
   reference to the corresponding TE topology.  Such a reference is
   modeled as follows:

   augment /nw:networks/nw:network/l3t:l3-topology-attributes:
     +--rw l3-te-topology-attributes
        +--rw network-ref?   -> /nw:networks/network/network-id

   Since ietf-te-topology augments ietf-network-topology defined in
   [RFC8345] [I-D.ietf-teas-yang-te-topo], the referenced leaf
   /nw:networks/network/network-id identifies an instance of TE topology
   by inheritance.  There is a "must" statement in ietf-l3-te-topology
   to ensure that the topology instance identified by this network-id is
   of type "te-topology".  Such "must" statements are also used in all
   the following leafref nodes in this section.

   If the TE topology is congruent to the layer 3 topology, the above
   reference can still be used to specified TE parameters defined in the
   TE topology model.

2.2.2.  Node Referencing

   When TE is enabled on a layer 3 topology, if the TE topology is not
   congruent to the layer 3 topology, a layer 3 network node may have a
   reference to the corresponding TE node.  Such a reference is modeled
   as follows:




Liu, et al.             Expires November 7, 2020                [Page 5]


Internet-Draft             YANG L3 TE Topology                  May 2020


   augment /nw:networks/nw:network/nw:node/l3t:l3-node-attributes:
     +--rw l3-te-node-attributes
        +--rw node-ref?      leafref
        +--rw network-ref?   -> /nw:networks/network/network-id

2.2.3.  Link Termination Point Referencing

   When TE is enabled on a layer 3 topology, if the TE topology is not
   congruent to the layer 3 topology, a layer 3 link termination point
   may have a reference to the corresponding TE link termination point.
   Such a reference is modeled as follows:

   augment /nw:networks/nw:network/nw:node/nt:termination-point
             /l3t:l3-termination-point-attributes:
     +--rw l3-te-tp-attributes
        +--rw tp-ref?        leafref
        +--rw node-ref?      leafref
        +--rw network-ref?   -> /nw:networks/network/network-id

2.2.4.  Link Referencing

   When TE is enabled on a layer 3 topology, if the TE topology is not
   congruent to the layer 3 topology, a layer 3 link may have a
   reference to the corresponding TE link.  Such a reference is modeled
   as follows:

   augment /nw:networks/nw:network/nt:link/l3t:l3-link-attributes:
     +--rw l3-te-link-attributes
        +--rw link-ref?      leafref
        +--rw network-ref?   -> /nw:networks/network/network-id

2.3.  Topology Type Modeling

   A new topology type is defined in this document, to indicate a
   topology that is a layer 3 topology with TE enabled.

   augment /nw:networks/nw:network/nw:network-types
             /l3t:l3-unicast-topology:
     +--rw l3-te!

3.  Packet Switching Technology Extensions

   The technology agnostic TE Topology model is defined in
   [I-D.ietf-teas-yang-te-topo], which is extended by this document to
   cover the Packet Switch Capable (PSC) technology [RFC3471] [RFC7074].






Liu, et al.             Expires November 7, 2020                [Page 6]


Internet-Draft             YANG L3 TE Topology                  May 2020


3.1.  Technology Specific Link Attributes

   The technology agnostic TE Topology model is augmented with packet
   switching specific link attributes:

   augment /nw:networks/tet:te/tet:templates/tet:link-template
             /tet:te-link-attributes
             /tet:interface-switching-capability:
     +--rw packet-switch-capable
        +--rw minimum-lsp-bandwidth?   rt-types:bandwidth-ieee-float32
        +--rw interface-mtu?           uint16
   augment /nw:networks/nw:network/nt:link/tet:te
             /tet:te-link-attributes
             /tet:interface-switching-capability:
     +--rw packet-switch-capable
        +--rw minimum-lsp-bandwidth?   rt-types:bandwidth-ieee-float32
        +--rw interface-mtu?           uint16
   augment /nw:networks/nw:network/nt:link/tet:te
             /tet:information-source-entry
             /tet:interface-switching-capability:
     +--ro packet-switch-capable
        +--ro minimum-lsp-bandwidth?   rt-types:bandwidth-ieee-float32
        +--ro interface-mtu?           uint16

3.2.  Performance Metric

   [RFC7471], [RFC8570] and [RFC7823] specify TE performance metric
   parameters and their usage.  The packet switching augmentations
   specified in this document support such a capability, which can be
   conditional enabled by a YANG feature "te-performance-metric".

   augment /nw:networks/nw:network/nw:node/tet:te
             /tet:te-node-attributes/tet:connectivity-matrices:
     +--rw performance-metric
        +--rw measurement
        |     ......
        +--rw normality
        |     ......
        +--rw throttle
              ......

   Such an augmentation has been applied to:

   o  Connectivity matrices container

   o  Connectivity matrix entry

   o  Local link connectivities container



Liu, et al.             Expires November 7, 2020                [Page 7]


Internet-Draft             YANG L3 TE Topology                  May 2020


   o  Local link connectivity entry

   o  TE link attributes container in a TE link template

   o  TE link attributes container in a TE link

   o  Information source entry in a TE link

4.  Complete Model Tree Structure

4.1.  Layer 3 TE Topology Module

   The model tree structure of the layer 3 TE topology module is as
   shown below:



   module: ietf-l3-te-topology
     augment /nw:networks/nw:network/nw:network-types
               /l3t:l3-unicast-topology:
       +--rw l3-te!
     augment /nw:networks/nw:network/l3t:l3-topology-attributes:
       +--rw l3-te-topology-attributes
          +--rw network-ref?   -> /nw:networks/network/network-id
     augment /nw:networks/nw:network/nw:node/l3t:l3-node-attributes:
       +--rw l3-te-node-attributes
          +--rw node-ref?      leafref
          +--rw network-ref?   -> /nw:networks/network/network-id
     augment /nw:networks/nw:network/nw:node/nt:termination-point
               /l3t:l3-termination-point-attributes:
       +--rw l3-te-tp-attributes
          +--rw tp-ref?        leafref
          +--rw node-ref?      leafref
          +--rw network-ref?   -> /nw:networks/network/network-id
     augment /nw:networks/nw:network/nt:link/l3t:l3-link-attributes:
       +--rw l3-te-link-attributes
          +--rw link-ref?      leafref
          +--rw network-ref?   -> /nw:networks/network/network-id



4.2.  Packet Switching TE Topology Module

   This is an augmentation to base TE topology model.



   module: ietf-te-topology-packet



Liu, et al.             Expires November 7, 2020                [Page 8]


Internet-Draft             YANG L3 TE Topology                  May 2020


     augment /nw:networks/nw:network/nw:node/tet:te
               /tet:te-node-attributes/tet:connectivity-matrices:
       +--ro performance-metrics-one-way {te-performance-metric}?
       |  +--ro one-way-delay?                           uint32
       |  +--ro one-way-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-residual-bandwidth?
       |  |       rt-types:bandwidth-ieee-float32
       |  +--ro one-way-residual-bandwidth-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-available-bandwidth?
       |  |       rt-types:bandwidth-ieee-float32
       |  +--ro one-way-available-bandwidth-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-utilized-bandwidth?
       |  |       rt-types:bandwidth-ieee-float32
       |  +--ro one-way-utilized-bandwidth-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-min-delay?                       uint32
       |  +--ro one-way-min-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-max-delay?                       uint32
       |  +--ro one-way-max-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-delay-variation?                 uint32
       |  +--ro one-way-delay-variation-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-packet-loss?                     decimal64
       |  +--ro one-way-packet-loss-normality?
       |          te-types:performance-metrics-normality
       +--ro performance-metrics-two-way {te-performance-metric}?
       |  +--ro two-way-delay?                       uint32
       |  +--ro two-way-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro two-way-min-delay?                   uint32
       |  +--ro two-way-min-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro two-way-max-delay?                   uint32
       |  +--ro two-way-max-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro two-way-delay-variation?             uint32
       |  +--ro two-way-delay-variation-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro two-way-packet-loss?                 decimal64
       |  +--ro two-way-packet-loss-normality?
       |          te-types:performance-metrics-normality
       +--rw throttle {te-performance-metric}?
          +--rw one-way-delay-offset?                  uint32



Liu, et al.             Expires November 7, 2020                [Page 9]


Internet-Draft             YANG L3 TE Topology                  May 2020


          +--rw measure-interval?                      uint32
          +--rw advertisement-interval?                uint32
          +--rw suppression-interval?                  uint32
          +--rw threshold-out
          |  +--rw one-way-delay?                 uint32
          |  +--rw one-way-residual-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--rw one-way-available-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--rw one-way-utilized-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--rw two-way-delay?                 uint32
          |  +--rw one-way-min-delay?             uint32
          |  +--rw one-way-max-delay?             uint32
          |  +--rw one-way-delay-variation?       uint32
          |  +--rw one-way-packet-loss?           decimal64
          |  +--rw two-way-min-delay?             uint32
          |  +--rw two-way-max-delay?             uint32
          |  +--rw two-way-delay-variation?       uint32
          |  +--rw two-way-packet-loss?           decimal64
          +--rw threshold-in
          |  +--rw one-way-delay?                 uint32
          |  +--rw one-way-residual-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--rw one-way-available-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--rw one-way-utilized-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--rw two-way-delay?                 uint32
          |  +--rw one-way-min-delay?             uint32
          |  +--rw one-way-max-delay?             uint32
          |  +--rw one-way-delay-variation?       uint32
          |  +--rw one-way-packet-loss?           decimal64
          |  +--rw two-way-min-delay?             uint32
          |  +--rw two-way-max-delay?             uint32
          |  +--rw two-way-delay-variation?       uint32
          |  +--rw two-way-packet-loss?           decimal64
          +--rw threshold-accelerated-advertisement
             +--rw one-way-delay?                 uint32
             +--rw one-way-residual-bandwidth?
             |       rt-types:bandwidth-ieee-float32
             +--rw one-way-available-bandwidth?
             |       rt-types:bandwidth-ieee-float32
             +--rw one-way-utilized-bandwidth?
             |       rt-types:bandwidth-ieee-float32
             +--rw two-way-delay?                 uint32
             +--rw one-way-min-delay?             uint32
             +--rw one-way-max-delay?             uint32



Liu, et al.             Expires November 7, 2020               [Page 10]


Internet-Draft             YANG L3 TE Topology                  May 2020


             +--rw one-way-delay-variation?       uint32
             +--rw one-way-packet-loss?           decimal64
             +--rw two-way-min-delay?             uint32
             +--rw two-way-max-delay?             uint32
             +--rw two-way-delay-variation?       uint32
             +--rw two-way-packet-loss?           decimal64
     augment /nw:networks/nw:network/nw:node/tet:te
               /tet:te-node-attributes/tet:connectivity-matrices
               /tet:connectivity-matrix:
       +--ro performance-metrics-one-way {te-performance-metric}?
       |  +--ro one-way-delay?                           uint32
       |  +--ro one-way-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-residual-bandwidth?
       |  |       rt-types:bandwidth-ieee-float32
       |  +--ro one-way-residual-bandwidth-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-available-bandwidth?
       |  |       rt-types:bandwidth-ieee-float32
       |  +--ro one-way-available-bandwidth-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-utilized-bandwidth?
       |  |       rt-types:bandwidth-ieee-float32
       |  +--ro one-way-utilized-bandwidth-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-min-delay?                       uint32
       |  +--ro one-way-min-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-max-delay?                       uint32
       |  +--ro one-way-max-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-delay-variation?                 uint32
       |  +--ro one-way-delay-variation-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-packet-loss?                     decimal64
       |  +--ro one-way-packet-loss-normality?
       |          te-types:performance-metrics-normality
       +--ro performance-metrics-two-way {te-performance-metric}?
       |  +--ro two-way-delay?                       uint32
       |  +--ro two-way-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro two-way-min-delay?                   uint32
       |  +--ro two-way-min-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro two-way-max-delay?                   uint32
       |  +--ro two-way-max-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro two-way-delay-variation?             uint32



Liu, et al.             Expires November 7, 2020               [Page 11]


Internet-Draft             YANG L3 TE Topology                  May 2020


       |  +--ro two-way-delay-variation-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro two-way-packet-loss?                 decimal64
       |  +--ro two-way-packet-loss-normality?
       |          te-types:performance-metrics-normality
       +--rw throttle {te-performance-metric}?
          +--rw one-way-delay-offset?                  uint32
          +--rw measure-interval?                      uint32
          +--rw advertisement-interval?                uint32
          +--rw suppression-interval?                  uint32
          +--rw threshold-out
          |  +--rw one-way-delay?                 uint32
          |  +--rw one-way-residual-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--rw one-way-available-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--rw one-way-utilized-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--rw two-way-delay?                 uint32
          |  +--rw one-way-min-delay?             uint32
          |  +--rw one-way-max-delay?             uint32
          |  +--rw one-way-delay-variation?       uint32
          |  +--rw one-way-packet-loss?           decimal64
          |  +--rw two-way-min-delay?             uint32
          |  +--rw two-way-max-delay?             uint32
          |  +--rw two-way-delay-variation?       uint32
          |  +--rw two-way-packet-loss?           decimal64
          +--rw threshold-in
          |  +--rw one-way-delay?                 uint32
          |  +--rw one-way-residual-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--rw one-way-available-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--rw one-way-utilized-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--rw two-way-delay?                 uint32
          |  +--rw one-way-min-delay?             uint32
          |  +--rw one-way-max-delay?             uint32
          |  +--rw one-way-delay-variation?       uint32
          |  +--rw one-way-packet-loss?           decimal64
          |  +--rw two-way-min-delay?             uint32
          |  +--rw two-way-max-delay?             uint32
          |  +--rw two-way-delay-variation?       uint32
          |  +--rw two-way-packet-loss?           decimal64
          +--rw threshold-accelerated-advertisement
             +--rw one-way-delay?                 uint32
             +--rw one-way-residual-bandwidth?
             |       rt-types:bandwidth-ieee-float32



Liu, et al.             Expires November 7, 2020               [Page 12]


Internet-Draft             YANG L3 TE Topology                  May 2020


             +--rw one-way-available-bandwidth?
             |       rt-types:bandwidth-ieee-float32
             +--rw one-way-utilized-bandwidth?
             |       rt-types:bandwidth-ieee-float32
             +--rw two-way-delay?                 uint32
             +--rw one-way-min-delay?             uint32
             +--rw one-way-max-delay?             uint32
             +--rw one-way-delay-variation?       uint32
             +--rw one-way-packet-loss?           decimal64
             +--rw two-way-min-delay?             uint32
             +--rw two-way-max-delay?             uint32
             +--rw two-way-delay-variation?       uint32
             +--rw two-way-packet-loss?           decimal64
     augment /nw:networks/nw:network/nw:node/tet:te
               /tet:information-source-entry/tet:connectivity-matrices:
       +--ro performance-metrics-one-way {te-performance-metric}?
       |  +--ro one-way-delay?                           uint32
       |  +--ro one-way-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-residual-bandwidth?
       |  |       rt-types:bandwidth-ieee-float32
       |  +--ro one-way-residual-bandwidth-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-available-bandwidth?
       |  |       rt-types:bandwidth-ieee-float32
       |  +--ro one-way-available-bandwidth-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-utilized-bandwidth?
       |  |       rt-types:bandwidth-ieee-float32
       |  +--ro one-way-utilized-bandwidth-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-min-delay?                       uint32
       |  +--ro one-way-min-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-max-delay?                       uint32
       |  +--ro one-way-max-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-delay-variation?                 uint32
       |  +--ro one-way-delay-variation-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-packet-loss?                     decimal64
       |  +--ro one-way-packet-loss-normality?
       |          te-types:performance-metrics-normality
       +--ro performance-metrics-two-way {te-performance-metric}?
       |  +--ro two-way-delay?                       uint32
       |  +--ro two-way-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro two-way-min-delay?                   uint32



Liu, et al.             Expires November 7, 2020               [Page 13]


Internet-Draft             YANG L3 TE Topology                  May 2020


       |  +--ro two-way-min-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro two-way-max-delay?                   uint32
       |  +--ro two-way-max-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro two-way-delay-variation?             uint32
       |  +--ro two-way-delay-variation-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro two-way-packet-loss?                 decimal64
       |  +--ro two-way-packet-loss-normality?
       |          te-types:performance-metrics-normality
       +--ro throttle {te-performance-metric}?
          +--ro one-way-delay-offset?                  uint32
          +--ro measure-interval?                      uint32
          +--ro advertisement-interval?                uint32
          +--ro suppression-interval?                  uint32
          +--ro threshold-out
          |  +--ro one-way-delay?                 uint32
          |  +--ro one-way-residual-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--ro one-way-available-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--ro one-way-utilized-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--ro two-way-delay?                 uint32
          |  +--ro one-way-min-delay?             uint32
          |  +--ro one-way-max-delay?             uint32
          |  +--ro one-way-delay-variation?       uint32
          |  +--ro one-way-packet-loss?           decimal64
          |  +--ro two-way-min-delay?             uint32
          |  +--ro two-way-max-delay?             uint32
          |  +--ro two-way-delay-variation?       uint32
          |  +--ro two-way-packet-loss?           decimal64
          +--ro threshold-in
          |  +--ro one-way-delay?                 uint32
          |  +--ro one-way-residual-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--ro one-way-available-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--ro one-way-utilized-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--ro two-way-delay?                 uint32
          |  +--ro one-way-min-delay?             uint32
          |  +--ro one-way-max-delay?             uint32
          |  +--ro one-way-delay-variation?       uint32
          |  +--ro one-way-packet-loss?           decimal64
          |  +--ro two-way-min-delay?             uint32
          |  +--ro two-way-max-delay?             uint32



Liu, et al.             Expires November 7, 2020               [Page 14]


Internet-Draft             YANG L3 TE Topology                  May 2020


          |  +--ro two-way-delay-variation?       uint32
          |  +--ro two-way-packet-loss?           decimal64
          +--ro threshold-accelerated-advertisement
             +--ro one-way-delay?                 uint32
             +--ro one-way-residual-bandwidth?
             |       rt-types:bandwidth-ieee-float32
             +--ro one-way-available-bandwidth?
             |       rt-types:bandwidth-ieee-float32
             +--ro one-way-utilized-bandwidth?
             |       rt-types:bandwidth-ieee-float32
             +--ro two-way-delay?                 uint32
             +--ro one-way-min-delay?             uint32
             +--ro one-way-max-delay?             uint32
             +--ro one-way-delay-variation?       uint32
             +--ro one-way-packet-loss?           decimal64
             +--ro two-way-min-delay?             uint32
             +--ro two-way-max-delay?             uint32
             +--ro two-way-delay-variation?       uint32
             +--ro two-way-packet-loss?           decimal64
     augment /nw:networks/nw:network/nw:node/tet:te
               /tet:information-source-entry/tet:connectivity-matrices
               /tet:connectivity-matrix:
       +--ro performance-metrics-one-way {te-performance-metric}?
       |  +--ro one-way-delay?                           uint32
       |  +--ro one-way-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-residual-bandwidth?
       |  |       rt-types:bandwidth-ieee-float32
       |  +--ro one-way-residual-bandwidth-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-available-bandwidth?
       |  |       rt-types:bandwidth-ieee-float32
       |  +--ro one-way-available-bandwidth-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-utilized-bandwidth?
       |  |       rt-types:bandwidth-ieee-float32
       |  +--ro one-way-utilized-bandwidth-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-min-delay?                       uint32
       |  +--ro one-way-min-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-max-delay?                       uint32
       |  +--ro one-way-max-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-delay-variation?                 uint32
       |  +--ro one-way-delay-variation-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-packet-loss?                     decimal64



Liu, et al.             Expires November 7, 2020               [Page 15]


Internet-Draft             YANG L3 TE Topology                  May 2020


       |  +--ro one-way-packet-loss-normality?
       |          te-types:performance-metrics-normality
       +--ro performance-metrics-two-way {te-performance-metric}?
       |  +--ro two-way-delay?                       uint32
       |  +--ro two-way-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro two-way-min-delay?                   uint32
       |  +--ro two-way-min-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro two-way-max-delay?                   uint32
       |  +--ro two-way-max-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro two-way-delay-variation?             uint32
       |  +--ro two-way-delay-variation-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro two-way-packet-loss?                 decimal64
       |  +--ro two-way-packet-loss-normality?
       |          te-types:performance-metrics-normality
       +--ro throttle {te-performance-metric}?
          +--ro one-way-delay-offset?                  uint32
          +--ro measure-interval?                      uint32
          +--ro advertisement-interval?                uint32
          +--ro suppression-interval?                  uint32
          +--ro threshold-out
          |  +--ro one-way-delay?                 uint32
          |  +--ro one-way-residual-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--ro one-way-available-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--ro one-way-utilized-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--ro two-way-delay?                 uint32
          |  +--ro one-way-min-delay?             uint32
          |  +--ro one-way-max-delay?             uint32
          |  +--ro one-way-delay-variation?       uint32
          |  +--ro one-way-packet-loss?           decimal64
          |  +--ro two-way-min-delay?             uint32
          |  +--ro two-way-max-delay?             uint32
          |  +--ro two-way-delay-variation?       uint32
          |  +--ro two-way-packet-loss?           decimal64
          +--ro threshold-in
          |  +--ro one-way-delay?                 uint32
          |  +--ro one-way-residual-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--ro one-way-available-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--ro one-way-utilized-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32



Liu, et al.             Expires November 7, 2020               [Page 16]


Internet-Draft             YANG L3 TE Topology                  May 2020


          |  +--ro two-way-delay?                 uint32
          |  +--ro one-way-min-delay?             uint32
          |  +--ro one-way-max-delay?             uint32
          |  +--ro one-way-delay-variation?       uint32
          |  +--ro one-way-packet-loss?           decimal64
          |  +--ro two-way-min-delay?             uint32
          |  +--ro two-way-max-delay?             uint32
          |  +--ro two-way-delay-variation?       uint32
          |  +--ro two-way-packet-loss?           decimal64
          +--ro threshold-accelerated-advertisement
             +--ro one-way-delay?                 uint32
             +--ro one-way-residual-bandwidth?
             |       rt-types:bandwidth-ieee-float32
             +--ro one-way-available-bandwidth?
             |       rt-types:bandwidth-ieee-float32
             +--ro one-way-utilized-bandwidth?
             |       rt-types:bandwidth-ieee-float32
             +--ro two-way-delay?                 uint32
             +--ro one-way-min-delay?             uint32
             +--ro one-way-max-delay?             uint32
             +--ro one-way-delay-variation?       uint32
             +--ro one-way-packet-loss?           decimal64
             +--ro two-way-min-delay?             uint32
             +--ro two-way-max-delay?             uint32
             +--ro two-way-delay-variation?       uint32
             +--ro two-way-packet-loss?           decimal64
     augment /nw:networks/nw:network/nw:node/tet:te
               /tet:tunnel-termination-point
               /tet:local-link-connectivities:
       +--ro performance-metrics-one-way {te-performance-metric}?
       |  +--ro one-way-delay?                           uint32
       |  +--ro one-way-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-residual-bandwidth?
       |  |       rt-types:bandwidth-ieee-float32
       |  +--ro one-way-residual-bandwidth-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-available-bandwidth?
       |  |       rt-types:bandwidth-ieee-float32
       |  +--ro one-way-available-bandwidth-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-utilized-bandwidth?
       |  |       rt-types:bandwidth-ieee-float32
       |  +--ro one-way-utilized-bandwidth-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-min-delay?                       uint32
       |  +--ro one-way-min-delay-normality?
       |  |       te-types:performance-metrics-normality



Liu, et al.             Expires November 7, 2020               [Page 17]


Internet-Draft             YANG L3 TE Topology                  May 2020


       |  +--ro one-way-max-delay?                       uint32
       |  +--ro one-way-max-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-delay-variation?                 uint32
       |  +--ro one-way-delay-variation-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-packet-loss?                     decimal64
       |  +--ro one-way-packet-loss-normality?
       |          te-types:performance-metrics-normality
       +--ro performance-metrics-two-way {te-performance-metric}?
       |  +--ro two-way-delay?                       uint32
       |  +--ro two-way-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro two-way-min-delay?                   uint32
       |  +--ro two-way-min-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro two-way-max-delay?                   uint32
       |  +--ro two-way-max-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro two-way-delay-variation?             uint32
       |  +--ro two-way-delay-variation-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro two-way-packet-loss?                 decimal64
       |  +--ro two-way-packet-loss-normality?
       |          te-types:performance-metrics-normality
       +--rw throttle {te-performance-metric}?
          +--rw one-way-delay-offset?                  uint32
          +--rw measure-interval?                      uint32
          +--rw advertisement-interval?                uint32
          +--rw suppression-interval?                  uint32
          +--rw threshold-out
          |  +--rw one-way-delay?                 uint32
          |  +--rw one-way-residual-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--rw one-way-available-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--rw one-way-utilized-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--rw two-way-delay?                 uint32
          |  +--rw one-way-min-delay?             uint32
          |  +--rw one-way-max-delay?             uint32
          |  +--rw one-way-delay-variation?       uint32
          |  +--rw one-way-packet-loss?           decimal64
          |  +--rw two-way-min-delay?             uint32
          |  +--rw two-way-max-delay?             uint32
          |  +--rw two-way-delay-variation?       uint32
          |  +--rw two-way-packet-loss?           decimal64
          +--rw threshold-in



Liu, et al.             Expires November 7, 2020               [Page 18]


Internet-Draft             YANG L3 TE Topology                  May 2020


          |  +--rw one-way-delay?                 uint32
          |  +--rw one-way-residual-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--rw one-way-available-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--rw one-way-utilized-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--rw two-way-delay?                 uint32
          |  +--rw one-way-min-delay?             uint32
          |  +--rw one-way-max-delay?             uint32
          |  +--rw one-way-delay-variation?       uint32
          |  +--rw one-way-packet-loss?           decimal64
          |  +--rw two-way-min-delay?             uint32
          |  +--rw two-way-max-delay?             uint32
          |  +--rw two-way-delay-variation?       uint32
          |  +--rw two-way-packet-loss?           decimal64
          +--rw threshold-accelerated-advertisement
             +--rw one-way-delay?                 uint32
             +--rw one-way-residual-bandwidth?
             |       rt-types:bandwidth-ieee-float32
             +--rw one-way-available-bandwidth?
             |       rt-types:bandwidth-ieee-float32
             +--rw one-way-utilized-bandwidth?
             |       rt-types:bandwidth-ieee-float32
             +--rw two-way-delay?                 uint32
             +--rw one-way-min-delay?             uint32
             +--rw one-way-max-delay?             uint32
             +--rw one-way-delay-variation?       uint32
             +--rw one-way-packet-loss?           decimal64
             +--rw two-way-min-delay?             uint32
             +--rw two-way-max-delay?             uint32
             +--rw two-way-delay-variation?       uint32
             +--rw two-way-packet-loss?           decimal64
     augment /nw:networks/nw:network/nw:node/tet:te
               /tet:tunnel-termination-point
               /tet:local-link-connectivities
               /tet:local-link-connectivity:
       +--ro performance-metrics-one-way {te-performance-metric}?
       |  +--ro one-way-delay?                           uint32
       |  +--ro one-way-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-residual-bandwidth?
       |  |       rt-types:bandwidth-ieee-float32
       |  +--ro one-way-residual-bandwidth-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-available-bandwidth?
       |  |       rt-types:bandwidth-ieee-float32
       |  +--ro one-way-available-bandwidth-normality?



Liu, et al.             Expires November 7, 2020               [Page 19]


Internet-Draft             YANG L3 TE Topology                  May 2020


       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-utilized-bandwidth?
       |  |       rt-types:bandwidth-ieee-float32
       |  +--ro one-way-utilized-bandwidth-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-min-delay?                       uint32
       |  +--ro one-way-min-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-max-delay?                       uint32
       |  +--ro one-way-max-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-delay-variation?                 uint32
       |  +--ro one-way-delay-variation-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-packet-loss?                     decimal64
       |  +--ro one-way-packet-loss-normality?
       |          te-types:performance-metrics-normality
       +--ro performance-metrics-two-way {te-performance-metric}?
       |  +--ro two-way-delay?                       uint32
       |  +--ro two-way-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro two-way-min-delay?                   uint32
       |  +--ro two-way-min-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro two-way-max-delay?                   uint32
       |  +--ro two-way-max-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro two-way-delay-variation?             uint32
       |  +--ro two-way-delay-variation-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro two-way-packet-loss?                 decimal64
       |  +--ro two-way-packet-loss-normality?
       |          te-types:performance-metrics-normality
       +--rw throttle {te-performance-metric}?
          +--rw one-way-delay-offset?                  uint32
          +--rw measure-interval?                      uint32
          +--rw advertisement-interval?                uint32
          +--rw suppression-interval?                  uint32
          +--rw threshold-out
          |  +--rw one-way-delay?                 uint32
          |  +--rw one-way-residual-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--rw one-way-available-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--rw one-way-utilized-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--rw two-way-delay?                 uint32
          |  +--rw one-way-min-delay?             uint32



Liu, et al.             Expires November 7, 2020               [Page 20]


Internet-Draft             YANG L3 TE Topology                  May 2020


          |  +--rw one-way-max-delay?             uint32
          |  +--rw one-way-delay-variation?       uint32
          |  +--rw one-way-packet-loss?           decimal64
          |  +--rw two-way-min-delay?             uint32
          |  +--rw two-way-max-delay?             uint32
          |  +--rw two-way-delay-variation?       uint32
          |  +--rw two-way-packet-loss?           decimal64
          +--rw threshold-in
          |  +--rw one-way-delay?                 uint32
          |  +--rw one-way-residual-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--rw one-way-available-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--rw one-way-utilized-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--rw two-way-delay?                 uint32
          |  +--rw one-way-min-delay?             uint32
          |  +--rw one-way-max-delay?             uint32
          |  +--rw one-way-delay-variation?       uint32
          |  +--rw one-way-packet-loss?           decimal64
          |  +--rw two-way-min-delay?             uint32
          |  +--rw two-way-max-delay?             uint32
          |  +--rw two-way-delay-variation?       uint32
          |  +--rw two-way-packet-loss?           decimal64
          +--rw threshold-accelerated-advertisement
             +--rw one-way-delay?                 uint32
             +--rw one-way-residual-bandwidth?
             |       rt-types:bandwidth-ieee-float32
             +--rw one-way-available-bandwidth?
             |       rt-types:bandwidth-ieee-float32
             +--rw one-way-utilized-bandwidth?
             |       rt-types:bandwidth-ieee-float32
             +--rw two-way-delay?                 uint32
             +--rw one-way-min-delay?             uint32
             +--rw one-way-max-delay?             uint32
             +--rw one-way-delay-variation?       uint32
             +--rw one-way-packet-loss?           decimal64
             +--rw two-way-min-delay?             uint32
             +--rw two-way-max-delay?             uint32
             +--rw two-way-delay-variation?       uint32
             +--rw two-way-packet-loss?           decimal64
     augment /nw:networks/tet:te/tet:templates/tet:link-template
               /tet:te-link-attributes:
       +--ro performance-metrics-one-way {te-performance-metric}?
       |  +--ro one-way-delay?                           uint32
       |  +--ro one-way-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-residual-bandwidth?



Liu, et al.             Expires November 7, 2020               [Page 21]


Internet-Draft             YANG L3 TE Topology                  May 2020


       |  |       rt-types:bandwidth-ieee-float32
       |  +--ro one-way-residual-bandwidth-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-available-bandwidth?
       |  |       rt-types:bandwidth-ieee-float32
       |  +--ro one-way-available-bandwidth-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-utilized-bandwidth?
       |  |       rt-types:bandwidth-ieee-float32
       |  +--ro one-way-utilized-bandwidth-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-min-delay?                       uint32
       |  +--ro one-way-min-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-max-delay?                       uint32
       |  +--ro one-way-max-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-delay-variation?                 uint32
       |  +--ro one-way-delay-variation-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-packet-loss?                     decimal64
       |  +--ro one-way-packet-loss-normality?
       |          te-types:performance-metrics-normality
       +--ro performance-metrics-two-way {te-performance-metric}?
       |  +--ro two-way-delay?                       uint32
       |  +--ro two-way-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro two-way-min-delay?                   uint32
       |  +--ro two-way-min-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro two-way-max-delay?                   uint32
       |  +--ro two-way-max-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro two-way-delay-variation?             uint32
       |  +--ro two-way-delay-variation-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro two-way-packet-loss?                 decimal64
       |  +--ro two-way-packet-loss-normality?
       |          te-types:performance-metrics-normality
       +--rw throttle {te-performance-metric}?
          +--rw one-way-delay-offset?                  uint32
          +--rw measure-interval?                      uint32
          +--rw advertisement-interval?                uint32
          +--rw suppression-interval?                  uint32
          +--rw threshold-out
          |  +--rw one-way-delay?                 uint32
          |  +--rw one-way-residual-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32



Liu, et al.             Expires November 7, 2020               [Page 22]


Internet-Draft             YANG L3 TE Topology                  May 2020


          |  +--rw one-way-available-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--rw one-way-utilized-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--rw two-way-delay?                 uint32
          |  +--rw one-way-min-delay?             uint32
          |  +--rw one-way-max-delay?             uint32
          |  +--rw one-way-delay-variation?       uint32
          |  +--rw one-way-packet-loss?           decimal64
          |  +--rw two-way-min-delay?             uint32
          |  +--rw two-way-max-delay?             uint32
          |  +--rw two-way-delay-variation?       uint32
          |  +--rw two-way-packet-loss?           decimal64
          +--rw threshold-in
          |  +--rw one-way-delay?                 uint32
          |  +--rw one-way-residual-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--rw one-way-available-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--rw one-way-utilized-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--rw two-way-delay?                 uint32
          |  +--rw one-way-min-delay?             uint32
          |  +--rw one-way-max-delay?             uint32
          |  +--rw one-way-delay-variation?       uint32
          |  +--rw one-way-packet-loss?           decimal64
          |  +--rw two-way-min-delay?             uint32
          |  +--rw two-way-max-delay?             uint32
          |  +--rw two-way-delay-variation?       uint32
          |  +--rw two-way-packet-loss?           decimal64
          +--rw threshold-accelerated-advertisement
             +--rw one-way-delay?                 uint32
             +--rw one-way-residual-bandwidth?
             |       rt-types:bandwidth-ieee-float32
             +--rw one-way-available-bandwidth?
             |       rt-types:bandwidth-ieee-float32
             +--rw one-way-utilized-bandwidth?
             |       rt-types:bandwidth-ieee-float32
             +--rw two-way-delay?                 uint32
             +--rw one-way-min-delay?             uint32
             +--rw one-way-max-delay?             uint32
             +--rw one-way-delay-variation?       uint32
             +--rw one-way-packet-loss?           decimal64
             +--rw two-way-min-delay?             uint32
             +--rw two-way-max-delay?             uint32
             +--rw two-way-delay-variation?       uint32
             +--rw two-way-packet-loss?           decimal64
     augment /nw:networks/nw:network/nt:link/tet:te



Liu, et al.             Expires November 7, 2020               [Page 23]


Internet-Draft             YANG L3 TE Topology                  May 2020


               /tet:te-link-attributes:
       +--ro performance-metrics-one-way {te-performance-metric}?
       |  +--ro one-way-delay?                           uint32
       |  +--ro one-way-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-residual-bandwidth?
       |  |       rt-types:bandwidth-ieee-float32
       |  +--ro one-way-residual-bandwidth-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-available-bandwidth?
       |  |       rt-types:bandwidth-ieee-float32
       |  +--ro one-way-available-bandwidth-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-utilized-bandwidth?
       |  |       rt-types:bandwidth-ieee-float32
       |  +--ro one-way-utilized-bandwidth-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-min-delay?                       uint32
       |  +--ro one-way-min-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-max-delay?                       uint32
       |  +--ro one-way-max-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-delay-variation?                 uint32
       |  +--ro one-way-delay-variation-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-packet-loss?                     decimal64
       |  +--ro one-way-packet-loss-normality?
       |          te-types:performance-metrics-normality
       +--ro performance-metrics-two-way {te-performance-metric}?
       |  +--ro two-way-delay?                       uint32
       |  +--ro two-way-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro two-way-min-delay?                   uint32
       |  +--ro two-way-min-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro two-way-max-delay?                   uint32
       |  +--ro two-way-max-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro two-way-delay-variation?             uint32
       |  +--ro two-way-delay-variation-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro two-way-packet-loss?                 decimal64
       |  +--ro two-way-packet-loss-normality?
       |          te-types:performance-metrics-normality
       +--rw throttle {te-performance-metric}?
          +--rw one-way-delay-offset?                  uint32
          +--rw measure-interval?                      uint32



Liu, et al.             Expires November 7, 2020               [Page 24]


Internet-Draft             YANG L3 TE Topology                  May 2020


          +--rw advertisement-interval?                uint32
          +--rw suppression-interval?                  uint32
          +--rw threshold-out
          |  +--rw one-way-delay?                 uint32
          |  +--rw one-way-residual-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--rw one-way-available-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--rw one-way-utilized-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--rw two-way-delay?                 uint32
          |  +--rw one-way-min-delay?             uint32
          |  +--rw one-way-max-delay?             uint32
          |  +--rw one-way-delay-variation?       uint32
          |  +--rw one-way-packet-loss?           decimal64
          |  +--rw two-way-min-delay?             uint32
          |  +--rw two-way-max-delay?             uint32
          |  +--rw two-way-delay-variation?       uint32
          |  +--rw two-way-packet-loss?           decimal64
          +--rw threshold-in
          |  +--rw one-way-delay?                 uint32
          |  +--rw one-way-residual-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--rw one-way-available-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--rw one-way-utilized-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--rw two-way-delay?                 uint32
          |  +--rw one-way-min-delay?             uint32
          |  +--rw one-way-max-delay?             uint32
          |  +--rw one-way-delay-variation?       uint32
          |  +--rw one-way-packet-loss?           decimal64
          |  +--rw two-way-min-delay?             uint32
          |  +--rw two-way-max-delay?             uint32
          |  +--rw two-way-delay-variation?       uint32
          |  +--rw two-way-packet-loss?           decimal64
          +--rw threshold-accelerated-advertisement
             +--rw one-way-delay?                 uint32
             +--rw one-way-residual-bandwidth?
             |       rt-types:bandwidth-ieee-float32
             +--rw one-way-available-bandwidth?
             |       rt-types:bandwidth-ieee-float32
             +--rw one-way-utilized-bandwidth?
             |       rt-types:bandwidth-ieee-float32
             +--rw two-way-delay?                 uint32
             +--rw one-way-min-delay?             uint32
             +--rw one-way-max-delay?             uint32
             +--rw one-way-delay-variation?       uint32



Liu, et al.             Expires November 7, 2020               [Page 25]


Internet-Draft             YANG L3 TE Topology                  May 2020


             +--rw one-way-packet-loss?           decimal64
             +--rw two-way-min-delay?             uint32
             +--rw two-way-max-delay?             uint32
             +--rw two-way-delay-variation?       uint32
             +--rw two-way-packet-loss?           decimal64
     augment /nw:networks/nw:network/nt:link/tet:te
               /tet:information-source-entry:
       +--ro performance-metrics-one-way {te-performance-metric}?
       |  +--ro one-way-delay?                           uint32
       |  +--ro one-way-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-residual-bandwidth?
       |  |       rt-types:bandwidth-ieee-float32
       |  +--ro one-way-residual-bandwidth-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-available-bandwidth?
       |  |       rt-types:bandwidth-ieee-float32
       |  +--ro one-way-available-bandwidth-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-utilized-bandwidth?
       |  |       rt-types:bandwidth-ieee-float32
       |  +--ro one-way-utilized-bandwidth-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-min-delay?                       uint32
       |  +--ro one-way-min-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-max-delay?                       uint32
       |  +--ro one-way-max-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-delay-variation?                 uint32
       |  +--ro one-way-delay-variation-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro one-way-packet-loss?                     decimal64
       |  +--ro one-way-packet-loss-normality?
       |          te-types:performance-metrics-normality
       +--ro performance-metrics-two-way {te-performance-metric}?
       |  +--ro two-way-delay?                       uint32
       |  +--ro two-way-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro two-way-min-delay?                   uint32
       |  +--ro two-way-min-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro two-way-max-delay?                   uint32
       |  +--ro two-way-max-delay-normality?
       |  |       te-types:performance-metrics-normality
       |  +--ro two-way-delay-variation?             uint32
       |  +--ro two-way-delay-variation-normality?
       |  |       te-types:performance-metrics-normality



Liu, et al.             Expires November 7, 2020               [Page 26]


Internet-Draft             YANG L3 TE Topology                  May 2020


       |  +--ro two-way-packet-loss?                 decimal64
       |  +--ro two-way-packet-loss-normality?
       |          te-types:performance-metrics-normality
       +--ro throttle {te-performance-metric}?
          +--ro one-way-delay-offset?                  uint32
          +--ro measure-interval?                      uint32
          +--ro advertisement-interval?                uint32
          +--ro suppression-interval?                  uint32
          +--ro threshold-out
          |  +--ro one-way-delay?                 uint32
          |  +--ro one-way-residual-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--ro one-way-available-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--ro one-way-utilized-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--ro two-way-delay?                 uint32
          |  +--ro one-way-min-delay?             uint32
          |  +--ro one-way-max-delay?             uint32
          |  +--ro one-way-delay-variation?       uint32
          |  +--ro one-way-packet-loss?           decimal64
          |  +--ro two-way-min-delay?             uint32
          |  +--ro two-way-max-delay?             uint32
          |  +--ro two-way-delay-variation?       uint32
          |  +--ro two-way-packet-loss?           decimal64
          +--ro threshold-in
          |  +--ro one-way-delay?                 uint32
          |  +--ro one-way-residual-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--ro one-way-available-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--ro one-way-utilized-bandwidth?
          |  |       rt-types:bandwidth-ieee-float32
          |  +--ro two-way-delay?                 uint32
          |  +--ro one-way-min-delay?             uint32
          |  +--ro one-way-max-delay?             uint32
          |  +--ro one-way-delay-variation?       uint32
          |  +--ro one-way-packet-loss?           decimal64
          |  +--ro two-way-min-delay?             uint32
          |  +--ro two-way-max-delay?             uint32
          |  +--ro two-way-delay-variation?       uint32
          |  +--ro two-way-packet-loss?           decimal64
          +--ro threshold-accelerated-advertisement
             +--ro one-way-delay?                 uint32
             +--ro one-way-residual-bandwidth?
             |       rt-types:bandwidth-ieee-float32
             +--ro one-way-available-bandwidth?
             |       rt-types:bandwidth-ieee-float32



Liu, et al.             Expires November 7, 2020               [Page 27]


Internet-Draft             YANG L3 TE Topology                  May 2020


             +--ro one-way-utilized-bandwidth?
             |       rt-types:bandwidth-ieee-float32
             +--ro two-way-delay?                 uint32
             +--ro one-way-min-delay?             uint32
             +--ro one-way-max-delay?             uint32
             +--ro one-way-delay-variation?       uint32
             +--ro one-way-packet-loss?           decimal64
             +--ro two-way-min-delay?             uint32
             +--ro two-way-max-delay?             uint32
             +--ro two-way-delay-variation?       uint32
             +--ro two-way-packet-loss?           decimal64
     augment /nw:networks/tet:te/tet:templates/tet:link-template
               /tet:te-link-attributes
               /tet:interface-switching-capability:
       +--rw packet-switch-capable
          +--rw minimum-lsp-bandwidth?   rt-types:bandwidth-ieee-float32
          +--rw interface-mtu?           uint16
     augment /nw:networks/nw:network/nt:link/tet:te
               /tet:te-link-attributes
               /tet:interface-switching-capability:
       +--rw packet-switch-capable
          +--rw minimum-lsp-bandwidth?   rt-types:bandwidth-ieee-float32
          +--rw interface-mtu?           uint16
     augment /nw:networks/nw:network/nt:link/tet:te
               /tet:information-source-entry
               /tet:interface-switching-capability:
       +--ro packet-switch-capable
          +--ro minimum-lsp-bandwidth?   rt-types:bandwidth-ieee-float32
          +--ro interface-mtu?           uint16



5.  YANG Modules

5.1.  Layer 3 TE Topology Module

   This module references [RFC8345], [RFC8346], and
   [I-D.ietf-teas-yang-te-topo].


   <CODE BEGINS> file "ietf-l3-te-topology@2020-05-03.yang"
   module ietf-l3-te-topology {
     yang-version 1.1;
     namespace "urn:ietf:params:xml:ns:yang:ietf-l3-te-topology";
     prefix "l3tet";

     import ietf-network {
       prefix "nw";



Liu, et al.             Expires November 7, 2020               [Page 28]


Internet-Draft             YANG L3 TE Topology                  May 2020


       reference "RFC 8345: A YANG Data Model for Network Topologies";
     }
     import ietf-network-topology {
       prefix "nt";
       reference "RFC 8345: A YANG Data Model for Network Topologies";
     }
     import ietf-l3-unicast-topology {
       prefix "l3t";
       reference "RFC 8346: A YANG Data Model for Layer 3 Topologies";
     }
     import ietf-te-topology {
       prefix "tet";
       reference
         "I-D.ietf-teas-yang-te-topo: YANG Data Model for Traffic
          Engineering (TE) Topologies";
     }

     organization
       "IETF Traffic Engineering Architecture and Signaling (TEAS)
        Working Group";

     contact
       "WG Web:   <http://tools.ietf.org/wg/teas/>
        WG List:  <mailto:teas@ietf.org>

        Editor:   Xufeng Liu
                  <mailto:xufeng.liu.ietf@gmail.com>

        Editor:   Igor Bryskin
                  <mailto:Igor.Bryskin@huawei.com>

        Editor:   Vishnu Pavan Beeram
                  <mailto:vbeeram@juniper.net>

        Editor:   Tarek Saad
                  <mailto:tsaad@cisco.com>

        Editor:   Himanshu Shah
                  <mailto:hshah@ciena.com>

        Editor:   Oscar Gonzalez De Dios
                  <mailto:oscar.gonzalezdedios@telefonica.com>";

     description
       "YANG data model for representing and manipulating Layer 3 TE
        Topologies.

        Copyright (c) 2018 IETF Trust and the persons identified as



Liu, et al.             Expires November 7, 2020               [Page 29]


Internet-Draft             YANG L3 TE Topology                  May 2020


        authors of the code.  All rights reserved.

        Redistribution and use in source and binary forms, with or
        without modification, is permitted pursuant to, and subject to
        the license terms contained in, the Simplified BSD License set
        forth in Section 4.c of the IETF Trust's Legal Provisions
        Relating to IETF Documents
        (http://trustee.ietf.org/license-info).

        This version of this YANG module is part of RFC XXXX; see the
        RFC itself for full legal notices.";

     revision 2020-05-03 {

       description
         "Initial revision";
       reference "RFC XXXX: YANG Data Model for Layer 3 TE Topologies";
     }

     grouping l3-te-topology-type {
       description
         "Identifies the L3 TE topology type.";
       container l3-te {
         presence "Indicates L3 TE Topology";
         description
           "Its presence identifies the L3 TE topology type.";
       }
     }

     augment "/nw:networks/nw:network/nw:network-types/"
       + "l3t:l3-unicast-topology" {
       description
         "Defines the L3 TE topology type.";
       uses l3-te-topology-type;
     }

     augment "/nw:networks/nw:network/l3t:l3-topology-attributes" {
       when "../nw:network-types/l3t:l3-unicast-topology/l3tet:l3-te" {
         description
           "Augment only for L3 TE topology";
       }
       description
         "Augment topology configuration";
       uses l3-te-topology-attributes;
     }

     augment "/nw:networks/nw:network/nw:node/l3t:l3-node-attributes" {
       when "../../nw:network-types/l3t:l3-unicast-topology/"



Liu, et al.             Expires November 7, 2020               [Page 30]


Internet-Draft             YANG L3 TE Topology                  May 2020


         + "l3tet:l3-te" {
         description
           "Augment only for L3 TE topology";
       }
       description
         "Augment node configuration";
       uses l3-te-node-attributes;
     }

     augment "/nw:networks/nw:network/nw:node/nt:termination-point/"
       + "l3t:l3-termination-point-attributes" {
       when "../../../nw:network-types/l3t:l3-unicast-topology/"
         + "l3tet:l3-te" {
         description
           "Augment only for L3 TE topology";
       }
       description
         "Augment termination point configuration";
       uses l3-te-tp-attributes;
     }

     augment "/nw:networks/nw:network/nt:link/l3t:l3-link-attributes" {
       when "../../nw:network-types/l3t:l3-unicast-topology/"
         + "l3tet:l3-te" {
         description
           "Augment only for L3 TE topology";
       }
       description
         "Augment link configuration";
       uses l3-te-link-attributes;
     }

     grouping l3-te-topology-attributes {
       description
         "L3 TE topology scope attributes";
       container l3-te-topology-attributes {
         must "/nw:networks/nw:network"
           + "[nw:network-id = current()/network-ref]/nw:network-types/"
           + "tet:te-topology" {
           error-message
             "The referenced network must be a TE topology.";
           description
             "The referenced network must be a TE topology.";
         }
         description
           "Containing TE topology references";
         uses nw:network-ref;
       } // l3-te-topology-attributes



Liu, et al.             Expires November 7, 2020               [Page 31]


Internet-Draft             YANG L3 TE Topology                  May 2020


     } // l3-te-topology-attributes

     grouping l3-te-node-attributes {
       description
         "L3 TE node scope attributes";
       container l3-te-node-attributes {
         must "/nw:networks/nw:network"
           + "[nw:network-id = current()/network-ref]/nw:network-types/"
           + "tet:te-topology" {
           error-message
             "The referenced network must be a TE topology.";
           description
             "The referenced network must be a TE topology.";
         }
         description
           "Containing TE node references";
         uses nw:node-ref;
       } // l3-te
     } // l3-te-node-attributes

     grouping l3-te-tp-attributes {
       description
         "L3 TE termination point scope attributes";
       container l3-te-tp-attributes {
         must "/nw:networks/nw:network"
           + "[nw:network-id = current()/network-ref]/nw:network-types/"
           + "tet:te-topology" {
           error-message
             "The referenced network must be a TE topology.";
           description
             "The referenced network must be a TE topology.";
         }
         description
           "Containing TE termination point references";
         uses nt:tp-ref;
       } // l3-te
     } // l3-te-tp-attributes

     grouping l3-te-link-attributes {
       description
         "L3 TE link scope attributes";
       container l3-te-link-attributes {
         must "/nw:networks/nw:network"
           + "[nw:network-id = current()/network-ref]/nw:network-types/"
           + "tet:te-topology" {
           error-message
             "The referenced network must be a TE topology.";
           description



Liu, et al.             Expires November 7, 2020               [Page 32]


Internet-Draft             YANG L3 TE Topology                  May 2020


             "The referenced network must be a TE topology.";
         }
         description
           "Containing TE link references";
         uses nt:link-ref;
       }
     } // l3-te-link-attributes
   }
   <CODE ENDS>



5.2.  Packet Switching TE Topology Module

   This module references [RFC7471], [RFC7823], [RFC8294], [RFC8345],
   [RFC8346].  [RFC8570], [I-D.ietf-teas-yang-te-types], and
   [I-D.ietf-teas-yang-te-topo].


   <CODE BEGINS> file "ietf-te-topology-packet@2019-06-28.yang"
   module ietf-te-topology-packet {
     yang-version 1.1;
     namespace "urn:ietf:params:xml:ns:yang:ietf-te-topology-packet";

     prefix "tet-pkt";

     import ietf-network {
       prefix "nw";
       reference
         "RFC 8345: A YANG Data Model for Network Topologies";
     }

     import ietf-network-topology {
       prefix "nt";
       reference
         "RFC 8345: A YANG Data Model for Network Topologies";
     }

     import ietf-routing-types {
       prefix "rt-types";
       reference
         "RFC 8294: Common YANG Data Types for the Routing Area";
     }

     import ietf-te-topology {
       prefix "tet";
       reference
         "I-D.ietf-teas-yang-te-topo: YANG Data Model for Traffic



Liu, et al.             Expires November 7, 2020               [Page 33]


Internet-Draft             YANG L3 TE Topology                  May 2020


          Engineering (TE) Topologies";
     }

     import ietf-te-types {
       prefix "te-types";
       reference
         "I-D.ietf-teas-yang-te-types: Traffic Engineering Common YANG
          Types";
     }

     import ietf-te-packet-types {
       prefix "te-packet-types";
       reference
         "I-D.ietf-teas-yang-te-types: Traffic Engineering Common YANG
          Types";
     }

     organization
       "Traffic Engineering Architecture and Signaling (TEAS)
        Working Group";

     contact
       "WG Web:   <http://tools.ietf.org/wg/teas/>
        WG List:  <mailto:teas@ietf.org>

        Editor:   Xufeng Liu
                  <mailto:xufeng.liu.ietf@gmail.com>

        Editor:   Igor Bryskin
                  <mailto:Igor.Bryskin@huawei.com>

        Editor:   Vishnu Pavan Beeram
                  <mailto:vbeeram@juniper.net>

        Editor:   Tarek Saad
                  <mailto:tsaad@cisco.com>

        Editor:   Himanshu Shah
                  <mailto:hshah@ciena.com>

        Editor:   Oscar Gonzalez De Dios
                  <mailto:oscar.gonzalezdedios@telefonica.com>";

     description
       "YANG data model for representing and manipulating PSC (Packet
        Switching) TE Topologies.

        Copyright (c) 2018 IETF Trust and the persons identified as



Liu, et al.             Expires November 7, 2020               [Page 34]


Internet-Draft             YANG L3 TE Topology                  May 2020


        authors of the code.  All rights reserved.

        Redistribution and use in source and binary forms, with or
        without modification, is permitted pursuant to, and subject to
        the license terms contained in, the Simplified BSD License set
        forth in Section 4.c of the IETF Trust's Legal Provisions
        Relating to IETF Documents
        (http://trustee.ietf.org/license-info).

        This version of this YANG module is part of RFC XXXX; see the
        RFC itself for full legal notices.";

     revision 2019-06-28 {
       description
         "Initial revision";
       reference
         "RFC XXXX: YANG Data Model for Layer 3 TE Topologies";
     }

     /*
      * Features
      */

     feature te-performance-metric {
       description
         "This feature indicates that the system supports
          TE performance metric.";
       reference
         "RFC7471: OSPF Traffic Engineering (TE) Metric Extensions.
          RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions.
          RFC7823: Performance-Based Path Selection for Explicitly
          Routed Label Switched Paths (LSPs) Using TE Metric
          Extensions";
     }

     /*
      * Groupings
      */
     grouping packet-switch-capable-container {
       description
         "The container of packet switch capable attributes.";
       container packet-switch-capable {
         description
           "Interface has packet-switching capabilities.";
         leaf minimum-lsp-bandwidth {
           type rt-types:bandwidth-ieee-float32;
           description
             "Minimum LSP Bandwidth. Units in bytes per second";



Liu, et al.             Expires November 7, 2020               [Page 35]


Internet-Draft             YANG L3 TE Topology                  May 2020


         }
         leaf interface-mtu {
           type uint16;
           description
             "Interface MTU.";
         }
       }
     }

     /*
      * Augmentations
      */
     /* Augmentations to connectivity-matrix */
     augment "/nw:networks/nw:network/nw:node/tet:te/"
       + "tet:te-node-attributes/tet:connectivity-matrices" {
       description
         "Parameters for PSC TE topology.";
       uses te-packet-types:performance-metrics-attributes-packet {
         if-feature te-performance-metric;
         refine performance-metrics-one-way {
           config false;
         }
         refine performance-metrics-two-way {
           config false;
         }
       }
       uses
         te-packet-types:performance-metrics-throttle-container-packet {
         if-feature te-performance-metric;
       }
     }

     augment "/nw:networks/nw:network/nw:node/tet:te/"
           + "tet:te-node-attributes/tet:connectivity-matrices/"
           + "tet:connectivity-matrix" {
       description
         "Parameters for PSC TE topology.";
       uses te-packet-types:performance-metrics-attributes-packet {
         if-feature te-performance-metric;
         refine performance-metrics-one-way {
           config false;
         }
         refine performance-metrics-two-way {
           config false;
         }
       }
       uses
         te-packet-types:performance-metrics-throttle-container-packet {



Liu, et al.             Expires November 7, 2020               [Page 36]


Internet-Draft             YANG L3 TE Topology                  May 2020


         if-feature te-performance-metric;
       }
     }

     augment "/nw:networks/nw:network/nw:node/tet:te/"
           + "tet:information-source-entry/tet:connectivity-matrices" {
       description
         "Parameters for PSC TE topology.";
       uses te-packet-types:performance-metrics-attributes-packet {
         if-feature te-performance-metric;
       }
       uses
         te-packet-types:performance-metrics-throttle-container-packet {
         if-feature te-performance-metric;
       }
     }

     augment "/nw:networks/nw:network/nw:node/tet:te/"
           + "tet:information-source-entry/tet:connectivity-matrices/"
           + "tet:connectivity-matrix" {
       description
         "Parameters for PSC TE topology.";
       uses te-packet-types:performance-metrics-attributes-packet {
         if-feature te-performance-metric;
       }
       uses
         te-packet-types:performance-metrics-throttle-container-packet {
         if-feature te-performance-metric;
       }
     }

     /* Augmentations to tunnel-termination-point */
     augment "/nw:networks/nw:network/nw:node/tet:te/"
           + "tet:tunnel-termination-point/"
           + "tet:local-link-connectivities" {
       description
         "Parameters for PSC TE topology.";
       uses te-packet-types:performance-metrics-attributes-packet {
         if-feature te-performance-metric;
         refine performance-metrics-one-way {
           config false;
         }
         refine performance-metrics-two-way {
           config false;
         }
       }
       uses
         te-packet-types:performance-metrics-throttle-container-packet {



Liu, et al.             Expires November 7, 2020               [Page 37]


Internet-Draft             YANG L3 TE Topology                  May 2020


         if-feature te-performance-metric;
       }
     }

     augment "/nw:networks/nw:network/nw:node/tet:te/"
           + "tet:tunnel-termination-point/"
           + "tet:local-link-connectivities/"
           + "tet:local-link-connectivity" {
       description
         "Parameters for PSC TE topology.";
       uses te-packet-types:performance-metrics-attributes-packet {
         if-feature te-performance-metric;
         refine performance-metrics-one-way {
           config false;
         }
         refine performance-metrics-two-way {
           config false;
         }
       }
       uses
         te-packet-types:performance-metrics-throttle-container-packet {
         if-feature te-performance-metric;
       }
     }

     /* Augmentations to te-link-attributes */
     augment "/nw:networks/tet:te/tet:templates/"
           + "tet:link-template/tet:te-link-attributes" {
       when "tet:interface-switching-capability "
         + "[tet:switching-capability = 'te-types:switching-psc1']" {
         description
           "Valid only for PSC";
       }
       description
         "Parameters for PSC TE topology.";
       uses te-packet-types:performance-metrics-attributes-packet {
         if-feature te-performance-metric;
         refine performance-metrics-one-way {
           config false;
         }
         refine performance-metrics-two-way {
           config false;
         }
       }
       uses
         te-packet-types:performance-metrics-throttle-container-packet {
         if-feature te-performance-metric;
       }



Liu, et al.             Expires November 7, 2020               [Page 38]


Internet-Draft             YANG L3 TE Topology                  May 2020


     }

     augment "/nw:networks/nw:network/nt:link/tet:te/"
           + "tet:te-link-attributes" {
       when "tet:interface-switching-capability "
         + "[tet:switching-capability = 'te-types:switching-psc1']" {
         description
           "Valid only for PSC";
       }
       description
         "Parameters for PSC TE topology.";
       uses te-packet-types:performance-metrics-attributes-packet {
         if-feature te-performance-metric;
         refine performance-metrics-one-way {
           config false;
         }
         refine performance-metrics-two-way {
           config false;
         }
       }
       uses
         te-packet-types:performance-metrics-throttle-container-packet {
         if-feature te-performance-metric;
       }
     }

     augment "/nw:networks/nw:network/nt:link/tet:te/"
           + "tet:information-source-entry" {
       when "tet:interface-switching-capability "
         + "[tet:switching-capability = 'te-types:switching-psc1']" {
         description
           "Valid only for PSC";
       }
       description
         "Parameters for PSC TE topology.";
       uses te-packet-types:performance-metrics-attributes-packet {
         if-feature te-performance-metric;
       }
       uses
         te-packet-types:performance-metrics-throttle-container-packet {
         if-feature te-performance-metric;
       }
     }

     /* Augmentations to interface-switching-capability */
     augment "/nw:networks/tet:te/tet:templates/"
           + "tet:link-template/tet:te-link-attributes/"
           + "tet:interface-switching-capability" {



Liu, et al.             Expires November 7, 2020               [Page 39]


Internet-Draft             YANG L3 TE Topology                  May 2020


       when "tet:switching-capability = 'te-types:switching-psc1' " {
         description
           "Valid only for PSC";
       }
       description
         "Parameters for PSC TE topology.";
       uses packet-switch-capable-container;
     }

     augment "/nw:networks/nw:network/nt:link/tet:te/"
           + "tet:te-link-attributes/"
           + "tet:interface-switching-capability" {
       when "tet:switching-capability = 'te-types:switching-psc1' " {
         description
           "Valid only for PSC";
       }
       description
         "Parameters for PSC TE topology.";
       uses packet-switch-capable-container;
     }

     augment "/nw:networks/nw:network/nt:link/tet:te/"
           + "tet:information-source-entry/"
           + "tet:interface-switching-capability" {
       when "tet:switching-capability = 'te-types:switching-psc1' " {
         description
           "Valid only for PSC";
       }
       description
         "Parameters for PSC TE topology.";
       uses packet-switch-capable-container;
     }
   }
   <CODE ENDS>



6.  IANA Considerations

   RFC Ed.: In this section, replace all occurrences of 'XXXX' with the
   actual RFC number (and remove this note).

   This document registers the following namespace URIs in the IETF XML
   registry [RFC3688]:







Liu, et al.             Expires November 7, 2020               [Page 40]


Internet-Draft             YANG L3 TE Topology                  May 2020


   --------------------------------------------------------------------
   URI: urn:ietf:params:xml:ns:yang:ietf-l3-te-topology
   Registrant Contact: The IESG.
   XML: N/A, the requested URI is an XML namespace.
   --------------------------------------------------------------------

   --------------------------------------------------------------------
   URI: urn:ietf:params:xml:ns:yang:ietf-l3-te-topology-state
   Registrant Contact: The IESG.
   XML: N/A, the requested URI is an XML namespace.
   --------------------------------------------------------------------

   --------------------------------------------------------------------
   URI: urn:ietf:params:xml:ns:yang:ietf-te-topology-packet
   Registrant Contact: The IESG.
   XML: N/A, the requested URI is an XML namespace.
   --------------------------------------------------------------------

   --------------------------------------------------------------------
   URI: urn:ietf:params:xml:ns:yang:ietf-te-topology-packet-state
   Registrant Contact: The IESG.
   XML: N/A, the requested URI is an XML namespace.
   --------------------------------------------------------------------

   This document registers the following YANG modules in the YANG Module
   Names registry [RFC6020]:

   --------------------------------------------------------------------
   name:         ietf-l3-te-topology
   namespace:    urn:ietf:params:xml:ns:yang:ietf-l3-te-topology
   prefix:       l3te
   reference:    RFC XXXX
   --------------------------------------------------------------------

   --------------------------------------------------------------------
   name:         ietf-l3-te-topology-state
   namespace:    urn:ietf:params:xml:ns:yang:ietf-l3-te-topology-state
   prefix:       l3te-s
   reference:    RFC XXXX
   --------------------------------------------------------------------

   --------------------------------------------------------------------
   name:         ietf-te-topology-packet
   namespace:    urn:ietf:params:xml:ns:yang:ietf-te-topology-packet
   prefix:       tet-pkt
   reference:    RFC XXXX
   --------------------------------------------------------------------




Liu, et al.             Expires November 7, 2020               [Page 41]


Internet-Draft             YANG L3 TE Topology                  May 2020


   --------------------------------------------------------------------
   name:         ietf-te-topology-packet-state
   namespace:  urn:ietf:params:xml:ns:yang:ietf-te-topology-packet-state
   prefix:       tet-pkt-s
   reference:    RFC XXXX
   --------------------------------------------------------------------

7.  Security Considerations

   The YANG module specified in this document defines a schema for data
   that is designed to be accessed via network management protocols such
   as NETCONF [RFC6241] or RESTCONF [RFC8040].  The lowest NETCONF layer
   is the secure transport layer, and the mandatory-to-implement secure
   transport is Secure Shell (SSH) [RFC6242].  The lowest RESTCONF layer
   is HTTPS, and the mandatory-to-implement secure transport is TLS
   [RFC8446].

   The Network Configuration Access Control Model (NACM) [RFC8341]
   provides the means to restrict access for particular NETCONF or
   RESTCONF users to a preconfigured subset of all available NETCONF or
   RESTCONF protocol operations and content.

   There are a number of data nodes defined in this YANG module that are
   writable/creatable/deletable (i.e., config true, which is the
   default).  These data nodes may be considered sensitive or vulnerable
   in some network environments.  Write operations (e.g., edit-config)
   to these data nodes without proper protection can have a negative
   effect on network operations.  These are the subtrees and data nodes
   and their sensitivity/vulnerability:

   /nw:networks/nw:network/nw:network-types/l3t:l3-unicast-topology/
   l3-te
      This subtree specifies the layer 3 TE topology type.  Modifying
      the configurations can make layer 3 TE topology type invalid and
      cause interruption to all layer 3 TE networks.

   /nw:networks/nw:network/l3t:l3-topology-attributes/l3-te-topology-
   attributes
      This subtree specifies the topology-wide configurations, including
      the reference to a TE topology from a layer 3 topology.  Modifying
      the configurations here can cause traffic disabled or rerouted in
      this topology and the connected topologies.

   /nw:networks/nw:network/nw:node/l3t:l3-node-attributes/l3-te-node-
   attributes
      This subtree specifies the configurations of layer 3 TE nodes.
      Modifying the configurations in this subtree can change the
      relationship between a TE node and a layer 3 node, causing traffic



Liu, et al.             Expires November 7, 2020               [Page 42]


Internet-Draft             YANG L3 TE Topology                  May 2020


      disabled or rerouted in the specified nodes and the related layer
      3 topologies.

   /nw:networks/nw:network/nw:node/nt:termination-point//l3t:l3-
   termination-point-attributes/l3-te-tp-attributes
      This subtree specifies the configurations of layer 3 TE link
      termination points.  Modifying the configurations in this subtree
      can change the relationship between a TE link termination point
      and a layer 3 link termination point, causing traffic disabled or
      rerouted on the related layer 3 links and the related layer 3
      topologies.

   /nw:networks/nw:network/nt:link/l3t:l3-link-attributes/l3-te-link-
   attributes
      This subtree specifies the configurations of layer 3 TE links.
      Modifying the configurations in this subtree can change the
      relationship between a TE link and a layer 3 link, causing traffic
      disabled or rerouted on the specified layer 3 link and the related
      layer 3 topologies.

   performance-metric containers
      The container "performance-metric" is augmented to multiple
      locations of the base TE topology model, as specified in
      Section 3.2.  Modifying the configuration in such a container can
      change the behaviors of performance metric monitoring, causing
      traffic disabled or rerouted on the related layer 3 links, nodes,
      or topologies.

   Some of the readable data nodes in this YANG module may be considered
   sensitive or vulnerable in some network environments.  It is thus
   important to control read access (e.g., via get, get-config, or
   notification) to these data nodes.  These are the subtrees and data
   nodes and their sensitivity/vulnerability:

   /nw:networks/nw:network/nw:network-types/l3t:l3-unicast-topology/
   l3-te
      Unauthorized access to this subtree can disclose the layer 3 TE
      topology type.

   /nw:networks/nw:network/l3t:l3-topology-attributes/l3-te-topology-
   attributes
      Unauthorized access to this subtree can disclose the topology-wide
      configurations, including the reference to a TE topology from a
      layer 3 topology.

   /nw:networks/nw:network/nw:node/l3t:l3-node-attributes/l3-te-node-
   attributes




Liu, et al.             Expires November 7, 2020               [Page 43]


Internet-Draft             YANG L3 TE Topology                  May 2020


      Unauthorized access to this subtree can disclose the operational
      state information of layer 3 TE nodes.

   /nw:networks/nw:network/nw:node/nt:termination-point//l3t:l3-
   termination-point-attributes/l3-te-tp-attributes
      Unauthorized access to this subtree can disclose the operational
      state information of layer 3 TE link termination points.

   /nw:networks/nw:network/nt:link/l3t:l3-link-attributes/l3-te-link-
   attributes
      Unauthorized access to this subtree can disclose the operational
      state information of layer 3 TE links.

   performance-metric containers
      The container "performance-metric" is augmented to multiple
      locations of the base TE topology model, as specified in
      Section 3.2.  Unauthorized access to this subtree can disclose the
      operational state information of performance metric monitoring.

8.  References

8.1.  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <https://www.rfc-editor.org/info/rfc2119>.

   [RFC3471]  Berger, L., Ed., "Generalized Multi-Protocol Label
              Switching (GMPLS) Signaling Functional Description",
              RFC 3471, DOI 10.17487/RFC3471, January 2003,
              <https://www.rfc-editor.org/info/rfc3471>.

   [RFC3688]  Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
              DOI 10.17487/RFC3688, January 2004,
              <https://www.rfc-editor.org/info/rfc3688>.

   [RFC6020]  Bjorklund, M., Ed., "YANG - A Data Modeling Language for
              the Network Configuration Protocol (NETCONF)", RFC 6020,
              DOI 10.17487/RFC6020, October 2010,
              <https://www.rfc-editor.org/info/rfc6020>.

   [RFC6241]  Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
              and A. Bierman, Ed., "Network Configuration Protocol
              (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
              <https://www.rfc-editor.org/info/rfc6241>.





Liu, et al.             Expires November 7, 2020               [Page 44]


Internet-Draft             YANG L3 TE Topology                  May 2020


   [RFC6242]  Wasserman, M., "Using the NETCONF Protocol over Secure
              Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
              <https://www.rfc-editor.org/info/rfc6242>.

   [RFC7074]  Berger, L. and J. Meuric, "Revised Definition of the GMPLS
              Switching Capability and Type Fields", RFC 7074,
              DOI 10.17487/RFC7074, November 2013,
              <https://www.rfc-editor.org/info/rfc7074>.

   [RFC7471]  Giacalone, S., Ward, D., Drake, J., Atlas, A., and S.
              Previdi, "OSPF Traffic Engineering (TE) Metric
              Extensions", RFC 7471, DOI 10.17487/RFC7471, March 2015,
              <https://www.rfc-editor.org/info/rfc7471>.

   [RFC7950]  Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
              RFC 7950, DOI 10.17487/RFC7950, August 2016,
              <https://www.rfc-editor.org/info/rfc7950>.

   [RFC8040]  Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
              Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
              <https://www.rfc-editor.org/info/rfc8040>.

   [RFC8174]  Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
              2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
              May 2017, <https://www.rfc-editor.org/info/rfc8174>.

   [RFC8294]  Liu, X., Qu, Y., Lindem, A., Hopps, C., and L. Berger,
              "Common YANG Data Types for the Routing Area", RFC 8294,
              DOI 10.17487/RFC8294, December 2017,
              <https://www.rfc-editor.org/info/rfc8294>.

   [RFC8341]  Bierman, A. and M. Bjorklund, "Network Configuration
              Access Control Model", STD 91, RFC 8341,
              DOI 10.17487/RFC8341, March 2018,
              <https://www.rfc-editor.org/info/rfc8341>.

   [RFC8342]  Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
              and R. Wilton, "Network Management Datastore Architecture
              (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
              <https://www.rfc-editor.org/info/rfc8342>.

   [RFC8345]  Clemm, A., Medved, J., Varga, R., Bahadur, N.,
              Ananthakrishnan, H., and X. Liu, "A YANG Data Model for
              Network Topologies", RFC 8345, DOI 10.17487/RFC8345, March
              2018, <https://www.rfc-editor.org/info/rfc8345>.






Liu, et al.             Expires November 7, 2020               [Page 45]


Internet-Draft             YANG L3 TE Topology                  May 2020


   [RFC8346]  Clemm, A., Medved, J., Varga, R., Liu, X.,
              Ananthakrishnan, H., and N. Bahadur, "A YANG Data Model
              for Layer 3 Topologies", RFC 8346, DOI 10.17487/RFC8346,
              March 2018, <https://www.rfc-editor.org/info/rfc8346>.

   [RFC8446]  Rescorla, E., "The Transport Layer Security (TLS) Protocol
              Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
              <https://www.rfc-editor.org/info/rfc8446>.

   [RFC8570]  Ginsberg, L., Ed., Previdi, S., Ed., Giacalone, S., Ward,
              D., Drake, J., and Q. Wu, "IS-IS Traffic Engineering (TE)
              Metric Extensions", RFC 8570, DOI 10.17487/RFC8570, March
              2019, <https://www.rfc-editor.org/info/rfc8570>.

   [I-D.ietf-teas-yang-te-types]
              Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin,
              "Traffic Engineering Common YANG Types", draft-ietf-teas-
              yang-te-types-13 (work in progress), November 2019.

   [I-D.ietf-teas-yang-te-topo]
              Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and
              O. Dios, "YANG Data Model for Traffic Engineering (TE)
              Topologies", draft-ietf-teas-yang-te-topo-22 (work in
              progress), June 2019.

8.2.  Informative References

   [RFC7823]  Atlas, A., Drake, J., Giacalone, S., and S. Previdi,
              "Performance-Based Path Selection for Explicitly Routed
              Label Switched Paths (LSPs) Using TE Metric Extensions",
              RFC 7823, DOI 10.17487/RFC7823, May 2016,
              <https://www.rfc-editor.org/info/rfc7823>.

   [RFC7951]  Lhotka, L., "JSON Encoding of Data Modeled with YANG",
              RFC 7951, DOI 10.17487/RFC7951, August 2016,
              <https://www.rfc-editor.org/info/rfc7951>.

   [RFC8340]  Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
              BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
              <https://www.rfc-editor.org/info/rfc8340>.











Liu, et al.             Expires November 7, 2020               [Page 46]


Internet-Draft             YANG L3 TE Topology                  May 2020


Appendix A.  Companion YANG Model for Non-NMDA Compliant Implementations

   The YANG modules ietf-l3-te-topology and ietf-te-topology-packet
   defined in this document are designed to be used in conjunction with
   implementations that support the Network Management Datastore
   Architecture (NMDA) defined in [RFC8342].  In order to allow
   implementations to use the model even in cases when NMDA is not
   supported, the following companion modules, ietf-l3-te-topology-state
   and ietf-te-topology-packet-state, are defined as state models, which
   mirror the modules ietf-l3-te-topology and ietf-te-topology-packet
   defined earlier in this document.  However, all data nodes in the
   companion module are non-configurable, to represent the applied
   configuration or the derived operational states.

   The companion modules, ietf-l3-te-topology-state and ietf-te-
   topology-packet-state, are redundant and SHOULD NOT be supported by
   implementations that support NMDA.

   As the structure of the companion modules mirrors that of the
   coorespinding NMDA models, the YANG trees of the companion modules
   are not depicted separately.

A.1.  Layer 3 TE Topology State Module

   This module references [RFC8345], and [RFC8346].


   <CODE BEGINS> file "ietf-l3-te-topology-state@2020-05-03.yang"
   module ietf-l3-te-topology-state {
     yang-version 1.1;
     namespace "urn:ietf:params:xml:ns:yang:ietf-l3-te-topology-state";
     prefix "l3tet-s";

     import ietf-l3-te-topology {
       prefix "l3tet";
     }
     import ietf-network-state {
       prefix "nw-s";
       reference "RFC 8345: A YANG Data Model for Network Topologies";
     }
     import ietf-network-topology-state {
       prefix "nt-s";
       reference "RFC 8345: A YANG Data Model for Network Topologies";
     }
     import ietf-l3-unicast-topology-state {
       prefix "l3t-s";
       reference "RFC 8346: A YANG Data Model for Layer 3 Topologies";
     }



Liu, et al.             Expires November 7, 2020               [Page 47]


Internet-Draft             YANG L3 TE Topology                  May 2020


     organization
       "IETF Traffic Engineering Architecture and Signaling (TEAS)
        Working Group";

     contact
       "WG Web:   <http://tools.ietf.org/wg/teas/>
        WG List:  <mailto:teas@ietf.org>

        Editor:   Xufeng Liu
                  <mailto:xufeng.liu.ietf@gmail.com>

        Editor:   Igor Bryskin
                  <mailto:Igor.Bryskin@huawei.com>

        Editor:   Vishnu Pavan Beeram
                  <mailto:vbeeram@juniper.net>

        Editor:   Tarek Saad
                  <mailto:tsaad@cisco.com>

        Editor:   Himanshu Shah
                  <mailto:hshah@ciena.com>

        Editor:   Oscar Gonzalez De Dios
                  <mailto:oscar.gonzalezdedios@telefonica.com>";

     description
       "YANG data model for representing operational state information
        of Layer 3 TE Topologies, when NMDA is not supported.

        Copyright (c) 2018 IETF Trust and the persons identified as
        authors of the code.  All rights reserved.

        Redistribution and use in source and binary forms, with or
        without modification, is permitted pursuant to, and subject to
        the license terms contained in, the Simplified BSD License set
        forth in Section 4.c of the IETF Trust's Legal Provisions
        Relating to IETF Documents
        (http://trustee.ietf.org/license-info).

        This version of this YANG module is part of RFC XXXX; see the
        RFC itself for full legal notices.";

     revision 2020-05-03 {
       description
         "Initial revision";
       reference "RFC XXXX: YANG Data Model for Layer 3 TE Topologies";
     }



Liu, et al.             Expires November 7, 2020               [Page 48]


Internet-Draft             YANG L3 TE Topology                  May 2020


     augment "/nw-s:networks/nw-s:network/nw-s:network-types/"
       + "l3t-s:l3-unicast-topology" {
       description
         "Defines the L3 TE topology type.";
       uses l3tet:l3-te-topology-type;
     }

     augment "/nw-s:networks/nw-s:network/"
       + "l3t-s:l3-topology-attributes" {
       when "../nw-s:network-types/l3t-s:l3-unicast-topology/"
         + "l3tet-s:l3-te" {
         description
           "Augment only for L3 TE topology";
       }
       description
         "Augment topology configuration";
       uses l3tet:l3-te-topology-attributes;
     }

     augment "/nw-s:networks/nw-s:network/nw-s:node/"
       + "l3t-s:l3-node-attributes" {
       when "../../nw-s:network-types/l3t-s:l3-unicast-topology/"
         + "l3tet-s:l3-te" {
         description
           "Augment only for L3 TE topology";
       }
       description
         "Augment node configuration";
       uses l3tet:l3-te-node-attributes;
     }

     augment "/nw-s:networks/nw-s:network/nw-s:node/"
       + "nt-s:termination-point/"
       + "l3t-s:l3-termination-point-attributes" {
       when "../../../nw-s:network-types/l3t-s:l3-unicast-topology/"
         + "l3tet-s:l3-te" {
         description
           "Augment only for L3 TE topology";
       }
       description
         "Augment termination point configuration";
       uses l3tet:l3-te-tp-attributes;
     }

     augment "/nw-s:networks/nw-s:network/nt-s:link/"
       + "l3t-s:l3-link-attributes" {
       when "../../nw-s:network-types/l3t-s:l3-unicast-topology/"
         + "l3tet-s:l3-te" {



Liu, et al.             Expires November 7, 2020               [Page 49]


Internet-Draft             YANG L3 TE Topology                  May 2020


         description
           "Augment only for L3 TE topology";
       }
       description
         "Augment link configuration";
       uses l3tet:l3-te-link-attributes;
     }
   }
   <CODE ENDS>



A.2.  Packet Switching TE Topology State Module


   <CODE BEGINS> file "ietf-te-topology-packet-state@2019-06-28.yang"
   module ietf-te-topology-packet-state {
     yang-version 1.1;
     namespace
       "urn:ietf:params:xml:ns:yang:ietf-te-topology-packet-state";

     prefix "tet-pkt-s";

     import ietf-te-topology-packet {
       prefix "tet-pkt";
     }

     import ietf-network-state {
       prefix "nw-s";
       reference
         "RFC 8345: A YANG Data Model for Network Topologies";
     }

     import ietf-network-topology-state {
       prefix "nt-s";
       reference
         "RFC 8345: A YANG Data Model for Network Topologies";
     }

     import ietf-te-topology-state {
       prefix "tet-s";
       reference
         "I-D.ietf-teas-yang-te-topo: YANG Data Model for Traffic
          Engineering (TE) Topologies";
     }

     import ietf-te-types {
       prefix "te-types";



Liu, et al.             Expires November 7, 2020               [Page 50]


Internet-Draft             YANG L3 TE Topology                  May 2020


       reference
         "I-D.ietf-teas-yang-te-types: Traffic Engineering Common YANG
          Types";
     }

     import ietf-te-packet-types {
       prefix "te-packet-types";
       reference
         "I-D.ietf-teas-yang-te-types: Traffic Engineering Common YANG
          Types";
     }

     organization
       "Traffic Engineering Architecture and Signaling (TEAS)
        Working Group";

     contact
       "WG Web:   <http://tools.ietf.org/wg/teas/>
        WG List:  <mailto:teas@ietf.org>

        Editor:   Xufeng Liu
                  <mailto:xufeng.liu.ietf@gmail.com>

        Editor:   Igor Bryskin
                  <mailto:Igor.Bryskin@huawei.com>

        Editor:   Vishnu Pavan Beeram
                  <mailto:vbeeram@juniper.net>

        Editor:   Tarek Saad
                  <mailto:tsaad@cisco.com>

        Editor:   Himanshu Shah
                  <mailto:hshah@ciena.com>

        Editor:   Oscar Gonzalez De Dios
                  <mailto:oscar.gonzalezdedios@telefonica.com>";

     description
       "YANG data model for representing operational state information
        of PSC (Packet Switching) TE Topologies, when NMDA is not
         supported.

        Copyright (c) 2018 IETF Trust and the persons identified as
        authors of the code.  All rights reserved.

        Redistribution and use in source and binary forms, with or
        without modification, is permitted pursuant to, and subject to



Liu, et al.             Expires November 7, 2020               [Page 51]


Internet-Draft             YANG L3 TE Topology                  May 2020


        the license terms contained in, the Simplified BSD License set
        forth in Section 4.c of the IETF Trust's Legal Provisions
        Relating to IETF Documents
        (http://trustee.ietf.org/license-info).

        This version of this YANG module is part of RFC XXXX; see the
        RFC itself for full legal notices.";

     revision 2019-06-28 {
       description
         "Initial revision";
       reference
         "RFC XXXX: YANG Data Model for Layer 3 TE Topologies";
     }

     /*
      * Augmentations
      */
     /* Augmentations to connectivity-matrix */
     augment "/nw-s:networks/nw-s:network/nw-s:node/tet-s:te/"
       + "tet-s:te-node-attributes/tet-s:connectivity-matrices" {
       description
         "Parameters for PSC (Packet Switching) TE topology.";
       uses te-packet-types:performance-metrics-attributes-packet {
         if-feature tet-pkt:te-performance-metric;
       }
       uses
         te-packet-types:performance-metrics-throttle-container-packet {
         if-feature tet-pkt:te-performance-metric;
       }
     }

     augment "/nw-s:networks/nw-s:network/nw-s:node/tet-s:te/"
           + "tet-s:te-node-attributes/tet-s:connectivity-matrices/"
           + "tet-s:connectivity-matrix" {
       description
         "Parameters for PSC TE topology.";
       uses te-packet-types:performance-metrics-attributes-packet {
         if-feature tet-pkt:te-performance-metric;
       }
       uses
         te-packet-types:performance-metrics-throttle-container-packet {
         if-feature tet-pkt:te-performance-metric;
       }
     }

     augment "/nw-s:networks/nw-s:network/nw-s:node/tet-s:te/"
           + "tet-s:information-source-entry/"



Liu, et al.             Expires November 7, 2020               [Page 52]


Internet-Draft             YANG L3 TE Topology                  May 2020


           + "tet-s:connectivity-matrices" {
       description
         "Parameters for PSC TE topology.";
       uses te-packet-types:performance-metrics-attributes-packet {
         if-feature tet-pkt:te-performance-metric;
       }
       uses
         te-packet-types:performance-metrics-throttle-container-packet {
         if-feature tet-pkt:te-performance-metric;
       }
     }

     augment "/nw-s:networks/nw-s:network/nw-s:node/tet-s:te/"
           + "tet-s:information-source-entry/"
           + "tet-s:connectivity-matrices/"
           + "tet-s:connectivity-matrix" {
       description
         "Parameters for PSC TE topology.";
       uses te-packet-types:performance-metrics-attributes-packet {
         if-feature tet-pkt:te-performance-metric;
       }
       uses
         te-packet-types:performance-metrics-throttle-container-packet {
         if-feature tet-pkt:te-performance-metric;
       }
     }

     /* Augmentations to tunnel-termination-point */
     augment "/nw-s:networks/nw-s:network/nw-s:node/tet-s:te/"
           + "tet-s:tunnel-termination-point/"
           + "tet-s:local-link-connectivities" {
       description
         "Parameters for PSC TE topology.";
       uses te-packet-types:performance-metrics-attributes-packet {
         if-feature tet-pkt:te-performance-metric;
       }
       uses
         te-packet-types:performance-metrics-throttle-container-packet {
         if-feature tet-pkt:te-performance-metric;
       }
     }

     augment "/nw-s:networks/nw-s:network/nw-s:node/tet-s:te/"
           + "tet-s:tunnel-termination-point/"
           + "tet-s:local-link-connectivities/"
           + "tet-s:local-link-connectivity" {
       description
         "Parameters for PSC TE topology.";



Liu, et al.             Expires November 7, 2020               [Page 53]


Internet-Draft             YANG L3 TE Topology                  May 2020


       uses te-packet-types:performance-metrics-attributes-packet {
         if-feature tet-pkt:te-performance-metric;
       }
       uses
         te-packet-types:performance-metrics-throttle-container-packet {
         if-feature tet-pkt:te-performance-metric;
       }
     }

     /* Augmentations to te-link-attributes */
     augment "/nw-s:networks/tet-s:te/tet-s:templates/"
           + "tet-s:link-template/tet-s:te-link-attributes" {
       when "tet-s:interface-switching-capability "
         + "[tet-s:switching-capability = 'te-types:switching-psc1']" {
         description
           "Valid only for PSC";
       }
       description
         "Parameters for PSC TE topology.";
       uses te-packet-types:performance-metrics-attributes-packet {
         if-feature tet-pkt:te-performance-metric;
       }
       uses
         te-packet-types:performance-metrics-throttle-container-packet {
         if-feature tet-pkt:te-performance-metric;
       }
     }

     augment "/nw-s:networks/nw-s:network/nt-s:link/tet-s:te/"
           + "tet-s:te-link-attributes" {
       when "tet-s:interface-switching-capability "
         + "[tet-s:switching-capability = 'te-types:switching-psc1']" {
         description "Valid only for PSC";
       }
       description
         "Parameters for PSC TE topology.";
       uses te-packet-types:performance-metrics-attributes-packet {
         if-feature tet-pkt:te-performance-metric;
       }
       uses
         te-packet-types:performance-metrics-throttle-container-packet {
         if-feature tet-pkt:te-performance-metric;
       }
     }

     augment "/nw-s:networks/nw-s:network/nt-s:link/tet-s:te/"
           + "tet-s:information-source-entry" {
       when "tet-s:interface-switching-capability "



Liu, et al.             Expires November 7, 2020               [Page 54]


Internet-Draft             YANG L3 TE Topology                  May 2020


         + "[tet-s:switching-capability = 'te-types:switching-psc1']" {
         description "Valid only for PSC";
       }
       description
         "Parameters for PSC TE topology.";
       uses te-packet-types:performance-metrics-attributes-packet {
         if-feature tet-pkt:te-performance-metric;
       }
       uses
         te-packet-types:performance-metrics-throttle-container-packet {
         if-feature tet-pkt:te-performance-metric;
       }
     }

     /* Augmentations to interface-switching-capability */
     augment "/nw-s:networks/tet-s:te/tet-s:templates/"
           + "tet-s:link-template/tet-s:te-link-attributes/"
           + "tet-s:interface-switching-capability" {
       when "tet-s:switching-capability = 'te-types:switching-psc1' " {
         description "Valid only for PSC";
       }
       description
         "Parameters for PSC TE topology.";
       uses tet-pkt:packet-switch-capable-container;
     }

     augment "/nw-s:networks/nw-s:network/nt-s:link/tet-s:te/"
           + "tet-s:te-link-attributes/"
           + "tet-s:interface-switching-capability" {
       when "tet-s:switching-capability = 'te-types:switching-psc1' " {
         description "Valid only for PSC";
       }
       description
         "Parameters for PSC TE topology.";
       uses tet-pkt:packet-switch-capable-container;
     }

     augment "/nw-s:networks/nw-s:network/nt-s:link/tet-s:te/"
           + "tet-s:information-source-entry/"
           + "tet-s:interface-switching-capability" {
       when "tet-s:switching-capability = 'te-types:switching-psc1' " {
         description
           "Valid only for PSC";
       }
       description
         "Parameters for PSC TE topology.";
       uses tet-pkt:packet-switch-capable-container;
     }



Liu, et al.             Expires November 7, 2020               [Page 55]


Internet-Draft             YANG L3 TE Topology                  May 2020


   }
   <CODE ENDS>



Appendix B.  Data Tree Example

   This section contains an example of an instance data tree in the JSON
   encoding [RFC7951].  The example instantiates "ietf-l3-te-topology"
   for the topology that is depicted in the following diagram.


                   +------------+                   +------------+
                   |     D1     |                   |     D2     |
                  /-\          /-\     (TE)        /-\          /-\
                  | | 1-0-1    | |---------------->| | 2-1-1    | |
                  | |    1-2-1 | |<----------------| |    2-0-1 | |
                  \-/  1-3-1   \-/     (TE)        \-/  2-3-1   \-/
                   |   /----\   |                   |   /----\   |
                   +---|    |---+                   +---|    |---+
                       \----/                           \----/
                        A  |                             A  |
                    (TE)|  |(TE)                 (Non-TE)|  |(Non-TE)
                        |  |                             |  |
                        |  |       +------------+        |  |
                        |  |       |     D3     |        |  |
                        |  |      /-\          /-\       |  |
                        |  +----->| | 3-1-1    | |-------+  |
                        +---------| |    3-2-1 | |<---------+
                                  \-/          \-/
                                   |            |
                                   +------------+


   The corresponding instance data tree is depicted below.  Note that
   some lines have been wrapped to adhere to the 72-character line
   limitation of RFCs.

   {
     "ietf-network:networks": {
       "network": [
         {
           "network-id":"example-topo-te",
           "network-types": {
             "ietf-te-topology:te-topology": {
             }
           },
           "ietf-te-topology:te-topology-identifier": {



Liu, et al.             Expires November 7, 2020               [Page 56]


Internet-Draft             YANG L3 TE Topology                  May 2020


             "provider-id":200,
             "client-id":300,
             "topology-id":"example-topo-te"
           },
           "ietf-te-topology:te": {
           },
           "node": [
             {
               "node-id":"D1",
               "ietf-te-topology:te-node-id":"2.0.1.1",
               "ietf-te-topology:te": {
                 "te-node-attributes": {
                 }
               },
               "ietf-network-topology:termination-point": [
                 {
                   "tp-id":"1-2-1",
                   "ietf-te-topology:te-tp-id":10201,
                   "ietf-te-topology:te": {
                     "interface-switching-capability": [
                       {
                         "switching-capability":
                           "ietf-te-types:switching-psc1",
                         "encoding":
                           "ietf-te-types:lsp-encoding-ethernet"
                       }
                     ]
                   }
                 },
                 {
                   "tp-id": "1-3-1",
                   "ietf-te-topology:te-tp-id":10301,
                   "ietf-te-topology:te": {
                     "interface-switching-capability": [
                       {
                         "switching-capability":
                           "ietf-te-types:switching-psc1",
                         "encoding":
                           "ietf-te-types:lsp-encoding-ethernet"
                       }
                     ]
                   }
                 }
               ]
             },
             {
               "node-id":"D2",
               "ietf-te-topology:te-node-id":"2.0.2.1",



Liu, et al.             Expires November 7, 2020               [Page 57]


Internet-Draft             YANG L3 TE Topology                  May 2020


               "ietf-te-topology:te": {
                 "te-node-attributes": {
                 }
               },
               "ietf-network-topology:termination-point": [
                 {
                   "tp-id":"2-1-1",
                   "ietf-te-topology:te-tp-id":20101,
                   "ietf-te-topology:te": {
                     "interface-switching-capability": [
                       {
                         "switching-capability":
                           "ietf-te-types:switching-psc1",
                         "encoding":
                           "ietf-te-types:lsp-encoding-ethernet"
                       }
                     ]
                   }
                 }
               ]
             },
             {
               "node-id":"D3",
               "ietf-te-topology:te-node-id":"2.0.3.1",
               "ietf-te-topology:te": {
                 "te-node-attributes": {
                 }
               },
               "ietf-network-topology:termination-point": [
                 {
                   "tp-id":"3-1-1",
                   "ietf-te-topology:te-tp-id":30101,
                   "ietf-te-topology:te": {
                     "interface-switching-capability": [
                       {
                         "switching-capability":
                           "ietf-te-types:switching-psc1",
                         "encoding":
                           "ietf-te-types:lsp-encoding-ethernet"
                       }
                     ]
                   }
                 }
               ]
             }
           ],
           "ietf-network-topology:link": [
             {



Liu, et al.             Expires November 7, 2020               [Page 58]


Internet-Draft             YANG L3 TE Topology                  May 2020


               "link-id":"D1,1-2-1,D2,2-1-1",
               "source": {
                 "source-node":"D1",
                 "source-tp":"1-2-1"
               },
               "destination": {
                 "dest-node":"D2",
                 "dest-tp":"2-1-1"
               },
               "ietf-te-topology:te": {
                 "te-link-attributes": {
                   "interface-switching-capability": [
                     {
                       "switching-capability":
                         "ietf-te-types:switching-psc1",
                       "encoding":"ietf-te-types:lsp-encoding-ethernet"
                     }
                   ],
                   "max-link-bandwidth": {
                     "te-bandwidth": {
                       "generic":"0x1p+18"
                     }
                   },
                   "te-default-metric":100
                 }
               }
             },
             {
               "link-id":"D2,2-1-1,D1,1-2-1",
               "source": {
                 "source-node":"D2",
                 "source-tp":"2-1-1"
               },
               "destination": {
                 "dest-node":"D1",
                 "dest-tp":"1-2-1"
               },
               "ietf-te-topology:te": {
                 "te-link-attributes": {
                   "interface-switching-capability": [
                     {
                       "switching-capability":
                         "ietf-te-types:switching-psc1",
                       "encoding":"ietf-te-types:lsp-encoding-ethernet"
                     }
                   ],
                   "max-link-bandwidth": {
                     "te-bandwidth": {



Liu, et al.             Expires November 7, 2020               [Page 59]


Internet-Draft             YANG L3 TE Topology                  May 2020


                       "generic":"0x1p+18"
                     }
                   },
                   "te-default-metric":100
                 }
               }
             },
             {
               "link-id":"D1,1-3-1,D3,3-1-1",
               "source": {
                 "source-node":"D1",
                 "source-tp":"1-3-1"
               },
               "destination": {
                 "dest-node":"D3",
                 "dest-tp":"3-1-1"
               },
               "ietf-te-topology:te": {
                 "te-link-attributes": {
                   "interface-switching-capability": [
                     {
                       "switching-capability":
                         "ietf-te-types:switching-psc1",
                       "encoding":"ietf-te-types:lsp-encoding-ethernet"
                     }
                   ],
                   "max-link-bandwidth": {
                     "te-bandwidth": {
                       "generic":"0x1p+18"
                     }
                   },
                   "te-default-metric":100
                 }
               }
             },
             {
               "link-id":"D3,3-1-1,D1,1-3-1",
               "source": {
                 "source-node":"D3",
                 "source-tp":"3-1-1"
               },
               "destination": {
                 "dest-node":"D1",
                 "dest-tp":"1-3-1"
               },
               "ietf-te-topology:te": {
                 "te-link-attributes": {
                   "interface-switching-capability": [



Liu, et al.             Expires November 7, 2020               [Page 60]


Internet-Draft             YANG L3 TE Topology                  May 2020


                     {
                       "switching-capability":
                         "ietf-te-types:switching-psc1",
                       "encoding":"ietf-te-types:lsp-encoding-ethernet"
                     }
                   ],
                   "max-link-bandwidth": {
                     "te-bandwidth": {
                       "generic":"0x1p+18"
                     }
                   },
                   "te-default-metric":100
                 }
               }
             }
           ]
         },
         {
           "network-id":"example-topo-l3-te",
           "network-types": {
             "ietf-l3-unicast-topology:l3-unicast-topology": {
               "ietf-l3-te-topology:l3-te": {
               }
             }
           },
           "ietf-l3-unicast-topology:l3-topology-attributes": {
             "ietf-l3-te-topology:l3-te-topology-attributes": {
               "network-ref":"example-topo-te"
             }
           },
           "node": [
             {
               "node-id":"D1",
               "ietf-l3-unicast-topology:l3-node-attributes": {
                 "router-id": [
                   "203.0.113.1"
                 ],
                 "prefix": [
                   {
                     "prefix":"203.0.113.1/32"
                   }
                 ],
                 "ietf-l3-te-topology:l3-te-node-attributes": {
                   "node-ref":"D1",
                   "network-ref":"example-topo-te"
                 }
               },
               "ietf-network-topology:termination-point": [



Liu, et al.             Expires November 7, 2020               [Page 61]


Internet-Draft             YANG L3 TE Topology                  May 2020


                 {
                   "tp-id":"1-0-1",
   "ietf-l3-unicast-topology:l3-termination-point-attributes": {
                     "unnumbered-id":101
                   }
                 },
                 {
                   "tp-id":"1-2-1",
   "ietf-l3-unicast-topology:l3-termination-point-attributes": {
                     "unnumbered-id":121,
                     "ietf-l3-te-topology:l3-te-tp-attributes": {
                       "network-ref":"example-topo-te",
                       "tp-ref":"1-2-1"
                     }
                   }
                 },
                 {
                   "tp-id":"1-3-1",
   "ietf-l3-unicast-topology:l3-termination-point-attributes": {
                     "unnumbered-id":131,
                     "ietf-l3-te-topology:l3-te-tp-attributes": {
                       "network-ref":"example-topo-te",
                       "tp-ref":"1-3-1"
                     }
                   }
                 }
               ]
             },
             {
               "node-id":"D2",
               "ietf-l3-unicast-topology:l3-node-attributes": {
                 "router-id": [
                   "203.0.113.2"
                 ],
                 "prefix": [
                   {
                     "prefix":"203.0.113.2/32"
                   }
                 ],
                 "ietf-l3-te-topology:l3-te-node-attributes": {
                   "node-ref":"D2",
                   "network-ref":"example-topo-te"
                 }
               },
               "ietf-network-topology:termination-point": [
                 {
                   "tp-id":"2-0-1",
   "ietf-l3-unicast-topology:l3-termination-point-attributes": {



Liu, et al.             Expires November 7, 2020               [Page 62]


Internet-Draft             YANG L3 TE Topology                  May 2020


                     "unnumbered-id":201
                   }
                 },
                 {
                   "tp-id":"2-1-1",
   "ietf-l3-unicast-topology:l3-termination-point-attributes": {
                     "unnumbered-id":211,
                     "ietf-l3-te-topology:l3-te-tp-attributes": {
                       "tp-ref":"2-1-1",
                       "network-ref":"example-topo-te"
                     }
                   }
                 },
                 {
                   "tp-id":"2-3-1",
   "ietf-l3-unicast-topology:l3-termination-point-attributes": {
                     "unnumbered-id":231
                   }
                 }
               ]
             },
             {
               "node-id":"D3",
               "ietf-l3-unicast-topology:l3-node-attributes": {
                 "router-id": [
                   "203.0.113.3"
                 ],
                 "prefix": [
                   {
                     "prefix":"203.0.113.3/32"
                   }
                 ],
                 "ietf-l3-te-topology:l3-te-node-attributes": {
                   "node-ref":"D3",
                   "network-ref":"example-topo-te"
                 }
               },
               "ietf-network-topology:termination-point": [
                 {
                   "tp-id":"3-0-1",
   "ietf-l3-unicast-topology:l3-termination-point-attributes": {
                     "unnumbered-id":301
                   }
                 },
                 {
                   "tp-id":"3-1-1",
   "ietf-l3-unicast-topology:l3-termination-point-attributes": {
                     "unnumbered-id":311,



Liu, et al.             Expires November 7, 2020               [Page 63]


Internet-Draft             YANG L3 TE Topology                  May 2020


                     "ietf-l3-te-topology:l3-te-tp-attributes": {
                       "tp-ref":"3-1-1",
                       "network-ref":"example-topo-te"
                     }
                   }
                 },
                 {
                   "tp-id":"3-2-1",
   "ietf-l3-unicast-topology:l3-termination-point-attributes": {
                     "unnumbered-id":321
                   }
                 }
               ]
             }
           ],
           "ietf-network-topology:link": [
             {
               "link-id":"D1,1-2-1,D2,2-1-1",
               "source": {
                 "source-node":"D1",
                 "source-tp":"1-2-1"
               },
               "destination": {
                 "dest-node":"D2",
                 "dest-tp":"2-1-1"
               },
               "ietf-l3-unicast-topology:l3-link-attributes": {
                 "metric1":"100",
                 "ietf-l3-te-topology:l3-te-link-attributes": {
                   "link-ref":"D1,1-2-1,D2,2-1-1",
                   "network-ref":"example-topo-te"
                 }
               }
             },
             {
               "link-id":"D2,2-1-1,D1,1-2-1",
               "source": {
                 "source-node":"D2",
                 "source-tp":"2-1-1"
               },
               "destination": {
                 "dest-node":"D1",
                 "dest-tp":"1-2-1"
               },
               "ietf-l3-unicast-topology:l3-link-attributes": {
                 "metric1":"100",
                 "ietf-l3-te-topology:l3-te-link-attributes": {
                   "link-ref":"D2,2-1-1,D1,1-2-1",



Liu, et al.             Expires November 7, 2020               [Page 64]


Internet-Draft             YANG L3 TE Topology                  May 2020


                   "network-ref":"example-topo-te"
                 }
               }
             },
             {
               "link-id":"D1,1-3-1,D3,3-1-1",
               "source": {
                 "source-node":"D1",
                 "source-tp":"1-3-1"
               },
               "destination": {
                 "dest-node":"D3",
                 "dest-tp":"3-1-1"
               },
               "ietf-l3-unicast-topology:l3-link-attributes": {
                 "metric1":"100",
                 "ietf-l3-te-topology:l3-te-link-attributes": {
                   "link-ref":"D1,1-3-1,D3,3-1-1",
                   "network-ref":"example-topo-te"
                 }
               }
             },
             {
               "link-id":"D3,3-1-1,D1,1-3-1",
               "source": {
                 "source-node":"D3",
                 "source-tp":"3-1-1"
               },
               "destination": {
                 "dest-node":"D1",
                 "dest-tp":"1-3-1"
               },
               "ietf-l3-unicast-topology:l3-link-attributes": {
                 "metric1":"100",
                 "ietf-l3-te-topology:l3-te-link-attributes": {
                   "link-ref":"D3,3-1-1,D1,1-3-1",
                   "network-ref":"example-topo-te"
                 }
               }
             },
             {
               "link-id":"D2,2-3-1,D3,3-2-1",
               "source": {
                 "source-node":"D2",
                 "source-tp":"2-3-1"
               },
               "destination": {
                 "dest-node":"D3",



Liu, et al.             Expires November 7, 2020               [Page 65]


Internet-Draft             YANG L3 TE Topology                  May 2020


                 "dest-tp":"3-2-1"
               },
               "ietf-l3-unicast-topology:l3-link-attributes": {
                 "metric1":"100"
               }
             },
             {
               "link-id":"D3,3-2-1,D2,2-3-1",
               "source": {
                 "source-node":"D3",
                 "source-tp":"3-2-1"
               },
               "destination": {
                 "dest-node":"D2",
                 "dest-tp":"2-3-1"
               },
               "ietf-l3-unicast-topology:l3-link-attributes": {
                 "metric1":"100"
               }
             }
           ]
         }
       ]
     }
   }


Authors' Addresses

   Xufeng Liu
   Volta Networks

   EMail: xufeng.liu.ietf@gmail.com


   Igor Bryskin
   Individual

   EMail: i_bryskin@yahoo.com


   Vishnu Pavan Beeram
   Juniper Networks

   EMail: vbeeram@juniper.net






Liu, et al.             Expires November 7, 2020               [Page 66]


Internet-Draft             YANG L3 TE Topology                  May 2020


   Tarek Saad
   Juniper Networks

   EMail: tsaad@juniper.net


   Himanshu Shah
   Ciena

   EMail: hshah@ciena.com


   Oscar Gonzalez de Dios
   Telefonica

   EMail: oscar.gonzalezdedios@telefonica.com



































Liu, et al.             Expires November 7, 2020               [Page 67]