From nobody Wed Feb 8 04:27:04 2017 Return-Path: X-Original-To: l2sm@ietfa.amsl.com Delivered-To: l2sm@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81F721293D6 for ; Wed, 8 Feb 2017 04:27:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.62 X-Spam-Level: X-Spam-Status: No, score=-2.62 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] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jO086mspWqmQ for ; Wed, 8 Feb 2017 04:27:01 -0800 (PST) Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C06231299FC for ; Wed, 8 Feb 2017 04:27:00 -0800 (PST) Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id v18CQuwC023782; Wed, 8 Feb 2017 12:26:56 GMT Received: from 950129200 ([176.241.251.3]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id v18CQprN023763 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Feb 2017 12:26:55 GMT From: "Adrian Farrel" To: Date: Wed, 8 Feb 2017 12:26:47 -0000 Message-ID: <068e01d28206$a2b4fab0$e81ef010$@olddog.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AdKCBpiJIug9PUVsRWy08N15q+zMLg== Content-Language: en-gb X-TM-AS-MML: disable X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.1.0.1062-22872.006 X-TM-AS-Result: No--8.915-10.0-31-10 X-imss-scan-details: No--8.915-10.0-31-10 X-TMASE-MatchedRID: r95+d//5g9eR8u6DOJbzpziPEKUh+xB+q8zyGnyMiHTnt4o2/Vm8Behu cPsHg+lU4gjwtqdxrGS2ApteWXXPToMB3UO03Wrtr51gSC67hpVt3qsaFY4DBO/FI0vC1VAHHSG EZ3gt1f6tfVFB3sECOW793anBBL+URrYNcarBmZ+4jAucHcCqnS3S35ohUu37TuOOxH2rT/ERZc CYVXElTiEn+59qml4SkZOl7WKIImq0P2qkGU0XypaWKijZlsbB2bNx1HEv7HAqtq5d3cxkNSAqw XSxSoYzHcwxoDHBQo/kJXWEjMMNnAjp3WgmyVwgoLKX6ZUUeAg= Archived-At: Cc: bclaise@cisco.com Subject: [L2sm] L2SM not meeting in Chicago X-BeenThere: l2sm@ietf.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: adrian@olddog.co.uk 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: Wed, 08 Feb 2017 12:27:03 -0000 Hi working group, The chairs believe that there is currently nothing to be gained from an L2SM WG meeting in Chicago. Rest assured that the draft authors are working on the document in the background. Tasks have included: - Checking the "technology-specific" parameters to ensure that they are applicable to the CE-PE access links and not to how the VPN is implemented by the provider. - Looking at "cloud services" - Adding examples - Cross-checking how to reference relevant MEF work There is a plan to get a new revision posted "soon". In the meantime: - You are all very welcome continued discussion on the list - Please speak up if you have a topic you want to address in a face-to-face meeting Thanks, Adrian and Qin From nobody Wed Feb 8 04:30:46 2017 Return-Path: X-Original-To: l2sm@ietf.org Delivered-To: l2sm@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B8C91294FA; Wed, 8 Feb 2017 04:30:45 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "\"IETF Meeting Session Request Tool\"" To: X-Test-IDTracker: no X-IETF-IDTracker: 6.42.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <148655704515.3884.6117573184831093905.idtracker@ietfa.amsl.com> Date: Wed, 08 Feb 2017 04:30:45 -0800 Archived-At: Cc: bclaise@cisco.com, l2sm-chairs@ietf.org, afarrel@juniper.net, l2sm@ietf.org Subject: [L2sm] l2sm - Not having a session at IETF 98 X-BeenThere: l2sm@ietf.org X-Mailman-Version: 2.1.17 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: Wed, 08 Feb 2017 12:30:45 -0000 Adrian Farrel, a chair of the l2sm working group, indicated that the l2sm working group does not plan to hold a session at IETF 98. This message was generated and sent by the IETF Meeting Session Request Tool. From nobody Wed Feb 8 09:11:48 2017 Return-Path: X-Original-To: l2sm@ietfa.amsl.com Delivered-To: l2sm@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D22A129485 for ; Wed, 8 Feb 2017 09:11:46 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KBUWDJwvnosX for ; Wed, 8 Feb 2017 09:11:45 -0800 (PST) Received: from mail-lf0-x22e.google.com (mail-lf0-x22e.google.com [IPv6:2a00:1450:4010:c07::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C0EAA12943B for ; Wed, 8 Feb 2017 09:11:44 -0800 (PST) Received: by mail-lf0-x22e.google.com with SMTP id v186so85944400lfa.1 for ; Wed, 08 Feb 2017 09:11:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=RZ9q0kP3d2q3R+R6XHUVG6VQWqwHmZyYLIJNNJnimoo=; b=DuTABbyWsU3Ekvv28kC1c55vlOgiGmA3eQ0LuTSR8X9X2Ob/dlneh1WQfwe4T8QjV/ HE0NErGG1MS8tRfoB79krENoMMNH/+r2o4YnGWAvARNJ6JnFZDYOJAYstvgjqsHTSDHH lcZLuL56y7wA/H3APEEmOf7G7xmx4Qn5mxMJTcULdsFI8+lKhTapJReZyTI3GQmmNmul n++sWYGlk1tLCqnEs6LaOBAAR/yBEViWmIP4kf6dsLc56C2HCeARqjr7P+CnYQjmjAlQ hlw+RO1oTimQiiTqJusqD4JvlzaUf/tG0b5SVplktjwtNYv9Bn9ra8e0is0UrQMUZ9+4 OPfA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=RZ9q0kP3d2q3R+R6XHUVG6VQWqwHmZyYLIJNNJnimoo=; b=rLZOK1AbsXev45zhStDEeLx/NIy0oYcjn27E1SJyAOUMSe5acaLFjh+EqcoFSxnmkl nF+TaII0290CX+lgl2UuaDk9wUl/Yli6JCdGUt13CI7Sksw1uCQ9/ru/Sxe7CBQdn6gK 2M/IdRDhca2TiwwgX4x7htOa5OHVUri63GT3zBobjleDXKg5KEYc4HvPGcgBa1VjxMrn K+Hs2tcSD0s5xLac2LpFMstLGk8OM4etD9Qk3I/xqM059DLTH1d0PqjjLKr+iTFotmV0 5xIscKbawqnfesrnBpHFCC/cizjgdcY3jtxK+y9Joy91/oD0d7afhM+KsmuSR1FvnoNI fC0w== X-Gm-Message-State: AIkVDXKz56SAUxG0JnJbOfUNhb/FcKhU7YEPv7l9cXh8ICpWJliAIN6rEv3fl+QMxaDQxzrb8lGdaz4Ss0n8aw== X-Received: by 10.25.40.4 with SMTP id o4mr8209228lfo.1.1486573902988; Wed, 08 Feb 2017 09:11:42 -0800 (PST) MIME-Version: 1.0 Received: by 10.25.21.203 with HTTP; Wed, 8 Feb 2017 09:11:42 -0800 (PST) In-Reply-To: <068e01d28206$a2b4fab0$e81ef010$@olddog.co.uk> References: <068e01d28206$a2b4fab0$e81ef010$@olddog.co.uk> From: John Strassner Date: Wed, 8 Feb 2017 09:11:42 -0800 Message-ID: To: Adrian Farrel Content-Type: multipart/alternative; boundary=001a11410e586b8e2d054807f5e6 Archived-At: Cc: Benoit Claise , l2sm@ietf.org Subject: Re: [L2sm] L2SM not meeting in Chicago X-BeenThere: l2sm@ietf.org X-Mailman-Version: 2.1.17 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: Wed, 08 Feb 2017 17:11:46 -0000 --001a11410e586b8e2d054807f5e6 Content-Type: text/plain; charset=UTF-8 Hi all, I am happy to provide advice on the relevant MEF work. Other sources are Scott Mansfield and David Ball. Best way to get a hold of me is strazpdj@gmail.com, or by offering coffee and/or scotch. :-) regards, John On Wed, Feb 8, 2017 at 4:26 AM, Adrian Farrel wrote: > Hi working group, > > The chairs believe that there is currently nothing to be gained from an > L2SM WG > meeting in Chicago. > > Rest assured that the draft authors are working on the document in the > background. Tasks have included: > > - Checking the "technology-specific" parameters to ensure that they are > applicable to the CE-PE access links and not to how the VPN is > implemented > by the provider. > > - Looking at "cloud services" > > - Adding examples > > - Cross-checking how to reference relevant MEF work > > There is a plan to get a new revision posted "soon". > > In the meantime: > - You are all very welcome continued discussion on the list > - Please speak up if you have a topic you want to address in a > face-to-face meeting > > Thanks, > Adrian and Qin > > _______________________________________________ > L2sm mailing list > L2sm@ietf.org > https://www.ietf.org/mailman/listinfo/l2sm > -- regards, John --001a11410e586b8e2d054807f5e6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi all,

I am happy to provid= e advice on the relevant MEF work. Other sources are Scott Mansfield and Da= vid Ball. Best way to get a hold of me is strazpdj@gmail.com, or by offering coffee and/or scotch. :-)
=

regards,
John

On Wed, Feb 8, 2017 at 4:26 AM, Adria= n Farrel <adrian@olddog.co.uk> wrote:
Hi working group,

The chairs believe that there is currently nothing to be gained from an L2S= M WG
meeting in Chicago.

Rest assured that the draft authors are working on the document in the
background. Tasks have included:

- Checking the "technology-specific" parameters to ensure that th= ey are
=C2=A0 =C2=A0applicable to the CE-PE access links and not to how the VPN is= implemented
=C2=A0 =C2=A0by the provider.

- Looking at "cloud services"

- Adding examples

- Cross-checking how to reference relevant MEF work

There is a plan to get a new revision posted "soon".

In the meantime:
- You are all very welcome continued discussion on the list
- Please speak up if you have a topic you want to address in a
=C2=A0 face-to-face meeting

Thanks,
Adrian and Qin

_______________________________________________
L2sm mailing list
L2sm@ietf.org
https://www.ietf.org/mailman/listinfo/l2sm



--
regards,
John
--001a11410e586b8e2d054807f5e6-- From nobody Wed Feb 15 09:53:46 2017 Return-Path: X-Original-To: l2sm@ietfa.amsl.com Delivered-To: l2sm@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF8A012955E for ; Wed, 15 Feb 2017 09:53:45 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8a1rMocjG9Zx for ; Wed, 15 Feb 2017 09:53:43 -0800 (PST) Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E6A4129B08 for ; Wed, 15 Feb 2017 09:53:42 -0800 (PST) Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id v1FHreqX028821 for ; Wed, 15 Feb 2017 17:53:40 GMT Received: from 950129200 ([176.241.251.4]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id v1FHram8028787 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 15 Feb 2017 17:53:39 GMT From: "Adrian Farrel" To: Date: Wed, 15 Feb 2017 17:53:36 -0000 Message-ID: <074d01d287b4$70dfbda0$529f38e0$@olddog.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AdKHtGvaYuu74oJISxyfrgW9mUWf/g== Content-Language: en-gb X-TM-AS-MML: disable X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.1.0.1062-22888.001 X-TM-AS-Result: No--20.825-10.0-31-10 X-imss-scan-details: No--20.825-10.0-31-10 X-TMASE-MatchedRID: Hl8mdRz2vU+XKs94NAOH8ru9iqQJLR0v9mnDjfUPq55gg+UjPGL1RevY XtvpGKMqPyIj4R5J2uvdXe2hdwlQb07wBr2c2+08e5NWR5iixe1wryoe90UcsPFJXtgF4GFL5gc Q9o9yjpskW2K8XClr39MDqPEOsvCb28kC8Kr7AslT46Ow+EhYOJyeCPjUvrMOStZtgyGdXLO7fo vhoOYjfIYtODbHEOdRdV5RalLqvEyJ+w2BcN2shpmug812qIbzlvTuxOaR0gLadW4iYSMjUV2tv sxNXD/lT+PN+LabUqBG+R/+80ybQUqkgzox/CQaCLNfGU4dffiowiOYoQ3GExDbjx2RiEl83QcA CR8vEHGFWYc1c3/uLH18Y330vpkb/lmiyIepCs3FlCgYxEaGE8QYGgcp3dr52viB/Jr4D1QJ/aH 0DaAUBZj8YEB3JMRbGhSpfcKQYBRZ4N8EjkhSSMQ7SONKBzNuwEM6ofA+CGMR34ro7k23nbJUBi cQ01GRgEBR2HjnXivaZiJAj8isJFYwdrAHWNZlHPCema1j/6va/szejBayyMJyVGyZPcv9o8WMk QWv6iV95l0nVeyiuFig9kCpMEfCVnRXm1iHN1bEQdG7H66TyOk/y0w7JiZo Archived-At: Subject: [L2sm] A question for the WG : I-D Action: draft-wen-l2sm-l2vpn-service-model-04.txt X-BeenThere: l2sm@ietf.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: adrian@olddog.co.uk 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: Wed, 15 Feb 2017 17:53:46 -0000 Thanks for this new revision, authors. Looking at the diff, I see that the main differences are 1. Add usage example in section 7 2. Change the model structure to be more in line with the L3SM model 3. Adjust the model to put service requirements in the top level so that they can be easily described using XML snippets in section 7 4. Addition of "cloud-access" as a mode of VPN 5. Fill in a few cases of "TBD" in the description of the module I also see quite a few places where the text has been cleaned up, but they don't make a substantial difference to the document (except for making it easier to read). The question for the WG is: Are there any remaining reservations about using this document as a starting point for IETF work to meet the WG objectives? That question is not "is this document perfect?" but we are asking whether the WG thinks it would be impossible to bend this document to meet the WG deliverables. If there are no more objections (oh, and feel free to express your support!) we can move forward and start the hard work. Thanks, Adrian and Qin > -----Original Message----- > From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf Of > internet-drafts@ietf.org > Sent: 15 February 2017 17:06 > To: i-d-announce@ietf.org > Subject: I-D Action: draft-wen-l2sm-l2vpn-service-model-04.txt > > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > > > Title : A YANG Data Model for L2VPN Service Delivery > Authors : Bin Wen > Giuseppe Fioccola > Chongfeng Xie > Luay Jalil > Filename : draft-wen-l2sm-l2vpn-service-model-04.txt > Pages : 116 > Date : 2017-02-15 > > 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 use 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-wen-l2sm-l2vpn-service-model/ > > There's also a htmlized version available at: > https://tools.ietf.org/html/draft-wen-l2sm-l2vpn-service-model-04 > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-wen-l2sm-l2vpn-service-model-04 > > > 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/ > > _______________________________________________ > I-D-Announce mailing list > I-D-Announce@ietf.org > https://www.ietf.org/mailman/listinfo/i-d-announce > Internet-Draft directories: http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt From nobody Tue Feb 21 07:54:24 2017 Return-Path: X-Original-To: l2sm@ietfa.amsl.com Delivered-To: l2sm@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF023129C2A for ; Tue, 21 Feb 2017 07:54:23 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.619 X-Spam-Level: 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RIfYrUy_opWS for ; Tue, 21 Feb 2017 07:54:21 -0800 (PST) Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D60A129C26 for ; Tue, 21 Feb 2017 07:54:21 -0800 (PST) Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id v1LFsJck003986 for ; Tue, 21 Feb 2017 15:54:19 GMT Received: from 950129200 ([176.241.251.3]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id v1LFsG11003847 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 21 Feb 2017 15:54:18 GMT From: "Adrian Farrel" To: Date: Tue, 21 Feb 2017 15:54:17 -0000 Message-ID: <02a201d28c5a$c3572820$4a057860$@olddog.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AdKMWkbAy7JwF/OkQ1uQ902OHEVP8w== Content-Language: en-gb X-TM-AS-MML: disable X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.1.0.1062-22900.000 X-TM-AS-Result: No--29.290-10.0-31-10 X-imss-scan-details: No--29.290-10.0-31-10 X-TMASE-MatchedRID: SO2Qg8dHVVuvhOOX3csmVwRH1Nr7oERd6fJcVqdnpZa638ZUY6gSdwK3 8IVwpUcJxPsZyShi1MSS78kPJmzLrpcqz3g0A4fyu72KpAktHS8NgFUqZt55A/5Ndkm9jGh501h hF+vnHUAtzVYgFhtGJb6K/YlfMDaJw5B5ycCESlvmAId+2bAQwrd2noO4P7rALraGNlLRahivmp qFRV6sXAgdquk/Orvb4TZn47t4x4AbTOp9RrvcoFz+axQLnAVBIaLR+2xKRDK4a2U7iYmMbkMbd Y98fcd4BMwsh2GIsZg0QJnXLcfAiAaK8f82C/nl9CCGBIPocclbAoaK+wS4jafnINz0/CVc/JNG PFwi6g2F0Sf8i/MG13iJBxa3l8XU2rvYheZgBXvIpMSwJEh3JZb07sTmkdICnvbaEOoeixPRrsO C8KeIZePAh1OktSEhojMcD3/yPlkIlmpWwuyl4c5Scd0yVs+bM3PBQtDBME/PX66ZUnrNV+tlDD 5mGP+X3f0e/BgwI9DShDtGsKTJ7TJWdXdBBzCxsyNb+yeIRAoHg23OuPl1dFfXgfL55invxOS+V hhIpA9BJqC3nHIp3JoI7wuYym4xyNkakgF4d95CvapcIkxJXyGZtiDVlw6eZNidnn9zXd/06z+X vHnOwbAW90NBxFF8BZ8G2UWkr6kM8jMXjBF+sDl/1fD/GopdyJ1gFgOMhOn6APa9i04WGCq2rl3 dzGQ1A/3R8k/14e0= Archived-At: Subject: [L2sm] Adoption of draft-wen-l2sm-l2vpn-service-model-04.txt X-BeenThere: l2sm@ietf.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: adrian@olddog.co.uk 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, 21 Feb 2017 15:54:23 -0000 Hi WG, When we polled before there was some moderate support for adoption of this document as a starting point for the WG's work. We have a small team of operators working on the draft, and a few (but only a few) more who were in the room in Seoul and expressed support on the list. There were also a few vendors who expressed support. There were a couple of voices raised against the document, and the authors made a new revision. My email (below) didn't attract anyone saying "no", so I think we should go ahead, adopt the draft, and then we can get down to the serious work of fixing the issues that exist in the draft. Authors, please re-post as draft-ietf-l2sm-l2vpn-service-model-00.txt Thanks, Adrian > -----Original Message----- > From: L2sm [mailto:l2sm-bounces@ietf.org] On Behalf Of Adrian Farrel > Sent: 15 February 2017 17:54 > To: l2sm@ietf.org > Subject: [L2sm] A question for the WG : I-D Action: draft-wen-l2sm-l2vpn- > service-model-04.txt > > Thanks for this new revision, authors. > > Looking at the diff, I see that the main differences are > > 1. Add usage example in section 7 > 2. Change the model structure to be more in line with the L3SM model > 3. Adjust the model to put service requirements in the top level so that they > can be easily described using XML snippets in section 7 > 4. Addition of "cloud-access" as a mode of VPN > 5. Fill in a few cases of "TBD" in the description of the module > > I also see quite a few places where the text has been cleaned up, but they don't > make a substantial difference to the document (except for making it easier to > read). > > The question for the WG is: > > Are there any remaining reservations about using this document as a starting > point for IETF work to meet the WG objectives? That question is not "is this > document perfect?" but we are asking whether the WG thinks it would be > impossible to bend this document to meet the WG deliverables. > > If there are no more objections (oh, and feel free to express your support!) we > can move forward and start the hard work. > > Thanks, > Adrian and Qin > > > > -----Original Message----- > > From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf Of > > internet-drafts@ietf.org > > Sent: 15 February 2017 17:06 > > To: i-d-announce@ietf.org > > Subject: I-D Action: draft-wen-l2sm-l2vpn-service-model-04.txt > > > > > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > > > > > Title : A YANG Data Model for L2VPN Service Delivery > > Authors : Bin Wen > > Giuseppe Fioccola > > Chongfeng Xie > > Luay Jalil > > Filename : draft-wen-l2sm-l2vpn-service-model-04.txt > > Pages : 116 > > Date : 2017-02-15 > > > > 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 use 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-wen-l2sm-l2vpn-service-model/ > > > > There's also a htmlized version available at: > > https://tools.ietf.org/html/draft-wen-l2sm-l2vpn-service-model-04 > > > > A diff from the previous version is available at: > > https://www.ietf.org/rfcdiff?url2=draft-wen-l2sm-l2vpn-service-model-04 > > > > > > 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/ > > > > _______________________________________________ > > I-D-Announce mailing list > > I-D-Announce@ietf.org > > https://www.ietf.org/mailman/listinfo/i-d-announce > > Internet-Draft directories: http://www.ietf.org/shadow.html > > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > _______________________________________________ > L2sm mailing list > L2sm@ietf.org > https://www.ietf.org/mailman/listinfo/l2sm From nobody Sun Feb 26 02:54:49 2017 Return-Path: X-Original-To: l2sm@ietf.org Delivered-To: l2sm@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 33DEA1294C0; Sun, 26 Feb 2017 02:54:48 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.46.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <148810648820.12490.15490366908969589796.idtracker@ietfa.amsl.com> Date: Sun, 26 Feb 2017 02:54:48 -0800 Archived-At: Cc: l2sm@ietf.org Subject: [L2sm] I-D Action: draft-ietf-l2sm-l2vpn-service-model-00.txt X-BeenThere: l2sm@ietf.org X-Mailman-Version: 2.1.17 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: Sun, 26 Feb 2017 10:54:48 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the L2VPN Service Model 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-00.txt Pages : 116 Date : 2017-02-26 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 use 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's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-l2sm-l2vpn-service-model-00 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/