1. A Yang Data Model for ACTN VN Operation draft-lee-teas-actn-vn-yang-01
A Yang Data Model for ACTN VN Operation draft-lee-teas-actn-vn-yang-01.txt
Young Lee (Huawei), Daniele Ceccarelli (Ericsson), Dhruv Doddy (Huawei) Takuya Miyasaka (KDDI), Peter Park (KT), Bin Young Yoon (ETRI)
Contributors: Sergio Belotti (Nokia), Xian Zhang, Haomian Zheng (Huawei)
July 17 – July 22, 2016
IETF 96, Berlin

2. ACTN Architectural Context:
This draft fulfills
Requirements 4-6 from
ACTN Requirement draft
VN Instantiate
VN Dynamic Control
VN Lifecycle M&O
CMI
MPI
SBI
Customer Network Controller
Physical Network Controller
Multi-domain Service
Coordinator
CNC
MDSC
PNC
July 17 – July 22, 2016
IETF 96, Berlin

3. VN
There are various definitions of what Virtual Network means. Here, we are focusing on customer’s network slicing of TE network resources.
A VN may comprise a set of end-to-end tunnels from a customer point of view that connects customer endpoints (i.e., source CE and destination CE).
2. A VN may comprise of a number of virtual nodes and virtual links (more than a tunnel).
July 17 – July 22, 2016
IETF 96, Berlin

4. VN Relationship VN VN Member 1 VN Member 2 VN Member N CNC View
E2E TE-Tunnel 1
E2E TE-Tunnel 2
E2E TE-Tunnel N
MDSC View
LSP
LSP
LSP
PNC View
July 17 – July 22, 2016
IETF 96, Berlin

5. VN Instantiate MDSC Domain 1 Domain 3 Endpoint Domain 2
VN “Berlin”
CNC
Member 1
6. VN Instantiate
Response
Member 2
Member 3
MDSC
2. VN
Instantiate
2. VN
Instantiate
2. VN
Instantiate
5. VN Instantiate
Response
PNC
PNC
PNC
Domain 1
Domain 3
Endpoint
July 17 – July 22, 2016
IETF 96, Berlin
Domain 2

6. VN Access Point (AP) Customer End Point (CE1) Customer End Point (CE2)
PE 1
PE 1 x w y z
Customer View
Provider View
|AP id| MaxResBw | AvailableBw | CE,port |
| AP1 | 10Gb | 10Gb |CE1,portX |
| AP2 | 40Gb | 40Gb |CE2,portZ |
|AP id| MaxResBw | AvailableBw | PE,port |
| AP1 | 10Gb | 10Gb |PE1,portW |
| AP2 | 40Gb | 40Gb |PE2,portY |
July 17 – July 22, 2016
IETF 96, Berlin

7. VN YANG Tree VN Member Performance Data Access Point Definition
module: ietf-actn-vn +--rw actn | +--rw ap | | +--rw access-point-list* [access-point-id] | | +--rw access-point-id uint32 | | +--rw access-point-name? string | | +--rw max-bandwidth? decimal64 | | +--rw avl-bandwidth? decimal64 | +--rw vn | +--rw vn-list* [vn-id] | +--rw vn-id uint32 | +--rw vn-name? string | +--rw vn-member-list* [vn-member-id] | | +--rw vn-member-id uint32 | | +--rw src? leafref | | +--rw src-vn-ap-id? uint32 | | +--rw dest? leafref | | +--rw dest-vn-ap-id? uint32 | +--rw delay? uint32 | +--rw delay-variation? uint32 | +--rw packet-loss? decimal64 | +--rw bandwidth? decimal64 | +--rw protection? identityref | +--rw local-reroute? boolean | +--rw push-allowed? boolean | +--rw incremental-update? boolean | +--rw admin-status? identityref +--ro actn-state
+--ro actn-state +--ro ap | +--ro access-point-list* [access-point-id] | +--ro access-point-id uint32 | +--ro access-point-name? string | +--ro max-bandwidth? decimal64 | +--ro avl-bandwidth? decimal64 +--ro vn +--ro vn-list* [vn-id] +--ro vn-id uint32 +--ro vn-name? string +--ro vn-member-list* [vn-member-id] | +--ro vn-member-id uint32 | +--ro src? leafref | +--ro src-vn-ap-id? uint32 | +--ro dest? leafref | +--ro dest-vn-ap-id? uint32 | +--ro delay? uint32 | +--ro delay-variation? uint32 | +--ro packet-loss? decimal64 | +--ro oper-status? identityref +--ro delay? uint32 +--ro delay-variation? uint32 +--ro packet-loss? decimal64 +--ro bandwidth? decimal64 +--ro protection? identityref +--ro local-reroute? boolean +--ro push-allowed? boolean +--ro incremental-update? boolean +--ro admin-status? identityref
Access Point
Definition
VN Definition
VN Member
Association with
Access Points
VN Member
Performance
Data
VN Service
Chracteristics
VN Service Policy/Preference
July 17 – July 22, 2016
IETF 96, Berlin

8. Next Steps
This draft is focused on the VN YANG model to provide VN Type of “e2e tunnel” between customer end points.
A more complex VN type can be presented in next version
Refine YANG models
Align with FW/Info Model
More work on Access Point Characteristics
Evaluate any missing items
July 17 – July 22, 2016
IETF 96, Berlin