YANG Model for TE Topologies Vishnu Pavan Beeram

YANG Model for TE Topologies Vishnu Pavan Beeram (Juniper Networks) Igor Bryskin (ADVA Optical Networking) Oscar Gonzalez de Dios (Telefonica) Xufeng Liu (Ericsson) Tarek Saad (Cisco) Himanshu Shah (Ciena) 1

Agenda • Existing Work: Recap • Design Team: Scope/Goals/Plans • Open Discussion Items 2

Current Work of Relevance • A fair number of “topology” specific models are currently being discussed within IETF. • Yang Models that address/directly-impact Traffic-Engineering Topologies: • Abstract TE Topologies • Optical TED • MPLS-TE specific entities 3

Recap: Abstract TE Topologies – Yang Model • Allows the provider to present the network TE Topology in “abstract” terms on per client basis. • Notifications to registered clients (can carry incremental updates). • Allows the client to retrieve/(re-)configure the abstract TE topological elements presented by the provider network. • Model captures overlay/underlay relationships for nodes and links • Time scheduling attributes • For each topological element (or) for the whole topology 4

Recap: Abstract TE Topologies – Yang Model: Relevant Drafts Network Topology <draft-clemm-i 2 rsyang-l 3 -topo> Abstract TE Topology L 3 -Unicast-IGP Topology OSPF-Topology <draft-clemm-i 2 rs-yang-network-topo> Building Blocks <draft-liu-yangabstract-te-topo> ISIS-Topology TED <draft-liu-yang-ted> Helper Module TE specific groupings 5

Recap: Optical TED – Yang Model • Draft: • draft-vergara-flexigrid-yang-00 • Module defines all the information needed to represent an optical node, optical transponder and an optical link 6

Recap: MPLS-TE specific entities • Collaborated effort in progress • Effort covers MPLS-TE Tunnels/LSPs, Links and other related entities • Placeholder: • https: //github. com/ietf-mpls-yang/te 7

Design Team – Goals/Scope • Collaborate and deliver a data-model for “TE Topologies” • Immediate focus: Technology-agnostic model (common to all network layers) • Next Phases - Technology specific models to be augmentations of the above model (Open Discussion Item). • Timeline: • Draft(s) ready by the next IETF 8

Design Team - Logistics • Bi-Weekly Meetings • Periodic updates to the WG • Github placeholder 9

Open Items/Questions • Dependency on generic network topology models • Augment link/node constructs defined in the <generic-network-topo> model (or) have stand-alone TED-link/TED-node constructs. • Dependency on MPLS-TE specific entity models • Needs close collaboration • Which attributes should get modeled in which data-model? • Other topology-model dependencies/relationships? • Should there be separate library(/ies) (helper module for TE specific groupings)? • Technology specific TE-Topology models • Sequential or parallel effort(s) 10

Thank You 11