[L2sm] Next steps with draft-ietf-l2sm-l2vpn-service-model

"Adrian Farrel" <adrian@olddog.co.uk> Wed, 17 January 2018 09:02 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: l2sm@ietfa.amsl.com
Delivered-To: l2sm@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id CA55C12FA93; Wed, 17 Jan 2018 01:02:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id id0k249QDKQ9; Wed, 17 Jan 2018 01:02:14 -0800 (PST)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4673212FAB6; Wed, 17 Jan 2018 01:02:07 -0800 (PST)
Received: from asmtp5.iomartmail.com (localhost.localdomain []) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id w0H92273007146; Wed, 17 Jan 2018 09:02:02 GMT
Received: from 950129200 ([]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id w0H920Ua007140 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Jan 2018 09:02:01 GMT
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: l2sm@ietf.org
Cc: draft-ietf-l2sm-l2vpn-service-model@ietf.org, l2sm-chairs@ietf.org, bclaise@cisco.com
Date: Wed, 17 Jan 2018 09:01:57 -0000
Message-ID: <058701d38f71$d52d2b60$7f878220$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdOPcdHzLYFpStp2Tc6QYweOw1cpSQ==
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-
X-TM-AS-Result: No--33.408-10.0-31-10
X-imss-scan-details: No--33.408-10.0-31-10
X-TMASE-MatchedRID: rPZRCuzwEyz7PYirXBVD5M98NT1MWuHvQPCWRE0Lo8K67Q3uPo9KI+H7 ZfhCofggcK5QyD9bSliKafM1hOxh+YjQo/Iw2s1SgOqr/r0d+CyLH4rzyQtUPY5t/XRqktxJwua niM9QXy013oPvTQ6OMo913mjfQ3KIHodpx3o6Gru4jAucHcCqneiY+s2L3xQEhn2bbI5joUWkDb FjTQ0CSi2Cn8nZ5xCf5g00vvdy6HqY+dHsEP/MFWMGiV639iF0Yu7s3QSSN+SQ2TbICkFOdmqMd wbSsCOujPVpVub5F3FmVMg6wIiaxg9FV6kNYiPHhCecAVGCOf0C5AMlEyiBEigMxnfFXjiIEmiH uEfayulqI3Rvf0ZV0LRzzYR4U4nd64YUNtZYBWEYBkxPlIuYCZqCl1R34jDPbcPp/oilsshxkDa YjAh4s8vnSCXBRWs5pp57/9F4tS94Bq+n7hYcraVzYsvffdUx5T1HpvyeXOQF9YmkHybWAHGtwv y18aR/EBDoMW2sVrCe8jJanTz+4rcH4/RZ7lQnCLNfGU4dffgZKp0SZ4P+dbNcuCb8CAxu0ISbJ BSoCMNhJ5Zyqn1oSzXysAHc5MpBs+KpsQUlyYXG693ff8j9ZJZ6zKu0q4rtfUOf4Mp5xtYu6lmG akqVh5j8YEB3JMRbGhSpfcKQYBSqYtZoSKdB4QtigoE0Deb+J/dPdoLAWDmh89mqiZyndkr24C3 H1DCPa2r3qllpBgBPgpGv/Pbptxcy5bypFl2Lqbg9uWhLYLf76a7w2Q6CXif663Ll9ACjayz+lI iY36jgFNHYA/U/9YNgn0LpDR/v+RahkyeUE56eAiCmPx4NwGNn8XPiALIb+gD2vYtOFhgqtq5d3 cxkNQwWxr7XDKH8lExlQIQeRG0=
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2sm/x-yM9VXTbd0BLRR3sp0g4Mkgct4>
Subject: [L2sm] Next steps with draft-ietf-l2sm-l2vpn-service-model
X-BeenThere: l2sm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "The Layer Two Virtual Private Network Service Model \(L2SM\)" <l2sm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2sm>, <mailto:l2sm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/l2sm/>
List-Post: <mailto:l2sm@ietf.org>
List-Help: <mailto:l2sm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2sm>, <mailto:l2sm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jan 2018 09:02:22 -0000


We're approaching Working Groups last call on our draft.

- I have requested a YANG Doctor review of the current revision
- I plan to do an English language review at the same time (unless
   someone else want to volunteer)
- NOW is the time for you to do your technical review. Don't leave
   is until WG last call!
- All things being equal, we will have WG last call in early February



> -----Original Message-----
> From: L2sm [mailto:l2sm-bounces@ietf.org] On Behalf Of Fioccola Giuseppe
> Sent: 16 January 2018 10:05
> To: l2sm@ietf.org
> Cc: draft-ietf-l2sm-l2vpn-service-model@ietf.org; l2sm-chairs@ietf.org
> Subject: [L2sm] I: I-D Action: draft-ietf-l2sm-l2vpn-service-model-05.txt
> Hi All,
> This is the new version of the draft-ietf-l2sm-l2vpn-service-model.
> It addresses some comments from people that are trying to implement the draft
> and it includes also an update to the references in particular to RFC8199 and
> RFC8309.
> As usual, the fundamental changes are summarized in the Appendix A "Changes
> Log":
>    Changes in v-(05) include:
>    o  Change type from 16-bit integer to string for the leaf id under
>       "qos-classification-policy" container.
>    o  Stick to using ordered-by user and remove inefficiency to map
>       service model sequence number to device model sequence number.
>    o  Remove mandating the use of deviations and add "if-feature target-
>       sites" under the leaf-list target-sites in section 5.10.2.
>    o  RFC2119 language changes on operation of the management system in
>       Section 5.6,3rd paragraph and section 7.
>    o  Fix incomplete description statements.
>    o  Change the use of the absolute paths to the use of relative paths
>       in the "must" statement or "path" statement for vpn-policy-id leaf
>       node, management container, location leaf node, devices container,
>       location case, location-reference leaf, device case, device-
>       reference leaf to make configuration is only applicable to the
>       current sites.
>    o  Change "must" statement to "when" statement for management
>       container device container.
>    o  Define new grouping vpn-profile-cfg for all the identifiers
>       provided by SP to the customer.  The identifiers include cloud-
>       identifier, std-qos-profile.
>    o  Add in the XPATH string representation and remove unqualified
>       name.
>    o  Remove redundant parameters in the cloud access.
>    o  Add a few text to clarify what the site is in section 6.3.
>    o  Add multi-filter and multi-VPN per entry support for VPN policy.
>    o  Modify description for svc-bandwidth leaf to make it consistent
>       with the text in section 5.10.1.
>    o  Add text to clarify the way to achieve Per-VPN QoS policy.
>    o  Change guaranteed-bw-percent data type from uint8 to decimal64.
> Reviews and Comments are always welcome.
> Best Regards,
> Giuseppe
> -----Messaggio originale-----
> Da: L2sm [mailto:l2sm-bounces@ietf.org] Per conto di internet-drafts@ietf.org
> Inviato: martedì 16 gennaio 2018 10:46
> A: i-d-announce@ietf.org
> Cc: l2sm@ietf.org
> Oggetto: [L2sm] I-D Action: draft-ietf-l2sm-l2vpn-service-model-05.txt
> A New Internet-Draft is available from the on-line Internet-Drafts
> 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-05.txt
> 	Pages           : 149
> 	Date            : 2018-01-16
> 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 data 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 IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-l2sm-l2vpn-service-model/
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-l2sm-l2vpn-service-model-05
> https://datatracker.ietf.org/doc/html/draft-ietf-l2sm-l2vpn-service-model-05
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-l2sm-l2vpn-service-model-05
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> _______________________________________________
> L2sm mailing list
> L2sm@ietf.org
> https://www.ietf.org/mailman/listinfo/l2sm
> Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle
> 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,
> 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.
> _______________________________________________
> L2sm mailing list
> L2sm@ietf.org
> https://www.ietf.org/mailman/listinfo/l2sm