1. draft-ietf-teas-yang-te-topo-06
Yang Data Model for TE Topologies draft-ietf-teas-yang-te-topo-06 Github:
Xufeng Liu (Kuatro Technologies)
Vishnu Pavan Beeram (Juniper Networks)
Igor Bryskin (Huawei Technologies)
Tarek Saad (Cisco)
Himanshu Shah (Ciena)
Oscar Gonzalez De Dios (Telefonica)
Contributors:
Sergio Belotti (Nokia)
Diete Beller (Nokia)

2. Summary of Changes Cleaned up notifications
Updated configuration scheduling
Fixed information source
Defined generic bandwidth
Removed technology specific attributes
Added statistics section
Completed connectivity matrix modeling
Added geographic location modeling
Completed local link connectivity list entry
Improved alternate key modeling
Adding MDLG (Mutually Disjoint Link Group)

3. Cleaned up notifications
Use draft-ietf-netconf-rfc5277bis and draft-ietf-netconf- yang-push
Separate model to configure event subscriptions
TE topology model does not include event schema
Events can be subscribed and filtered on any schema node
+--rw subscription-config
| +--rw subscription* [subscription-id]
| rw subscription-id
| rw (filter-type)?
| | +--:(yp:update-filter)
| | rw (yp:update-filter)?
| | :(yp:subtree)
| | | +--rw yp:subtree-filter
| | :(yp:xpath)
| | rw yp:xpath-filter?
| rw (yp:update-trigger)?
| | +--:(yp:periodic)
| | | +--rw yp:period
| | +--:(yp:on-change) {on-change}?
| | rw yp:no-synch-on-start?
| | rw yp:dampening-period
| | rw yp:excluded-change*
augment /nw:networks/nw:network/nt:link:
+--rw te!
+--rw config
| +--rw te-link-template*
| +--rw te-link-attributes
| rw access-type?
| rw external-domain
| rw is-abstract?
| rw name?
+---n te-link-event
+--ro event-type?
+--ro link-ref?
+--ro network-ref?
+--ro te-topology!
+--ro te-link-attributes
+--ro oper-status?
+--ro is-transitional?
+--ro information-source?

4. Updated configuration scheduling
Separate model to configure scheduling
TE topology model does not include scheduling schema
Scheduling model can be used for any target models without altering, e.g. te-tunnel model
More powerful, capable of changing leaf values
module: ietf-schedule
+--rw configuration-schedules
+--rw target* [object]
+--rw object yang:xpath1.0
+--rw data-value? string
+--rw schedules
| +--rw schedule*
| rw schedule-id
| rw inclusive-exclusive?
| rw start?
| rw schedule-duration?
| rw repeat-interval?
augment /nw:networks/nw:network/nt:link:
+--rw te!
+--rw config
| +--rw te-link-template*
| +--rw te-link-attributes
| rw schedules
| | +--rw schedule*
| | rw schedule-id
| | rw start?
| | rw schedule-duration?
| | rw repeat-interval?
| rw access-type?
| rw external-domain
| rw is-abstract?
| rw name?

5. Fixed information source
Completed information source attributes
augment /nw:networks/nw:network/nw:node:
+--rw te-node-id? te-types:te-node-id
+--rw te!
+--ro state
| +--ro information-source-state
| | +--ro credibility-preference? uint16
| | +--ro logical-network-element? string
| | +--ro network-instance? string
| | +--ro topology
| | ro provider-ref? leafref
| | ro client-ref? leafref
| | ro te-topology-ref? leafref
| | ro network-ref? leafref
| | ro node-ref? Leafref
augment /nw:networks/nw:network/nt:link:
| | ro link-ref? leafref

6. Information Source Example
Domain TE topologies
renamed and merged into client’s native TE topology
C-11
C-21
S13
S15
S23
S25
C-22
S18
S24
S28
C-12
S19
S17
S29
S27
C-23
Information Source
Information Source
Domain 1 TE topology
Domain 2 TE topology S3 S5 S3 S5 S8 S4 S8 S9 S7 S9 S7

7. Defined generic bandwidth
A list of numbers separated by commas
Packet switching: a float number is used, e.g. 0x1p10
OTN switching: a list of integers, e.g. '0,2,3,1', indicating 2 odu0's and 1 odu3
DWDM, a list of slot number and width, e.g. '0, 2, 3, 3', indicating slot 0 with slot width 2 and slot 3 with slot width 3
typedef te-bandwidth {
type string {
pattern
'0[xX](0((\.0?)?[pP](\+)?0?|(\.0?))|'
+ '1(\.([\da-fA-F]{0,5}[02468aAcCeE]?)?)?[pP](\+)?(12[0-7]|'
+ '1[01]\d|0?\d?\d)?)|0[xX][\da-fA-F]{1,8}|\d+'
+ '(,(0[xX](0((\.0?)?[pP](\+)?0?|(\.0?))|'
+ '1[01]\d|0?\d?\d)?)|0[xX][\da-fA-F]{1,8}|\d+))*'; }

8. Removed technology specific attributes
To make this model technology agnostic, removed
Performance metric
Time division multiplex capable attributes

9. Added statistics section
Node level statistics
augment /nw:networks/nw:network/nw:node:
+--rw te-node-id? te-types:te-node-id
+--rw te!
+--ro statistics
+--ro discontinuity-time yang:date-and-time
+--ro tunnel-termination-point
| +--ro disables? yang:counter32
| +--ro enables? yang:counter32
| +--ro maintenance-clears? yang:counter32
| +--ro maintenance-sets? yang:counter32
| +--ro modifies? yang:counter32
| +--ro downs? yang:counter32
| +--ro ups? yang:counter32
| +--ro in-service-clears? yang:counter32
| +--ro in-service-sets? yang:counter32
+--ro local-link-connectivity
+--ro creates? yang:counter32
+--ro deletes? yang:counter32
+--ro disables? yang:counter32
+--ro enables? yang:counter32
+--ro modifies? yang:counter32

10. Added statistics section
Link level statistics
augment /nw:networks/nw:network/nt:link:
+--rw te!
+--ro statistics
+--ro discontinuity-time yang:date-and-time
+--ro disables? yang:counter32
+--ro enables? yang:counter32
+--ro maintenance-clears? yang:counter32
+--ro maintenance-sets? yang:counter32
+--ro modifies? yang:counter32
+--ro downs? yang:counter32
+--ro ups? yang:counter32
+--ro fault-clears? yang:counter32
+--ro fault-detects? yang:counter32
+--ro protection-switches? yang:counter32
+--ro protection-reverts? yang:counter32
+--ro restoration-failures? yang:counter32
+--ro restoration-starts? yang:counter32
+--ro restoration-successes? yang:counter32
+--ro restoration-reversion-failures? yang:counter32
+--ro restoration-reversion-starts? yang:counter32
+--ro restoration-reversion-successes? yang:counter32

11. Completed connectivity matrix modeling
Added underlay information as in a TE link
Connectivity matrix entry {LTP-6,LTP-1} is catered by underlay TE-path {E’-M-P-Q-N-F’} in Topology-Red
LTP-1
Server Link Termination Point (S-LTP)
LTP-6
LTP-2
LTP-5
LTP-4
LTP-3
Topology -Red E’ M N F’ O P Q R

12. Completed local link connectivity list entry
Added
Bandwidth information
Max LSP bandwidth
Max link bandwidth
Max reserved bandwidth
Unreserved bandwidth per priority
TE metric
SRLG
C-LTP-1,2,3
C-LTP-4,5,6
Tunnel Termination Point (TTP)
Server Link Termination Point (S-LTP)
Client Link Termination Point (C-LTP)
TTP-1
TTP-3
TTP-2
LTP-1
Local Link Connectivity List Entry
LTP-6
LTP-2
LTP-5
LTP-4
LTP-3

13. Added geographic location modeling
Requested from operator
Added the geographic location information to
Node
Link termination point
Tunnel termination point
Information is read-only
+--ro geolocation
+--ro altitude? int64
+--ro latitude? geographic-coordinate-degree
+--ro longitude? geographic-coordinate-degree

14. Improved alternate key modeling
Alternate keys can be used more easily by XPath
augment /nw:networks/nw:network:
+--rw provider-id? te-types:te-global-id
+--rw client-id? te-types:te-global-id
+--rw te-topology-id? te-types:te-topology-id
+--rw te!
+--rw provider-id te-types:te-global-id
+--rw client-id te-types:te-global-id
+--rw te-topology-id te-types:te-topology-id
+--rw config
+--ro state
augment /nw:networks/nw:network/nw:node:
+--rw te-node-id? te-types:te-node-id
+--rw te-node-id te-types:te-node-id
| +--ro oper-status? te-types:te-oper-status
Example XPath queries
Use primary key (existing):
/networks/network/node[node-id="node-1"]/te/state/oper-status
Or use alternate key (new):
/networks/network/node[te-node-id=" "]/te/state/oper-status

15. MDLG (Mutually Disjoint Link Group)
When an abstract TE link is configured, client can request a TE link to be mutually diverse disjoint with other TE links in the same topology
Opposite to SRLG. The alternative name can be: “NRLG (Not-shared Risk)” or “MILG (Mutually Independent)”.
e.g. TE Links B-C and EF are diverse at link-disjoint level
Topology -Blue B C A D
TE-Link B-C in Topology-Blue is catered to by underlay TE-path {B’-O-M-N-P-C’} in Topology-Red E F
Topology -Red M N B’ O P C’
TE-Link E-F in Topology-Blue is catered to by underlay TE-path {E’-Q-O-P-R-F’} in Topology-Red E’ Q R F’

16. MDLG Modeling On TE Link MDLG Definition
augment /nw:networks/nw:network/nt:link:
+--rw te!
+--rw config
| +--rw te-link-attributes
| rw is-abstract? empty
| rw underlay! {te-topology-hierarchy}?
......
| rw te-srlgs
| rw value* te-types:srlg
| rw te-mdlgs {mdlg}?
| rw id* leafref
+--ro state
| +--ro te-link-attributes
| | +--ro te-mdlgs {mdlg}?
| | ro id* uint32
MDLG Definition
augment /nw:networks/nw:network:
+--rw provider-id? te-types:te-global-id
+--rw client-id? te-types:te-global-id
+--rw te-topology-id? te-types:te-topology-id
+--rw te!
+--rw config
| +--rw preference? uint8
| +--rw optimization-criterion? identityref
| +--rw mdlg* [id] {mdlg}?
| rw id uint32
| rw disjointness? enumeration {none, node, link, srlg}

17. Next Steps
Request further review
WG last call

18. draft-liu-teas-yang-l3-te-topo-02
Yang Data Model for Layer 3 TE Topologies draft-liu-teas-yang-l3-te-topo-02
Xufeng Liu (Kuatro Technologies)
Vishnu Pavan Beeram (Juniper Networks)
Igor Bryskin (Huawei Technologies)
Tarek Saad (Cisco)
Himanshu Shah (Ciena)
Oscar Gonzalez De Dios (Telefonica)

19. Augmentation Hierarchy
draft-liu-teas-yang-l3-te-topo-01
Augmentation Hierarchy
L3 TE Topology augments L3 Topology and references TE Topology.
Packet extension module augments ietf-te-topology.
Changed name to ietf-te-topology-packet from ietf-te-topology-pcs based on WG feedbacks.
Layer 3 Topology ietf-l3-topology
TE Topology ietf-te-topology
Augment,
a “inheritance” relation
Leafref,
an “association” relation
Layer 3 TE Topology ietf-l3-te-topology
TE Topology Packet Extension ietf-te-topology-packet

20. Model Reorganizations
draft-liu-teas-yang-l3-te-topo-01
Model Reorganizations
Moved some packet specific schema from based TE topology to this model
module: ietf-te-topology-packet
Augment /nw:networks/nw:network/nw:node/tet:te/tet:config/ tet:te-node-attributes/tet:connectivity-matrix:
+--rw performance-metric {te-performance-metric}?
| +--rw measurement
| | +--rw unidirectional-delay? uint32
| | +--rw unidirectional-min-delay? uint32
| | +--rw unidirectional-max-delay? uint32
| | +--rw unidirectional-delay-variation? uint32
| | +--rw unidirectional-packet-loss? decimal64
| | +--rw unidirectional-residual-bandwidth? decimal64
| | +--rw unidirectional-available-bandwidth? decimal64
| | +--rw unidirectional-utilized-bandwidth? decimal64
| +--rw normality
......
+--rw performance-metric-throttle {te-performance-metric}?
+--rw unidirectional-delay-offset? Uint32

21. Next Steps
Request further review.
Ask for WG adoption.

22. draft-liu-teas-yang-sr-te-topo-01
Yang Data Model for SR and SR TE Topologies draft-liu-teas-yang-sr-te-topo-01
Xufeng Liu (Kuatro Technologies)
Vishnu Pavan Beeram (Juniper Networks)
Igor Bryskin (Huawei Technologies)
Tarek Saad (Cisco)
Himanshu Shah (Ciena)
Stephane Litkowski (Orange)

23. SR (Segment Routing) Topology
draft-liu-teas-yang-sr-te-topo-01
SR (Segment Routing) Topology
Augment layer 3 network topology model
Updated according to latest version of layer 3 topology model
Layer 3 Network Topology ietf-l3-unicast-topology
Segment Rougint Topology ietf-sr-topology

24. SR (Segment Routing) TE Topology
Multiple inheritance:
Is both SR topology and layer 3 TE topology model.
Uses multiple network types: “l3-te” and “sr”.
SR Topology ietf-sr-topology
Layer 3 TE Topology ietf-l3-te-topology
SR TE Topology

25. Collaboration with SR Yang Model
Worked with authors of draft-ietf-spring-sr-yang
Split shared groupings into ietf-segment-routing-common.yang
Used shared SR groupings instead of own definitions

26. Next Steps Add support for protection on link.
Add support for link bundle.