What: OpsAWG / OpsArea 107 Virtual Interim When: 11:00 - 13:30 UTC Tuesday, April 7, 2020 Where: Webex Available During Session: Jabber: xmpp:opsawg@jabber.ietf.org?join Etherpad: https://etherpad.ietf.org/p/notes-ietf-107-opsawg ICal: https://datatracker.ietf.org/meeting/interim-2020-opsawg-01/sessions/opsawg.ics Slides: https://datatracker.ietf.org/meeting/interim-2020-opsawg-01/session/opsawg BLUESHEETS: if you haven't already, please sign the Bluesheet located at the bottom on the Etherpad page here: https://etherpad.ietf.org/p/notes-ietf-107-opsawg WebEx Chat: For virtual queue control (type "+q" and "-q" to enter/leave) WebEx A/V: For session (see below for info) JOIN BY WEBEX: URL: https://ietf.webex.com/ietf/j.php?MTID=m181b4bb69ed226d7e809ba2f15382ee1 Meeting number (access code): 617 456 544 Meeting password: F7pFAv3gM5f Available Post Session: Recording: WebEx recording be made available after the meeting. Jabber Logs: https://www.ietf.org/jabber/logs/opsawg Etherpad: https://etherpad.ietf.org/p/notes-ietf-107-opsawg Slides: https://datatracker.ietf.org/meeting/interim-2020-opsawg-01/session/opsawg OpsAWG Section ============== Administrivia - scribes, minutes, rules, introduction of our new AD, etc. Tianran / Joe 15 minutes (reordered due to mic issues for Qin) A Layer 3 VPN Network YANG Model Oscar González de Dios Draft: https://datatracker.ietf.org/doc/draft-ietf-opsawg-l3sm-l3nm/ 10 minutes Joe: Please take issues from GitHub to the mailing list to get full WG visibility Oscar: Will do after the meeting TODO: YANG doctor review A Framework for Automating Service and Network Management with YANG Qin Wu Draft: https://datatracker.ietf.org/doc/draft-ietf-opsawg-model-automation-framework 10 minutes Joe: suggest to bring up new example to the list if there is. A Layer 2 VPN Network Yang Model Oscar González de Dios Draft: https://datatracker.ietf.org/doc/draft-barguil-opsawg-l2sm-l2nm 5 minutes Q1: open issues for eVPN support. Is eVPN not supported? Or just some cases? A: started to add eVPN support. Now supported. Zhenbin Li: Is EVPN supported in this draft at all or just some cases? Oscar: Support has been added in the last version; work required to see about additional properties for EVPN Zhenbin Li: L2VPN is complex; can hierarchical VPN be supported in this SM? Oscar: Yes, but more review is needed to see if it is fully supportable Zhenbin Li: Inter-AS scenario? Oscar: Perhaps Samir Barguil: Inter-AS is a use case to support; still enhancing the set of network parameters Italo: CCAMP working group has some overlapping work; client signal model (https://tools.ietf.org/html/draft-ietf-ccamp-client-signal-yang) Oscar: This model is pure transport; more research to be done Rob Wilton: How much work is in the general area for network models Oscar: We feel the scope is well-defined now Joe: This may change in the future if there is a proliferation of services 07:49 A YANG Model for User-Network Interface (UNI) Topologies Med Boucadair Draft: https://datatracker.ietf.org/doc/draft-ogondio-opsawg-uni-topology 5 minutes Italo Busi: CCAMP has a similar draft; need to know the UNIs; need to know the capabilities of the UNIs; UNI discovery is generic, but capabilities are specific Med: Let's work together. Tianran: What is the type of this model? Med: Topology model; augments network model Tianran: Who will consume this model Med: L3SM, L3NM can consume this model; this is a network controller model Oscar Gonzalez de Dios: This is a topology view that is exposed from the network controller layer Tianran: Is this is a new type of service abstraction to be described by Qin's document Qin Wu: UNI topology model is a network model; we can reflect this in the network automation framework draft Rob Wilton: Compliments the L2NM and L3NM; does this augment both or does there need to be a generic underlying model Med:This is described in the draft already Rob: Need to study this more to see how everything fits together MUD (D)TLS profiles for IoT Devices Tirumal Reddy Draft: https://datatracker.ietf.org/doc/draft-reddy-opsawg-mud-tls 5 minutes Tianran: Are the 8520 security considerations enough? Tiru: We are simply extending on that model Tianran: Does MUD provide any security mechanisms itself Tiru: Eliot Lear: Are the security considerations of 8520 are sufficient for this draft? Tianran: In MUD there are already security considerations; does it already provide a security mechanism or just the requirements? Eliot: Tiru's draft relies on the underlying MUD mechanisms but does not introduce new security mechanisms for discovering the URL TODO: Raise a WG list question on what to do with collective MUD work MUD and SUIT, Operational considerations for MUD, MUD and quarantined access to firmware Michael Richardson Drafts: https://datatracker.ietf.org/doc/draft-richardson-opsawg-mud-acceptable-urls https://datatracker.ietf.org/doc/draft-richardson-opsawg-mud-iot-dns-considerations Eliot: Working occuring at ICANN (CIRA), DNS for IoT. Policy enforcement point is not well bound to the name->IP mapping. Mentions that DHCP options can been parameterized in YANG. Tiru: we have been using domain names to do fingerprinting of devices. IoT need to move to using DoT and DoH for privacy reasons. How to discover the network provided DoT/DoH servers. https://datatracker.ietf.org/doc/draft-richardson-shg-mud-quarantined-access 15 minutes Tiru: seems obvious and the right thing to do? ended at: 8:32 Sampled Traffic Streaming Andrew Gray Draft: https://datatracker.ietf.org/doc/draft-gray-sampled-streaming 10 minutes All the way down to changes since -02. MCR: suggests that there are synergies with pcap-ng, to either encapsulate these formats to disk, or to use pcap-ng as the on-the-wire format. A request was made to have an IPFIX example. A question about YANG doctor review, or looking for YANG-fu co-author? Author wants to do -04 first. In-situ Flow Information Telemetry Framework Haoyu Song Draft: https://datatracker.ietf.org/doc/draft-song-opsawg-ifit-framework/ 10 minutes Discussion between Frank Brockners and Haoyu and Zhenbin Li on terminology. While the word IFIT has been removed, the underlying idea about specialized components (head node, end node, etc.) remain Why do we need a new name? Haoyu and Zhenbin comment that this is a new framework and thus needs a new name Frank comments that this uses existing components already defined in other areas (e.g., IOAM) Tianran: It's not just classificaiton of existing data plane technologies. It's more about the higher level framework on orchistration. Ultimately, the authors asked for pointed comments as to their modifications. This needs to be sorted out on the WG mailing list as we cannot solve this on the call. Service Assurance for Intent-based Networking Architecture and YANG modules Benoit Claise Drafts: https://datatracker.ietf.org/doc/draft-claise-opsawg-service-assurance-architecture https://datatracker.ietf.org/doc/draft-claise-opsawg-service-assurance-yang 15 minutes Sue Hares asked if the IS-IS depicted in the slides is a formal part of the document Joe: No, this is an example of an underlying subservice in this service instance. Other services may use a different routing protocol Joe: The spec is flexible to allow for different types of subservices YANG Data Models for the IP Flow Information Export (IPFIX) Protocol, Packet Sampling (PSAMP) Protocol, and Bulk Data Export Joey Boyd Draft: https://datatracker.ietf.org/doc/draft-boydseda-ipfix-psamp-bulk-data-yang-model/ 20 minutes This is currently an AD-sponsored document (Ignas had it, now it will pass from Warren to Rob) Rob: We should see if opsawg wants to pick up this work (adopt it) and if so, hopefully it can progress quickly Rob: If the WG doesn't want it, then it will remain AD-sponsored Rob: Because of the obsolescence issue, it would be best if the WG taks it TODO: Call for adoption === We ran out of time for these extra presentations. They can have first crack at a non-WG slot for IETF 108. Active-Scanning profiles for IoT devices Jie Yang Draft: https://datatracker.ietf.org/doc/draft-yang-opsawg-iot-devices-active-scanning/ 5 minutes Export of MPLS-SR Label Type Information in IPFIX Thomas Graf Draft: https://datatracker.ietf.org/doc/draft-tgraf-ipfix-mpls-sr-label 5 minutes OpsArea Section =============== Administrivia and Introduction Warren / Rob Warren introduced Rob Wilton as the new Ops and Mgmt Area Director Rob has spent over 20 years for Cisco as a software engineer in the SP business unit Background in SP OS focusing on L2 tech like VLANs Recently focused on manageability issues and YANG Contributes at the IETF on YANG including NMDA and YANG versioning Vision: see IETF finish device-level YANG modules; interest in service and network YANG models and how they map to the devices; interest in service-level models in other SDOs and how they map to device and network models; interesting in lifecycle monitoring Open Mic No questions for open mic -------------------------------------------------------------------------- Blue Sheet webex has 34 participants jabber has 8 participants Name Affiliation Tianran Zhou Huawei Warren Kumari Google Mohamed Boucadair Orange Qin Wu Huawei Michael Richardson, Sandelman Software Works Bo Wu Huawei William Lupton Broadband Forum Thomas Graf Swisscom Matthias Arnold Swisscom Erez Segev ECI Telecom Simon Leinen SWITCH Cathy Aronson, ARIN Andrew Gray Charter Communications Yuichi Takita SECOM Dhruv Dhody Huawei-India Joey Boyd ADTRAN Oscar Gonzalez de Dios Telefonica Éric Vyncke Cisco Laurent Ciavaglia Nokia (as Network Management Research Group) Joseph Clarke Cisco Frank Brockners Haoyu Song Italo Busi, Huawei Juergen Schoenwalder Lucia Olivia, Telefonica Med Mudumbai Ranganathan Samier Barguil Telefonica Paolo Lucente Philip Eardley Robert Wilton, Cisco Tiru Reddy Konda y00468095 (Yangjie?) Yali Wang， Huawei Zhenbin Li Kyle Rose Miao Fuyou Yoshifumi Atarashi Susan Hares Carsten Bormann, TZI Guangying zheng Benoit Claise, Cisco Eliot Lear, Cisco Frank Brockners, Cisco Miao Fuyou, Huawei Luis M. Contreras, Telefonica Wei Pan, Huawei Yunan, Huawei Sergio Belotti Nokia