1. Subscriptions for Event Notification + Yang-push IETF NETCONF WG Contributors Call 26 - May - 2016

2. Agenda Intro of new members resulting out of NETCONF Interim (Balazs, Susan, Tim, Ebben) Results from NETMOD interim – Discussion: minimal text worthy of submitting for WG adoption. YANG Datastore Push Rqts doc through IESG Summary of open issues found during our meetings to date. – Timing and/or interest groups desiring to addressing the issues

3. Current Issues being Worked IssueTo work proposal Supporting multiple Receivers for a Configured Subscriptiontoday Proper behavior for on-change, detecting and indicating changes within a Dampening period today Negotiate vs. auto-adjustdiscuss What are the domains of different Stream types. QoS parameters for subscriptions. Relevance for buffering and loss of connectivity (i.e., this isn’t just about HTTP2) Layering security requirements/considerations into the YANG model for Configured Subscription. Mechanisms/RPCs for defined for Diagnostics OpState requirements and implications Deltas for OpenConfig-Telemetry.yang Replay support for different stream types (modify vs. delete) Event Dampening (overwhelming receivers) & rejecting certain subscription types How to structure for non-standardizable encodings

4. High level agreements/proposals waiting to be added to models Moving from separate start/stop to Anchor time for Periodic Test-only option for a subscription Periodic interval goes to seconds from timeticks Subtree-filter definition so that 6241 doesn't apply field filtering. Need the filters for Notification not for GET Balancing Augment vs. Parallel Model structures

5. Supporting multiple Receivers for a Configured Subscription Stream Type (Examples) Events NETCONF Config Operational Operational & Counters Custom Configured Subscription (two IP addresses) Filter Implementation Domain Dynamic Subscription (#3) Dynamic Subscription (#4) Filtered Stream D4 D3 D2 D1 Configured Receiver (#1) Configured Receiver (#2) Filtered Stream goes away when there is no attached subscription All four have one destination IP and one Subscription ID (Unique or not for Publisher or Publisher+Destination?) D D = Destination Streams have characteristics like replay support, ability to support on-change, others

6. Subscription to interface state Subscription Interfaces-state interface [name] oper-status E0E1 E0 E1 E0 E1 E0 10200405030 E0 E1 E0 E1 E0 1121233343 100 YANG Push Dampening period =10 On-change OC-Telemetry.yang Period =10 Suppress Redundant = Yes Interface UP Interface DOWN Time Update Stream Faster reaction Shows flaps underway Update Stream State at a certain time

7. Subscription to Access Control List Subscription ACL* ACL entries ACE YANG Push Dampening period = 60 On-change OC-Telemetry.yang Period = 60 Suppress Redundant = Yes Time matches action 50 access-list permit ip any any 100 access-list permit host 192.168.1.1 200 access-list deny any any 601200 125 8525 create 200 Update Stream Exposes existence of transient config Current 6020 conflict create 100 delete 50 create 100 200 commit 100 200 commit 50 100 200 commit 100 200 commit 200

8. © 2014 Cisco - All Rights Reserved8 Synchronization between SDN controller and routers/switches enables data plane counters to be used in domain wide services Data Center 1 Data Center n DDoS Thresholding & Remediation Traffic Engineering Applications Segment Routing Service Chaining Similar dynamics with other SDN services See draft-voit-netmod-peer-mount-requirements

9. © 2014 Cisco - All Rights Reserved9 Data Center / Cloud DC2 DC2 DC1DC1 WAN WAN Traffic Spike VM Move P P P P P P Continuous rebalancing of policers Policer values modified across Domain Bandwidth threshold recognition DC DC Synchronized Counter Delivery (YANG) Out of Profile Traffic Policed Traffic P P Policer In Profile Traffic

10. © 2014 Cisco - All Rights Reserved10 Network PE3 56.0.0.0/8 = 2 MB/s PE1 PE2 Offered Downstream Traffic: 4 MB/s 56.0.0.0/8 = 1 MB/s Ingress interface stats Interface E0 56.0.0.0/8 = 1 MB/s Ingress interface stats Interface E0 Network Element Police 56.0.0.0/8 to 7 MB/s* Police 56.0.0.0/8 to 7 MB/s* Police 56.0.0.0/8 to 8 MB/s* Ingress interface stats Interface E0 DC2 DC2 DC1DC1 WAN WAN Global Rule: Police ∑ traffic to 10 MBs Subnet: 56.0.0.0/8 18 8 9 Domain Wide Calculation Policy continually updated Traffic Spike 4.4 0.6 5.0 VM Move 0.6 4.7 8.5 1 10MB/s Max Cloud Usage Statistics from the PE Minimal config