draft-ietf-teas-yang-te-topo-07.txt   draft-ietf-teas-yang-te-topo-08.txt 
skipping to change at page 1, line 15 skipping to change at page 1, line 15
Huawei Technologies Huawei Technologies
Vishnu Pavan Beeram Vishnu Pavan Beeram
Juniper Networks Juniper Networks
Tarek Saad Tarek Saad
Cisco Systems Inc Cisco Systems Inc
Himanshu Shah Himanshu Shah
Ciena Ciena
Oscar Gonzalez De Dios Oscar Gonzalez De Dios
Telefonica Telefonica
Expires: September 12, 2017 March 12, 2017 Expires: September 13, 2017 March 13, 2017
YANG Data Model for TE Topologies YANG Data Model for TE Topologies
draft-ietf-teas-yang-te-topo-07 draft-ietf-teas-yang-te-topo-08
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.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 41 skipping to change at page 1, line 41
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on September 12, 2017. This Internet-Draft will expire on September 13, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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 3, line 23 skipping to change at page 3, line 23
5.5. Generic TE Link Attributes...............................27 5.5. Generic TE Link Attributes...............................27
5.6. Generic TE Node Attributes...............................28 5.6. Generic TE Node Attributes...............................28
5.7. TED Information Sources..................................30 5.7. TED Information Sources..................................30
5.8. Overlay/Underlay Relationship............................31 5.8. Overlay/Underlay Relationship............................31
5.9. Templates................................................32 5.9. Templates................................................32
5.10. Scheduling Parameters...................................33 5.10. Scheduling Parameters...................................33
5.11. Notifications...........................................33 5.11. Notifications...........................................33
6. Tree Structure................................................34 6. Tree Structure................................................34
7. TE Topology Yang Module.......................................66 7. TE Topology Yang Module.......................................66
8. Security Considerations......................................117 8. Security Considerations......................................117
9. IANA Considerations..........................................117 9. IANA Considerations..........................................118
10. References..................................................118 10. References..................................................118
10.1. Normative References...................................118 10.1. Normative References...................................118
10.2. Informative References.................................118 10.2. Informative References.................................119
11. Acknowledgments.............................................119 11. Acknowledgments.............................................119
Contributors....................................................119 Contributors....................................................119
Authors' Addresses..............................................119 Authors' Addresses..............................................119
1. Introduction 1. Introduction
The Traffic Engineering Database (TED) is an essential component of The Traffic Engineering Database (TED) is an essential component of
Traffic Engineered (TE) systems that are based on MPLS-TE [RFC2702] Traffic Engineered (TE) systems that are based on MPLS-TE [RFC2702]
and GMPLS [RFC3945]. The TED is a collection of all TE information and GMPLS [RFC3945]. The TED is a collection of all TE information
about all TE nodes and TE links in the network. The TE Topology is a about all TE nodes and TE links in the network. The TE Topology is a
skipping to change at page 59, line 22 skipping to change at page 59, line 22
| | +--ro in-service-clears? yang:counter32 | | +--ro in-service-clears? yang:counter32
| | +--ro in-service-sets? yang:counter32 | | +--ro in-service-sets? yang:counter32
| +--ro local-link-connectivity | +--ro local-link-connectivity
| +--ro creates? yang:counter32 | +--ro creates? yang:counter32
| +--ro deletes? yang:counter32 | +--ro deletes? yang:counter32
| +--ro disables? yang:counter32 | +--ro disables? yang:counter32
| +--ro enables? yang:counter32 | +--ro enables? yang:counter32
| +--ro modifies? yang:counter32 | +--ro modifies? yang:counter32
+--rw supporting-tunnel-termination-point* [node-ref tunnel- +--rw supporting-tunnel-termination-point* [node-ref tunnel-
tp-ref] tp-ref]
+--rw node-ref union +--rw node-ref inet:uri
+--rw tunnel-tp-ref union +--rw tunnel-tp-ref binary
augment /nw:networks/nw:network/nt:link: augment /nw:networks/nw:network/nt:link:
+--rw te! +--rw te!
+--rw config +--rw config
| +--rw (bundle-stack-level)? | +--rw (bundle-stack-level)?
| | +--:(bundle) | | +--:(bundle)
| | | +--rw bundled-links | | | +--rw bundled-links
| | | +--rw bundled-link* [sequence] | | | +--rw bundled-link* [sequence]
| | | +--rw sequence uint32 | | | +--rw sequence uint32
| | | +--rw src-tp-ref? leafref | | | +--rw src-tp-ref? leafref
| | | +--rw des-tp-ref? leafref | | | +--rw des-tp-ref? leafref
skipping to change at page 66, line 16 skipping to change at page 66, line 16
| +--ro priority uint8 | +--ro priority uint8
| +--ro bandwidth? te-bandwidth | +--ro bandwidth? te-bandwidth
+--ro inter-layer-lock-id? uint32 +--ro inter-layer-lock-id? uint32
+--ro geolocation +--ro geolocation
+--ro altitude? int64 +--ro altitude? int64
+--ro latitude? geographic-coordinate-degree +--ro latitude? geographic-coordinate-degree
+--ro longitude? geographic-coordinate-degree +--ro longitude? geographic-coordinate-degree
7. TE Topology Yang Module 7. TE Topology Yang Module
<CODE BEGINS> file "ietf-te-topology@2017-03-10.yang" <CODE BEGINS> file "ietf-te-topology@2017-03-12.yang"
module ietf-te-topology { module ietf-te-topology {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-te-topology"; namespace "urn:ietf:params:xml:ns:yang:ietf-te-topology";
prefix "tet"; prefix "tet";
import ietf-yang-types { import ietf-yang-types {
prefix "yang"; prefix "yang";
} }
skipping to change at page 67, line 38 skipping to change at page 67, line 38
<mailto:tsaad@cisco.com> <mailto:tsaad@cisco.com>
Editor: Himanshu Shah Editor: Himanshu Shah
<mailto:hshah@ciena.com> <mailto:hshah@ciena.com>
Editor: Oscar Gonzalez De Dios Editor: Oscar Gonzalez De Dios
<mailto:oscar.gonzalezdedios@telefonica.com>"; <mailto:oscar.gonzalezdedios@telefonica.com>";
description "TE topology model"; description "TE topology model";
revision "2017-03-10" { revision "2017-03-12" {
description "Initial revision"; description "Initial revision";
reference "TBD"; reference "TBD";
} }
/* /*
* Features * Features
*/ */
feature nsrlg { feature nsrlg {
description description
"This feature indicates that the system supports NSRLG "This feature indicates that the system supports NSRLG
(Not Sharing Risk Link Group)."; (Not Sharing Risk Link Group).";
skipping to change at page 99, line 20 skipping to change at page 99, line 20
uses statistics-per-ttp; uses statistics-per-ttp;
} // statistics } // statistics
// Relations to other tunnel termination points // Relations to other tunnel termination points
list supporting-tunnel-termination-point { list supporting-tunnel-termination-point {
key "node-ref tunnel-tp-ref"; key "node-ref tunnel-tp-ref";
description description
"Identifies the tunnel termination points, that this "Identifies the tunnel termination points, that this
tunnel termination point is depending on."; tunnel termination point is depending on.";
leaf node-ref { leaf node-ref {
type inet:uri;
/* The followings are the intended valications
* but some Yang validation tools fail on them.
type union { type union {
type leafref { type leafref {
path "../../../../nw:supporting-node/nw:node-ref"; path "../../../../nw:supporting-node/nw:node-ref";
require-instance false; require-instance false;
} }
type leafref { type leafref {
path "/nw:networks/nw:network"+ path "/nw:networks/nw:network"+
"[nw:network-id="+ "[nw:network-id="+
"current()/../../../../te/config/"+ "current()/../../../../te/config/"+
"te-node-attributes/underlay-topology/"+ "te-node-attributes/underlay-topology/"+
skipping to change at page 99, line 41 skipping to change at page 100, line 4
require-instance false; require-instance false;
} }
type leafref { type leafref {
path "/nw:networks/nw:network"+ path "/nw:networks/nw:network"+
"[nw:network-id="+ "[nw:network-id="+
"current()/../../../../te/state/"+ "current()/../../../../te/state/"+
"te-node-attributes/underlay-topology/"+ "te-node-attributes/underlay-topology/"+
"network-ref]/nw:node/nw:node-id"; "network-ref]/nw:node/nw:node-id";
require-instance false; require-instance false;
} }
} }
***************************************************/
description description
"This leaf identifies in which node the supporting "This leaf identifies in which node the supporting
tunnel termination point is present."; tunnel termination point is present.";
} }
leaf tunnel-tp-ref { leaf tunnel-tp-ref {
type binary;
/* The followings are the intended valications
* but some Yang validation tools fail on them.
type union { type union {
type leafref { type leafref {
path "/nw:networks/nw:network"+ path "/nw:networks/nw:network"+
"[nw:network-id="+ "[nw:network-id="+
"current()/../../../../nw:supporting-node/"+ "current()/../../../../nw:supporting-node/"+
"nw:network-ref]/"+ "nw:network-ref]/"+
"nw:node[nw:node-id=current()/../node-ref]/te/"+ "nw:node[nw:node-id=current()/../node-ref]/te/"+
"tunnel-termination-point/tunnel-tp-id"; "tunnel-termination-point/tunnel-tp-id";
require-instance false; require-instance false;
} }
skipping to change at page 100, line 37 skipping to change at page 101, line 4
type leafref { type leafref {
path "/nw:networks/nw:network"+ path "/nw:networks/nw:network"+
"[nw:network-id="+ "[nw:network-id="+
"current()/../../../../te/state/"+ "current()/../../../../te/state/"+
"te-node-attributes/underlay-topology/"+ "te-node-attributes/underlay-topology/"+
"network-ref]/"+ "network-ref]/"+
"nw:node[nw:node-id=current()/../node-ref]/te/"+ "nw:node[nw:node-id=current()/../node-ref]/te/"+
"tunnel-termination-point/tunnel-tp-id"; "tunnel-termination-point/tunnel-tp-id";
require-instance false; require-instance false;
} }
} }
***************************************************/
description description
"Reference to the underlay node, must be in a "Reference to a tunnel terminiation point, which is
different topology"; either in the supporting node or a node in an
underlay topology.";
} }
} // supporting-tunnel-termination-point } // supporting-tunnel-termination-point
} // tunnel-termination-point } // tunnel-termination-point
} // te } // te
} // te-node-augment } // te-node-augment
grouping te-node-config { grouping te-node-config {
description "TE node configuration grouping."; description "TE node configuration grouping.";
leaf-list te-node-template { leaf-list te-node-template {
if-feature template; if-feature template;
type leafref { type leafref {
path "../../../../../te/templates/node-template/name"; path "../../../../../te/templates/node-template/name";
 End of changes. 16 change blocks. 
12 lines changed or deleted 22 lines changed or added

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