L2SM Working Group IETF 100, Singapore Thursday November 16, 2017 18:10 - 19:10 Canning Room AD Benoit Claise (bclaise@cisco.com) Chairs Qin Wu (bill.wu@huawei.com) Adrian Farrel (afarrel@juniper.net) Charter https://datatracker.ietf.org/wg/l2sm/about/ Jabber xmpp:l2sm@jabber.ietf.org Mailing list https://www.ietf.org/mailman/listinfo/l2sm Minutes https://etherpad.tools.ietf.org/p/notes-ietf-100-l2sm Document https://datatracker.ietf.org/doc/draft-ietf-l2sm-l2vpn-service-model/ ===== 1. Administrivia and Agenda Bash (chairs, 5 mins) See slides 2. WG status and plans (chairs, 5 mins) See slides Jeff Tantsura: Are you aligned with LNE? Giuseppe: Yes, already done. 3. YANG Data Model for L2VPN Service Delivery (Authors, 45 mins) draft-ietf-l2sm-l2vpn-service-model - Overview refresher - Recent changes - Open issues - Open discussion Giuseppe presents Himanshu Shah: Have you considered multi-PE connectivity Giuseppe: Yes, it is supported, just not shown on this slide. Himanshu: (on signaling options) The operators probably know what they are talking about. Himanshu: Consider a 500G PW. What about OAM, and protection? Giuseppe: Yes we have Y.1731 etc. (just not on this slide). Limit to CE-PE for specifics. Himanshu: How about adding calendaring? Adrian: Is that a lifecycle issue? Himanshu: Yes. Giuseppe: Not in this document, but we can ask the list. Michael Scharf: Calendaring is somehow orthogonal and generic. It would similarly apply to L3SM. It could be an independent module. Adrian: Does Benoit know of anything in the YANG catalog? Benoit Claise: There is some stuff, but might not be relevant. But am worried about getting in to lifecycle management, so this could be a stretch. This is typically what MEF would be working on and we are pretty sure they Michael: In agreement (including that other standards bodies are working on this) Himanshu: Scheduling may have implications for the operator for booking the network resources. Reza Rokui: Fundamental question from customer perspective: do I care if the VPN is achieved using PW or EVPN, etc.? Doesn't this break the concept of abstraction? Giuseppe: Yes, the customer is interested in some cases. Reza: What is the percentage that is interested? Giuseppe: It depends by the customer. Reza: How does this work if the customer doesn't care? Giuseppe: Should be "optional" parameters ACTION authors: check that all such "network internals" are optional (with defaults where appropriate) Himanshu: Please ping the BESS list ACTION chairs: - mention in BESS meeting - send mail to BESS and PALS Himanshu: Look at this from an automation perspective (wrt optional parms, above) Benoit: Is this plan achievable? Giuseppe: It could be. Benoit: How might we get more review and feedback? Giuseppe: I will get my operational department to review. I believe there is a need for this work. Adrian: We have been struggling to find operators to provide review, can Benoit help? Adrian: Risks to plan 1. Giuseppe becomes unavailable. 2. Detailed reviews cause work - would be a good result even if it wrecks the plan. 3. Silence during review. Benoit: Agree on 2 that it would be a delay, but also a good thing. 3 is OK so long as the author-operators are supportive. 4. Any other business (5 mins) Giuseppe presents on relationship to L1 work in CCAMP