Re: [L2sm] Adoption poll for draft-wen-l2sm-l2vpn-service-model-03.txt

David Ball <daviball@cisco.com> Fri, 18 November 2016 10:32 UTC

Return-Path: <daviball@cisco.com>
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 <l2sm@ietfa.amsl.com>; 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 <l2sm@ietfa.amsl.com>; 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 <l2sm@ietf.org>; 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: A0DOAQCM1y5Y/xbLJq1eGQEBAQEBAQEBAQEBBwEBAQEBgzcBAQEBAXcsVI0/lxCUZoIHHQuFeQKCWRQBAgEBAQEBAQFiKIRpAQEEAQEBNTYbCxguJzAHDAYCAQGIaA6uH4tUAQEBAQEFAQEBAQEBHAWGPIF9CIJVhBsRAYV9AQSaSIkLh2eBcIR3gxwjhgGJeINghAseN10REQwdhSE+NIYdgi0BAQE
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 <daviball@cisco.com>
Message-ID: <fe6e128f-6bc2-7164-3882-ad4d9de862a1@cisco.com>
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: <https://mailarchive.ietf.org/arch/msg/l2sm/7qxelSQ0WEYHcRq3hUS-L59Xu8U>
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\)" <l2sm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2sm>, <mailto:l2sm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/l2sm/>
List-Post: <mailto:l2sm@ietf.org>
List-Help: <mailto:l2sm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2sm>, <mailto:l2sm-request@ietf.org?subject=subscribe>
X-List-Received-Date: 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
<daviball@cisco.com>