From nobody Tue Nov 1 19:37:09 2016 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 A41CC1295CD; Tue, 1 Nov 2016 19:37:03 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "Spencer Dawkins" To: "The IESG" X-Test-IDTracker: no X-IETF-IDTracker: 6.37.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <147805422362.23900.9066271692003933992.idtracker@ietfa.amsl.com> Date: Tue, 01 Nov 2016 19:37:03 -0700 Archived-At: Cc: l2sm-chairs@ietf.org, l2sm@ietf.org Subject: [L2sm] Spencer Dawkins' No Objection on charter-ietf-l2sm-00-05: (with COMMENT) 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, 02 Nov 2016 02:37:04 -0000 Spencer Dawkins has entered the following ballot position for charter-ietf-l2sm-00-05: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/charter-ietf-l2sm/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- I have a few editorial suggestions. I think "full system configuration that enable service agility" should be s/enable/enables/. I think "recognized it would be beneficial" would be better as "recognized that it would be beneficial". I think you can drop "attempt to" from "The working group will attempt to derive a single data model". That should be possible, especially if the working group has L3SM for guidance. I think "(that work is expected to be carried out in other protocol-specific working groups)" would be easier to read as a separate sentence, not as a parenthetical insertion. From nobody Tue Nov 1 19:58:23 2016 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 9EA381299BE for ; Tue, 1 Nov 2016 19:58:21 -0700 (PDT) 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 1Imn8VPMwH6A for ; Tue, 1 Nov 2016 19:58:19 -0700 (PDT) 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 80949129971 for ; Tue, 1 Nov 2016 19:58:19 -0700 (PDT) Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id uA22wGMD031493 for ; Wed, 2 Nov 2016 02:58:16 GMT Received: from 950129200 (248.206.189.80.dyn.plus.net [80.189.206.248]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id uA22wFQA031483 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for ; Wed, 2 Nov 2016 02:58:16 GMT From: "Adrian Farrel" To: Date: Wed, 2 Nov 2016 02:58:10 -0000 Message-ID: <02f001d234b4$f27817c0$d7684740$@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: AdI0tOrfBA9/8lRwTNK4tLFEl3tQPQ== Content-Language: en-gb X-TM-AS-MML: disable X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.0.0.1202-22674.004 X-TM-AS-Result: No--4.612-10.0-31-10 X-imss-scan-details: No--4.612-10.0-31-10 X-TMASE-MatchedRID: sSIbS+JguC6DdXzEYxbu90+4wmL9kCTxFDp5CXMsVL8R34ro7k23nWFH /UMdxgIxrbTNFpU8lA/amyCqELKWrK+E45fdyyZXjoyKzEmtrEdt3qsaFY4DBDEWMGxJoAJB876 azl5+m3vi8zVgXoAltlwtzewu2M63APw73OVea/Bq8/xv2Um1avoLR4+zsDTtB00/kkeBTwD7y3 fGVbiP5gSO9unOUIxZ+a4vBbwkxue4RE22CpmJlk35cndsQ33QBhvZJ1RivVdePBxBBayI76N9P L7aXLWxvtj6SHi+/Ka563mv0F2G93TpyPFjxiWbVyxrQAZX9JvC/B26YUA7+A== Archived-At: Subject: [L2sm] Liaison message from the MEF Forum 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, 02 Nov 2016 02:58:21 -0000 Hi, Just for you information, the IESG received a message from the MEF Forum about the possible formation of an L2SM working group. You can see it in the datatracker at https://datatracker.ietf.org/liaison/1498/ The main content is some references to relevant work that should be useful. There is also a really helpful login to allow access to the relevant MEF work in progress. Otherwise I read the message as one of cooperation which sounds good. Cheers, Adrian From nobody Wed Nov 2 10:19:57 2016 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 B5B941294A3 for ; Wed, 2 Nov 2016 10:19:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -16.018 X-Spam-Level: X-Spam-Status: No, score=-16.018 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.497, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 mUfpXQ3HnStc for ; Wed, 2 Nov 2016 10:19:54 -0700 (PDT) Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 006E512941D for ; Wed, 2 Nov 2016 10:19:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5534; q=dns/txt; s=iport; t=1478107194; x=1479316794; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=4PvWUjIJXOBUbHMCuj+Ep1VDQ46l0PYm3BcfElV3Xdw=; b=EpsgX6pB6PNPUTnNiXm+QLRVDa4ELm+Kyek4jk/wt+UJv1ckQSLSJSFX UaptyawHYbourV+Pxvgwh1IE0NREbqZwW2H5apRIqJ1H+RPO7yyt6WQOy 4cLXrTMXBBQ7sC+3xKDEoQATdVhOZ60pNd2x+2ED+zhhNs7dUw5Fwe50O E=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BYAgBBHxpY/xbLJq1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgnM5AQEBAQGBIY4JlwGPMIUXggeGIgKCYxQBAgEBAQEBAQFiKIR?= =?us-ascii?q?iAQEDAXkQC0ZXBAIBDAgBAYhKCLpFAQEBAQEBAQEBAQEBAQEBAQEBAQEBHIY9g?= =?us-ascii?q?X2CWIonBYhJkVSQOol1hhSJP4ddHjZWCAmEWj49iRABAQE?= X-IronPort-AV: E=Sophos;i="5.31,583,1473120000"; d="scan'208,217";a="649640465" Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Nov 2016 17:19:52 +0000 Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id uA2HJp53002794; Wed, 2 Nov 2016 17:19:51 GMT To: "chongfeng.xie@foxmail.com" <1848418658@qq.com>, l2sm References: <201610262137532695733@ctbri.com.cn> From: Benoit Claise Message-ID: <014a8020-1e65-a77a-47af-357c4fd22710@cisco.com> Date: Wed, 2 Nov 2016 18:19:52 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <201610262137532695733@ctbri.com.cn> Content-Type: multipart/alternative; boundary="------------E97C5A0FCBE4FAE23E5B6F15" Archived-At: Cc: adrian Subject: Re: [L2sm] L2SM charter proposal 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, 02 Nov 2016 17:19:55 -0000 This is a multi-part message in MIME format. --------------E97C5A0FCBE4FAE23E5B6F15 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Hi Chongfeng, Which organizations are working on related L2VPN data models, other than MEF? Regards, Benoit > > > > >> But we could... > >> OLD > >> The working group will coordinate with other working groups responsible for > >> L2VPN protocol work (most notably with BESS and PALS) and with the MEF. > >> NEW > >> The working group will coordinate with other working groups responsible for > >> L2VPN protocol work (most notably with BESS and PALS). It will also coordinate > >> with other organizations working on related L2VPN data models (such as the > >> MEF). > >> END > > >Noting external dependencies in a separate sentence is better. > > >Do the WG proponents plan to share details on how they plan to deal with the overlapping work in MEF? > ** > * > Sorry for late reply, talking with our delegate in MEF,I think the collaboration is needed if the detailed performance parameters, performance metric, performance objective should be modeled in l2sm model, but the debate point is how much details we should cover, since I don't believe we should focus on enumerating a large list of perf measurement related data, if it is healthy to have them, I think we should create a sla container for placeholder to include these parameters that are defined by MEF 23.2,definitely MEF reference is needed, right now we authors still debate on details we should cover.* > * > * > *Chongfeng Xie* > > ------------------------------------------------------------------------ > --------------E97C5A0FCBE4FAE23E5B6F15 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 8bit
Hi Chongfeng,

Which organizations are working on related L2VPN data models, other than MEF?

Regards, Benoit



>> But we could...
>> OLD
>> The working group will coordinate with other working groups responsible for
>> L2VPN protocol work (most notably with BESS and PALS) and with the MEF.
>> NEW
>> The working group will coordinate with other working groups responsible for
>> L2VPN protocol work (most notably with BESS and PALS). It will also coordinate
>> with other organizations working on related L2VPN data models (such as the
>> MEF).
>> END
 
>Noting external dependencies in a separate sentence is better.
 
>Do the WG proponents plan to share details on how they plan to deal with the overlapping work in MEF?
 

Sorry for late reply, talking with our delegate in MEF,I think the collaboration is needed if the detailed performance parameters, performance metric, performance objective should be modeled in l2sm model, but the debate point is how much details we should cover, since I don't believe we should focus on enumerating a large list of perf measurement related data, if it is healthy to have them, I think we should create a sla container for placeholder to include these parameters that are defined by MEF 23.2,definitely MEF reference is needed, right now we authors still debate on details we should cover.

Chongfeng Xie



--------------E97C5A0FCBE4FAE23E5B6F15-- From nobody Wed Nov 2 10:22:39 2016 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 B6DB01296F5; Wed, 2 Nov 2016 10:22:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -16.019 X-Spam-Level: X-Spam-Status: No, score=-16.019 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.497, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 ehCKx3-6G9uw; Wed, 2 Nov 2016 10:22:35 -0700 (PDT) Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F5C21296F2; Wed, 2 Nov 2016 10:22:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1468; q=dns/txt; s=iport; t=1478107345; x=1479316945; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=WmdmUMVvLk3XahgnvqL3RED23wew4JC73kn2HS5lmrY=; b=ZE7Ke39qmplU3NXQ9yLcMH5340/3kh9Y8cPGV6LRIgKDSC7MMVicLQQW mp7UHhZL9wKBhbvpN6WTI5xXxLaMGzKJwdGK+MQX6Yjy6Ntkhou27XhN2 UeuclWMLARZ0D8owcR+fhw3jL+/ULXLx52TwLb/KUNYNagEBPxjD/GSG5 w=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BQAgCrHxpY/xbLJq1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgywBAQEBAXcqUo03q0iCBx0LhXoCgmMUAQIBAQEBAQEBYiiEYgE?= =?us-ascii?q?BBAEBATUvBwsQC0YnMAYBDAYCAQGIUg66NwEBAQEBAQEBAQEBAQEBAQEBAQEBG?= =?us-ascii?q?AWGPYF9CIJQhBkRAYV8AQSISZFUhjOKB4FuhG+DGCOFcYk/h10eNlYICYNcgTw?= =?us-ascii?q?9NIYwgiwBAQE?= X-IronPort-AV: E=Sophos;i="5.31,583,1473120000"; d="scan'208";a="647819237" Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Nov 2016 17:22:23 +0000 Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id uA2HMMrn016556; Wed, 2 Nov 2016 17:22:23 GMT To: Spencer Dawkins , The IESG References: <147805422362.23900.9066271692003933992.idtracker@ietfa.amsl.com> From: Benoit Claise Message-ID: <915326b9-3822-a186-f13c-5626bba52e1a@cisco.com> Date: Wed, 2 Nov 2016 18:22:23 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <147805422362.23900.9066271692003933992.idtracker@ietfa.amsl.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Cc: l2sm-chairs@ietf.org, l2sm@ietf.org Subject: Re: [L2sm] Spencer Dawkins' No Objection on charter-ietf-l2sm-00-05: (with COMMENT) 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, 02 Nov 2016 17:22:37 -0000 Thank you Spencer, I updated the charter with your suggestions. Regards, B. > Spencer Dawkins has entered the following ballot position for > charter-ietf-l2sm-00-05: No Objection > > When responding, please keep the subject line intact and reply to all > email addresses included in the To and CC lines. (Feel free to cut this > introductory paragraph, however.) > > > > The document, along with other ballot positions, can be found here: > https://datatracker.ietf.org/doc/charter-ietf-l2sm/ > > > > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > I have a few editorial suggestions. > > I think "full system configuration that enable service agility" should be > s/enable/enables/. > > I think "recognized it would be beneficial" would be better as > "recognized that it would be beneficial". > > I think you can drop "attempt to" from "The working group will attempt to > derive a single data model". That should be possible, especially if the > working group has L3SM for guidance. > > I think "(that work is expected to be carried out in other > protocol-specific working groups)" would be easier to read as a separate > sentence, not as a parenthetical insertion. > > > _______________________________________________ > L2sm mailing list > L2sm@ietf.org > https://www.ietf.org/mailman/listinfo/l2sm > . > From nobody Wed Nov 2 19:25:28 2016 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 36CE01298B3; Wed, 2 Nov 2016 19:25:27 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "Ben Campbell" To: "The IESG" X-Test-IDTracker: no X-IETF-IDTracker: 6.37.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <147813992718.24057.8654858944560143534.idtracker@ietfa.amsl.com> Date: Wed, 02 Nov 2016 19:25:27 -0700 Archived-At: Cc: l2sm-chairs@ietf.org, l2sm@ietf.org Subject: [L2sm] Ben Campbell's No Objection on charter-ietf-l2sm-00-06: (with COMMENT) 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: Thu, 03 Nov 2016 02:25:27 -0000 Ben Campbell has entered the following ballot position for charter-ietf-l2sm-00-06: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/charter-ietf-l2sm/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- A strictly editorial comment: The second sentence in the third paragraph would benefit from being broken into a few shorter sentences. From nobody Thu Nov 3 04:22:30 2016 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 D5649129988; Thu, 3 Nov 2016 04:22:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -16.018 X-Spam-Level: X-Spam-Status: No, score=-16.018 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.497, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 ZIgLXbpEtg6T; Thu, 3 Nov 2016 04:22:27 -0700 (PDT) Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 812E0129971; Thu, 3 Nov 2016 04:22:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4849; q=dns/txt; s=iport; t=1478172147; x=1479381747; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=ou4f/i9cY/8YCr6u7vwvtUbpfoqycpmulFchUsMASgE=; b=fNnicliHZEAlocl7t8qiCoQWq44W6RnL3VTz3nrvM8y2maFAAR947/78 N/Au58LTxKKKoYNW49P6FB/Y1ogKhHqrUUhQjkKY6PA+1X9Mfz0dr+ehF EHA6avdjKewEIa5OzBA+N624rkMrWqJS88gj4NtcYCgTRMfmGAvO2Za65 0=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AkAQDCHBtY/xbLJq1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgnM9AQEBAQF3Ko4Jln+PL4MJgg+CCCiFegKCYxQBAgEBAQEBAQF?= =?us-ascii?q?iKIRiAQEEI1YQCxgqAgJXBgEMCAEBiFIOrU6NAAEBAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBARcFhj+BfQiCUIQZEQGDIIJcBYhJBZFShjSKCYFuhG+DGIYViUSDWYQEHjd?= =?us-ascii?q?ZCQmFID2GAoIsAQEB?= X-IronPort-AV: E=Sophos;i="5.31,438,1473120000"; d="scan'208,217";a="647845710" Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Nov 2016 11:22:24 +0000 Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id uA3BMNYB021896; Thu, 3 Nov 2016 11:22:24 GMT To: Ben Campbell , The IESG References: <147813992718.24057.8654858944560143534.idtracker@ietfa.amsl.com> From: Benoit Claise Message-ID: Date: Thu, 3 Nov 2016 12:22:23 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <147813992718.24057.8654858944560143534.idtracker@ietfa.amsl.com> Content-Type: multipart/alternative; boundary="------------6F3C61B73BAA6C876C7F41A0" Archived-At: Cc: l2sm-chairs@ietf.org, l2sm@ietf.org Subject: Re: [L2sm] Ben Campbell's No Objection on charter-ietf-l2sm-00-06: (with COMMENT) 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: Thu, 03 Nov 2016 11:22:29 -0000 This is a multi-part message in MIME format. --------------6F3C61B73BAA6C876C7F41A0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit On 11/3/2016 3:25 AM, Ben Campbell wrote: > Ben Campbell has entered the following ballot position for > charter-ietf-l2sm-00-06: No Objection > > When responding, please keep the subject line intact and reply to all > email addresses included in the To and CC lines. (Feel free to cut this > introductory paragraph, however.) > > > > The document, along with other ballot positions, can be found here: > https://datatracker.ietf.org/doc/charter-ietf-l2sm/ > > > > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > A strictly editorial comment: > > The second sentence in the third paragraph would benefit from being > broken into a few shorter sentences. You're right. New text, proposed by Adrian: The working group will derive a single data model that includes support for the following: - point-to-point Virtual Private Wire Services (VPWS), - multipoint Virtual Private LAN services (VPLS) that use LDP-signaled Pseudowires - multipoint Virtual Private LAN services (VPLS) that use a Border Gateway Protocol (BGP) control plane as described in RFC4761 and RFC6624 - Ethernet VPNs specified in RFC 7432 Regards, Benoit > > . > --------------6F3C61B73BAA6C876C7F41A0 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit
On 11/3/2016 3:25 AM, Ben Campbell wrote:
Ben Campbell has entered the following ballot position for
charter-ietf-l2sm-00-06: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)



The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/charter-ietf-l2sm/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

A strictly editorial comment:

The second sentence in the third paragraph would benefit from being
broken into a few shorter sentences.
You're right.
New text, proposed by Adrian:

The working group will derive a single data model that includes support for the following:

- point-to-point Virtual Private Wire Services (VPWS),

- multipoint Virtual Private LAN services (VPLS) that use LDP-signaled Pseudowires

- multipoint Virtual Private LAN services (VPLS) that use a Border Gateway Protocol

  (BGP) control plane as described in RFC4761 and RFC6624

- Ethernet VPNs specified in RFC 7432

Regards, Benoit

.

--------------6F3C61B73BAA6C876C7F41A0-- From nobody Thu Nov 3 06:25:11 2016 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 043771295EF; Thu, 3 Nov 2016 06:25:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.397 X-Spam-Level: X-Spam-Status: No, score=-3.397 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.497] 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 ZKF8Xzj4-vkW; Thu, 3 Nov 2016 06:25:04 -0700 (PDT) Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 00ECC1295EC; Thu, 3 Nov 2016 06:24:35 -0700 (PDT) Received: from [10.0.1.21] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id uA3DOWOE022769 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 3 Nov 2016 08:24:33 -0500 (CDT) (envelope-from ben@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.21] From: "Ben Campbell" To: "Benoit Claise" Date: Thu, 03 Nov 2016 08:24:32 -0500 Message-ID: In-Reply-To: References: <147813992718.24057.8654858944560143534.idtracker@ietfa.amsl.com> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Mailer: MailMate (1.9.5r5263) Archived-At: Cc: l2sm-chairs@ietf.org, The IESG , l2sm@ietf.org Subject: Re: [L2sm] Ben Campbell's No Objection on charter-ietf-l2sm-00-06: (with COMMENT) 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: Thu, 03 Nov 2016 13:25:10 -0000 On 3 Nov 2016, at 6:22, Benoit Claise wrote: > On 11/3/2016 3:25 AM, Ben Campbell wrote: >> Ben Campbell has entered the following ballot position for >> charter-ietf-l2sm-00-06: No Objection >> >> When responding, please keep the subject line intact and reply to all >> email addresses included in the To and CC lines. (Feel free to cut >> this >> introductory paragraph, however.) >> >> >> >> The document, along with other ballot positions, can be found here: >> https://datatracker.ietf.org/doc/charter-ietf-l2sm/ >> >> >> >> ---------------------------------------------------------------------- >> COMMENT: >> ---------------------------------------------------------------------- >> >> A strictly editorial comment: >> >> The second sentence in the third paragraph would benefit from being >> broken into a few shorter sentences. > You're right. > New text, proposed by Adrian: > > The working group will derive a single data model that includes > support for the following: > > - point-to-point Virtual Private Wire Services (VPWS), > > - multipoint Virtual Private LAN services (VPLS) that use LDP-signaled > Pseudowires > > - multipoint Virtual Private LAN services (VPLS) that use a Border > Gateway Protocol > > (BGP) control plane as described in RFC4761 and RFC6624 > > - Ethernet VPNs specified in RFC 7432 That's much better, thanks! From nobody Thu Nov 3 08:39:08 2016 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 B2E3E1296A4 for ; Thu, 3 Nov 2016 08:39:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: 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, FREEMAIL_FROM=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 nC_JW4eH4s4J for ; Thu, 3 Nov 2016 08:39:05 -0700 (PDT) Received: from mail-pf0-x236.google.com (mail-pf0-x236.google.com [IPv6:2607:f8b0:400e:c00::236]) (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 88A7D1295F2 for ; Thu, 3 Nov 2016 08:39:05 -0700 (PDT) Received: by mail-pf0-x236.google.com with SMTP id n85so33600392pfi.1 for ; Thu, 03 Nov 2016 08:39:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-transfer-encoding:mime-version:subject:message-id:date :to; bh=LCOGJ92hjZ5icQQm9gOVvb13VTDsDwXgmUOajeg+uUI=; b=wW4eG/1Zsdwc5EUHXiISo4q7v5UG70zKXv0xXiYPUXV0hhhP5rgygSOIa/K0Y36gNo XeuhuawnNpCd+nuMpta6P8mq64MYbN+8SdrSwgMt7q2nEcNgbmENmc4iQ2w/AGeaj0t2 zkzqqfC2Scrq3EHhDacsROeBcNTlLN7+r4k4uL7o399bqVD0m90mxkx3ouH3XjYJSPRF Nu9eTKp8CtyF57nT2kLHaJu9iF4bKy41vCs3seMxE5W9L/bCs6GfptGDYqT/tYWuqUui 2NaQ7C0Ve1tJk19ofiGhwbE/43uuVKDWqydM8Yowz+L1G4qeBYjp1ivpRt9YWpUqrESZ Kn8w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:to; bh=LCOGJ92hjZ5icQQm9gOVvb13VTDsDwXgmUOajeg+uUI=; b=Bxd4y+pNbjaszciYnOzdTHs55SCyb7WJjUPDeV41ELdwkbKRg6qzfvu0lx93wGS0jP g+uZCX0Gwi8Ja8bHLeBcBpJvmMKh9P64UxydbZjvjcABZOeRrTjIgYyPu+4OlnwCXAKS R59BciQHp2dsDxqMF1RnabnVsNFdpgikQELy5MEE4hmoRDFASgEVqTOIbZ2/HRYRu3hU b0EMv5EKoadpiDr5GRj5xjvTkKh3VW9v57bKEFtnsOXvxfSlNZBH9V41P+1R96+yaQsX 0CTbUGfFfKvU6bTOGuK0IbbdVkQFe+WdVo+SAUGIrbBDq2/v3mk1dAb/mquLf0ArysYO 9SkA== X-Gm-Message-State: ABUngvfCWx77Z7tRtmGKE8jHsqaosmyE+OBABciosnyoJWT3yCAZKhvYmrKQKP998vP2fg== X-Received: by 10.98.157.148 with SMTP id a20mr17956329pfk.1.1478187544885; Thu, 03 Nov 2016 08:39:04 -0700 (PDT) Received: from [10.103.107.106] ([166.170.40.242]) by smtp.gmail.com with ESMTPSA id rx1sm13675572pab.32.2016.11.03.08.39.04 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 03 Nov 2016 08:39:04 -0700 (PDT) From: Mahesh Jethanandani Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Message-Id: <65B06CBB-28F8-49A8-9733-C31A3ECA8A58@gmail.com> Date: Thu, 3 Nov 2016 08:39:03 -0700 To: l2sm@ietf.org X-Mailer: iPhone Mail (13G36) Archived-At: Subject: [L2sm] Request for an agenda slot 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: Thu, 03 Nov 2016 15:39:07 -0000 I do not know whether an agenda slot request has been posted, but would like= to request a 10 min slot to present.=20 Thanks.=20 Mahesh Jethanandani=20 mjethanandani@gmail.com= From nobody Thu Nov 3 08:48:05 2016 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 ABC5F129A8E for ; Thu, 3 Nov 2016 08:48:03 -0700 (PDT) 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 a6h-RhjAY9Sd for ; Thu, 3 Nov 2016 08:48:01 -0700 (PDT) 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 EFC0E12966D for ; Thu, 3 Nov 2016 08:47:56 -0700 (PDT) Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id uA3FlreZ013480; Thu, 3 Nov 2016 15:47:53 GMT Received: from 950129200 (248.206.189.80.dyn.plus.net [80.189.206.248]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id uA3FlqZZ013458 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Thu, 3 Nov 2016 15:47:53 GMT From: "Adrian Farrel" To: "'Mahesh Jethanandani'" , References: <65B06CBB-28F8-49A8-9733-C31A3ECA8A58@gmail.com> In-Reply-To: <65B06CBB-28F8-49A8-9733-C31A3ECA8A58@gmail.com> Date: Thu, 3 Nov 2016 15:47:46 -0000 Message-ID: <068401d235e9$9fc73390$df559ab0$@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: AQJpgU01cTFqdlZ0FH6mD6LmpXwv/Z+Yz5VQ Content-Language: en-gb X-TM-AS-MML: disable X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.0.0.1202-22676.007 X-TM-AS-Result: No--11.370-10.0-31-10 X-imss-scan-details: No--11.370-10.0-31-10 X-TMASE-MatchedRID: VfovoVrt/obW/bDrA6VrLcOD5TU1KZy5MJebi1vXnNOC7uI8epmqsICu qghmtWfXAmrvAJndFpcIgJXv+daDCaDUMTFlJZ9NU+OjsPhIWDjSde/CNbaZJUmDyxNPdHMX2gl ssGrvJsajPwdOX7PV9n8vHqIwBzQYVB55dkRMs8xCvapcIkxJXyAiV9lwjDugHYyoxCSlv+9pGe 7B2ogoe/4lyIiQLcz28U8MeFCSDHIIVzx51Rv3HpVRzPxemJL0FJFr2qlKix+o+b+yOP0oGA42c I60OgkFslVouE/7acIeYZj+jjPzyU1+zyfzlN7y/sToY2qzpx7dB/CxWTRRu25FeHtsUoHu0iNC oZws+VZwWsvF8nKPCnUI3uJ0+Pj6UShv21P7R1sJK2MK45H+GA== Archived-At: Subject: Re: [L2sm] Request for an agenda slot 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: Thu, 03 Nov 2016 15:48:04 -0000 Hi Mahesh, You're keen! The WG was only formed less than two hours ago. Well, the announcement hasn't even gone out :-) Anyway, what would you like to talk about? BTW... We have a 90 minute slot. Things we MUST cover include... - review of the charter - reminder of what a "customer service model" is - update on what the MEF forum has been doing and how we will share our progress with them - overview of draft-wen-l2sm-l2vpn-service-model You can consider that our draft agenda. Cheers, Adrian -- Support an author and your imagination. Tales from the Wood - Eighteen new fairy tales. More Tales from the Wood - Eighteen MORE new fairy tales. https://www.feedaread.com/profiles/8604/ http://www.amazon.co.uk/Tales-Wood-Adrian-Farrel/dp/1786100924 Or buy from me direct. > -----Original Message----- > From: L2sm [mailto:l2sm-bounces@ietf.org] On Behalf Of Mahesh Jethanandani > Sent: 03 November 2016 15:39 > To: l2sm@ietf.org > Subject: [L2sm] Request for an agenda slot > > I do not know whether an agenda slot request has been posted, but would like to > request a 10 min slot to present. > > Thanks. > > Mahesh Jethanandani > mjethanandani@gmail.com > _______________________________________________ > L2sm mailing list > L2sm@ietf.org > https://www.ietf.org/mailman/listinfo/l2sm From nobody Fri Nov 4 10:58:58 2016 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 1B2FD1295EC; Fri, 4 Nov 2016 10:58:56 -0700 (PDT) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: "IETF-Announce" X-Test-IDTracker: no X-IETF-IDTracker: 6.37.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <147828233610.17040.11733309909516035095.idtracker@ietfa.amsl.com> Date: Fri, 04 Nov 2016 10:58:56 -0700 Archived-At: Cc: l2sm-chairs@ietf.org, The IESG , l2sm@ietf.org Subject: [L2sm] WG Action: Formed L2VPN Service Model (l2sm) 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: Fri, 04 Nov 2016 17:58:56 -0000 A new IETF WG has been formed in the Operations and Management Area. For additional information, please contact the Area Directors or the WG Chairs. L2VPN Service Model (l2sm) ----------------------------------------------------------------------- Current status: Proposed WG Chairs: Adrian Farrel Qin Wu Assigned Area Director: Benoit Claise Operations and Management Area Directors: Benoit Claise Joel Jaeggli Mailing list: Address: l2sm@ietf.org To subscribe: https://www.ietf.org/mailman/listinfo/l2sm Archive: https://mailarchive.ietf.org/arch/browse/l2sm/ Charter: https://datatracker.ietf.org/doc/charter-ietf-l2sm/ The IETF and the industry in general is currently specifying a set of YANG models for network element and protocol configuration. This is an essential first step, but the end goal is a full system configuration that enables service agility to speed service creation and delivery and allows the deployment of innovative new services across networks. Services are built from a combination of network element and protocol configuration, but are specified to service users in more abstract terms. The Layer Two Virtual Private Network Service Model (L2SM) working group is a short-lived WG. It is tasked to create a YANG data model that describes a L2VPN service (a L2VPN customer service model). The model can be used for communication between customers and network operators, and to provide input to automated control and configuration applications. It is recognized that it would be beneficial to have a common base model that addresses multiple popular L2VPN service types. The working group will derive a single data model that includes support for the following: - point-to-point Virtual Private Wire Services (VPWS), - multipoint Virtual Private LAN services (VPLS) that use LDP-signaled Pseudowires - multipoint Virtual Private LAN services (VPLS) that use a Border Gateway Protocol (BGP) control plane as described in RFC4761 and RFC6624 - Ethernet VPNs specified in RFC 7432. Other L2VPN service types may be included if there is consensus in the working group. It needs to be clearly understood that this L2VPN customer service model is not an L2VPN configuration model. That is, it does not provide details for configuring network elements or protocols: that work is expected to be carried out in other protocol-specific working groups. Instead, the L2VPN customer service model contains the characteristics of the service as discussed between the operators and their customers. A separate process is responsible for mapping this customer service model onto the protocols and network elements depending on how the network operator chooses to realise the service. The deliverable from this working group will provide information that other working groups can use to evaluate the set of YANG models that they have already developed or that are under development. This will help them to identify any missing models or details. Thus, the deliverable can be viewed as driving requirements for service delivery models so that the customer service parameters can be mapped into inputs used by the protocol configuration models. The working group will learn from the experience of the L3SM working group and it is expected that the L2SM data model will have similar structure to the L3SM data model to enable benefits of common code, provide shared user experience, and leverage discussions that took place during the L3SM development. The working group should consider draft-wen-l2sm-l2vpn-service-model as a starting point. The working group will coordinate with other working groups responsible for L2VPN protocol work (most notably with BESS and PALS). It will also coordinate with other organizations working on related L2VPN data models (such as the MEF). Milestones: Dec 2016 - Adopt WG draft for data model Oct 2017 - Request publication of data model as Standards Track RFC Dec 2017 - Close working group From nobody Fri Nov 4 11:09:18 2016 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 8DA2712940A for ; Fri, 4 Nov 2016 11:09:17 -0700 (PDT) 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 GgaY0AeuFbDO for ; Fri, 4 Nov 2016 11:09:16 -0700 (PDT) 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 0D872129482 for ; Fri, 4 Nov 2016 11:09:14 -0700 (PDT) Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id uA4I9CIh011631 for ; Fri, 4 Nov 2016 18:09:12 GMT Received: from 950129200 (248.206.189.80.dyn.plus.net [80.189.206.248]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id uA4I9Bqp011624 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for ; Fri, 4 Nov 2016 18:09:11 GMT From: "Adrian Farrel" To: Date: Fri, 4 Nov 2016 18:09:05 -0000 Message-ID: <027e01d236c6$8875ed20$9961c760$@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: AdI2xm3SvWdQTj23T2ShWqGy28hbDg== Content-Language: en-gb X-TM-AS-MML: disable X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.0.0.1202-22680.001 X-TM-AS-Result: No--4.730-10.0-31-10 X-imss-scan-details: No--4.730-10.0-31-10 X-TMASE-MatchedRID: JIe4g56MgFD+7Rdj+OqYTNOEZs/2oH3cr+tNHluPfDK2DHpETYCEs/KR 7FciFjttBHwOCfYyy7f+OkqLUfiUr+VHGbcDbAq6OX/V8P8ail1bCjvvWZW+SUf4Jcwf9/jZUEh Wy9W70AEnRE+fI6etkvIdyfqko4FrpwJHN7nD6O3oi7GSm4vhz+kwzPEy2z43sBtVChEB5w4s/0 anQS0uqra3uQmnju7gGiLPcDnidjzx+698PBd7tE3+9BzFCkVzNAW83zYDw/v1OlCIPxKfizngM RAgrdeEyfkWaeG5p9A= Archived-At: Subject: [L2sm] Welcome to L2SM and provisional agenda 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: Fri, 04 Nov 2016 18:09:17 -0000 Hi, Welcome to the newly formed L2SM working group. Our charter is at https://datatracker.ietf.org/group/l2sm/charter/ I have uploaded a provisional agenda for Seoul https://datatracker.ietf.org/meeting/97/agenda/l2sm/ Please shout to me and Qin if there any questions or issues. Cheers, Adrian From nobody Sun Nov 6 15:21:42 2016 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 C7ECD129A50 for ; Sun, 6 Nov 2016 15:21:40 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: 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, FREEMAIL_FROM=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 VwBSbS6hylgH for ; Sun, 6 Nov 2016 15:21:38 -0800 (PST) Received: from mail-pf0-x233.google.com (mail-pf0-x233.google.com [IPv6:2607:f8b0:400e:c00::233]) (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 BEAD8129A4D for ; Sun, 6 Nov 2016 15:21:38 -0800 (PST) Received: by mail-pf0-x233.google.com with SMTP id 189so81139588pfz.3 for ; Sun, 06 Nov 2016 15:21:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=RO+9Vmr1hGIyauo9iQSUV9DJ6bBP7dajn/pWBebW3Ak=; b=su+7K0v/dWrDpA1XPZ4PDYOBzNzjJITO/M4JF3llv5b6ISONakIASpSqJqcM+twO1a zV4N9R8wZQBb9UGUhdaHgLRPG24TYiPx6A5fUmmjzCe/xsUkL24FuXIgvw/t/uMxcVRf es45FbokeCeCVTaTbjBBGBNeQ1yyJ3DON5MhMdy2AcaRbLOaHR+r+E9fDYAOXNoHddvE Gsw63N6gD5DPlCIremDVs1jt5Z+npzn6uJqQ1xjsvlPy7eKO/cRs9/hRF+lENy8hA8J5 Q2Z9Qxt1khWOo/SEXMks1tpE86hVigIzPkA5AhZ9EEL8DFKBruU1KIbT4vtPl/Bj6Ypd fFDA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=RO+9Vmr1hGIyauo9iQSUV9DJ6bBP7dajn/pWBebW3Ak=; b=ZVaB8qNXeHWOryKZZqg5dNFp0cK7kMnJ/c9SSPSSm59g1Vk+yqgVQKFoH6zBDOvxjq SqhDwkGLX4yNA4AmoIfqmEX+EN/4KjoU3LNb49OYJjKyaWP6JiDwoEi0swJ+Q7/1I1yY 9Zj6AXP3fOCF9jWTi82o7kcTu56/lu/4owxtLkUAd8KhfpjdCyI6jTQsedZFggFP+Erd h11zKytFoS1RKtVBiWJYKsQymb2iudntty8KTI1CKmcocC5S9fLMZWbK3txO3SyS+WOR jb6XlCLhOG3f9QGtUbkcEmYU4dXzsx1BS/r26pHzpXSExzTj38IsDHD1WrwcbRhgSB8B LYtA== X-Gm-Message-State: ABUngvfqQxIbYcMd59DsSoGrwW9t/l7oDiKLuWIIrh1hl8VeIkd/oimhMiRULxYSrLusQA== X-Received: by 10.99.125.14 with SMTP id y14mr6380916pgc.163.1478474498162; Sun, 06 Nov 2016 15:21:38 -0800 (PST) Received: from [10.10.11.18] ([203.189.142.108]) by smtp.gmail.com with ESMTPSA id p14sm35194935par.25.2016.11.06.15.21.35 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sun, 06 Nov 2016 15:21:37 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) From: Mahesh Jethanandani In-Reply-To: <068401d235e9$9fc73390$df559ab0$@olddog.co.uk> Date: Mon, 7 Nov 2016 06:21:32 +0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <65B06CBB-28F8-49A8-9733-C31A3ECA8A58@gmail.com> <068401d235e9$9fc73390$df559ab0$@olddog.co.uk> To: Adrian Farell X-Mailer: Apple Mail (2.3124) Archived-At: Cc: John Strassner , l2sm@ietf.org, scott.mansfield@ericsson.com, stephan.pelletier@oracle.com, "Ranganathan, Raghu" , David Ball Subject: Re: [L2sm] Request for an agenda slot 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: Sun, 06 Nov 2016 23:21:41 -0000 > On Nov 3, 2016, at 10:47 PM, Adrian Farrel = wrote: >=20 > Hi Mahesh, >=20 > You're keen! > The WG was only formed less than two hours ago. Well, the announcement = hasn't > even gone out :-) >=20 > Anyway, what would you like to talk about? >=20 > BTW...=20 > We have a 90 minute slot. Things we MUST cover include... > - review of the charter > - reminder of what a "customer service model" is > - update on what the MEF forum has been doing and how we will share = our progress > with them I would like to talk about the above item. You must have already = received the liaison statement sent by MEF. I would be happy to go over = the work we have already done in MEF, and understand what this WG would = like to do that is not already done by MEF. Thanks. > - overview of draft-wen-l2sm-l2vpn-service-model >=20 > You can consider that our draft agenda. >=20 > Cheers, > Adrian > -- > Support an author and your imagination. > Tales from the Wood - Eighteen new fairy tales. > More Tales from the Wood - Eighteen MORE new fairy tales. > https://www.feedaread.com/profiles/8604/ > http://www.amazon.co.uk/Tales-Wood-Adrian-Farrel/dp/1786100924 > Or buy from me direct. >=20 >=20 >=20 >=20 >> -----Original Message----- >> From: L2sm [mailto:l2sm-bounces@ietf.org] On Behalf Of Mahesh = Jethanandani >> Sent: 03 November 2016 15:39 >> To: l2sm@ietf.org >> Subject: [L2sm] Request for an agenda slot >>=20 >> I do not know whether an agenda slot request has been posted, but = would like > to >> request a 10 min slot to present. >>=20 >> Thanks. >>=20 >> Mahesh Jethanandani >> mjethanandani@gmail.com >> _______________________________________________ >> L2sm mailing list >> L2sm@ietf.org >> https://www.ietf.org/mailman/listinfo/l2sm >=20 Mahesh Jethanandani mjethanandani@gmail.com From nobody Sun Nov 6 15:39:31 2016 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 219D5129575 for ; Sun, 6 Nov 2016 15:39:30 -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 ahBm-XfT_gou for ; Sun, 6 Nov 2016 15:39:28 -0800 (PST) Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01F5F1294C8 for ; Sun, 6 Nov 2016 15:39:27 -0800 (PST) Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id uA6NdDUF012422; Sun, 6 Nov 2016 23:39:13 GMT Received: from 950129200 (248.206.189.80.dyn.plus.net [80.189.206.248]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id uA6NdCfw012416 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Sun, 6 Nov 2016 23:39:13 GMT From: "Adrian Farrel" To: "'Mahesh Jethanandani'" References: <65B06CBB-28F8-49A8-9733-C31A3ECA8A58@gmail.com> <068401d235e9$9fc73390$df559ab0$@olddog.co.uk> In-Reply-To: Date: Sun, 6 Nov 2016 23:39:11 -0000 Message-ID: <01d301d23886$fabf7470$f03e5d50$@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: AQJpgU01cTFqdlZ0FH6mD6LmpXwv/QFolVdBAVtCwaSfh+v+0A== Content-Language: en-gb X-TM-AS-MML: disable X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.0.0.1202-22684.003 X-TM-AS-Result: No--30.296-10.0-31-10 X-imss-scan-details: No--30.296-10.0-31-10 X-TMASE-MatchedRID: fE0JoqABJp3W/bDrA6VrLVPjo7D4SFg4GSqdEmeD/nWna6U74e0+qDOK rPIVSxe23uE1tjZVXBZO6CI7rIh2itcUNjoF7YuVgFd2TFaysMh69Yesg60Qd5722hDqHosTj7V ue0RgT/UOqi00k0kR/al34qM4sYv4Nn8+CHTxhrYD2WXLXdz+AYKrWx24sNNz2qqh/6B8PpGd/n bmOv6MvIeJ9MGEI0MwEQfhcD1BvhGf8qK5CV5AhbdQIb8hCnY+CQ3xS+zL6e1Jg8sTT3RzF9oJb LBq7ybGoz8HTl+z1fZ/Lx6iMAc0GMjZGpIBeHfeQr2qXCJMSV8gIlfZcIw7oGmj1qXcLu1iaRnu wdqIKHtn7HNrvldMNtGLiYIi41Qmdi4y/Ho0/wAc8J6ZrWP/q30tCKdnhB58vqq8s2MNhPDPPeN 6HN6d7K85Gjho6PlWC24oEZ6SpSk+Mqg+CyrtwA== Archived-At: Cc: 'John Strassner' , l2sm@ietf.org, scott.mansfield@ericsson.com, stephan.pelletier@oracle.com, "'Ranganathan, Raghu'" , 'David Ball' Subject: Re: [L2sm] Request for an agenda slot 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: Sun, 06 Nov 2016 23:39:30 -0000 OK. I have already put Scott on the agenda for this, mainly because I had been talking with him off-line about the liaison communication. Question: can you work with Scott on this, or do you need separate time? There will also be scope for comments at the mic. Thanks, Adrian > -----Original Message----- > From: Mahesh Jethanandani [mailto:mjethanandani@gmail.com] > Sent: 06 November 2016 23:22 > To: Adrian Farell > Cc: l2sm@ietf.org; Ranganathan, Raghu; David Ball; John Strassner; > scott.mansfield@ericsson.com; stephan.pelletier@oracle.com > Subject: Re: [L2sm] Request for an agenda slot > > > > On Nov 3, 2016, at 10:47 PM, Adrian Farrel wrote: > > > > Hi Mahesh, > > > > You're keen! > > The WG was only formed less than two hours ago. Well, the announcement > hasn't > > even gone out :-) > > > > Anyway, what would you like to talk about? > > > > BTW... > > We have a 90 minute slot. Things we MUST cover include... > > - review of the charter > > - reminder of what a "customer service model" is > > - update on what the MEF forum has been doing and how we will share our > progress > > with them > > I would like to talk about the above item. You must have already received the > liaison statement sent by MEF. I would be happy to go over the work we have > already done in MEF, and understand what this WG would like to do that is not > already done by MEF. > > Thanks. > > > - overview of draft-wen-l2sm-l2vpn-service-model > > > > You can consider that our draft agenda. > > > > Cheers, > > Adrian > > -- > > Support an author and your imagination. > > Tales from the Wood - Eighteen new fairy tales. > > More Tales from the Wood - Eighteen MORE new fairy tales. > > https://www.feedaread.com/profiles/8604/ > > http://www.amazon.co.uk/Tales-Wood-Adrian-Farrel/dp/1786100924 > > Or buy from me direct. > > > > > > > > > >> -----Original Message----- > >> From: L2sm [mailto:l2sm-bounces@ietf.org] On Behalf Of Mahesh > Jethanandani > >> Sent: 03 November 2016 15:39 > >> To: l2sm@ietf.org > >> Subject: [L2sm] Request for an agenda slot > >> > >> I do not know whether an agenda slot request has been posted, but would > like > > to > >> request a 10 min slot to present. > >> > >> Thanks. > >> > >> Mahesh Jethanandani > >> mjethanandani@gmail.com > >> _______________________________________________ > >> L2sm mailing list > >> L2sm@ietf.org > >> https://www.ietf.org/mailman/listinfo/l2sm > > > > Mahesh Jethanandani > mjethanandani@gmail.com > From nobody Sun Nov 6 15:46:58 2016 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 5BCB612954F for ; Sun, 6 Nov 2016 15:46:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: 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, FREEMAIL_FROM=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 mjUghXZhJ6if for ; Sun, 6 Nov 2016 15:46:54 -0800 (PST) Received: from mail-pf0-x22c.google.com (mail-pf0-x22c.google.com [IPv6:2607:f8b0:400e:c00::22c]) (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 3A826129521 for ; Sun, 6 Nov 2016 15:46:54 -0800 (PST) Received: by mail-pf0-x22c.google.com with SMTP id 189so81347277pfz.3 for ; Sun, 06 Nov 2016 15:46:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=yGVcFSjrTY9WrltJtz+UAsbdHUXMw+JbP0Wl5w8XAlQ=; b=fzKX+uhOHnMzSWnX2KK4ahPNTTmrUNfHLjF+HxA09w9lUqBqvx4kjYfRraGzqbzA6A jRYMRsYErJCoSMo2GUay4S2A7v+e9gAaCG58Vy15/ySIWX2lVo6udazk6he6J0ywTpzL +Y4S2x9hgsfOiCxeFRL80TcRJ+R1k1254AazNCHxnRJZq6eyV4NdjJsV8sY0VqUMW3nI TwSyNvxrArO1m8/87wNj+diZmuooLhkfi1vHix7jhm4bVAzyaAx9bjO8nK4uRB44OC1w Ryrk3zx0QFmZBz4OmOElWMNBYQ0wCezkFlIJ4ej2wt0O3yC2mtXBHDBi85jf5I9x2QMc bJuQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=yGVcFSjrTY9WrltJtz+UAsbdHUXMw+JbP0Wl5w8XAlQ=; b=k9wnDBeA5m0XgVc1ZhvmZZVWWx1TzwJ4TMLrhEtJu9WK6iFjnYWkA18AdtR7kj+G8O JMwcKSrRpBhkMjM4rb08Pz9UyY3LcPdaHSJ32YWPUwiYjtrH/SgOrkXVGJiTha8NwhPv /rhuD9XEG8qS+QSPR0DZ4t+i25JIHAcmacIHVReM1pHxLrQmdiqFR77M396IJqVG7Qve PN5UWgm1Czl2HlW3AiD3WdSxofFiTJKHR/oVXnj+8ZIMn6PcZmkHErGpVGNRGZ0YLErG GfRAo2OWA37VXBAjattfMKpa8JreWsoSktIFIIRfJYmH0n2R6ChF/bREe6YxlsKwZaGy xDug== X-Gm-Message-State: ABUngvd5CykynXXAWR7Ily5f0Ss6eJ6MjMvJqYYuiwOA6O4KoO/FL1U6khaDMwSotnsvmQ== X-Received: by 10.99.159.17 with SMTP id g17mr6511498pge.149.1478476013775; Sun, 06 Nov 2016 15:46:53 -0800 (PST) Received: from [10.10.11.18] ([203.189.142.108]) by smtp.gmail.com with ESMTPSA id q28sm35110921pfj.73.2016.11.06.15.46.51 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sun, 06 Nov 2016 15:46:53 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) From: Mahesh Jethanandani In-Reply-To: <01d301d23886$fabf7470$f03e5d50$@olddog.co.uk> Date: Mon, 7 Nov 2016 06:46:48 +0700 Content-Transfer-Encoding: quoted-printable Message-Id: <03F5949B-AA5C-4965-BD25-590D15CC8446@gmail.com> References: <65B06CBB-28F8-49A8-9733-C31A3ECA8A58@gmail.com> <068401d235e9$9fc73390$df559ab0$@olddog.co.uk> <01d301d23886$fabf7470$f03e5d50$@olddog.co.uk> To: Adrian Farell X-Mailer: Apple Mail (2.3124) Archived-At: Cc: John Strassner , l2sm@ietf.org, scott.mansfield@ericsson.com, stephan.pelletier@oracle.com, "Ranganathan, Raghu" , David Ball Subject: Re: [L2sm] Request for an agenda slot 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: Sun, 06 Nov 2016 23:46:56 -0000 I will work with Scott. Thanks. > On Nov 7, 2016, at 6:39 AM, Adrian Farrel wrote: >=20 > OK. >=20 > I have already put Scott on the agenda for this, mainly because I had = been > talking with him off-line about the liaison communication. >=20 > Question: can you work with Scott on this, or do you need separate = time? There > will also be scope for comments at the mic. >=20 > Thanks, > Adrian >=20 >> -----Original Message----- >> From: Mahesh Jethanandani [mailto:mjethanandani@gmail.com] >> Sent: 06 November 2016 23:22 >> To: Adrian Farell >> Cc: l2sm@ietf.org; Ranganathan, Raghu; David Ball; John Strassner; >> scott.mansfield@ericsson.com; stephan.pelletier@oracle.com >> Subject: Re: [L2sm] Request for an agenda slot >>=20 >>=20 >>> On Nov 3, 2016, at 10:47 PM, Adrian Farrel = wrote: >>>=20 >>> Hi Mahesh, >>>=20 >>> You're keen! >>> The WG was only formed less than two hours ago. Well, the = announcement >> hasn't >>> even gone out :-) >>>=20 >>> Anyway, what would you like to talk about? >>>=20 >>> BTW... >>> We have a 90 minute slot. Things we MUST cover include... >>> - review of the charter >>> - reminder of what a "customer service model" is >>> - update on what the MEF forum has been doing and how we will share = our >> progress >>> with them >>=20 >> I would like to talk about the above item. You must have already = received the >> liaison statement sent by MEF. I would be happy to go over the work = we have >> already done in MEF, and understand what this WG would like to do = that is not >> already done by MEF. >>=20 >> Thanks. >>=20 >>> - overview of draft-wen-l2sm-l2vpn-service-model >>>=20 >>> You can consider that our draft agenda. >>>=20 >>> Cheers, >>> Adrian >>> -- >>> Support an author and your imagination. >>> Tales from the Wood - Eighteen new fairy tales. >>> More Tales from the Wood - Eighteen MORE new fairy tales. >>> https://www.feedaread.com/profiles/8604/ >>> http://www.amazon.co.uk/Tales-Wood-Adrian-Farrel/dp/1786100924 >>> Or buy from me direct. >>>=20 >>>=20 >>>=20 >>>=20 >>>> -----Original Message----- >>>> From: L2sm [mailto:l2sm-bounces@ietf.org] On Behalf Of Mahesh >> Jethanandani >>>> Sent: 03 November 2016 15:39 >>>> To: l2sm@ietf.org >>>> Subject: [L2sm] Request for an agenda slot >>>>=20 >>>> I do not know whether an agenda slot request has been posted, but = would >> like >>> to >>>> request a 10 min slot to present. >>>>=20 >>>> Thanks. >>>>=20 >>>> Mahesh Jethanandani >>>> mjethanandani@gmail.com >>>> _______________________________________________ >>>> L2sm mailing list >>>> L2sm@ietf.org >>>> https://www.ietf.org/mailman/listinfo/l2sm >>>=20 >>=20 >> Mahesh Jethanandani >> mjethanandani@gmail.com >>=20 >=20 >=20 Mahesh Jethanandani mjethanandani@gmail.com From nobody Wed Nov 16 17:50:37 2016 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 5751C129627 for ; Wed, 16 Nov 2016 17:50:21 -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 2B6oLeCNuZOp for ; Wed, 16 Nov 2016 17:50:19 -0800 (PST) Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D593129478 for ; Wed, 16 Nov 2016 17:50:19 -0800 (PST) Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id uAH1oGeA032430 for ; Thu, 17 Nov 2016 01:50:16 GMT Received: from 950129200 (dhcp-8717.meeting.ietf.org [31.133.135.23]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id uAH1oC5k032416 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for ; Thu, 17 Nov 2016 01:50:15 GMT From: "Adrian Farrel" To: Date: Thu, 17 Nov 2016 01:50:11 -0000 Message-ID: <092601d24074$f0a40230$d1ec0690$@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: AdJAdOwHxn/mPPqOTZ60iHj+kJtYcg== Content-Language: en-gb X-TM-AS-MML: disable X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.0.0.1202-22704.004 X-TM-AS-Result: No--7.033-10.0-31-10 X-imss-scan-details: No--7.033-10.0-31-10 X-TMASE-MatchedRID: 9KhQTl9YfS9R6DT7jy4uvam4PbloS2C3+KgiyLtJrSDLuEdMBn2IDBch drJv3xSnQg7ami9Nm5ToCQmdfigNPnojljdZUlWjtT4jIeGRd/VBldmDYjwlpijPntpmZSbDk1F e0KkV71PQVt5FSA+AZ5Zh+q4adi+mGAdnzrnkM485f9Xw/xqKXdivpTdmVCR22bNx1HEv7HAqtq 5d3cxkNRME7z1CCNiPw76LMAJE07u0XMCOh6R71LgcO/s7mXpz6KibADJHm1DAvpLE+mvX8g== Archived-At: Subject: [L2sm] The I-D we mentioned that discussed "service models" 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: Thu, 17 Nov 2016 01:50:21 -0000 Hi, Benoit pointed our discussion of "what is a service model" to: - The OPSAWG mailing list - https://datatracker.ietf.org/doc/draft-wu-opsawg-service-model-explained/ Noting that this is not an OPSAWG draft at the moment, but that there was (apparently) some support for working on it when it was presented in the OPSAWG meeting this week. See also the slides for that presentation at https://www.ietf.org/proceedings/97/slides/slides-97-opsawg-service-model-explai ned-00.pdf I think what Benoit means is "Please have the discussion in OPSAWG so that we can reach an Area-wide decision and then apply it to L2SM." Thanks, Adrian From nobody Wed Nov 16 18:01:01 2016 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 A8B1C1293D8; Wed, 16 Nov 2016 18:00:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.718 X-Spam-Level: X-Spam-Status: No, score=-5.718 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.497, SPF_PASS=-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 6iXTVazSbqlp; Wed, 16 Nov 2016 18:00:54 -0800 (PST) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E52541293F9; Wed, 16 Nov 2016 18:00:53 -0800 (PST) Received: from 172.18.7.190 (EHLO lhreml703-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DAR45425; Thu, 17 Nov 2016 02:00:51 +0000 (GMT) Received: from NKGEML413-HUB.china.huawei.com (10.98.56.74) by lhreml703-cah.china.huawei.com (10.201.5.104) with Microsoft SMTP Server (TLS) id 14.3.235.1; Thu, 17 Nov 2016 02:00:51 +0000 Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by NKGEML413-HUB.china.huawei.com ([10.98.56.74]) with mapi id 14.03.0235.001; Thu, 17 Nov 2016 10:00:45 +0800 From: Zhoutianran To: "adrian@olddog.co.uk" , "l2sm@ietf.org" Thread-Topic: [L2sm] The I-D we mentioned that discussed "service models" Thread-Index: AdJAdOwHxn/mPPqOTZ60iHj+kJtYcgAAIk0Y Date: Thu, 17 Nov 2016 02:00:45 +0000 Message-ID: References: <092601d24074$f0a40230$d1ec0690$@olddog.co.uk> In-Reply-To: <092601d24074$f0a40230$d1ec0690$@olddog.co.uk> Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.47.112.153] Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020205.582D0F54.0051, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: d9dfe5c3556fbf20bf8bcd39f8ebe296 Archived-At: Cc: "opsawg@ietf.org" Subject: [L2sm] FW: The I-D we mentioned that discussed "service models" 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: Thu, 17 Nov 2016 02:00:56 -0000 WWVzLiBJIGFtIHNpdHRpbmcgaW4gdGhlIEwyU00gbWVldGluZyByb29tLCBhbmQgaGVhcmQgbWFu eSBkaXNjdXNzaW9ucyBhYm91dCB0aGUgdGVybWlub2xvZ3kgd3J0IHRoZSBzZXJ2aWNlIG1vZGVs LiANCk9idmlvdXNseSwgdGhvc2UgdGVybXMgYW5kIGRlZmluaXRpb25zIGFyZSBjb25mdXNpb24s IGJ1dCBpbXBvcnRhbnQgYW5kIG5lZWQgd2lkZWx5IGRpc2N1c3NlZC4NClBsZWFzZSBjb21lIHRv IHRoZSBvcHNhd2cgbWFpbGluZyBsaXN0LCBhbmQgaGVscCB0aGUgYXV0aG9ycyB0byBpbXByb3Zl IHRoZSBkb2N1bWVudC4NCg0KQmVzdCwNClRpYW5yYW4NCg0KX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fXw0Kt6K8/sjLOiBMMnNtIFtsMnNtLWJvdW5jZXNAaWV0Zi5vcmdd ILT6se0gQWRyaWFuIEZhcnJlbCBbYWRyaWFuQG9sZGRvZy5jby51a10NCreiy83KsbzkOiAyMDE2 xOoxMdTCMTfI1SA5OjUwDQrK1bz+yMs6IGwyc21AaWV0Zi5vcmcNCtb3zOI6IFtMMnNtXSBUaGUg SS1EIHdlIG1lbnRpb25lZCB0aGF0IGRpc2N1c3NlZCAic2VydmljZSBtb2RlbHMiDQoNCkhpLA0K DQpCZW5vaXQgcG9pbnRlZCBvdXIgZGlzY3Vzc2lvbiBvZiAid2hhdCBpcyBhIHNlcnZpY2UgbW9k ZWwiIHRvOg0KLSBUaGUgT1BTQVdHIG1haWxpbmcgbGlzdA0KLSBodHRwczovL2RhdGF0cmFja2Vy LmlldGYub3JnL2RvYy9kcmFmdC13dS1vcHNhd2ctc2VydmljZS1tb2RlbC1leHBsYWluZWQvDQoN Ck5vdGluZyB0aGF0IHRoaXMgaXMgbm90IGFuIE9QU0FXRyBkcmFmdCBhdCB0aGUgbW9tZW50LCBi dXQgdGhhdCB0aGVyZSB3YXMNCihhcHBhcmVudGx5KSBzb21lIHN1cHBvcnQgZm9yIHdvcmtpbmcg b24gaXQgd2hlbiBpdCB3YXMgcHJlc2VudGVkIGluIHRoZSBPUFNBV0cNCm1lZXRpbmcgdGhpcyB3 ZWVrLg0KDQpTZWUgYWxzbyB0aGUgc2xpZGVzIGZvciB0aGF0IHByZXNlbnRhdGlvbiBhdA0KaHR0 cHM6Ly93d3cuaWV0Zi5vcmcvcHJvY2VlZGluZ3MvOTcvc2xpZGVzL3NsaWRlcy05Ny1vcHNhd2ct c2VydmljZS1tb2RlbC1leHBsYWkNCm5lZC0wMC5wZGYNCg0KSSB0aGluayB3aGF0IEJlbm9pdCBt ZWFucyBpcyAiUGxlYXNlIGhhdmUgdGhlIGRpc2N1c3Npb24gaW4gT1BTQVdHIHNvIHRoYXQgd2UN CmNhbiByZWFjaCBhbiBBcmVhLXdpZGUgZGVjaXNpb24gYW5kIHRoZW4gYXBwbHkgaXQgdG8gTDJT TS4iDQoNClRoYW5rcywNCkFkcmlhbg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fXw0KTDJzbSBtYWlsaW5nIGxpc3QNCkwyc21AaWV0Zi5vcmcNCmh0dHBz Oi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbDJzbQ== From nobody Thu Nov 17 16:26:28 2016 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 D48001294FF for ; Thu, 17 Nov 2016 16:26:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.721 X-Spam-Level: X-Spam-Status: No, score=-0.721 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, 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 VwBXURcCUwvV for ; Thu, 17 Nov 2016 16:26:25 -0800 (PST) Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F14A12959C for ; Thu, 17 Nov 2016 16:26:24 -0800 (PST) Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id uAI0QMOF004752 for ; Fri, 18 Nov 2016 00:26:22 GMT Received: from 950129200 (dhcp-885c.meeting.ietf.org [31.133.136.92]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id uAI0QJdf004698 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for ; Fri, 18 Nov 2016 00:26:21 GMT From: "Adrian Farrel" To: Date: Fri, 18 Nov 2016 00:26:17 -0000 Message-ID: <0d4501d24132$62ceb590$286c20b0$@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: AdJBMl9LkbuTL93GR8uhCc0ETwHqcw== Content-Language: en-gb X-TM-AS-MML: disable X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.0.0.1202-22706.003 X-TM-AS-Result: No--2.074-10.0-31-10 X-imss-scan-details: No--2.074-10.0-31-10 X-TMASE-MatchedRID: 15LlVZSTLD3rqihpsG2+NFu4M/xm4KZeKx5ICGp/WtEGgDV8o5u6E5UG jQVyKb6/ZkfRt8PnKSOmUYrrr7uKPeClVqpL2c7Qb8JTZf0kEzs6En2bnefhoItoPF88Qg37f32 kZnGEZ9wvotHzb3LJBaf+ArRCQiv/3CtEsOTZxuLmAId+2bAQwn0tCKdnhB58vqq8s2MNhPB9j2 GwzTE3vSq2rl3dzGQ1Frkn+1l2s1VXHXGqNHTqg+jPF/BpG47AEkeiWvfxtD3B9JIL0Q6K51sc5 LctGMWNUFbtMJ748tQ0yFypOTFNh8oRstJ4jyWiz50AY+Tfm+evcsTuUejg0omQ2vqumwAFVUH8 5vIcwrl2A/3Nl4P8kQ== Archived-At: Subject: [L2sm] Adoption poll for draft-wen-l2sm-l2vpn-service-model-03.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: Fri, 18 Nov 2016 00:26:27 -0000 Hi, Our charter mandates that we consider basing our work on draft-wen-l2sm-l2vpn-service-model-03.txt As we discussed in the meeting, that draft is not perfect. But when I asked the room whether we thought that it would provide a good starting point that we could work with to polish and adapt to become the I-D that we ultimately submit for publication as an RFC, I believe I heard a good hum in favour and silence in opposition. So this email starts a formal poll for adoption. Please answer: Do you think that the WG should adopt draft-wen-l2sm-l2vpn-service-model-03.txt? If "yes," it would help if you could indicate whether you have read the draft and how happy you are with it. If "no", it is important that you provide reasons. This poll will last for two weeks, ending on Saturday 3rd December. Just to reassure everyone that adoption does not imply that anything is set in stone: we expect the WG to continue to develop the content and change whatever needs to be changed. Thanks, Adrian and Qin From nobody Thu Nov 17 17:22:18 2016 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 CF0C4128E18 for ; Thu, 17 Nov 2016 17:22:16 -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 4afVFUGxbpsA for ; Thu, 17 Nov 2016 17:22:15 -0800 (PST) Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93A6B126579 for ; Thu, 17 Nov 2016 17:22:15 -0800 (PST) Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id uAI1MCa2008525 for ; Fri, 18 Nov 2016 01:22:13 GMT Received: from 950129200 (dhcp-885c.meeting.ietf.org [31.133.136.92]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id uAI1M97P008513 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for ; Fri, 18 Nov 2016 01:22:12 GMT From: "Adrian Farrel" To: Date: Fri, 18 Nov 2016 01:22:07 -0000 Message-ID: <0d6801d2413a$2fa6e0e0$8ef4a2a0$@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: AdJBOhBIlyfjMEmNRC2INN5CcvGuTQ== Content-Language: en-gb X-TM-AS-MML: disable X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.0.0.1202-22706.004 X-TM-AS-Result: No--2.539-10.0-31-10 X-imss-scan-details: No--2.539-10.0-31-10 X-TMASE-MatchedRID: hLCpkDKaeHYR9y8WJPyXEBJEh4A6+HuFYu7s3QSSN+T2nE4Y4IcpXG8A 97SYsaq8iCMyfrGuZhdpykTUaVN5S5DQGJm7p8JD/c0+LJTMrN1oFNaNcVdd3wpcq1+LTpsUo8W MkQWv6iV95l0nVeyiuBQF+BLVItD4C24oEZ6SpSmcfuxsiY4QFBcNsK3MAovEJOsMB+uQ9VP7AG hGO8MhdODCRKrdUZ3hh6E8FGha9eoRxZ5k5S3drrgrpCiF0ClCAr3gsUencER7BAT9a9xCDfR5g LDNdb9LuOZoyiCGGN8YgmnfWgSln5vaf0QvfUyeS4W/MRhJ1X4= Archived-At: Subject: [L2sm] Opinions on issue tracker for L2SM please 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: Fri, 18 Nov 2016 01:22:17 -0000 Hi, During the development of the current draft, the authors used issues tracked in github using an old (and possibly inappropriate user ID) at https://github.com/alreadytiredofnomcom/L2SMissues/issues This worked "somewhat" depending on which authors had access to github. We have a three-way choice, IMHO: 1. just continue that issue tracker in github 2. stay in github but move to a better account 3. move issue tracking into the IETF using IETF tools Does anyone have an opinion? Thanks, Adrian From nobody Fri Nov 18 02:32:21 2016 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 95EF51295A0 for ; Fri, 18 Nov 2016 02:32:20 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -16.019 X-Spam-Level: X-Spam-Status: No, score=-16.019 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.497, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 r-6SuhnJaEwo for ; Fri, 18 Nov 2016 02:32:19 -0800 (PST) Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9AE7C129501 for ; Fri, 18 Nov 2016 02:32:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1967; q=dns/txt; s=iport; t=1479465138; x=1480674738; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=t8jP2bvlshMDhxKWzQMRXw+E2ljgFcIr4NAAluNTRPw=; b=TmrZrG599UIkB4f73N91nwyLW1j9iFX8W5xoAdagipVn0LP+vV3SWYq5 fkwwlUJpDGPyFPW44WTqeYfhtgu70z9ZtpJt/J+6advm97oK4OeJ3LWMw Q3KOBYz/OYquSfPrxtwlKIr/HqjDFlx66KLbfqnpNQdqQM3xHMAraK4j1 E=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DOAQCM1y5Y/xbLJq1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgzcBAQEBAXcsVI0/lxCUZoIHHQuFeQKCWRQBAgEBAQEBAQFiKIR?= =?us-ascii?q?pAQEEAQEBNTYbCxguJzAHDAYCAQGIaA6uH4tUAQEBAQEFAQEBAQEBHAWGPIF9C?= =?us-ascii?q?IJVhBsRAYV9AQSaSIkLh2eBcIR3gxwjhgGJeINghAseN10REQwdhSE+NIYdgi0?= =?us-ascii?q?BAQE?= X-IronPort-AV: E=Sophos;i="5.31,509,1473120000"; d="scan'208";a="648206031" Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Nov 2016 10:32:16 +0000 Received: from [10.63.23.90] (dhcp-ensft1-uk-vla370-10-63-23-90.cisco.com [10.63.23.90]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id uAIAWGQu019138; Fri, 18 Nov 2016 10:32:16 GMT To: adrian@olddog.co.uk, l2sm@ietf.org References: <0d4501d24132$62ceb590$286c20b0$@olddog.co.uk> From: David Ball Message-ID: Date: Fri, 18 Nov 2016 10:32:16 +0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <0d4501d24132$62ceb590$286c20b0$@olddog.co.uk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [L2sm] Adoption poll for draft-wen-l2sm-l2vpn-service-model-03.txt 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: Fri, 18 Nov 2016 10:32:20 -0000 I do not believe that draft is a good basis for L2SM work as is - much of the content pertains to information that is internal to the SP's network and implementation of the service, rather than what is relevant to the customer of the service. Such content does not belong in a customer service model (which is what L2SM is chartered to develop). In addition the draft is not well aligned with MEF specifications. I have given further feedback to the authors of the draft offline, including asking them to clarify the intent of their draft. To date I have had assurances from Adrian but no response from the authors. David On 18/11/2016 00:26, Adrian Farrel wrote: > Hi, > > Our charter mandates that we consider basing our work on > draft-wen-l2sm-l2vpn-service-model-03.txt > > As we discussed in the meeting, that draft is not perfect. But when I asked the > room whether we thought that it would provide a good starting point that we > could work with to polish and adapt to become the I-D that we ultimately submit > for publication as an RFC, I believe I heard a good hum in favour and silence in > opposition. > > So this email starts a formal poll for adoption. Please answer: > > Do you think that the WG should adopt draft-wen-l2sm-l2vpn-service-model-03.txt? > > If "yes," it would help if you could indicate whether you have read the draft > and how happy you are with it. > If "no", it is important that you provide reasons. > > This poll will last for two weeks, ending on Saturday 3rd December. > > Just to reassure everyone that adoption does not imply that anything is set in > stone: we expect the WG to continue to develop the content and change whatever > needs to be changed. > > Thanks, > Adrian and Qin > > _______________________________________________ > L2sm mailing list > L2sm@ietf.org > https://www.ietf.org/mailman/listinfo/l2sm -- David Ball From nobody Fri Nov 18 06:25:28 2016 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 E7AD312944D for ; Fri, 18 Nov 2016 06:25:26 -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 Pdm4ShHTgcyY for ; Fri, 18 Nov 2016 06:25:25 -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 9F1EF12941C for ; Fri, 18 Nov 2016 06:25:24 -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 uAIEPJJB001671; Fri, 18 Nov 2016 14:25:19 GMT Received: from 950129200 ([58.120.104.2]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id uAIEPFSN001510 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Fri, 18 Nov 2016 14:25:18 GMT From: "Adrian Farrel" To: "'David Ball'" , References: <0d4501d24132$62ceb590$286c20b0$@olddog.co.uk> In-Reply-To: Date: Fri, 18 Nov 2016 14:25:12 -0000 Message-ID: <0f1f01d241a7$959b1c00$c0d15400$@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: AQKr5J3krbFM/YS1TonUwzHGXgh46QJyHoO4nxfoDOA= Content-Language: en-gb X-TM-AS-MML: disable X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.0.0.1202-22706.007 X-TM-AS-Result: No--30.354-10.0-31-10 X-imss-scan-details: No--30.354-10.0-31-10 X-TMASE-MatchedRID: nI1cAR4k0HZwyAmzxb7Z08WUKBjERoYTbv16+gil4jecpGufbGiAqLsI asnPqvyQd24Rguv/KKI3vYlaZwwyvdPYURkTpZRibBu6+EIezdzS+VqQO/GHvMi9AjK6C8p1fyQ W2LN7ubFtK35dXf54/2AEpbtQJ9CedYq+JDDD9d51fPeXvwXdieiY+s2L3xQEauHKE5Laxl/S4n ZpaTqEVhZoMlHjnT1RGNuEWCXlYde2eMRDvAoUtRHRbGr1ECgHI5K4Cd+0ao9BRe0Gd+ZWd5iF9 1oJeq4SWxwLlsLfqJjxTwx4UJIMcgHu7QwNULrhgFd2TFaysMgZskwWqoib3ARixCz2NMPb8eqZ Vr8C7tXT1jRavQ81vcb1hFT4R4iE932fm8yB1Z4mtTGirqG/D34yToAKzDgmuu0N7j6PSiOQoxD k18vskQLsIFHWD2ZFddFy8k5Fp0PMy6K24fisq691/YHX0i1l9wGZvWYZl5eNhQy64yjQD1i8QT zWbO3PgTWj4N8Xhb2WEHRkALXtipj50ewQ/8wVFqNNeSB7ZZBimi8LvNfmr8naL1ri/ilX2zUIf ORoaiIRW3Fo+hK3sB5hmP6OM/PJTX7PJ/OU3vL+xOhjarOnHrHlqZYrZqdI+gtHj7OwNO0CpgET eT0ynA== Archived-At: Subject: Re: [L2sm] Adoption poll for draft-wen-l2sm-l2vpn-service-model-03.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: Fri, 18 Nov 2016 14:25:27 -0000 Hi David, A similar question about the amount of protocol or network implementation details in the model was raised a couple of times at the mic in the meeting. IIRC it was Himanshu who offered to take a pass on the document to try to list those excessive objects. But I think there are several categories that we need to consider. 1. Those parameters that described the CE-PE link in a PE-mode VPN. These can be presented per-service or per-link. They are a necessary part of the service specification and cannot be omitted, I believe. 2. Those parameters that describe behaviors within the network. As I understand it, these fall into two sub-categories: a. Parameters that don't belong in a truly abstract description of the service, but which customers habitually request the ability to specify and which the service providers habitually offer. I think we will need to have support for these because we are aiming for a model that will see support and deployment at once, as (obviously) this is not an academic exercise. b. Parameter that are a "step to far" and which should be removed. Determining the balance between these categories will probably require some discussion. But let's quickly jump from that discussion to try to understand the way forward you would like to see. Clearly you think changes to the document are needed and it sounds like everyone agrees that that is true. And that sounds (to me) like you believe we have a document we can work with to serve as a basis for updates. What isn't obvious to me is why you don't think that the working group should have control of this discussion and the changes to the document. What do you propose? Thanks, Adrian > -----Original Message----- > From: David Ball [mailto:daviball@cisco.com] > Sent: 18 November 2016 10:32 > To: adrian@olddog.co.uk; l2sm@ietf.org > Subject: Re: [L2sm] Adoption poll for draft-wen-l2sm-l2vpn-service-model-03.txt > > I do not believe that draft is a good basis for L2SM work as is - much > of the content pertains to information that is internal to the SP's > network and implementation of the service, rather than what is relevant > to the customer of the service. Such content does not belong in a > customer service model (which is what L2SM is chartered to develop). In > addition the draft is not well aligned with MEF specifications. > > I have given further feedback to the authors of the draft offline, > including asking them to clarify the intent of their draft. To date I > have had assurances from Adrian but no response from the authors. > > > David > > > On 18/11/2016 00:26, Adrian Farrel wrote: > > Hi, > > > > Our charter mandates that we consider basing our work on > > draft-wen-l2sm-l2vpn-service-model-03.txt > > > > As we discussed in the meeting, that draft is not perfect. But when I asked the > > room whether we thought that it would provide a good starting point that we > > could work with to polish and adapt to become the I-D that we ultimately > submit > > for publication as an RFC, I believe I heard a good hum in favour and silence in > > opposition. > > > > So this email starts a formal poll for adoption. Please answer: > > > > Do you think that the WG should adopt draft-wen-l2sm-l2vpn-service-model- > 03.txt? > > > > If "yes," it would help if you could indicate whether you have read the draft > > and how happy you are with it. > > If "no", it is important that you provide reasons. > > > > This poll will last for two weeks, ending on Saturday 3rd December. > > > > Just to reassure everyone that adoption does not imply that anything is set in > > stone: we expect the WG to continue to develop the content and change > whatever > > needs to be changed. > > > > Thanks, > > Adrian and Qin > > > > _______________________________________________ > > L2sm mailing list > > L2sm@ietf.org > > https://www.ietf.org/mailman/listinfo/l2sm > > -- > David Ball > From nobody Mon Nov 21 01:38:21 2016 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 8404F129953 for ; Mon, 21 Nov 2016 01:38:19 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -16.018 X-Spam-Level: X-Spam-Status: No, score=-16.018 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.497, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 cHDbn3q5XkkE for ; Mon, 21 Nov 2016 01:38:18 -0800 (PST) Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F9861298C1 for ; Mon, 21 Nov 2016 01:38:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3690; q=dns/txt; s=iport; t=1479721097; x=1480930697; h=from:subject:to:references:message-id:date:mime-version: in-reply-to; bh=ere3yur1KhIeXuu7fAuhyZH5yp1MWKskO5dnJll+f2o=; b=SasvqFoXAfdQqDuNBWUpf1CmS21eVxLr1bLxbJWbimQH98A7TKpWIiKc 0pdnrCOFBCnzC80XkMDUQuc2sEghAX5/WdWIzN3eptagmBPBIyJf0z5/I 9hpfGHNQZJ5Nfb6koqBKhIShJyzTqyuVS9Psp2LjDavLMVjWATeh9xiM7 o=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AKAgAjwDJY/xbLJq1cGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBgzgBAQEBAYEjVI0/lxCPT4UfggWGIQKCSBQBAgEBAQEBAQFiKIRpAQE?= =?us-ascii?q?EgQkLBBQuVwcMBgIBAYhprCIvixwBAQEBAQUBAQEBAQEBIIY8gX2CXYoqBZpNk?= =?us-ascii?q?HeKA4YkiX+DYIQLHjdzEwyFQT40iDwBAQE?= X-IronPort-AV: E=Sophos;i="5.31,674,1473120000"; d="scan'208,217";a="650091160" Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Nov 2016 09:38:15 +0000 Received: from [10.63.23.90] (dhcp-ensft1-uk-vla370-10-63-23-90.cisco.com [10.63.23.90]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id uAL9cFpe028606; Mon, 21 Nov 2016 09:38:15 GMT From: David Ball To: adrian@olddog.co.uk, l2sm@ietf.org References: <0d4501d24132$62ceb590$286c20b0$@olddog.co.uk> <0f1f01d241a7$959b1c00$c0d15400$@olddog.co.uk> Message-ID: <1a94d940-9cce-26c9-be2e-a5ac5fd93acf@cisco.com> Date: Mon, 21 Nov 2016 09:38:15 +0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <0f1f01d241a7$959b1c00$c0d15400$@olddog.co.uk> Content-Type: multipart/alternative; boundary="------------437C3C626A9910E3329A56B6" Archived-At: Subject: Re: [L2sm] Adoption poll for draft-wen-l2sm-l2vpn-service-model-03.txt 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: Mon, 21 Nov 2016 09:38:19 -0000 This is a multi-part message in MIME format. --------------437C3C626A9910E3329A56B6 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Hi Adrian, On 18/11/2016 14:25, Adrian Farrel wrote: > But let's quickly jump from that discussion to try to understand the way forward > you would like to see. Clearly you think changes to the document are needed and > it sounds like everyone agrees that that is true. And that sounds (to me) like > you believe we have a document we can work with to serve as a basis for updates. > What isn't obvious to me is why you don't think that the working group should > have control of this discussion and the changes to the document. What do you > propose? Fundamentally, given the amount of work needed on this document, it's not clear to me that taking it as a basis for the WG work is the least-effort option; we should as a minimum consider alternatives - e.g. starting from scratch, or using the MEF modules as a basis (I believe MEF have recently liaised their in-progress work to IETF). I also really would like to hear from the authors - their document may be useful in its own right (just not aligned with the WG charter), so it may be that they want to proceed with it in that direction, as an individual draft. Of course that doesn't stop the WG "forking" it, but one might imagine the authors would be less inclined to participate in the WG in that case. David -- David Ball --------------437C3C626A9910E3329A56B6 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 8bit

Hi Adrian,

On 18/11/2016 14:25, Adrian Farrel wrote:
But let's quickly jump from that discussion to try to understand the way forward
you would like to see. Clearly you think changes to the document are needed and
it sounds like everyone agrees that that is true. And that sounds (to me) like
you believe we have a document we can work with to serve as a basis for updates.
What isn't obvious to me is why you don't think that the working group should
have control of this discussion and the changes to the document. What do you
propose?

Fundamentally, given the amount of work needed on this document, it's not clear to me that taking it as a basis for the WG work is the least-effort option; we should as a minimum consider alternatives - e.g. starting from scratch, or using the MEF modules as a basis (I believe MEF have recently liaised their in-progress work to IETF).

I also really would like to hear from the authors - their document may be useful in its own right (just not aligned with the WG charter), so it may be that they want to proceed with it in that direction, as an individual draft.  Of course that doesn't stop the WG "forking" it, but one might imagine the authors would be less inclined to participate in the WG in that case.


    David


-- 
David Ball
<daviball@cisco.com>
--------------437C3C626A9910E3329A56B6-- From nobody Mon Nov 21 17:58:27 2016 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 470A1129416 for ; Mon, 21 Nov 2016 17:58:25 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.718 X-Spam-Level: X-Spam-Status: No, score=-5.718 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.497, SPF_PASS=-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 bTyRdO29YuWz for ; Mon, 21 Nov 2016 17:58:23 -0800 (PST) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7918126D73 for ; Mon, 21 Nov 2016 17:58:22 -0800 (PST) Received: from 172.18.7.190 (EHLO lhreml707-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DBC48852; Tue, 22 Nov 2016 01:58:20 +0000 (GMT) Received: from NKGEML413-HUB.china.huawei.com (10.98.56.74) by lhreml707-cah.china.huawei.com (10.201.5.199) with Microsoft SMTP Server (TLS) id 14.3.235.1; Tue, 22 Nov 2016 01:58:19 +0000 Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.151]) by NKGEML413-HUB.china.huawei.com ([10.98.56.74]) with mapi id 14.03.0235.001; Tue, 22 Nov 2016 09:58:14 +0800 From: Qin Wu To: "adrian@olddog.co.uk" , "l2sm@ietf.org" Thread-Topic: [L2sm] Opinions on issue tracker for L2SM please Thread-Index: AdJBOhBIlyfjMEmNRC2INN5CcvGuTQDKW1vA Date: Tue, 22 Nov 2016 01:58:14 +0000 Message-ID: References: <0d6801d2413a$2fa6e0e0$8ef4a2a0$@olddog.co.uk> In-Reply-To: <0d6801d2413a$2fa6e0e0$8ef4a2a0$@olddog.co.uk> Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.136.78.218] Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020205.5833A63D.0053, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.1.151, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: a1a5206490bfbd0921c87abbada6c7b2 Archived-At: Subject: Re: [L2sm] Opinions on issue tracker for L2SM please 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: Tue, 22 Nov 2016 01:58:26 -0000 TWFpbnRhaW5pbmcgTDJTTWlzc3VlIGluIGJvdGggZ2l0aHViIGFuZCBJRVRGIGlzc3VlIHRyYWNr ZXIgcmVxdWlyZXMgc3luY3VwIGJldHdlZW4gdGhlbS4NCkkgcHJlZmVyIHRvIHVzZSBJRVRGIHRv b2wgdG8ga2VlcCB0cmFjayBvZiB0aGVzZSBvcGVuIGlzc3Vlcy4NCg0KLVFpbg0KLS0tLS3Tyrz+ 1K28/i0tLS0tDQq3orz+yMs6IEwyc20gW21haWx0bzpsMnNtLWJvdW5jZXNAaWV0Zi5vcmddILT6 se0gQWRyaWFuIEZhcnJlbA0Kt6LLzcqxvOQ6IDIwMTbE6jEx1MIxOMjVIDk6MjINCsrVvP7Iyzog bDJzbUBpZXRmLm9yZw0K1vfM4jogW0wyc21dIE9waW5pb25zIG9uIGlzc3VlIHRyYWNrZXIgZm9y IEwyU00gcGxlYXNlDQoNCkhpLA0KDQpEdXJpbmcgdGhlIGRldmVsb3BtZW50IG9mIHRoZSBjdXJy ZW50IGRyYWZ0LCB0aGUgYXV0aG9ycyB1c2VkIGlzc3VlcyB0cmFja2VkIGluIGdpdGh1YiB1c2lu ZyBhbiBvbGQgKGFuZCBwb3NzaWJseSBpbmFwcHJvcHJpYXRlIHVzZXIgSUQpIGF0IGh0dHBzOi8v Z2l0aHViLmNvbS9hbHJlYWR5dGlyZWRvZm5vbWNvbS9MMlNNaXNzdWVzL2lzc3VlcyAgVGhpcyB3 b3JrZWQgInNvbWV3aGF0IiBkZXBlbmRpbmcgb24gd2hpY2ggYXV0aG9ycyBoYWQgYWNjZXNzIHRv IGdpdGh1Yi4NCg0KV2UgaGF2ZSBhIHRocmVlLXdheSBjaG9pY2UsIElNSE86DQoNCjEuIGp1c3Qg Y29udGludWUgdGhhdCBpc3N1ZSB0cmFja2VyIGluIGdpdGh1YiAyLiBzdGF5IGluIGdpdGh1YiBi dXQgbW92ZSB0byBhIGJldHRlciBhY2NvdW50IDMuIG1vdmUgaXNzdWUgdHJhY2tpbmcgaW50byB0 aGUgSUVURiB1c2luZyBJRVRGIHRvb2xzDQoNCkRvZXMgYW55b25lIGhhdmUgYW4gb3Bpbmlvbj8N Cg0KVGhhbmtzLA0KQWRyaWFuDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fDQpMMnNtIG1haWxpbmcgbGlzdA0KTDJzbUBpZXRmLm9yZw0KaHR0cHM6Ly93 d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9sMnNtDQo= From nobody Mon Nov 21 19:36:00 2016 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 DC45712946E for ; Mon, 21 Nov 2016 19:35:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.019 X-Spam-Level: X-Spam-Status: No, score=-2.019 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_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=outlook.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 aVTUhnypGzLQ for ; Mon, 21 Nov 2016 19:35:56 -0800 (PST) Received: from BAY004-OMC4S9.hotmail.com (bay004-omc4s9.hotmail.com [65.54.190.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54CD7129429 for ; Mon, 21 Nov 2016 19:35:56 -0800 (PST) Received: from APC01-HK2-obe.outbound.protection.outlook.com ([65.54.190.199]) by BAY004-OMC4S9.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Mon, 21 Nov 2016 19:35:56 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=yCpO9jQOgUV23wjyx1ZVFgkUTXpEJbcIqbNVcr6KdDs=; b=awJ+befx2p+k43idztUckFojR8y+LH7O4kal4RkZIMr5/3NUgQlLsBtZKIjJQXw8AnESjw3yotyy8bzRuLYJLMo62u32KbAUybd+TqExqSv4o+3h3f7QRxS8Cgrg/j0auj555ERn/h763eE0BK+mKqexl2IM6snXPSCcp4p/phQkdSYZKMl1Vlv1bcVTDKP0bw8lXyOWeobZfepH+eKlf3oHXiJvwaHqculQ/rzrEqSs9N8uuoY74Hi8QOcOaVg9a0lX7zO1NKT48ddY6tlHiOKYuB9RzxEGJiJUGbixJaXzf9IrEQCNcqNT1paSCm55fUAiLtO8meX5QnZp4wcv4Q== Received: from HK2APC01FT020.eop-APC01.prod.protection.outlook.com (10.152.248.54) by HK2APC01HT032.eop-APC01.prod.protection.outlook.com (10.152.249.30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.721.5; Tue, 22 Nov 2016 03:35:46 +0000 Received: from KL1PR0201MB1656.apcprd02.prod.outlook.com (10.152.248.57) by HK2APC01FT020.mail.protection.outlook.com (10.152.248.186) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.721.5 via Frontend Transport; Tue, 22 Nov 2016 03:35:46 +0000 Received: from KL1PR0201MB1656.apcprd02.prod.outlook.com ([10.167.58.150]) by KL1PR0201MB1656.apcprd02.prod.outlook.com ([10.167.58.150]) with mapi id 15.01.0734.012; Tue, 22 Nov 2016 03:35:46 +0000 From: =?gb2312?B?ucsgyNY=?= To: "l2sm@ietf.org" , "adrian@olddog.co.uk" Thread-Topic: [L2sm] Opinions on issue tracker for L2SM please Thread-Index: AdJBOhBIlyfjMEmNRC2INN5CcvGuTQDNz7Qp Date: Tue, 22 Nov 2016 03:35:45 +0000 Message-ID: References: <0d6801d2413a$2fa6e0e0$8ef4a2a0$@olddog.co.uk> In-Reply-To: <0d6801d2413a$2fa6e0e0$8ef4a2a0$@olddog.co.uk> Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=outlook.com; x-incomingtopheadermarker: OriginalChecksum:; UpperCasedChecksum:; SizeAsReceived:7471; Count:38 x-tmn: [EIkb92wj05MGDQY1AxIbIunqhoHB2Cen+Eb+uwWZX/0=] x-incomingheadercount: 38 x-eopattributedmessage: 0 x-microsoft-exchange-diagnostics: 1; HK2APC01HT032; 5:U9sxzyGB6iO5ponw6ies1vLrjGxDyx9SF9TLfIR47TcWUSzqp1PxJUrVwT8lBLNbnXiKmioTQ1BOCAtOujJq2k5m/gHn2LJHa0OlNhwiqoHk1fr+vZvkAJwJCJyDALnobYpRkrMFtS0B/67vUfdNRw==; 24:0F6I30rUdJZmskj/TvxXGQWoCIuPPU2en5pbuQstXwXA66Mw2Mt8FM2CTfKTakbyJijixOtSJLMdtuDPlSvQNdf/MlYCxBVZuGi0rSe0M5w=; 7:uIRnXQf40c2LbfMj+CgoiRcXQsL6+inKWlIFd0qDzKTdGGFpCHPMjlsAZsIvjST+8XzM8Q5orJl/U5vusp2HPN4baICihw+WwXAzZBTj6AVznzP2ABXOqkhyF3ycU/pZdw4TJA2T4UtaMDgK9fKcka+Uq8kOrBnf5tavPBflfiSZeOXd6MJuU/QpRdNXmkMKXOUH/vMkNAJkWHKGva3LQ7WCflG+9ytInd5Fe0T4JJOoKDFG+sg3nW96dmokmOTGT1tU5t/kkqio+g2w2Xx8QWN6MzmrSfxvtNdohjpdkIFFqgY5/uiWcp++2hZG5AzVGf7pxT2+029bUVtEAEpXZ/vIB3Aw0M6QmawAstURfiQ= x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(10019020)(98900003); DIR:OUT; SFP:1102; SCL:1; SRVR:HK2APC01HT032; H:KL1PR0201MB1656.apcprd02.prod.outlook.com; FPR:; SPF:None; LANG:en; x-ms-office365-filtering-correlation-id: 42ff562a-1730-44aa-253d-08d41288a51d x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(1601124038)(1603103113)(1603101340)(1601125047); SRVR:HK2APC01HT032; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(432015012)(82015046); SRVR:HK2APC01HT032; BCL:0; PCL:0; RULEID:; SRVR:HK2APC01HT032; x-forefront-prvs: 0134AD334F spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: multipart/alternative; boundary="_000_KL1PR0201MB1656B5F2B1CD3FF9F523E39B8BB40KL1PR0201MB1656_" MIME-Version: 1.0 X-OriginatorOrg: outlook.com X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Nov 2016 03:35:45.9474 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: HK2APC01HT032 X-OriginalArrivalTime: 22 Nov 2016 03:35:56.0021 (UTC) FILETIME=[888EAA50:01D24471] Archived-At: Subject: [L2sm] =?gb2312?b?tPC4tDogIE9waW5pb25zIG9uIGlzc3VlIHRyYWNrZXIg?= =?gb2312?b?Zm9yIEwyU00gcGxlYXNl?= 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: Tue, 22 Nov 2016 03:35:58 -0000 --_000_KL1PR0201MB1656B5F2B1CD3FF9F523E39B8BB40KL1PR0201MB1656_ Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 SGksDQoNCkkgcHJlZmVyIHRvIHVzZSBJRVRGIHRvb2wgdG8gdHJhY2sgTDJTTSBvcGVuIGlzc3Vl IHNpbmNlIEwyU00gaGFzIGJlZW4gZm9ybWVkIGFuZCBpdCB3b3VsZCBiZSBncmVhdCB0byBtYWtl IGRpc2N1c3Npb24gYW5kIG9wZW4gaXNzdWUgdHJhbnNwYXJlbnQgdG8gZXZlcnlib2R5IHdobyBh cmUgaW50ZXJlc3RlZCBhbmQgd2FudCB0byBwcm92aWRlIGlucHV0Lg0KDQoNCkd1IFJvbmcNCg0K Z3Vyb25nQGNoaW5hbW9iaWxlLmNvbQ0KDQpndXJvbmdfY21jY0BvdXRsb29rLmNvbQ0KDQoNCg0K X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCreivP7IyzogTDJzbSA8bDJzbS1ib3Vu Y2VzQGlldGYub3JnPiC0+rHtIEFkcmlhbiBGYXJyZWwgPGFkcmlhbkBvbGRkb2cuY28udWs+DQq3 osvNyrG85DogMjAxNsTqMTHUwjE4yNUgMToyMg0KytW8/sjLOiBsMnNtQGlldGYub3JnDQrW98zi OiBbTDJzbV0gT3BpbmlvbnMgb24gaXNzdWUgdHJhY2tlciBmb3IgTDJTTSBwbGVhc2UNCg0KSGks DQoNCkR1cmluZyB0aGUgZGV2ZWxvcG1lbnQgb2YgdGhlIGN1cnJlbnQgZHJhZnQsIHRoZSBhdXRo b3JzIHVzZWQgaXNzdWVzIHRyYWNrZWQgaW4NCmdpdGh1YiB1c2luZyBhbiBvbGQgKGFuZCBwb3Nz aWJseSBpbmFwcHJvcHJpYXRlIHVzZXIgSUQpIGF0DQpodHRwczovL2dpdGh1Yi5jb20vYWxyZWFk eXRpcmVkb2Zub21jb20vTDJTTWlzc3Vlcy9pc3N1ZXMgIFRoaXMgd29ya2VkDQoic29tZXdoYXQi IGRlcGVuZGluZyBvbiB3aGljaCBhdXRob3JzIGhhZCBhY2Nlc3MgdG8gZ2l0aHViLg0KDQpXZSBo YXZlIGEgdGhyZWUtd2F5IGNob2ljZSwgSU1ITzoNCg0KMS4ganVzdCBjb250aW51ZSB0aGF0IGlz c3VlIHRyYWNrZXIgaW4gZ2l0aHViDQoyLiBzdGF5IGluIGdpdGh1YiBidXQgbW92ZSB0byBhIGJl dHRlciBhY2NvdW50DQozLiBtb3ZlIGlzc3VlIHRyYWNraW5nIGludG8gdGhlIElFVEYgdXNpbmcg SUVURiB0b29scw0KDQpEb2VzIGFueW9uZSBoYXZlIGFuIG9waW5pb24/DQoNClRoYW5rcywNCkFk cmlhbg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0K TDJzbSBtYWlsaW5nIGxpc3QNCkwyc21AaWV0Zi5vcmcNCmh0dHBzOi8vd3d3LmlldGYub3JnL21h aWxtYW4vbGlzdGluZm8vbDJzbQ0K --_000_KL1PR0201MB1656B5F2B1CD3FF9F523E39B8BB40KL1PR0201MB1656_ Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable

Hi,

I prefer to use IETF tool to= track L2SM open issue since L2SM has been formed and it would be great to = make discussion and open issue transparent to everybody who are interested = and want to provide input.


Gu Rong

gurong@chinamobile.com

gurong_cmcc@outlook.com




=B7=A2=BC=FE=C8=CB: L2sm = <l2sm-bounces@ietf.org> =B4=FA=B1=ED Adrian Farrel <adrian@olddog.= co.uk>
=B7=A2=CB=CD=CA=B1=BC=E4: 2016=C4=EA11=D4=C218=C8=D5 1:22
=CA=D5=BC=FE=C8=CB: l2sm@ietf.org
=D6=F7=CC=E2: [L2sm] Opinions on issue tracker for L2SM please
 
Hi,

During the development of the current draft, the authors used issues tracke= d in
github using an old (and possibly inappropriate user ID) at
https://github.com/alreadytiredofnomc= om/L2SMissues/issues  This worked
"somewhat" depending on which authors had access to github.

We have a three-way choice, IMHO:

1. just continue that issue tracker in github
2. stay in github but move to a better account
3. move issue tracking into the IETF using IETF tools

Does anyone have an opinion?

Thanks,
Adrian

_______________________________________________
L2sm mailing list
L2sm@ietf.org
https://www.ietf.org/mailman/listinfo/l2sm
--_000_KL1PR0201MB1656B5F2B1CD3FF9F523E39B8BB40KL1PR0201MB1656_-- From nobody Mon Nov 21 20:01:56 2016 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 3B2CD129488 for ; Mon, 21 Nov 2016 20:01:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.009 X-Spam-Level: X-Spam-Status: No, score=-2.009 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_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=outlook.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 PQ4v6-QfTxqN for ; Mon, 21 Nov 2016 20:01:53 -0800 (PST) Received: from BAY004-OMC1S11.hotmail.com (bay004-omc1s11.hotmail.com [65.54.190.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D99A9129401 for ; Mon, 21 Nov 2016 20:01:52 -0800 (PST) Received: from APC01-HK2-obe.outbound.protection.outlook.com ([65.54.190.60]) by BAY004-OMC1S11.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Mon, 21 Nov 2016 20:01:52 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=BPLQXLQg4E+T3Rdktv0pkdKyta751F3Q6A9lTJ6FlA4=; b=g3VLE98MspYXw8LfVr6i3K584j2Hm9+14Xa4K7vBwmKjvWpZ6bryb/HlY0l1RWkBTRnL8slzjQnMfSdz7roSPLTZq6Z4DD7F97TImmnFZdwzR9tUEh/NyIF0J/D/QWUVhZ1Nb4hUVBm38lMowv2Me4Z+aSh6i7UD32VG+wzsHaVUjyxDqrD4ZASoRY5UTgmzVjV+MigPNZso2D8NNAxRtfB+7y6ZD0ittSGSm9YOQShqM2dVex2tUO0UIXKQWZj5dmrxGdNSjq1Okq/YYl6v/XvBQQF4Fh5BEpafpBFCh/ySfN+qmft0clHLy+Z24mfw6oHlbwQyWAyFl17ilVQ5YQ== Received: from SG2APC01FT051.eop-APC01.prod.protection.outlook.com (10.152.250.59) by SG2APC01HT215.eop-APC01.prod.protection.outlook.com (10.152.251.64) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.721.5; Tue, 22 Nov 2016 04:01:50 +0000 Received: from KL1PR0201MB1656.apcprd02.prod.outlook.com (10.152.250.57) by SG2APC01FT051.mail.protection.outlook.com (10.152.251.112) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.679.5 via Frontend Transport; Tue, 22 Nov 2016 04:01:50 +0000 Received: from KL1PR0201MB1656.apcprd02.prod.outlook.com ([10.167.58.150]) by KL1PR0201MB1656.apcprd02.prod.outlook.com ([10.167.58.150]) with mapi id 15.01.0734.012; Tue, 22 Nov 2016 04:01:49 +0000 From: =?gb2312?B?ucsgyNY=?= To: "l2sm@ietf.org" , "adrian@olddog.co.uk" Thread-Topic: [L2sm] Adoption poll for draft-wen-l2sm-l2vpn-service-model-03.txt Thread-Index: AdJBMl9LkbuTL93GR8uhCc0ETwHqcwDQLHEs Date: Tue, 22 Nov 2016 04:01:49 +0000 Message-ID: References: <0d4501d24132$62ceb590$286c20b0$@olddog.co.uk> In-Reply-To: <0d4501d24132$62ceb590$286c20b0$@olddog.co.uk> Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=outlook.com; x-incomingtopheadermarker: OriginalChecksum:; UpperCasedChecksum:; SizeAsReceived:7508; Count:38 x-tmn: [o+gJHL3DPWB+oF0gGAGg8eJv42tvriVtwk6fEMzMVJ8=] x-incomingheadercount: 38 x-eopattributedmessage: 0 x-microsoft-exchange-diagnostics: 1; SG2APC01HT215; 5:UqmgJmsptSEsdqCj38enzYh+ZUOo8Z3X9VGRZzhKZa4+NOdRerb9pwuOhrEnjeKvnA9cOsyz1zKZIc83xTfRwUOAdmYgZPM/ErHKIvbyumJKcA4e8OdFLwPjDqTUhtP/sVxbtHnkb+UMcklEKKMDxw==; 24:aPZ73Ozk2twRHO5lcws5lA9+kq7BAbGcaHdfHe+GYcWXS57h61y1O44JExjo0XKnb8LfgaJZlseQMrjPY+3PThLFx5jBa3ROO47Gl+z4ejA=; 7:wZhSKPDvg6FAZ6/+vPzZJ96lMTYt8q4FEU8OMq/Qh8Xf0DniYJRQ3iL4dvx8gAmT1WC3auPcihOjGOAuxXnRqU+DWtTLJpSpBO/hq5GdQMRA/V5UtViHQ1wGdShEaeRLe8jtwD8XVxp43hcRrQBJ+JkaonkIrEHgPheCWkxmhs4fxBQPwetF91De4uOpUhEdc8cr+wExY9haOtSh0pvYUU6xUNWwt9uv1JIZfgDRCezjJ2xg9DETxjX5of572rdpRS4MOTcdG/JlMI4bn8DG0TZtndl+HfP3R0KAgAVtNJK0Pb0wO1rfHPVyK5Q1zKirigDoT9Zwt7Uc/Pt18tl9+im4l+W3XJG/weT0xPtEThg= x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(10019020)(98900003); DIR:OUT; SFP:1102; SCL:1; SRVR:SG2APC01HT215; H:KL1PR0201MB1656.apcprd02.prod.outlook.com; FPR:; SPF:None; LANG:en; x-ms-office365-filtering-correlation-id: 198cba52-774e-4b59-0ac7-08d4128c4911 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(1601124038)(1603103113)(1603101340)(1601125047); SRVR:SG2APC01HT215; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(432015012)(82015046); SRVR:SG2APC01HT215; BCL:0; PCL:0; RULEID:; SRVR:SG2APC01HT215; x-forefront-prvs: 0134AD334F spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: multipart/alternative; boundary="_000_KL1PR0201MB16562583F0DAA18E0499EAFB8BB40KL1PR0201MB1656_" MIME-Version: 1.0 X-OriginatorOrg: outlook.com X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Nov 2016 04:01:49.3044 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: SG2APC01HT215 X-OriginalArrivalTime: 22 Nov 2016 04:01:52.0564 (UTC) FILETIME=[28544740:01D24475] Archived-At: Subject: [L2sm] =?gb2312?b?tPC4tDogIEFkb3B0aW9uIHBvbGwgZm9yIGRyYWZ0LXdl?= =?gb2312?b?bi1sMnNtLWwydnBuLXNlcnZpY2UtbW9kZWwtMDMudHh0?= 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: Tue, 22 Nov 2016 04:01:55 -0000 --_000_KL1PR0201MB16562583F0DAA18E0499EAFB8BB40KL1PR0201MB1656_ Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 SGksIGNoYWlycyBhbmQgYXV0aG9ycy4NCg0KDQpJIGFncmVlIHdpdGggdGhlIFdHIGFkb3B0aW9u IG9mIHRoZSBMMlNNIHNlcnZpY2UgbW9kZWwgZHJhZnQuIEFzIEkgYXR0ZW5kIHRoZSBMMlNNIGlu IFNlb3VsLCBJIHRoaW5rIHNlcnZpY2UgbW9kZWwgaXMgYWN0dWFsbHkgaW1wb3J0YW50IHdoaWNo IGNhbiBiZSByZWdhcmRlZCBhcyBhIHJlZmVyZW5jZSBvciBndWlkYW5jZSB0byB0aGUgb3BlcmF0 b3Igd2hlbiBwcm92aWRpbmcgdGhlIFZQTiBzZXJ2aWNlLiBUaGlzIGlzIHRoZSByZWFzb24gb2Yg bXkgYWdyZWVtZW50Lg0KDQpIb3dldmVyLCB0aGlzIGRyYWZ0IG5lZWRzIHRvIGJlIHVwZGF0ZWQg YXMgYSBtdWNoIG1vcmUgYWJzdHJhY3Qgc2VydmljZSBtb2RlbC4NCg0KDQpHdSBSb25nDQoNCmd1 cm9uZ0BjaGluYW1vYmlsZS5jb20NCg0KZ3Vyb25nX2NtY2NAb3V0bG9vay5jb20NCl9fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fDQq3orz+yMs6IEwyc20gPGwyc20tYm91bmNlc0BpZXRm Lm9yZz4gtPqx7SBBZHJpYW4gRmFycmVsIDxhZHJpYW5Ab2xkZG9nLmNvLnVrPg0Kt6LLzcqxvOQ6 IDIwMTbE6jEx1MIxOMjVIDA6MjYNCsrVvP7IyzogbDJzbUBpZXRmLm9yZw0K1vfM4jogW0wyc21d IEFkb3B0aW9uIHBvbGwgZm9yIGRyYWZ0LXdlbi1sMnNtLWwydnBuLXNlcnZpY2UtbW9kZWwtMDMu dHh0DQoNCkhpLA0KDQpPdXIgY2hhcnRlciBtYW5kYXRlcyB0aGF0IHdlIGNvbnNpZGVyIGJhc2lu ZyBvdXIgd29yayBvbg0KZHJhZnQtd2VuLWwyc20tbDJ2cG4tc2VydmljZS1tb2RlbC0wMy50eHQN Cg0KQXMgd2UgZGlzY3Vzc2VkIGluIHRoZSBtZWV0aW5nLCB0aGF0IGRyYWZ0IGlzIG5vdCBwZXJm ZWN0LiBCdXQgd2hlbiBJIGFza2VkIHRoZQ0Kcm9vbSB3aGV0aGVyIHdlIHRob3VnaHQgdGhhdCBp dCB3b3VsZCBwcm92aWRlIGEgZ29vZCBzdGFydGluZyBwb2ludCB0aGF0IHdlDQpjb3VsZCB3b3Jr IHdpdGggdG8gcG9saXNoIGFuZCBhZGFwdCB0byBiZWNvbWUgdGhlIEktRCB0aGF0IHdlIHVsdGlt YXRlbHkgc3VibWl0DQpmb3IgcHVibGljYXRpb24gYXMgYW4gUkZDLCBJIGJlbGlldmUgSSBoZWFy ZCBhIGdvb2QgaHVtIGluIGZhdm91ciBhbmQgc2lsZW5jZSBpbg0Kb3Bwb3NpdGlvbi4NCg0KU28g dGhpcyBlbWFpbCBzdGFydHMgYSBmb3JtYWwgcG9sbCBmb3IgYWRvcHRpb24uIFBsZWFzZSBhbnN3 ZXI6DQoNCkRvIHlvdSB0aGluayB0aGF0IHRoZSBXRyBzaG91bGQgYWRvcHQgZHJhZnQtd2VuLWwy c20tbDJ2cG4tc2VydmljZS1tb2RlbC0wMy50eHQ/DQoNCklmICJ5ZXMsIiBpdCB3b3VsZCBoZWxw IGlmIHlvdSBjb3VsZCBpbmRpY2F0ZSB3aGV0aGVyIHlvdSBoYXZlIHJlYWQgdGhlIGRyYWZ0DQph bmQgaG93IGhhcHB5IHlvdSBhcmUgd2l0aCBpdC4NCklmICJubyIsIGl0IGlzIGltcG9ydGFudCB0 aGF0IHlvdSBwcm92aWRlIHJlYXNvbnMuDQoNClRoaXMgcG9sbCB3aWxsIGxhc3QgZm9yIHR3byB3 ZWVrcywgZW5kaW5nIG9uIFNhdHVyZGF5IDNyZCBEZWNlbWJlci4NCg0KSnVzdCB0byByZWFzc3Vy ZSBldmVyeW9uZSB0aGF0IGFkb3B0aW9uIGRvZXMgbm90IGltcGx5IHRoYXQgYW55dGhpbmcgaXMg c2V0IGluDQpzdG9uZTogd2UgZXhwZWN0IHRoZSBXRyB0byBjb250aW51ZSB0byBkZXZlbG9wIHRo ZSBjb250ZW50IGFuZCBjaGFuZ2Ugd2hhdGV2ZXINCm5lZWRzIHRvIGJlIGNoYW5nZWQuDQoNClRo YW5rcywNCkFkcmlhbiBhbmQgUWluDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fDQpMMnNtIG1haWxpbmcgbGlzdA0KTDJzbUBpZXRmLm9yZw0KaHR0cHM6 Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9sMnNtDQpMMnNtIEluZm8gUGFnZSAtIGll dGYub3JnPGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbDJzbT4NCnd3dy5p ZXRmLm9yZw0KWW91ciBlbWFpbCBhZGRyZXNzOiBZb3VyIG5hbWUgKG9wdGlvbmFsKTogWW91IG1h eSBlbnRlciBhIHByaXZhY3kgcGFzc3dvcmQgYmVsb3cuIFRoaXMgcHJvdmlkZXMgb25seSBtaWxk IHNlY3VyaXR5LCBidXQgc2hvdWxkIHByZXZlbnQgb3RoZXJzIGZyb20gbWVzc2luZyB3aXRoIC4u Lg0KDQoNCg0K --_000_KL1PR0201MB16562583F0DAA18E0499EAFB8BB40KL1PR0201MB1656_ Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable

Hi, chairs and authors.


I agree with the WG adoption of the L2SM service model draft. As I = attend the L2SM in Seoul, I think service model is actually important = which can be regarded as a reference or guidance to the operator when = providing the VPN service. This is the reason of my agreement. 

However, this draft needs to be updated as a much more abstract&nbs= p;service model.


Gu Rong

gurong@chinamobile.com

gurong_cmcc@outlook.com
=B7=A2=BC=FE=C8=CB: L2sm = <l2sm-bounces@ietf.org> =B4=FA=B1=ED Adrian Farrel <adrian@olddog.= co.uk>
=B7=A2=CB=CD=CA=B1=BC=E4: 2016=C4=EA11=D4=C218=C8=D5 0:26
=CA=D5=BC=FE=C8=CB: l2sm@ietf.org
=D6=F7=CC=E2: [L2sm] Adoption poll for draft-wen-l2sm-l2vpn-service-= model-03.txt
 
Hi,

Our charter mandates that we consider basing our work on
draft-wen-l2sm-l2vpn-service-model-03.txt

As we discussed in the meeting, that draft is not perfect. But when I asked= the
room whether we thought that it would provide a good starting point that we=
could work with to polish and adapt to become the I-D that we ultimately su= bmit
for publication as an RFC, I believe I heard a good hum in favour and silen= ce in
opposition.

So this email starts a formal poll for adoption. Please answer:

Do you think that the WG should adopt draft-wen-l2sm-l2vpn-service-model-03= .txt?

If "yes," it would help if you could indicate whether you have re= ad the draft
and how happy you are with it.
If "no", it is important that you provide reasons.

This poll will last for two weeks, ending on Saturday 3rd December.

Just to reassure everyone that adoption does not imply that anything is set= in
stone: we expect the WG to continue to develop the content and change whate= ver
needs to be changed.

Thanks,
Adrian and Qin

_______________________________________________
L2sm mailing list
L2sm@ietf.org
https://www.ietf.org/mailman/listinfo/l2sm
www.ietf.org
Your email address: Your name (optional): You may enter a privacy password = below. This provides only mild security, but should prevent others from mes= sing with ...


--_000_KL1PR0201MB16562583F0DAA18E0499EAFB8BB40KL1PR0201MB1656_-- From nobody Tue Nov 22 05:28:57 2016 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 68E2E129622 for ; Tue, 22 Nov 2016 05:28:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=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 O14UOouZux57 for ; Tue, 22 Nov 2016 05:28:53 -0800 (PST) Received: from layerfree.net (heronab2.miniserver.com [89.200.138.104]) (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 7CB73129503 for ; Tue, 22 Nov 2016 05:28:53 -0800 (PST) X-Default-Received-SPF: pass (skip=loggedin (res=PASS)); From: Giles Heron Message-Id: <64B4D851-79F1-44BB-AE48-DBC79F32C635@layerfree.net> Content-Type: multipart/alternative; boundary="Apple-Mail=_8AB95596-4DAC-4804-B9AE-2841AA8EF261" Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Date: Tue, 22 Nov 2016 13:28:48 +0000 In-Reply-To: <1a94d940-9cce-26c9-be2e-a5ac5fd93acf@cisco.com> To: David Ball References: <0d4501d24132$62ceb590$286c20b0$@olddog.co.uk> <0f1f01d241a7$959b1c00$c0d15400$@olddog.co.uk> <1a94d940-9cce-26c9-be2e-a5ac5fd93acf@cisco.com> X-Mailer: Apple Mail (2.3251) X-Info: aspam skipped due to (g_smite_skip_relay) X-Encryption: SSL encrypted Archived-At: Cc: adrian@olddog.co.uk, l2sm@ietf.org Subject: Re: [L2sm] Adoption poll for draft-wen-l2sm-l2vpn-service-model-03.txt 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: Tue, 22 Nov 2016 13:28:56 -0000 --Apple-Mail=_8AB95596-4DAC-4804-B9AE-2841AA8EF261 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi David, > On 21 Nov 2016, at 09:38, David Ball wrote: >=20 > Hi Adrian, > On 18/11/2016 14:25, Adrian Farrel wrote: >> But let's quickly jump from that discussion to try to understand the = way forward >> you would like to see. Clearly you think changes to the document are = needed and >> it sounds like everyone agrees that that is true. And that sounds (to = me) like >> you believe we have a document we can work with to serve as a basis = for updates. >> What isn't obvious to me is why you don't think that the working = group should >> have control of this discussion and the changes to the document. What = do you >> propose? > Fundamentally, given the amount of work needed on this document, it's = not clear to me that taking it as a basis for the WG work is the = least-effort option; we should as a minimum consider alternatives - e.g. = starting from scratch, or using the MEF modules as a basis (I believe = MEF have recently liaised their in-progress work to IETF). >=20 agreed. I think we need to stand back and look at what needs to be in = an L2VPN service model and then compare that to this draft and to the = MEF work (perhaps without going as far as a formal requirements draft). and I think we should perhaps consider a layered approach where we have: a) technology-specific models for PWE-based VPWS/VPLS and for EVPN, = which expose the internal details of the protocols (e.g. PW IDs, BGP = RTs/RDs to the layer above) and which can be used as components in more = complex end-to-end models (e.g. PWE access to an L3VPN). b) technology-neutral but still resource-facing service models for e.g. = E-Line and E-LAN which can be implemented using PWE, EVPN, L2TPv3, = Ethernet VLANs, wet string etc. c) customer-facing service models with constructs such as customer = info/account number etc. Were we to take the layered approach I=E2=80=99d suggest that IETF be = responsible for (a), MEF for (b) and the individual service provider for = (c) (though there may be value in standardising some of the = customer-facing stuff to enable multi-provider orchestration etc.)=20 within the context of (a) we should also look to maximise reuse between = the L2VPN and L3VPN models (e.g. using common groupings for BGP RTs/RDs = etc., using common site definitions etc.) we may also want to consider whether we look to augment the I2RS network = and topology models rather than creating models from scratch. The = =E2=80=9CN=E2=80=9D in =E2=80=9CVPN=E2=80=9D stands for =E2=80=9CNetwork=E2= =80=9D after all. That also gives us a potential approach to exposing = the dependencies between layers (a), (b) and (c) by using the = =E2=80=9Csupporting-=E2=80=9C network/node/link concepts. Giles > I also really would like to hear from the authors - their document may = be useful in its own right (just not aligned with the WG charter), so it = may be that they want to proceed with it in that direction, as an = individual draft. Of course that doesn't stop the WG "forking" it, but = one might imagine the authors would be less inclined to participate in = the WG in that case. >=20 > David >=20 > --=20 > David Ball > = _______________________________________________= > L2sm mailing list > L2sm@ietf.org > https://www.ietf.org/mailman/listinfo/l2sm --Apple-Mail=_8AB95596-4DAC-4804-B9AE-2841AA8EF261 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hi David,

On 21 Nov 2016, at 09:38, David = Ball <daviball@cisco.com> wrote:

=20 =20

Hi = Adrian,

On 18/11/2016 14:25, Adrian Farrel wrote:
But let's quickly jump from that =
discussion to try to understand the way forward
you would like to see. Clearly you think changes to the document are =
needed and
it sounds like everyone agrees that that is true. And that sounds (to =
me) like
you believe we have a document we can work with to serve as a basis for =
updates.
What isn't obvious to me is why you don't think that the working group =
should
have control of this discussion and the changes to the document. What do =
you
propose?

Fundamentally, given the amount of work = needed on this document, it's not clear to me that taking it as a basis for the WG work is the least-effort option; we should as a minimum consider alternatives - e.g. starting from scratch, or using the MEF modules as a basis (I believe MEF have recently liaised their in-progress work to IETF).

agreed. =   I think we need to stand back and look at what needs to be in an = L2VPN service model and then compare that to this draft and to the MEF = work (perhaps without going as far as a formal requirements = draft).

and I think we should = perhaps consider a layered approach where we have:
a) = technology-specific models for PWE-based VPWS/VPLS and for EVPN, which = expose the internal details of the protocols (e.g. PW IDs, BGP RTs/RDs = to the layer above) and which can be used as components in more complex = end-to-end models (e.g. PWE access to an L3VPN).
b) = technology-neutral but still resource-facing service models for e.g. = E-Line and E-LAN which can be implemented using PWE, EVPN, L2TPv3, = Ethernet VLANs, wet string etc.
c) customer-facing service = models with constructs such as customer info/account number = etc.

Were we to take the layered = approach I=E2=80=99d suggest that IETF be responsible for (a), MEF for = (b) and the individual service provider for (c) (though there may be = value in standardising some of the customer-facing stuff to enable = multi-provider orchestration etc.) 

within the context of (a) we should also look to = maximise reuse between the L2VPN and L3VPN models (e.g. using common = groupings for BGP RTs/RDs etc., using common site definitions = etc.)

we may also want to consider = whether we look to augment the I2RS network and topology models rather = than creating models from scratch.   The =E2=80=9CN=E2=80=9D in = =E2=80=9CVPN=E2=80=9D stands for =E2=80=9CNetwork=E2=80=9D after all. =   That also gives us a potential approach to exposing the = dependencies between layers (a), (b) and (c) by using the = =E2=80=9Csupporting-=E2=80=9C network/node/link concepts.

Giles

I also really would like to hear from the authors = - their document may be useful in its own right (just not aligned with the WG charter), so it may be that they want to proceed with it in that direction, as an individual draft.  Of course that = doesn't stop the WG "forking" it, but one might imagine the authors would be less inclined to participate in the WG in that case.


    David


--=20
David Ball
<daviball@cisco.com>
_______________________________________________
L2sm = mailing list
L2sm@ietf.org
https://www.ietf.org/mailman/listinfo/l2sm

= --Apple-Mail=_8AB95596-4DAC-4804-B9AE-2841AA8EF261-- From nobody Tue Nov 22 05:53:26 2016 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 1FFCE1293DB for ; Tue, 22 Nov 2016 05:53:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.718 X-Spam-Level: X-Spam-Status: No, score=-5.718 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.497, SPF_PASS=-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 UFUjLPyOFtuh for ; Tue, 22 Nov 2016 05:53:24 -0800 (PST) Received: from TELEDG001RM001.telecomitalia.it (teledg001rm001.telecomitalia.it [217.169.121.18]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF27812947A for ; Tue, 22 Nov 2016 05:53:23 -0800 (PST) Received: from TELMBXB02RM001.telecomitalia.local (10.14.252.27) by TELEDG001RM001.telecomitalia.it (10.19.3.111) with Microsoft SMTP Server (TLS) id 14.3.319.2; Tue, 22 Nov 2016 14:53:20 +0100 Received: from TELMBXB02RM001.telecomitalia.local (10.14.252.27) by TELMBXB02RM001.telecomitalia.local (10.14.252.27) with Microsoft SMTP Server (TLS) id 15.0.1236.3; Tue, 22 Nov 2016 14:53:20 +0100 Received: from TELMBXB02RM001.telecomitalia.local ([fe80::2845:411e:c732:e844]) by TELMBXB02RM001.telecomitalia.local ([fe80::2845:411e:c732:e844%20]) with mapi id 15.00.1236.000; Tue, 22 Nov 2016 14:53:20 +0100 From: Fioccola Giuseppe To: "adrian@olddog.co.uk" , "l2sm@ietf.org" Thread-Topic: [L2sm] Opinions on issue tracker for L2SM please Thread-Index: AdJBOhBIlyfjMEmNRC2INN5CcvGuTQDYmdVQ Date: Tue, 22 Nov 2016 13:53:20 +0000 Message-ID: <1d400463cd4a498eaf7e8cab3df331c7@TELMBXB02RM001.telecomitalia.local> References: <0d6801d2413a$2fa6e0e0$8ef4a2a0$@olddog.co.uk> In-Reply-To: <0d6801d2413a$2fa6e0e0$8ef4a2a0$@olddog.co.uk> Accept-Language: it-IT, en-US Content-Language: it-IT X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.14.252.245] x-ti-disclaimer: Disclaimer1 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Subject: [L2sm] R: Opinions on issue tracker for L2SM please 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: Tue, 22 Nov 2016 13:53:26 -0000 We should move issue tracking into IETF tools, that could be better in orde= r to have only one reference for the open issues. Thanks, Giuseppe -----Messaggio originale----- Da: L2sm [mailto:l2sm-bounces@ietf.org] Per conto di Adrian Farrel Inviato: venerd=EC 18 novembre 2016 02:22 A: l2sm@ietf.org Oggetto: [L2sm] Opinions on issue tracker for L2SM please Hi, During the development of the current draft, the authors used issues tracke= d in github using an old (and possibly inappropriate user ID) at https://gi= thub.com/alreadytiredofnomcom/L2SMissues/issues This worked "somewhat" dep= ending on which authors had access to github. We have a three-way choice, IMHO: 1. just continue that issue tracker in github 2. stay in github but move to= a better account 3. move issue tracking into the IETF using IETF tools Does anyone have an opinion? Thanks, Adrian _______________________________________________ L2sm mailing list L2sm@ietf.org https://www.ietf.org/mailman/listinfo/l2sm Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle per= sone indicate. La diffusione, copia o qualsiasi altra azione derivante dall= a conoscenza di queste informazioni sono rigorosamente vietate. Qualora abb= iate ricevuto questo documento per errore siete cortesemente pregati di dar= ne 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, pri= nting or use by anybody else is unauthorised. If you are not the intended r= ecipient, please delete this message and any attachments and advise the sen= der by return e-mail, Thanks.