Minutes interim-2017-l2sm-02: Wed 14:00
minutes-interim-2017-l2sm-02-201709271400-00

L2SM Virtual interim - Minutes

27th September 2017, 2pm (London)

Duration 90 minutes

Webex:
  Meeting number; 646 686 906
  Meeting password: m92q3CcT
  Link for meeting connection
    https://ietf.webex.com/ietf/j.php?MTID=m269230aaa9b65847700af143006c1a55
  Telephone connection:
    1-877-668-4493 Call-in toll free number (US/Canada)
    1-650-479-3208 Call-in toll number (US/Canada)
    https://www.webex.com/pdf/tollfree_restrictions.pdf

WG:
  https://datatracker.ietf.org/wg/l2sm/documents/

Chairs:
  Qin Wu <bill.wu@huawei.com>
  Adrian Farrel <adrian@olddog.co.uk>

AD:
  Benoit Claise <bclaise@cisco.com>

Document:
  https://datatracker.ietf.org/doc/draft-ietf-l2sm-l2vpn-service-model/

===========
Attendees

Name                      | Affiliation
--------------------------+------------------------------
Adrian Farrel             | Juniper Networks
Qin Wu                    | Huawei
Michael Scharf            | Nokia
Giuseppe Fioccola         | TI

Agenda / Minutes
================

> Introduction
>  Administrivia and Agenda Bash (Chairs, 2 mins)
>  WG Status (Chairs, 3 mins)
> Document Status (Giuseppe, 15 mins)
>  High-level overview of model

In the absence of a large attendance we jumped straight here in the agenda

>  Changes since last revision

Giuseppe ran through the "Document Status" slide

>  Work on Open Issues (Giuseppe / everyone, 45 mins)
>
>  1. Support for EVC

Giuseppe: Consider EVC but without detail

Adrian: How?

Giuseppe: Need a new service type. Most of the service can be mapped from
existing module.
   But would require a detailed understanding of all EVC services

Qin: Mixed up EVPN with EVC? We EVPN to realise EVC service. Currently we don't
have a service type for EVC.

Qin: We have EVC optional attributes

Qin: Would we also get rid of OVC attributes.

Adrian:

   Suggested resolution:
    - Limit this module to describing IETF L2VPN services
    - Suggest that mapping to the MEF's EVC service attributes may be possible
    but is out of scope for this document

   Does anyone on the call object to removing the evc and ovc subtrees?
    - silence

ACTION: Adrian to send mail to list to propose removing evc and ovc subtrees

Adrian: Retain metro-networks as useful for multi-domain (but drop ovc-id)

>  2. LAG Loop Avoidance

Qin: Member link doesn't provide site redundancy support.

ACTION: Adrian to explain to mailing list that no change was made. We think
everything is covered.

>  3. L2VPN Interworking Support

Qin: We don't currently have text to cover interworking support. Not sure
anyone is interested in legacy.

ACTION: Adrian to propose to list that we declare support of legacy services
(ATMoMPLS, PPPoMPLS, FRoMPLS) as out of scope.
        Therefore, we suggest that interworking with ATM PVC is also out of
        scope.

>  4. Signaling Option Parameters

Adrian: This ties in with a complaint receieved off-list that this module
describes technologies operating within the provider network.
        We should be very careful to limit ourselves to only describe
        technology outside the operator's network. A lot of the issues seem to
        be driven by how you connect the service at an AS boundary between
        operators.

ACTIONs:
    - Limit ourselves to CE-PE signaling
    - Remove/clean-up all parameters for the PE-to-EdgeGateway signaling

ISSUE:
    - In EVPN CE can have an IP address. How does CE and PE talk? Do we need to
    configure a routing protocol for this?

>  5. Applicability to Inter-Provider and Inter-Domain Case

A service orchestrator may need to perform coordination between different
networks (domains or providers), but this is hidden from the customer.

The customer just sees the end sites, the inter-domain stitching point are
determined by the service orchestrator.

ACTION: Adrian to write-up the "agreement" to check we agree

>  6. Get text to describe all multi-homing options

Just check the document covers all cases

>  7. Trivial pyang error & warning from IETF tools

The error is in an included module, so out of our control
Check before posting next revision

> Lessons from L3SM revision (Qin, 10 mins)

Big lesson is to get YANG Doctor review!

    Jan from tail-f has put himself in the frame to do this.

Should attempt some housekeeping on the draft *before* sending it for review

ACTIONs:
    - Qin to scan this draft to see if he can mop up any issues now
    - Adrian to ask for MIB Dr review when next vesion is posted

> Raise new issues (All, 10 mins)

No new issues raised.

> Next steps and wrap-up (Chairs, 5 mins)

For actions see minutes