Re: [L2sm] I: I-D Action: draft-ietf-l2sm-l2vpn-service-model-09.txt

"Joel M. Halpern" <> Tue, 03 April 2018 16:37 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 406D9129C53; Tue, 3 Apr 2018 09:37:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id H-09LEjyGo6t; Tue, 3 Apr 2018 09:37:08 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E2C51126BFD; Tue, 3 Apr 2018 09:37:08 -0700 (PDT)
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8C3C32402C4; Tue, 3 Apr 2018 09:37:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=2.tigertech; t=1522773428; bh=pivTALvz9toBpQyDOliHOw8o4mMhQXvQM7s4sRF3nN4=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=IDrxGCETd3mafjyFqAP/QUvvzXoxQ3Z02nIjxV2mDr/07tAuqYIUb2vZuFoja5l1Q b1qXmGH/SQ3zELUnM2SCEAykOFkbVGmfVV01Gvg6nRHw0B5x0lWR3hSKgzpwZ7yjzg ZbqyNd5a5OkoMvcyaY7ObSdZOcSIIIVnuRpeZQ5U=
X-Virus-Scanned: Debian amavisd-new at
Received: from Joels-MacBook-Pro.local (unknown []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id A5B8C24013B; Tue, 3 Apr 2018 09:37:06 -0700 (PDT)
To: Fioccola Giuseppe <>, "" <>, "" <>
Cc: Ladislav Lhotka <>, "" <>
References: <> <50220800e12244bb938bb1d0db4ccf8b@TELMBXB02RM001.telecomitalia.local>
From: "Joel M. Halpern" <>
Message-ID: <>
Date: Tue, 3 Apr 2018 12:37:05 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <50220800e12244bb938bb1d0db4ccf8b@TELMBXB02RM001.telecomitalia.local>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <>
Subject: Re: [L2sm] I: I-D Action: draft-ietf-l2sm-l2vpn-service-model-09.txt
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "The Layer Two Virtual Private Network Service Model \(L2SM\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 03 Apr 2018 16:37:11 -0000

The following minor items from my review do not seem to have been dealt 
with.  They are rephrased ehre for clarity:

     Section 5.2 still says in the definition of Cloud Access that 
"[a]ll sites in the L2VPN MUST be authorized ..." while section 5.3.2 
says SHOULD, with clear instructions for how to handle exceptions.  I 
presume 5.2 should say SHOULD?

     Section 5.3 still talks about a site having multiple locations 
without any specific requirement that there be internal connectivity 
among those locations.  I understand that the model does not represent 
that connectivity.  But it seems pretty clear that things will break if 
that connectivity is not present.

      Section on connecting to multiple VPNs still talks about 
prefixes.  This is, as far as I know, an L2VPN service.  And L2VPNs work 
in MAC addresses, which do not use prefix based routing.  I think the 
solution is to replace "destination-based routing" with "MAC destination 
based forwarding", and to replace "mapping of its prefixes" with 
"mapping of its MAC addresses".
      Given that this is MAC address based forwarding, I think there 
also needs to be some text about what happens with BUM packets?

     In section it is still unclear what it means to name LANs 
in a site.

     IN section 5.6, the text says that although constraints must be 
met, some specific constraints are just hints.  I would have thought 
those would be something other than constraints, but okay.  However, the 
wording is "Parameters such as ... as special constraints are just 
hints"  given the use of "such as", this implies that maybe some other 
constraints are special and just hints.  But the reader has no idea 
whether there are other hints.


On 4/3/18 5:45 AM, Fioccola Giuseppe wrote:
> Hi All,
> This new revision of draft-ietf-l2sm-l2vpn-service-model addresses Lada's and Joel's comments.
> Thanks,
> Giuseppe
> -----Messaggio originale-----
> Da: L2sm [] Per conto di
> Inviato: martedì 3 aprile 2018 11:39
> A:
> Cc:
> Oggetto: [L2sm] I-D Action: draft-ietf-l2sm-l2vpn-service-model-09.txt
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the L2VPN Service Model WG of the IETF.
>          Title           : A YANG Data Model for L2VPN Service Delivery
>          Authors         : Bin Wen
>                            Giuseppe Fioccola
>                            Chongfeng Xie
>                            Luay Jalil
> 	Filename        : draft-ietf-l2sm-l2vpn-service-model-09.txt
> 	Pages           : 156
> 	Date            : 2018-04-03
> Abstract:
>     This document defines a YANG data model that can be used to configure
>     a Layer 2 Provider Provisioned VPN service.
>     This model is intended to be instantiated at management system to
>     deliver the overall service.  This model is not a configuration model
>     to be used directly on network elements, but provides an abstracted
>     view of the Layer 2 VPN service configuration components.  It is up
>     to a management system to take this as an input and generate specific
>     configurations models to configure the different network elements to
>     deliver the service.  How configuration of network elements is done
>     is out of scope of the document.
>     The YANG model in this document includes support for point-to-point
>     Virtual Private Wire Services (VPWS) and multipoint Virtual Private
>     LAN services (VPLS) that use Pseudowires signaled using the Label
>     Distribution Protocol (LDP) and the Border Gateway Protocol (BGP) as
>     described in RFC4761 and RFC6624.
>     The YANG model in this document conforms to the Network Management
>     Datastore Architecture defined in I-D.ietf-netmod-revised-datastores.
> The IETF datatracker status page for this draft is:
> There are also htmlized versions available at:
> A diff from the previous version is available at:
> Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at
> Internet-Drafts are also available by anonymous FTP at:
> _______________________________________________
> L2sm mailing list
> Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.
> This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.
> Rispetta l'ambiente. Non stampare questa mail se non è necessario.