< draft-ietf-teas-yang-l3-te-topo-04.txt   draft-ietf-teas-yang-l3-te-topo-05.txt >
Network Working Group X. Liu Network Working Group X. Liu
Internet-Draft Volta Networks Internet-Draft Volta Networks
Intended status: Standards Track I. Bryskin Intended status: Standards Track I. Bryskin
Expires: September 12, 2019 Huawei Technologies Expires: January 9, 2020 Futurewei
V. Beeram V. Beeram
Juniper Networks
T. Saad T. Saad
Cisco Systems Inc Juniper Networks
H. Shah H. Shah
Ciena Ciena
O. Gonzalez de Dios O. Gonzalez de Dios
Telefonica Telefonica
March 11, 2019 July 8, 2019
YANG Data Model for Layer 3 TE Topologies YANG Data Model for Layer 3 TE Topologies
draft-ietf-teas-yang-l3-te-topo-04 draft-ietf-teas-yang-l3-te-topo-05
Abstract Abstract
This document defines a YANG data model for layer 3 traffic This document defines a YANG data model for layer 3 traffic
engineering topologies. engineering topologies.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 40 skipping to change at page 1, line 39
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 12, 2019. This Internet-Draft will expire on January 9, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 27 skipping to change at page 2, line 26
2.1. Relationship Between Layer 3 Topology and TE topology . . 3 2.1. Relationship Between Layer 3 Topology and TE topology . . 3
2.2. Relationship Modeling . . . . . . . . . . . . . . . . . . 4 2.2. Relationship Modeling . . . . . . . . . . . . . . . . . . 4
2.2.1. Topology Referencing . . . . . . . . . . . . . . . . 4 2.2.1. Topology Referencing . . . . . . . . . . . . . . . . 4
2.2.2. Node Referencing . . . . . . . . . . . . . . . . . . 4 2.2.2. Node Referencing . . . . . . . . . . . . . . . . . . 4
2.2.3. Link Termination Point Referencing . . . . . . . . . 4 2.2.3. Link Termination Point Referencing . . . . . . . . . 4
2.2.4. Link Referencing . . . . . . . . . . . . . . . . . . 5 2.2.4. Link Referencing . . . . . . . . . . . . . . . . . . 5
2.3. Topology Type Modeling . . . . . . . . . . . . . . . . . 5 2.3. Topology Type Modeling . . . . . . . . . . . . . . . . . 5
3. Packet Switching Technology Extensions . . . . . . . . . . . 5 3. Packet Switching Technology Extensions . . . . . . . . . . . 5
3.1. Technology Specific Link Attributes . . . . . . . . . . . 5 3.1. Technology Specific Link Attributes . . . . . . . . . . . 5
3.2. Performance Metric . . . . . . . . . . . . . . . . . . . 6 3.2. Performance Metric . . . . . . . . . . . . . . . . . . . 6
4. Model Structure . . . . . . . . . . . . . . . . . . . . . . . 6 4. Complete Model Tree Structure . . . . . . . . . . . . . . . . 7
4.1. Layer 3 TE Topology Module . . . . . . . . . . . . . . . 6 4.1. Layer 3 TE Topology Module . . . . . . . . . . . . . . . 7
4.2. Packet Switching TE Topology Module . . . . . . . . . . . 7 4.2. Packet Switching TE Topology Module . . . . . . . . . . . 7
5. YANG Modules . . . . . . . . . . . . . . . . . . . . . . . . 27 5. YANG Modules . . . . . . . . . . . . . . . . . . . . . . . . 27
5.1. Layer 3 TE Topology Module . . . . . . . . . . . . . . . 27 5.1. Layer 3 TE Topology Module . . . . . . . . . . . . . . . 27
5.2. Packet Switching TE Topology Module . . . . . . . . . . . 31 5.2. Packet Switching TE Topology Module . . . . . . . . . . . 32
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 38 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 39
7. Security Considerations . . . . . . . . . . . . . . . . . . . 40 7. Security Considerations . . . . . . . . . . . . . . . . . . . 41
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 42 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 43
8.1. Normative References . . . . . . . . . . . . . . . . . . 42 8.1. Normative References . . . . . . . . . . . . . . . . . . 43
8.2. Informative References . . . . . . . . . . . . . . . . . 44 8.2. Informative References . . . . . . . . . . . . . . . . . 45
Appendix A. Companion YANG Model for Non-NMDA Compliant Appendix A. Companion YANG Model for Non-NMDA Compliant
Implementations . . . . . . . . . . . . . . . . . . 45 Implementations . . . . . . . . . . . . . . . . . . 46
A.1. Layer 3 TE Topology State Module . . . . . . . . . . . . 45 A.1. Layer 3 TE Topology State Module . . . . . . . . . . . . 46
A.2. Packet Switching TE Topology State Module . . . . . . . . 48 A.2. Packet Switching TE Topology State Module . . . . . . . . 49
Appendix B. Data Tree Example . . . . . . . . . . . . . . . . . 53 Appendix B. Data Tree Example . . . . . . . . . . . . . . . . . 55
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 63 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 65
1. Introduction 1. Introduction
This document defines a YANG [RFC7950] data model for describing the This document defines a YANG [RFC7950] data model for describing the
relationship between a layer 3 network topology [RFC8346] and a TE relationship between a layer 3 network topology [RFC8346] and a
topology [I-D.ietf-teas-yang-te-topo]. Traffic Engineering (TE) topology [I-D.ietf-teas-yang-te-topo].
When traffic engineering is enabled on a layer 3 network topology, When traffic engineering is enabled on a layer 3 network topology,
there will be a corresponding TE topology. The TE topology may or there will be a corresponding TE topology. The TE topology may or
may not be congruent to the layer 3 network topology. When such a may not be congruent to the layer 3 network topology. When such a
congruent TE topology exists, there will be a one-to-one association congruent TE topology exists, there will be a one-to-one association
between the one modeling element in the layer 3 topology to another between the one modeling element in the layer 3 topology to another
element in the TE topology. When such a congruent TE topology does 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 not exist, the association will not be one-to-one. This YANG data
model allows both cases. model allows both cases.
1.1. Terminology 1.1. Terminology
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14, [RFC2119]. 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 The following terms are defined in [RFC7950] and are not redefined
here: here:
o augment o augment
o data model o data model
o data node o data node
1.2. Tree Diagrams 1.2. Tree Diagrams
Tree diagrams used in this document follow the notation defined in Tree diagrams used in this document follow the notation defined in
[RFC8340]. [RFC8340].
2. Modeling Considerations for L3 TE Topologies 2. Modeling Considerations for L3 TE Topologies
The YANG modulues ietf-l3-te-topology and ietf-l3-te-topology-state
model configuration and operational state of layer 3 TE network
topologies. These two modules augment ietf-l3-te-topology and ietf-
l3-te-topology-state respectively, so a layer 3 TE network topology
is a layer 3 network topoology with addtional TE capability enabled.
2.1. Relationship Between Layer 3 Topology and TE topology 2.1. Relationship Between Layer 3 Topology and TE topology
In general, layer 3 network topology model and TE topology model can In general, layer 3 network topology model and TE topology model can
be used independently. When traffic engineering is enabled on a be used independently. When traffic engineering is enabled on a
layer 3 network topology, there will be associations between objects layer 3 network topology, there will be associations between objects
in layer 3 network topologies and objects in TE topologies. The in layer 3 network topologies and objects in TE topologies. The
properties of these relations are: properties of these relations are:
o The associations are between objects of the same class, i.e. node o The associations are between objects of the same class, i.e. node
to node or link to link. to node or link to link.
o The multiplicity of such an association is: 0..1 to 0..1. An o The multiplicity of such an association is: 0..1 to 0..1. An
object in a layer 3 network may have zero or one associated object object in a layer 3 network may have zero or one associated object
in the corresponding TE network. in the corresponding TE network.
2.2. Relationship Modeling 2.2. Relationship Modeling
YANG data type leafref is used to model the association relationship YANG data type leafref is used to model the association relationship
between a layer 3 network topology and a TE topology. YANG must between a layer 3 network topology and a TE topology. YANG must
statements are used to enforce the referenced objects are in the statements are used to enforce that the referenced objects are in the
topologies of proper type. topologies of proper type.
2.2.1. Topology Referencing 2.2.1. Topology Referencing
When TE is enabled on a layer 3 network topology, if the TE topology When TE is enabled on a layer 3 network topology, if the TE topology
is not congruent to the layer 3 network topology, the layer 3 network is not congruent to the layer 3 network topology, the layer 3 network
topology will have a reference to the corresponding TE topology. topology will have a reference to the corresponding TE topology.
Such a reference is modeled as follows: Such a reference is modeled as follows:
augment /nw:networks/nw:network/l3t:l3-topology-attributes: augment /nw:networks/nw:network/l3t:l3-topology-attributes:
skipping to change at page 5, line 28 skipping to change at page 5, line 35
A new topology type is defined in this document, to indicate a A new topology type is defined in this document, to indicate a
topology that is a layer 3 topology with TE enabled. topology that is a layer 3 topology with TE enabled.
augment /nw:networks/nw:network/nw:network-types augment /nw:networks/nw:network/nw:network-types
/l3t:l3-unicast-topology: /l3t:l3-unicast-topology:
+--rw l3-te! +--rw l3-te!
3. Packet Switching Technology Extensions 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].
3.1. Technology Specific Link Attributes 3.1. Technology Specific Link Attributes
The technology agnostic TE Topology model is augmented with packet The technology agnostic TE Topology model is augmented with packet
switching specific link attributes: switching specific link attributes:
augment /nw:networks/tet:te/tet:templates/tet:link-template augment /nw:networks/tet:te/tet:templates/tet:link-template
/tet:te-link-attributes /tet:te-link-attributes
/tet:interface-switching-capability: /tet:interface-switching-capability:
+--rw packet-switch-capable +--rw packet-switch-capable
+--rw minimum-lsp-bandwidth? rt-types:bandwidth-ieee-float32 +--rw minimum-lsp-bandwidth? rt-types:bandwidth-ieee-float32
skipping to change at page 6, line 7 skipping to change at page 6, line 26
+--rw interface-mtu? uint16 +--rw interface-mtu? uint16
augment /nw:networks/nw:network/nt:link/tet:te augment /nw:networks/nw:network/nt:link/tet:te
/tet:information-source-entry /tet:information-source-entry
/tet:interface-switching-capability: /tet:interface-switching-capability:
+--ro packet-switch-capable +--ro packet-switch-capable
+--ro minimum-lsp-bandwidth? rt-types:bandwidth-ieee-float32 +--ro minimum-lsp-bandwidth? rt-types:bandwidth-ieee-float32
+--ro interface-mtu? uint16 +--ro interface-mtu? uint16
3.2. Performance Metric 3.2. Performance Metric
[RFC7471], [RFC7810] and [RFC7823] specify TE performance metric [RFC7471], [RFC8570] and [RFC7823] specify TE performance metric
parameters and their usage. The packet switching augmentations parameters and their usage. The packet switching augmentations
specified in this moducment support such a capability, which can be specified in this moducment support such a capability, which can be
conditional enabled by a YANG feature "te-performance-metric". conditional enabled by a YANG feature "te-performance-metric".
augment /nw:networks/nw:network/nw:node/tet:te augment /nw:networks/nw:network/nw:node/tet:te
/tet:te-node-attributes/tet:connectivity-matrices: /tet:te-node-attributes/tet:connectivity-matrices:
+--rw performance-metric +--rw performance-metric
+--rw measurement +--rw measurement
| ...... | ......
+--rw normality +--rw normality
skipping to change at page 6, line 33 skipping to change at page 7, line 4
o Connectivity matrices container o Connectivity matrices container
o Connectivity matrix entry o Connectivity matrix entry
o Local ink connectivities container o Local ink connectivities container
o Local ink connectivity entry o Local ink connectivity entry
o TE link attributes container in a TE link template o TE link attributes container in a TE link template
o TE link attributes container in a TE link o TE link attributes container in a TE link
o Information source entry in a TE link o Information source entry in a TE link
4. Model Structure 4. Complete Model Tree Structure
4.1. Layer 3 TE Topology Module 4.1. Layer 3 TE Topology Module
The model tree structure of the layer 3 TE topology module is as The model tree structure of the layer 3 TE topology module is as
shown below: shown below:
module: ietf-l3-te-topology module: ietf-l3-te-topology
augment /nw:networks/nw:network/nw:network-types augment /nw:networks/nw:network/nw:network-types
/l3t:l3-unicast-topology: /l3t:l3-unicast-topology:
+--rw l3-te! +--rw l3-te!
skipping to change at page 27, line 25 skipping to change at page 27, line 35
+--ro minimum-lsp-bandwidth? rt-types:bandwidth-ieee-float32 +--ro minimum-lsp-bandwidth? rt-types:bandwidth-ieee-float32
+--ro interface-mtu? uint16 +--ro interface-mtu? uint16
5. YANG Modules 5. YANG Modules
5.1. Layer 3 TE Topology Module 5.1. Layer 3 TE Topology Module
This module references [RFC8345], [RFC8346], and This module references [RFC8345], [RFC8346], and
[I-D.ietf-teas-yang-te-topo]. [I-D.ietf-teas-yang-te-topo].
<CODE BEGINS> file "ietf-l3-te-topology@2019-02-28.yang" <CODE BEGINS> file "ietf-l3-te-topology@2019-06-28.yang"
module ietf-l3-te-topology { module ietf-l3-te-topology {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-l3-te-topology"; namespace "urn:ietf:params:xml:ns:yang:ietf-l3-te-topology";
prefix "l3tet"; prefix "l3tet";
import ietf-network { import ietf-network {
prefix "nw"; prefix "nw";
reference "RFC 8345: A YANG Data Model for Network Topologies"; reference "RFC 8345: A YANG Data Model for Network Topologies";
} }
import ietf-network-topology { import ietf-network-topology {
skipping to change at page 28, line 47 skipping to change at page 29, line 10
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set the license terms contained in, the Simplified BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the This version of this YANG module is part of RFC XXXX; see the
RFC itself for full legal notices."; RFC itself for full legal notices.";
revision 2019-02-28 { revision 2019-06-28 {
description "Initial revision"; description
"Initial revision";
reference "RFC XXXX: YANG Data Model for Layer 3 TE Topologies"; reference "RFC XXXX: YANG Data Model for Layer 3 TE Topologies";
} }
grouping l3-te-topology-type { grouping l3-te-topology-type {
description description
"Identifies the L3 TE topology type."; "Identifies the L3 TE topology type.";
container l3-te { container l3-te {
presence "indiates L3 TE Topology"; presence "Indiates L3 TE Topology";
description description
"Its presence identifies the L3 TE topology type."; "Its presence identifies the L3 TE topology type.";
} }
} }
augment "/nw:networks/nw:network/nw:network-types/" augment "/nw:networks/nw:network/nw:network-types/"
+ "l3t:l3-unicast-topology" { + "l3t:l3-unicast-topology" {
description description
"Defines the L3 TE topology type."; "Defines the L3 TE topology type.";
uses l3-te-topology-type; uses l3-te-topology-type;
} }
augment "/nw:networks/nw:network/l3t:l3-topology-attributes" { augment "/nw:networks/nw:network/l3t:l3-topology-attributes" {
when "../nw:network-types/l3t:l3-unicast-topology/l3tet:l3-te" { when "../nw:network-types/l3t:l3-unicast-topology/l3tet:l3-te" {
description "Augment only for L3 TE topology"; description
"Augment only for L3 TE topology";
} }
description "Augment topology configuration"; description
"Augment topology configuration";
uses l3-te-topology-attributes; uses l3-te-topology-attributes;
} }
augment "/nw:networks/nw:network/nw:node/l3t:l3-node-attributes" { augment "/nw:networks/nw:network/nw:node/l3t:l3-node-attributes" {
when "../../nw:network-types/l3t:l3-unicast-topology/" when "../../nw:network-types/l3t:l3-unicast-topology/"
+ "l3tet:l3-te" { + "l3tet:l3-te" {
description "Augment only for L3 TE topology"; description
"Augment only for L3 TE topology";
} }
description "Augment node configuration"; description
"Augment node configuration";
uses l3-te-node-attributes; uses l3-te-node-attributes;
} }
augment "/nw:networks/nw:network/nw:node/nt:termination-point/" augment "/nw:networks/nw:network/nw:node/nt:termination-point/"
+ "l3t:l3-termination-point-attributes" { + "l3t:l3-termination-point-attributes" {
when "../../../nw:network-types/l3t:l3-unicast-topology/" when "../../../nw:network-types/l3t:l3-unicast-topology/"
+ "l3tet:l3-te" { + "l3tet:l3-te" {
description "Augment only for L3 TE topology"; description
"Augment only for L3 TE topology";
} }
description "Augment termination point configuration"; description
"Augment termination point configuration";
uses l3-te-tp-attributes; uses l3-te-tp-attributes;
} }
augment "/nw:networks/nw:network/nt:link/l3t:l3-link-attributes" { augment "/nw:networks/nw:network/nt:link/l3t:l3-link-attributes" {
when "../../nw:network-types/l3t:l3-unicast-topology/" when "../../nw:network-types/l3t:l3-unicast-topology/"
+ "l3tet:l3-te" { + "l3tet:l3-te" {
description "Augment only for L3 TE topology"; description
"Augment only for L3 TE topology";
} }
description "Augment link configuration"; description
"Augment link configuration";
uses l3-te-link-attributes; uses l3-te-link-attributes;
} }
grouping l3-te-topology-attributes { grouping l3-te-topology-attributes {
description "L3 TE topology scope attributes"; description
"L3 TE topology scope attributes";
container l3-te-topology-attributes { container l3-te-topology-attributes {
must "/nw:networks/nw:network" must "/nw:networks/nw:network"
+ "[nw:network-id = current()/network-ref]/nw:network-types/" + "[nw:network-id = current()/network-ref]/nw:network-types/"
+ "tet:te-topology" { + "tet:te-topology" {
error-message error-message
"The referenced network must be a TE topology."; "The referenced network must be a TE topology.";
description description
"The referenced network must be a TE topology."; "The referenced network must be a TE topology.";
} }
description "Containing TE topology references"; description
"Containing TE topology references";
uses nw:network-ref; uses nw:network-ref;
} // l3-te-topology-attributes } // l3-te-topology-attributes
} // l3-te-topology-attributes } // l3-te-topology-attributes
grouping l3-te-node-attributes { grouping l3-te-node-attributes {
description "L3 TE node scope attributes"; description
"L3 TE node scope attributes";
container l3-te-node-attributes { container l3-te-node-attributes {
must "/nw:networks/nw:network" must "/nw:networks/nw:network"
+ "[nw:network-id = current()/network-ref]/nw:network-types/" + "[nw:network-id = current()/network-ref]/nw:network-types/"
+ "tet:te-topology" { + "tet:te-topology" {
error-message error-message
"The referenced network must be a TE topology."; "The referenced network must be a TE topology.";
description description
"The referenced network must be a TE topology."; "The referenced network must be a TE topology.";
} }
description "Containing TE node references"; description
"Containing TE node references";
uses nw:node-ref; uses nw:node-ref;
} // l3-te } // l3-te
} // l3-te-node-attributes } // l3-te-node-attributes
grouping l3-te-tp-attributes { grouping l3-te-tp-attributes {
description "L3 TE termination point scope attributes"; description
"L3 TE termination point scope attributes";
container l3-te-tp-attributes { container l3-te-tp-attributes {
must "/nw:networks/nw:network" must "/nw:networks/nw:network"
+ "[nw:network-id = current()/network-ref]/nw:network-types/" + "[nw:network-id = current()/network-ref]/nw:network-types/"
+ "tet:te-topology" { + "tet:te-topology" {
error-message error-message
"The referenced network must be a TE topology."; "The referenced network must be a TE topology.";
description description
"The referenced network must be a TE topology."; "The referenced network must be a TE topology.";
} }
description "Containing TE termination point references"; description
"Containing TE termination point references";
uses nt:tp-ref; uses nt:tp-ref;
} // l3-te } // l3-te
} // l3-te-tp-attributes } // l3-te-tp-attributes
grouping l3-te-link-attributes { grouping l3-te-link-attributes {
description "L3 TE link scope attributes"; description
"L3 TE link scope attributes";
container l3-te-link-attributes { container l3-te-link-attributes {
must "/nw:networks/nw:network" must "/nw:networks/nw:network"
+ "[nw:network-id = current()/network-ref]/nw:network-types/" + "[nw:network-id = current()/network-ref]/nw:network-types/"
+ "tet:te-topology" { + "tet:te-topology" {
error-message error-message
"The referenced network must be a TE topology."; "The referenced network must be a TE topology.";
description description
"The referenced network must be a TE topology."; "The referenced network must be a TE topology.";
} }
description "Containing TE link references"; description
"Containing TE link references";
uses nt:link-ref; uses nt:link-ref;
} }
} // l3-te-link-attributes } // l3-te-link-attributes
} }
<CODE ENDS> <CODE ENDS>
5.2. Packet Switching TE Topology Module 5.2. Packet Switching TE Topology Module
This module references [RFC7471], [RFC7810], [RFC7823], [RFC8294], This module references [RFC7471], [RFC7823], [RFC8294], [RFC8345],
[RFC8345], [RFC8346]. [I-D.ietf-teas-yang-te-types], and [RFC8346]. [RFC8570], [I-D.ietf-teas-yang-te-types], and
[I-D.ietf-teas-yang-te-topo]. [I-D.ietf-teas-yang-te-topo].
<CODE BEGINS> file "ietf-te-topology-packet@2019-02-28.yang" <CODE BEGINS> file "ietf-te-topology-packet@2019-06-28.yang"
module ietf-te-topology-packet { module ietf-te-topology-packet {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-te-topology-packet"; namespace "urn:ietf:params:xml:ns:yang:ietf-te-topology-packet";
prefix "tet-pkt"; prefix "tet-pkt";
import ietf-network { import ietf-network {
prefix "nw"; prefix "nw";
reference "RFC 8345: A YANG Data Model for Network Topologies"; reference
"RFC 8345: A YANG Data Model for Network Topologies";
} }
import ietf-network-topology { import ietf-network-topology {
prefix "nt"; prefix "nt";
reference "RFC 8345: A YANG Data Model for Network Topologies"; reference
"RFC 8345: A YANG Data Model for Network Topologies";
} }
import ietf-routing-types { import ietf-routing-types {
prefix "rt-types"; prefix "rt-types";
reference reference
"RFC 8294: Common YANG Data Types for the Routing Area"; "RFC 8294: Common YANG Data Types for the Routing Area";
} }
import ietf-te-topology { import ietf-te-topology {
prefix "tet"; prefix "tet";
reference reference
"I-D.ietf-teas-yang-te-topo: YANG Data Model for Traffic "I-D.ietf-teas-yang-te-topo: YANG Data Model for Traffic
skipping to change at page 33, line 26 skipping to change at page 34, line 10
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set the license terms contained in, the Simplified BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the This version of this YANG module is part of RFC XXXX; see the
RFC itself for full legal notices."; RFC itself for full legal notices.";
revision 2019-02-28 { revision 2019-06-28 {
description "Initial revision"; description
reference "RFC XXXX: YANG Data Model for Layer 3 TE Topologies"; "Initial revision";
reference
"RFC XXXX: YANG Data Model for Layer 3 TE Topologies";
} }
/* /*
* Features * Features
*/ */
feature te-performance-metric { feature te-performance-metric {
description description
"This feature indicates that the system supports "This feature indicates that the system supports
TE performance metric."; TE performance metric.";
reference reference
"RFC7471: OSPF Traffic Engineering (TE) Metric Extensions. "RFC7471: OSPF Traffic Engineering (TE) Metric Extensions.
RFC7810: IS-IS Traffic Engineering (TE) Metric Extensions. RFC8570: IS-IS Traffic Engineering (TE) Metric Extensions.
RFC7823: Performance-Based Path Selection for Explicitly RFC7823: Performance-Based Path Selection for Explicitly
Routed Label Switched Paths (LSPs) Using TE Metric Routed Label Switched Paths (LSPs) Using TE Metric
Extensions"; Extensions";
} }
/* /*
* Groupings * Groupings
*/ */
grouping packet-switch-capable-container { grouping packet-switch-capable-container {
description description
skipping to change at page 36, line 42 skipping to change at page 37, line 28
te-packet-types:performance-metrics-throttle-container-packet { te-packet-types:performance-metrics-throttle-container-packet {
if-feature te-performance-metric; if-feature te-performance-metric;
} }
} }
/* Augmentations to te-link-attributes */ /* Augmentations to te-link-attributes */
augment "/nw:networks/tet:te/tet:templates/" augment "/nw:networks/tet:te/tet:templates/"
+ "tet:link-template/tet:te-link-attributes" { + "tet:link-template/tet:te-link-attributes" {
when "tet:interface-switching-capability " when "tet:interface-switching-capability "
+ "[tet:switching-capability = 'te-types:switching-psc1']" { + "[tet:switching-capability = 'te-types:switching-psc1']" {
description "Valid only for PSC"; description
"Valid only for PSC";
} }
description description
"Parameters for PSC TE topology."; "Parameters for PSC TE topology.";
uses te-packet-types:performance-metrics-attributes-packet { uses te-packet-types:performance-metrics-attributes-packet {
if-feature te-performance-metric; if-feature te-performance-metric;
refine performance-metrics-one-way { refine performance-metrics-one-way {
config false; config false;
} }
refine performance-metrics-two-way { refine performance-metrics-two-way {
config false; config false;
skipping to change at page 37, line 17 skipping to change at page 38, line 4
uses uses
te-packet-types:performance-metrics-throttle-container-packet { te-packet-types:performance-metrics-throttle-container-packet {
if-feature te-performance-metric; if-feature te-performance-metric;
} }
} }
augment "/nw:networks/nw:network/nt:link/tet:te/" augment "/nw:networks/nw:network/nt:link/tet:te/"
+ "tet:te-link-attributes" { + "tet:te-link-attributes" {
when "tet:interface-switching-capability " when "tet:interface-switching-capability "
+ "[tet:switching-capability = 'te-types:switching-psc1']" { + "[tet:switching-capability = 'te-types:switching-psc1']" {
description "Valid only for PSC"; description
"Valid only for PSC";
} }
description description
"Parameters for PSC TE topology."; "Parameters for PSC TE topology.";
uses te-packet-types:performance-metrics-attributes-packet { uses te-packet-types:performance-metrics-attributes-packet {
if-feature te-performance-metric; if-feature te-performance-metric;
refine performance-metrics-one-way { refine performance-metrics-one-way {
config false; config false;
} }
refine performance-metrics-two-way { refine performance-metrics-two-way {
config false; config false;
skipping to change at page 37, line 40 skipping to change at page 38, line 28
uses uses
te-packet-types:performance-metrics-throttle-container-packet { te-packet-types:performance-metrics-throttle-container-packet {
if-feature te-performance-metric; if-feature te-performance-metric;
} }
} }
augment "/nw:networks/nw:network/nt:link/tet:te/" augment "/nw:networks/nw:network/nt:link/tet:te/"
+ "tet:information-source-entry" { + "tet:information-source-entry" {
when "tet:interface-switching-capability " when "tet:interface-switching-capability "
+ "[tet:switching-capability = 'te-types:switching-psc1']" { + "[tet:switching-capability = 'te-types:switching-psc1']" {
description "Valid only for PSC"; description
"Valid only for PSC";
} }
description description
"Parameters for PSC TE topology."; "Parameters for PSC TE topology.";
uses te-packet-types:performance-metrics-attributes-packet { uses te-packet-types:performance-metrics-attributes-packet {
if-feature te-performance-metric; if-feature te-performance-metric;
} }
uses uses
te-packet-types:performance-metrics-throttle-container-packet { te-packet-types:performance-metrics-throttle-container-packet {
if-feature te-performance-metric; if-feature te-performance-metric;
} }
skipping to change at page 38, line 4 skipping to change at page 38, line 41
description description
"Parameters for PSC TE topology."; "Parameters for PSC TE topology.";
uses te-packet-types:performance-metrics-attributes-packet { uses te-packet-types:performance-metrics-attributes-packet {
if-feature te-performance-metric; if-feature te-performance-metric;
} }
uses uses
te-packet-types:performance-metrics-throttle-container-packet { te-packet-types:performance-metrics-throttle-container-packet {
if-feature te-performance-metric; if-feature te-performance-metric;
} }
} }
/* Augmentations to interface-switching-capability */ /* Augmentations to interface-switching-capability */
augment "/nw:networks/tet:te/tet:templates/" augment "/nw:networks/tet:te/tet:templates/"
+ "tet:link-template/tet:te-link-attributes/" + "tet:link-template/tet:te-link-attributes/"
+ "tet:interface-switching-capability" { + "tet:interface-switching-capability" {
when "tet:switching-capability = 'te-types:switching-psc1' " { when "tet:switching-capability = 'te-types:switching-psc1' " {
description "Valid only for PSC"; description
"Valid only for PSC";
} }
description description
"Parameters for PSC TE topology."; "Parameters for PSC TE topology.";
uses packet-switch-capable-container; uses packet-switch-capable-container;
} }
augment "/nw:networks/nw:network/nt:link/tet:te/" augment "/nw:networks/nw:network/nt:link/tet:te/"
+ "tet:te-link-attributes/" + "tet:te-link-attributes/"
+ "tet:interface-switching-capability" { + "tet:interface-switching-capability" {
when "tet:switching-capability = 'te-types:switching-psc1' " { when "tet:switching-capability = 'te-types:switching-psc1' " {
description "Valid only for PSC"; description
"Valid only for PSC";
} }
description description
"Parameters for PSC TE topology."; "Parameters for PSC TE topology.";
uses packet-switch-capable-container; uses packet-switch-capable-container;
} }
augment "/nw:networks/nw:network/nt:link/tet:te/" augment "/nw:networks/nw:network/nt:link/tet:te/"
+ "tet:information-source-entry/" + "tet:information-source-entry/"
+ "tet:interface-switching-capability" { + "tet:interface-switching-capability" {
when "tet:switching-capability = 'te-types:switching-psc1' " { when "tet:switching-capability = 'te-types:switching-psc1' " {
description "Valid only for PSC"; description
"Valid only for PSC";
} }
description description
"Parameters for PSC TE topology."; "Parameters for PSC TE topology.";
uses packet-switch-capable-container; uses packet-switch-capable-container;
} }
} }
<CODE ENDS> <CODE ENDS>
6. IANA Considerations 6. IANA Considerations
skipping to change at page 40, line 19 skipping to change at page 41, line 13
-------------------------------------------------------------------- --------------------------------------------------------------------
7. Security Considerations 7. Security Considerations
The YANG module specified in this document defines a schema for data The YANG module specified in this document defines a schema for data
that is designed to be accessed via network management protocols such that is designed to be accessed via network management protocols such
as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer
is the secure transport layer, and the mandatory-to-implement secure is the secure transport layer, and the mandatory-to-implement secure
transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer
is HTTPS, and the mandatory-to-implement secure transport is TLS is HTTPS, and the mandatory-to-implement secure transport is TLS
[RFC5246]. [RFC8446].
The NETCONF access control model [RFC6536] provides the means to The Network Configuration Access Control Model (NACM) [RFC8341]
restrict access for particular NETCONF or RESTCONF users to a provides the means to restrict access for particular NETCONF or
preconfigured subset of all available NETCONF or RESTCONF protocol RESTCONF users to a preconfigured subset of all available NETCONF or
operations and content. RESTCONF protocol operations and content.
There are a number of data nodes defined in this YANG module that are There are a number of data nodes defined in this YANG module that are
writable/creatable/deletable (i.e., config true, which is the writable/creatable/deletable (i.e., config true, which is the
default). These data nodes may be considered sensitive or vulnerable default). These data nodes may be considered sensitive or vulnerable
in some network environments. Write operations (e.g., edit-config) in some network environments. Write operations (e.g., edit-config)
to these data nodes without proper protection can have a negative to these data nodes without proper protection can have a negative
effect on network operations. These are the subtrees and data nodes effect on network operations. These are the subtrees and data nodes
and their sensitivity/vulnerability: and their sensitivity/vulnerability:
/nw:networks/nw:network/nw:network-types/l3t:l3-unicast-topology/ /nw:networks/nw:network/nw:network-types/l3t:l3-unicast-topology/
skipping to change at page 42, line 32 skipping to change at page 43, line 25
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security [RFC3471] Berger, L., Ed., "Generalized Multi-Protocol Label
(TLS) Protocol Version 1.2", RFC 5246, Switching (GMPLS) Signaling Functional Description",
DOI 10.17487/RFC5246, August 2008, RFC 3471, DOI 10.17487/RFC3471, January 2003,
<https://www.rfc-editor.org/info/rfc5246>. <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., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/info/rfc6241>. <https://www.rfc-editor.org/info/rfc6241>.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
<https://www.rfc-editor.org/info/rfc6242>. <https://www.rfc-editor.org/info/rfc6242>.
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration [RFC7074] Berger, L. and J. Meuric, "Revised Definition of the GMPLS
Protocol (NETCONF) Access Control Model", RFC 6536, Switching Capability and Type Fields", RFC 7074,
DOI 10.17487/RFC6536, March 2012, DOI 10.17487/RFC7074, November 2013,
<https://www.rfc-editor.org/info/rfc6536>. <https://www.rfc-editor.org/info/rfc7074>.
[RFC7471] Giacalone, S., Ward, D., Drake, J., Atlas, A., and S. [RFC7471] Giacalone, S., Ward, D., Drake, J., Atlas, A., and S.
Previdi, "OSPF Traffic Engineering (TE) Metric Previdi, "OSPF Traffic Engineering (TE) Metric
Extensions", RFC 7471, DOI 10.17487/RFC7471, March 2015, Extensions", RFC 7471, DOI 10.17487/RFC7471, March 2015,
<https://www.rfc-editor.org/info/rfc7471>. <https://www.rfc-editor.org/info/rfc7471>.
[RFC7810] Previdi, S., Ed., Giacalone, S., Ward, D., Drake, J., and
Q. Wu, "IS-IS Traffic Engineering (TE) Metric Extensions",
RFC 7810, DOI 10.17487/RFC7810, May 2016,
<https://www.rfc-editor.org/info/rfc7810>.
[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>.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016, RFC 7950, DOI 10.17487/RFC7950, August 2016,
<https://www.rfc-editor.org/info/rfc7950>. <https://www.rfc-editor.org/info/rfc7950>.
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
<https://www.rfc-editor.org/info/rfc8040>. <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, [RFC8294] Liu, X., Qu, Y., Lindem, A., Hopps, C., and L. Berger,
"Common YANG Data Types for the Routing Area", RFC 8294, "Common YANG Data Types for the Routing Area", RFC 8294,
DOI 10.17487/RFC8294, December 2017, DOI 10.17487/RFC8294, December 2017,
<https://www.rfc-editor.org/info/rfc8294>. <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., [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore Architecture and R. Wilton, "Network Management Datastore Architecture
(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
<https://www.rfc-editor.org/info/rfc8342>. <https://www.rfc-editor.org/info/rfc8342>.
[RFC8345] Clemm, A., Medved, J., Varga, R., Bahadur, N., [RFC8345] Clemm, A., Medved, J., Varga, R., Bahadur, N.,
Ananthakrishnan, H., and X. Liu, "A YANG Data Model for Ananthakrishnan, H., and X. Liu, "A YANG Data Model for
Network Topologies", RFC 8345, DOI 10.17487/RFC8345, March Network Topologies", RFC 8345, DOI 10.17487/RFC8345, March
2018, <https://www.rfc-editor.org/info/rfc8345>. 2018, <https://www.rfc-editor.org/info/rfc8345>.
[RFC8346] Clemm, A., Medved, J., Varga, R., Liu, X., [RFC8346] Clemm, A., Medved, J., Varga, R., Liu, X.,
Ananthakrishnan, H., and N. Bahadur, "A YANG Data Model Ananthakrishnan, H., and N. Bahadur, "A YANG Data Model
for Layer 3 Topologies", RFC 8346, DOI 10.17487/RFC8346, for Layer 3 Topologies", RFC 8346, DOI 10.17487/RFC8346,
March 2018, <https://www.rfc-editor.org/info/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] [I-D.ietf-teas-yang-te-types]
Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin,
"Traffic Engineering Common YANG Types", draft-ietf-teas- "Traffic Engineering Common YANG Types", draft-ietf-teas-
yang-te-types-06 (work in progress), February 2019. yang-te-types-09 (work in progress), May 2019.
[I-D.ietf-teas-yang-te-topo] [I-D.ietf-teas-yang-te-topo]
Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and Liu, X., Bryskin, I., Beeram, V., Saad, T., Shah, H., and
O. Dios, "YANG Data Model for Traffic Engineering (TE) O. Dios, "YANG Data Model for Traffic Engineering (TE)
Topologies", draft-ietf-teas-yang-te-topo-19 (work in Topologies", draft-ietf-teas-yang-te-topo-22 (work in
progress), February 2019. progress), June 2019.
8.2. Informative References 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", [RFC7951] Lhotka, L., "JSON Encoding of Data Modeled with YANG",
RFC 7951, DOI 10.17487/RFC7951, August 2016, RFC 7951, DOI 10.17487/RFC7951, August 2016,
<https://www.rfc-editor.org/info/rfc7951>. <https://www.rfc-editor.org/info/rfc7951>.
[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
<https://www.rfc-editor.org/info/rfc8340>. <https://www.rfc-editor.org/info/rfc8340>.
Appendix A. Companion YANG Model for Non-NMDA Compliant Implementations Appendix A. Companion YANG Model for Non-NMDA Compliant Implementations
skipping to change at page 45, line 31 skipping to change at page 46, line 31
implementations that support NMDA. implementations that support NMDA.
As the structure of the companion modules mirrors that of the As the structure of the companion modules mirrors that of the
coorespinding NMDA models, the YANG trees of the companion modules coorespinding NMDA models, the YANG trees of the companion modules
are not depicted separately. are not depicted separately.
A.1. Layer 3 TE Topology State Module A.1. Layer 3 TE Topology State Module
This module references [RFC8345], and [RFC8346]. This module references [RFC8345], and [RFC8346].
<CODE BEGINS> file "ietf-l3-te-topology-state@2019-02-28.yang" <CODE BEGINS> file "ietf-l3-te-topology-state@2019-06-28.yang"
module ietf-l3-te-topology-state { module ietf-l3-te-topology-state {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-l3-te-topology-state"; namespace "urn:ietf:params:xml:ns:yang:ietf-l3-te-topology-state";
prefix "l3tet-s"; prefix "l3tet-s";
import ietf-l3-te-topology { import ietf-l3-te-topology {
prefix "l3tet"; prefix "l3tet";
} }
import ietf-network-state { import ietf-network-state {
prefix "nw-s"; prefix "nw-s";
skipping to change at page 46, line 47 skipping to change at page 47, line 47
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set the license terms contained in, the Simplified BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the This version of this YANG module is part of RFC XXXX; see the
RFC itself for full legal notices."; RFC itself for full legal notices.";
revision 2019-02-28 { revision 2019-06-28 {
description
description "Initial revision"; "Initial revision";
reference "RFC XXXX: YANG Data Model for Layer 3 TE Topologies"; reference "RFC XXXX: YANG Data Model for Layer 3 TE Topologies";
} }
augment "/nw-s:networks/nw-s:network/nw-s:network-types/" augment "/nw-s:networks/nw-s:network/nw-s:network-types/"
+ "l3t-s:l3-unicast-topology" { + "l3t-s:l3-unicast-topology" {
description description
"Defines the L3 TE topology type."; "Defines the L3 TE topology type.";
uses l3tet:l3-te-topology-type; uses l3tet:l3-te-topology-type;
} }
augment "/nw-s:networks/nw-s:network/" augment "/nw-s:networks/nw-s:network/"
+ "l3t-s:l3-topology-attributes" { + "l3t-s:l3-topology-attributes" {
when "../nw-s:network-types/l3t-s:l3-unicast-topology/" when "../nw-s:network-types/l3t-s:l3-unicast-topology/"
+ "l3tet-s:l3-te" { + "l3tet-s:l3-te" {
description "Augment only for L3 TE topology"; description
"Augment only for L3 TE topology";
} }
description "Augment topology configuration"; description
"Augment topology configuration";
uses l3tet:l3-te-topology-attributes; uses l3tet:l3-te-topology-attributes;
} }
augment "/nw-s:networks/nw-s:network/nw-s:node/" augment "/nw-s:networks/nw-s:network/nw-s:node/"
+ "l3t-s:l3-node-attributes" { + "l3t-s:l3-node-attributes" {
when "../../nw-s:network-types/l3t-s:l3-unicast-topology/" when "../../nw-s:network-types/l3t-s:l3-unicast-topology/"
+ "l3tet-s:l3-te" { + "l3tet-s:l3-te" {
description "Augment only for L3 TE topology"; description
"Augment only for L3 TE topology";
} }
description "Augment node configuration"; description
"Augment node configuration";
uses l3tet:l3-te-node-attributes; uses l3tet:l3-te-node-attributes;
} }
augment "/nw-s:networks/nw-s:network/nw-s:node/" augment "/nw-s:networks/nw-s:network/nw-s:node/"
+ "nt-s:termination-point/" + "nt-s:termination-point/"
+ "l3t-s:l3-termination-point-attributes" { + "l3t-s:l3-termination-point-attributes" {
when "../../../nw-s:network-types/l3t-s:l3-unicast-topology/" when "../../../nw-s:network-types/l3t-s:l3-unicast-topology/"
+ "l3tet-s:l3-te" { + "l3tet-s:l3-te" {
description "Augment only for L3 TE topology"; description
"Augment only for L3 TE topology";
} }
description "Augment termination point configuration"; description
"Augment termination point configuration";
uses l3tet:l3-te-tp-attributes; uses l3tet:l3-te-tp-attributes;
} }
augment "/nw-s:networks/nw-s:network/nt-s:link/" augment "/nw-s:networks/nw-s:network/nt-s:link/"
+ "l3t-s:l3-link-attributes" { + "l3t-s:l3-link-attributes" {
when "../../nw-s:network-types/l3t-s:l3-unicast-topology/" when "../../nw-s:network-types/l3t-s:l3-unicast-topology/"
+ "l3tet-s:l3-te" { + "l3tet-s:l3-te" {
description "Augment only for L3 TE topology"; description
"Augment only for L3 TE topology";
} }
description "Augment link configuration"; description
"Augment link configuration";
uses l3tet:l3-te-link-attributes; uses l3tet:l3-te-link-attributes;
} }
} }
<CODE ENDS> <CODE ENDS>
A.2. Packet Switching TE Topology State Module A.2. Packet Switching TE Topology State Module
<CODE BEGINS> file "ietf-te-topology-packet-state@2019-02-28.yang" <CODE BEGINS> file "ietf-te-topology-packet-state@2019-06-28.yang"
module ietf-te-topology-packet-state { module ietf-te-topology-packet-state {
yang-version 1.1; yang-version 1.1;
namespace namespace
"urn:ietf:params:xml:ns:yang:ietf-te-topology-packet-state"; "urn:ietf:params:xml:ns:yang:ietf-te-topology-packet-state";
prefix "tet-pkt-s"; prefix "tet-pkt-s";
import ietf-te-topology-packet { import ietf-te-topology-packet {
prefix "tet-pkt"; prefix "tet-pkt";
} }
import ietf-network-state { import ietf-network-state {
prefix "nw-s"; prefix "nw-s";
reference "RFC 8345: A YANG Data Model for Network Topologies"; reference
"RFC 8345: A YANG Data Model for Network Topologies";
} }
import ietf-network-topology-state { import ietf-network-topology-state {
prefix "nt-s"; prefix "nt-s";
reference "RFC 8345: A YANG Data Model for Network Topologies"; reference
"RFC 8345: A YANG Data Model for Network Topologies";
} }
import ietf-te-topology-state { import ietf-te-topology-state {
prefix "tet-s"; prefix "tet-s";
reference reference
"I-D.ietf-teas-yang-te-topo: YANG Data Model for Traffic "I-D.ietf-teas-yang-te-topo: YANG Data Model for Traffic
Engineering (TE) Topologies"; Engineering (TE) Topologies";
} }
import ietf-te-types { import ietf-te-types {
skipping to change at page 49, line 51 skipping to change at page 51, line 12
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set the license terms contained in, the Simplified BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the This version of this YANG module is part of RFC XXXX; see the
RFC itself for full legal notices."; RFC itself for full legal notices.";
revision 2019-02-28 { revision 2019-06-28 {
description "Initial revision"; description
reference "RFC XXXX: YANG Data Model for Layer 3 TE Topologies"; "Initial revision";
reference
"RFC XXXX: YANG Data Model for Layer 3 TE Topologies";
} }
/* /*
* Augmentations * Augmentations
*/ */
/* Augmentations to connectivity-matrix */ /* Augmentations to connectivity-matrix */
augment "/nw-s:networks/nw-s:network/nw-s:node/tet-s:te/" augment "/nw-s:networks/nw-s:network/nw-s:node/tet-s:te/"
+ "tet-s:te-node-attributes/tet-s:connectivity-matrices" { + "tet-s:te-node-attributes/tet-s:connectivity-matrices" {
description description
"Parameters for PSC (Packet Switching) TE topology."; "Parameters for PSC (Packet Switching) TE topology.";
skipping to change at page 52, line 4 skipping to change at page 53, line 17
} }
uses uses
te-packet-types:performance-metrics-throttle-container-packet { te-packet-types:performance-metrics-throttle-container-packet {
if-feature tet-pkt:te-performance-metric; if-feature tet-pkt:te-performance-metric;
} }
} }
/* Augmentations to te-link-attributes */ /* Augmentations to te-link-attributes */
augment "/nw-s:networks/tet-s:te/tet-s:templates/" augment "/nw-s:networks/tet-s:te/tet-s:templates/"
+ "tet-s:link-template/tet-s:te-link-attributes" { + "tet-s:link-template/tet-s:te-link-attributes" {
when "tet-s:interface-switching-capability " when "tet-s:interface-switching-capability "
+ "[tet-s:switching-capability = 'te-types:switching-psc1']" { + "[tet-s:switching-capability = 'te-types:switching-psc1']" {
description "Valid only for PSC"; description
"Valid only for PSC";
} }
description description
"Parameters for PSC TE topology."; "Parameters for PSC TE topology.";
uses te-packet-types:performance-metrics-attributes-packet { uses te-packet-types:performance-metrics-attributes-packet {
if-feature tet-pkt:te-performance-metric; if-feature tet-pkt:te-performance-metric;
} }
uses uses
te-packet-types:performance-metrics-throttle-container-packet { te-packet-types:performance-metrics-throttle-container-packet {
if-feature tet-pkt:te-performance-metric; if-feature tet-pkt:te-performance-metric;
} }
skipping to change at page 53, line 31 skipping to change at page 54, line 45
} }
description description
"Parameters for PSC TE topology."; "Parameters for PSC TE topology.";
uses tet-pkt:packet-switch-capable-container; uses tet-pkt:packet-switch-capable-container;
} }
augment "/nw-s:networks/nw-s:network/nt-s:link/tet-s:te/" augment "/nw-s:networks/nw-s:network/nt-s:link/tet-s:te/"
+ "tet-s:information-source-entry/" + "tet-s:information-source-entry/"
+ "tet-s:interface-switching-capability" { + "tet-s:interface-switching-capability" {
when "tet-s:switching-capability = 'te-types:switching-psc1' " { when "tet-s:switching-capability = 'te-types:switching-psc1' " {
description "Valid only for PSC"; description
"Valid only for PSC";
} }
description description
"Parameters for PSC TE topology."; "Parameters for PSC TE topology.";
uses tet-pkt:packet-switch-capable-container; uses tet-pkt:packet-switch-capable-container;
} }
} }
<CODE ENDS> <CODE ENDS>
Appendix B. Data Tree Example Appendix B. Data Tree Example
This section contains an example of an instance data tree in the JSON This section contains an example of an instance data tree in the JSON
encoding [RFC7951]. The example instantiates "ietf-l3-te-topology" encoding [RFC7951]. The example instantiates "ietf-l3-te-topology"
for the topology that is depicted in the following diagram. for the topology that is depicted in the following diagram.
+------------+ +------------+ +------------+ +------------+
skipping to change at page 54, line 34 skipping to change at page 55, line 43
+------------+ +------------+
The corresponding instance data tree is depicted below. Note that The corresponding instance data tree is depicted below. Note that
some lines have been wrapped to adhere to the 72-character line some lines have been wrapped to adhere to the 72-character line
limitation of RFCs. limitation of RFCs.
{ {
"ietf-network:networks": { "ietf-network:networks": {
"network": [ "network": [
{ {
"network-id":"example-topo-te",
"network-types": { "network-types": {
"ietf-te-topology:te-topology": {} "ietf-te-topology:te-topology": {
}
},
"ietf-te-topology:te-topology-identifier": {
"provider-id":200,
"client-id":300,
"topology-id":"example-topo-te"
}, },
"network-id": "example-topo-te",
"ietf-te-topology:provider-id": 200,
"ietf-te-topology:client-id": 300,
"ietf-te-topology:te-topology-id": "example-topo-te",
"ietf-te-topology:te": { "ietf-te-topology:te": {
}, },
"node": [ "node": [
{ {
"node-id": "D1", "node-id":"D1",
"ietf-te-topology:te-node-id": "2.0.1.1", "ietf-te-topology:te-node-id":"2.0.1.1",
"ietf-te-topology:te": { "ietf-te-topology:te": {
"te-node-attributes": { "te-node-attributes": {
} }
}, },
"ietf-network-topology:termination-point": [ "ietf-network-topology:termination-point": [
{ {
"tp-id": "1-2-1", "tp-id":"1-2-1",
"ietf-te-topology:te-tp-id": 10201, "ietf-te-topology:te-tp-id":10201,
"ietf-te-topology:te": { "ietf-te-topology:te": {
"interface-switching-capability": [ "interface-switching-capability": [
{ {
"switching-capability": "switching-psc1", "switching-capability":
"encoding": "lsp-encoding-ethernet" "ietf-te-types:switching-psc1",
"encoding":
"ietf-te-types:lsp-encoding-ethernet"
} }
] ]
} }
}, },
{ {
"tp-id": "1-3-1", "tp-id": "1-3-1",
"ietf-te-topology:te-tp-id": 10301, "ietf-te-topology:te-tp-id":10301,
"ietf-te-topology:te": { "ietf-te-topology:te": {
"interface-switching-capability": [ "interface-switching-capability": [
{ {
"switching-capability": "switching-psc1", "switching-capability":
"encoding": "lsp-encoding-ethernet" "ietf-te-types:switching-psc1",
"encoding":
"ietf-te-types:lsp-encoding-ethernet"
} }
] ]
} }
} }
] ]
}, },
{ {
"node-id": "D2", "node-id":"D2",
"ietf-te-topology:te-node-id": "2.0.2.1", "ietf-te-topology:te-node-id":"2.0.2.1",
"ietf-te-topology:te": { "ietf-te-topology:te": {
"te-node-attributes": { "te-node-attributes": {
} }
}, },
"ietf-network-topology:termination-point": [ "ietf-network-topology:termination-point": [
{ {
"tp-id": "2-1-1", "tp-id":"2-1-1",
"ietf-te-topology:te-tp-id": 20101, "ietf-te-topology:te-tp-id":20101,
"ietf-te-topology:te": { "ietf-te-topology:te": {
"interface-switching-capability": [ "interface-switching-capability": [
{ {
"switching-capability": "switching-psc1", "switching-capability":
"encoding": "lsp-encoding-ethernet" "ietf-te-types:switching-psc1",
"encoding":
"ietf-te-types:lsp-encoding-ethernet"
} }
] ]
} }
} }
] ]
}, },
{ {
"node-id": "D3", "node-id":"D3",
"ietf-te-topology:te-node-id": "2.0.3.1", "ietf-te-topology:te-node-id":"2.0.3.1",
"ietf-te-topology:te": { "ietf-te-topology:te": {
"te-node-attributes": { "te-node-attributes": {
} }
}, },
"ietf-network-topology:termination-point": [ "ietf-network-topology:termination-point": [
{ {
"tp-id": "3-1-1", "tp-id":"3-1-1",
"ietf-te-topology:te-tp-id": 30101, "ietf-te-topology:te-tp-id":30101,
"ietf-te-topology:te": { "ietf-te-topology:te": {
"interface-switching-capability": [ "interface-switching-capability": [
{ {
"switching-capability": "switching-psc1", "switching-capability":
"encoding": "lsp-encoding-ethernet" "ietf-te-types:switching-psc1",
"encoding":
"ietf-te-types:lsp-encoding-ethernet"
} }
] ]
} }
} }
] ]
} }
], ],
"ietf-network-topology:link": [ "ietf-network-topology:link": [
{ {
"link-id": "D1,1-2-1,D2,2-1-1", "link-id":"D1,1-2-1,D2,2-1-1",
"source": { "source": {
"source-node": "D1", "source-node":"D1",
"source-tp": "1-2-1" "source-tp":"1-2-1"
}, },
"destination": { "destination": {
"dest-node": "D2", "dest-node":"D2",
"dest-tp": "2-1-1" "dest-tp":"2-1-1"
}, },
"ietf-te-topology:te": { "ietf-te-topology:te": {
"te-link-attributes": { "te-link-attributes": {
"interface-switching-capability": [ "interface-switching-capability": [
{ {
"switching-capability": "switching-psc1", "switching-capability":
"encoding": "lsp-encoding-ethernet" "ietf-te-types:switching-psc1",
"encoding":"ietf-te-types:lsp-encoding-ethernet"
} }
], ],
"max-link-bandwidth": { "max-link-bandwidth": {
"te-bandwidth": { "te-bandwidth": {
"generic": "0x1p+18" "generic":"0x1p+18"
} }
}, },
"te-default-metric": 100 "te-default-metric":100
} }
} }
}, },
{ {
"link-id": "D2,2-1-1,D1,1-2-1", "link-id":"D2,2-1-1,D1,1-2-1",
"source": { "source": {
"source-node": "D2", "source-node":"D2",
"source-tp": "2-1-1" "source-tp":"2-1-1"
}, },
"destination": { "destination": {
"dest-node": "D1", "dest-node":"D1",
"dest-tp": "1-2-1" "dest-tp":"1-2-1"
}, },
"ietf-te-topology:te": { "ietf-te-topology:te": {
"te-link-attributes": { "te-link-attributes": {
"interface-switching-capability": [ "interface-switching-capability": [
{ {
"switching-capability": "switching-psc1", "switching-capability":
"encoding": "lsp-encoding-ethernet" "ietf-te-types:switching-psc1",
"encoding":"ietf-te-types:lsp-encoding-ethernet"
} }
], ],
"max-link-bandwidth": { "max-link-bandwidth": {
"te-bandwidth": { "te-bandwidth": {
"generic": "0x1p+18" "generic":"0x1p+18"
} }
}, },
"te-default-metric": 100 "te-default-metric":100
} }
} }
}, },
{ {
"link-id": "D1,1-3-1,D3,3-1-1", "link-id":"D1,1-3-1,D3,3-1-1",
"source": { "source": {
"source-node": "D1", "source-node":"D1",
"source-tp": "1-3-1" "source-tp":"1-3-1"
}, },
"destination": { "destination": {
"dest-node": "D3", "dest-node":"D3",
"dest-tp": "3-1-1" "dest-tp":"3-1-1"
}, },
"ietf-te-topology:te": { "ietf-te-topology:te": {
"te-link-attributes": { "te-link-attributes": {
"interface-switching-capability": [ "interface-switching-capability": [
{ {
"switching-capability": "switching-psc1", "switching-capability":
"encoding": "lsp-encoding-ethernet" "ietf-te-types:switching-psc1",
"encoding":"ietf-te-types:lsp-encoding-ethernet"
} }
], ],
"max-link-bandwidth": { "max-link-bandwidth": {
"te-bandwidth": { "te-bandwidth": {
"generic": "0x1p+18" "generic":"0x1p+18"
} }
}, },
"te-default-metric": 100 "te-default-metric":100
} }
} }
}, },
{ {
"link-id": "D3,3-1-1,D1,1-3-1", "link-id":"D3,3-1-1,D1,1-3-1",
"source": { "source": {
"source-node": "D3", "source-node":"D3",
"source-tp": "3-1-1" "source-tp":"3-1-1"
}, },
"destination": { "destination": {
"dest-node": "D1", "dest-node":"D1",
"dest-tp": "1-3-1" "dest-tp":"1-3-1"
}, },
"ietf-te-topology:te": { "ietf-te-topology:te": {
"te-link-attributes": { "te-link-attributes": {
"interface-switching-capability": [ "interface-switching-capability": [
{ {
"switching-capability": "switching-psc1", "switching-capability":
"encoding": "lsp-encoding-ethernet" "ietf-te-types:switching-psc1",
"encoding":"ietf-te-types:lsp-encoding-ethernet"
} }
], ],
"max-link-bandwidth": { "max-link-bandwidth": {
"te-bandwidth": { "te-bandwidth": {
"generic": "0x1p+18" "generic":"0x1p+18"
} }
}, },
"te-default-metric": 100 "te-default-metric":100
} }
} }
} }
] ]
}, },
{ {
"network-id":"example-topo-l3-te",
"network-types": { "network-types": {
"ietf-l3-unicast-topology:l3-unicast-topology": { "ietf-l3-unicast-topology:l3-unicast-topology": {
"ietf-l3-te-topology:l3-te": {} "ietf-l3-te-topology:l3-te": {
}
} }
}, },
"network-id": "example-topo-l3-te",
"ietf-l3-unicast-topology:l3-topology-attributes": { "ietf-l3-unicast-topology:l3-topology-attributes": {
"ietf-l3-te-topology:l3-te-topology-attributes": { "ietf-l3-te-topology:l3-te-topology-attributes": {
"network-ref": "example-topo-te" "network-ref":"example-topo-te"
} }
}, },
"node": [ "node": [
{ {
"node-id": "D1", "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": [ "ietf-network-topology:termination-point": [
{ {
"tp-id": "1-0-1", "tp-id":"1-0-1",
"ietf-l3-unicast-topology:l3-termination-point-attributes": { "ietf-l3-unicast-topology:l3-termination-point-attributes": {
"unnumbered-id": 101 "unnumbered-id":101
} }
}, },
{ {
"tp-id": "1-2-1", "tp-id":"1-2-1",
"ietf-l3-unicast-topology:l3-termination-point-attributes": { "ietf-l3-unicast-topology:l3-termination-point-attributes": {
"unnumbered-id": 121, "unnumbered-id":121,
"ietf-l3-te-topology:l3-te-tp-attributes": { "ietf-l3-te-topology:l3-te-tp-attributes": {
"tp-ref": "1-2-1" "network-ref":"example-topo-te",
"tp-ref":"1-2-1"
} }
} }
}, },
{ {
"tp-id": "1-3-1", "tp-id":"1-3-1",
"ietf-l3-unicast-topology:l3-termination-point-attributes": { "ietf-l3-unicast-topology:l3-termination-point-attributes": {
"unnumbered-id": 131, "unnumbered-id":131,
"ietf-l3-te-topology:l3-te-tp-attributes": { "ietf-l3-te-topology:l3-te-tp-attributes": {
"tp-ref": "1-3-1" "network-ref":"example-topo-te",
"tp-ref":"1-3-1"
} }
} }
} }
], ]
},
{
"node-id":"D2",
"ietf-l3-unicast-topology:l3-node-attributes": { "ietf-l3-unicast-topology:l3-node-attributes": {
"router-id": ["203.0.113.1"], "router-id": [
"203.0.113.2"
],
"prefix": [ "prefix": [
{ {
"prefix": "203.0.113.1/32" "prefix":"203.0.113.2/32"
} }
], ],
"ietf-l3-te-topology:l3-te-node-attributes": { "ietf-l3-te-topology:l3-te-node-attributes": {
"node-ref": "D1" "node-ref":"D2",
"network-ref":"example-topo-te"
} }
} },
},
{
"node-id": "D2",
"ietf-network-topology:termination-point": [ "ietf-network-topology:termination-point": [
{ {
"tp-id": "2-0-1", "tp-id":"2-0-1",
"ietf-l3-unicast-topology:l3-termination-point-attributes": { "ietf-l3-unicast-topology:l3-termination-point-attributes": {
"unnumbered-id": 201 "unnumbered-id":201
} }
}, },
{ {
"tp-id": "2-1-1", "tp-id":"2-1-1",
"ietf-l3-unicast-topology:l3-termination-point-attributes": { "ietf-l3-unicast-topology:l3-termination-point-attributes": {
"unnumbered-id": 211, "unnumbered-id":211,
"ietf-l3-te-topology:l3-te-tp-attributes": { "ietf-l3-te-topology:l3-te-tp-attributes": {
"tp-ref": "2-1-1" "tp-ref":"2-1-1",
"network-ref":"example-topo-te"
} }
} }
}, },
{ {
"tp-id": "2-3-1", "tp-id":"2-3-1",
"ietf-l3-unicast-topology:l3-termination-point-attributes": { "ietf-l3-unicast-topology:l3-termination-point-attributes": {
"unnumbered-id": 231 "unnumbered-id":231
} }
} }
], ]
},
{
"node-id":"D3",
"ietf-l3-unicast-topology:l3-node-attributes": { "ietf-l3-unicast-topology:l3-node-attributes": {
"router-id": ["203.0.113.2"], "router-id": [
"203.0.113.3"
],
"prefix": [ "prefix": [
{ {
"prefix": "203.0.113.2/32" "prefix":"203.0.113.3/32"
} }
], ],
"ietf-l3-te-topology:l3-te-node-attributes": { "ietf-l3-te-topology:l3-te-node-attributes": {
"node-ref": "D2" "node-ref":"D3",
"network-ref":"example-topo-te"
} }
} },
},
{
"node-id": "D3",
"ietf-network-topology:termination-point": [ "ietf-network-topology:termination-point": [
{ {
"tp-id": "3-1-1", "tp-id":"3-0-1",
"ietf-l3-unicast-topology:l3-termination-point-attributes": { "ietf-l3-unicast-topology:l3-termination-point-attributes": {
"unnumbered-id": 311, "unnumbered-id":301
}
},
{
"tp-id":"3-1-1",
"ietf-l3-unicast-topology:l3-termination-point-attributes": {
"unnumbered-id":311,
"ietf-l3-te-topology:l3-te-tp-attributes": { "ietf-l3-te-topology:l3-te-tp-attributes": {
"tp-ref": "3-1-1" "tp-ref":"3-1-1",
"network-ref":"example-topo-te"
} }
} }
}, },
{ {
"tp-id": "3-2-1", "tp-id":"3-2-1",
"ietf-l3-unicast-topology:l3-termination-point-attributes": { "ietf-l3-unicast-topology:l3-termination-point-attributes": {
"unnumbered-id": 321 "unnumbered-id":321
}
}
],
"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"
} }
} ]
} }
], ],
"ietf-network-topology:link": [ "ietf-network-topology:link": [
{ {
"link-id": "D1,1-2-1,D2,2-1-1", "link-id":"D1,1-2-1,D2,2-1-1",
"source": { "source": {
"source-node": "D1", "source-node":"D1",
"source-tp": "1-2-1" "source-tp":"1-2-1"
}, },
"destination": { "destination": {
"dest-node": "D2", "dest-node":"D2",
"dest-tp": "2-1-1" "dest-tp":"2-1-1"
}, },
"ietf-l3-unicast-topology:l3-link-attributes": { "ietf-l3-unicast-topology:l3-link-attributes": {
"metric1": "100", "metric1":"100",
"ietf-l3-te-topology:l3-te-link-attributes": { "ietf-l3-te-topology:l3-te-link-attributes": {
"link-ref": "D1,1-2-1,D2,2-1-1" "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", "link-id":"D2,2-1-1,D1,1-2-1",
"source": { "source": {
"source-node": "D2", "source-node":"D2",
"source-tp": "2-1-1" "source-tp":"2-1-1"
}, },
"destination": { "destination": {
"dest-node": "D1", "dest-node":"D1",
"dest-tp": "1-2-1" "dest-tp":"1-2-1"
}, },
"ietf-l3-unicast-topology:l3-link-attributes": { "ietf-l3-unicast-topology:l3-link-attributes": {
"metric1": "100", "metric1":"100",
"ietf-l3-te-topology:l3-te-link-attributes": { "ietf-l3-te-topology:l3-te-link-attributes": {
"link-ref": "D2,2-1-1,D1,1-2-1" "link-ref":"D2,2-1-1,D1,1-2-1",
"network-ref":"example-topo-te"
} }
} }
}, },
{ {
"link-id": "D1,1-3-1,D3,3-1-1", "link-id":"D1,1-3-1,D3,3-1-1",
"source": { "source": {
"source-node": "D1", "source-node":"D1",
"source-tp": "1-3-1" "source-tp":"1-3-1"
}, },
"destination": { "destination": {
"dest-node": "D3", "dest-node":"D3",
"dest-tp": "3-1-1" "dest-tp":"3-1-1"
}, },
"ietf-l3-unicast-topology:l3-link-attributes": { "ietf-l3-unicast-topology:l3-link-attributes": {
"metric1": "100", "metric1":"100",
"ietf-l3-te-topology:l3-te-link-attributes": { "ietf-l3-te-topology:l3-te-link-attributes": {
"link-ref": "D1,1-3-1,D3,3-1-1" "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", "link-id":"D3,3-1-1,D1,1-3-1",
"source": { "source": {
"source-node": "D3", "source-node":"D3",
"source-tp": "3-1-1" "source-tp":"3-1-1"
}, },
"destination": { "destination": {
"dest-node": "D1", "dest-node":"D1",
"dest-tp": "1-3-1" "dest-tp":"1-3-1"
}, },
"ietf-l3-unicast-topology:l3-link-attributes": { "ietf-l3-unicast-topology:l3-link-attributes": {
"metric1": "100", "metric1":"100",
"ietf-l3-te-topology:l3-te-link-attributes": { "ietf-l3-te-topology:l3-te-link-attributes": {
"link-ref": "D3,3-1-1,D1,1-3-1" "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", "link-id":"D2,2-3-1,D3,3-2-1",
"source": { "source": {
"source-node": "D2", "source-node":"D2",
"source-tp": "2-3-1" "source-tp":"2-3-1"
}, },
"destination": { "destination": {
"dest-node": "D3", "dest-node":"D3",
"dest-tp": "3-2-1" "dest-tp":"3-2-1"
}, },
"ietf-l3-unicast-topology:l3-link-attributes": { "ietf-l3-unicast-topology:l3-link-attributes": {
"metric1": "100" "metric1":"100"
} }
}, },
{ {
"link-id": "D3,3-2-1,D2,2-3-1", "link-id":"D3,3-2-1,D2,2-3-1",
"source": { "source": {
"source-node": "D3", "source-node":"D3",
"source-tp": "3-2-1" "source-tp":"3-2-1"
}, },
"destination": { "destination": {
"dest-node": "D2", "dest-node":"D2",
"dest-tp": "2-3-1" "dest-tp":"2-3-1"
}, },
"ietf-l3-unicast-topology:l3-link-attributes": { "ietf-l3-unicast-topology:l3-link-attributes": {
"metric1": "100" "metric1":"100"
} }
} }
] ]
} }
] ]
} }
} }
Authors' Addresses Authors' Addresses
Xufeng Liu Xufeng Liu
Volta Networks Volta Networks
EMail: xufeng.liu.ietf@gmail.com EMail: xufeng.liu.ietf@gmail.com
Igor Bryskin Igor Bryskin
Huawei Technologies Futurewei
EMail: Igor.Bryskin@huawei.com EMail: igor.bryskin@futurewei.com
Vishnu Pavan Beeram Vishnu Pavan Beeram
Juniper Networks Juniper Networks
EMail: vbeeram@juniper.net EMail: vbeeram@juniper.net
Tarek Saad Tarek Saad
Cisco Systems Inc Juniper Networks
EMail: tsaad@juniper.net
EMail: tsaad@cisco.com
Himanshu Shah Himanshu Shah
Ciena Ciena
EMail: hshah@ciena.com EMail: hshah@ciena.com
Oscar Gonzalez de Dios Oscar Gonzalez de Dios
Telefonica Telefonica
EMail: oscar.gonzalezdedios@telefonica.com EMail: oscar.gonzalezdedios@telefonica.com
 End of changes. 192 change blocks. 
275 lines changed or deleted 386 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/