IETF Logo Mail Archive

Re: [L3sm] Poll for adoption of draft-ltsd-l3sm-l3vpn-service-model

"Dacheng Zhang" <dacheng.zdc@alibaba-inc.com> Wed, 24 June 2015 09:05 UTC

Return-Path: <dacheng.zdc@alibaba-inc.com>
X-Original-To: l3sm@ietfa.amsl.com
Delivered-To: l3sm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68FEC1B3270 for <l3sm@ietfa.amsl.com>; Wed, 24 Jun 2015 02:05:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.052
X-Spam-Level: *
X-Spam-Status: No, score=1.052 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, J_CHICKENPOX_12=0.6, MIME_CHARSET_FARAWAY=2.45, MIME_QP_LONG_LINE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=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 TVRHG7n6IIZP for <l3sm@ietfa.amsl.com>; Wed, 24 Jun 2015 02:05:49 -0700 (PDT)
Received: from out4133-130.mail.aliyun.com (out4133-130.mail.aliyun.com [42.120.133.130]) by ietfa.amsl.com (Postfix) with ESMTP id 15B711B325B for <l3sm@ietf.org>; Wed, 24 Jun 2015 02:05:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alibaba-inc.com; s=default; t=1435136747; h=Date:Subject:From:To:Message-ID:Mime-version:Content-type; bh=do+5KT8N+6sdDrLILge85RgA7+lkWS1lIEcTEnahuJA=; b=koSPHmuRWaTBNE6OV19c1PBWPB8907/eLHD4QvnRnAnL78v7DeFaXH/3AYSdLRMetkWb+V0eH7sol5CHPb2M/zOKeXpsnBNIJNuyf32LBcwZjpzHI+yBuLeO4oUWVgG49bzDdgNCXhNG9+e0ouxYvkTMA/K+pEhzU4PLJ+b6z+I=
X-Alimail-AntiSpam: AC=PASS; BC=-1|-1; BR=01201311R141e4; FP=0|-1|-1|-1|0|-1|-1|-1; HT=r41g03021; MF=dacheng.zdc@alibaba-inc.com; PH=DS; RN=1; RT=1; SR=0;
Received: from 10.32.178.6(mailfrom:dacheng.zdc@alibaba-inc.com ip:182.92.253.16) by smtp.aliyun-inc.com(127.0.0.1); Wed, 24 Jun 2015 17:05:42 +0800
User-Agent: Microsoft-MacOutlook/14.5.1.150515
Date: Wed, 24 Jun 2015 17:05:38 +0800
From: Dacheng Zhang <dacheng.zdc@alibaba-inc.com>
To: l3sm@ietf.org
Message-ID: <D1B093E1.1C94A%dacheng.zdc@alibaba-inc.com>
Thread-Topic: [L3sm] Poll for adoption of draft-ltsd-l3sm-l3vpn-service-model
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3518010342_42664026"
Archived-At: <http://mailarchive.ietf.org/arch/msg/l3sm/ImD_DtKo3skcVyRncN-LWnLW8k8>
Subject: Re: [L3sm] Poll for adoption of draft-ltsd-l3sm-l3vpn-service-model
X-BeenThere: l3sm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: L3VPN Service YANG Model discussion group <l3sm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3sm>, <mailto:l3sm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/l3sm/>
List-Post: <mailto:l3sm@ietf.org>
List-Help: <mailto:l3sm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3sm>, <mailto:l3sm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Jun 2015 09:05:54 -0000

Hi, 

I just got a chance to read the draft with a big interest. I think this work
is ready for adoption as a WG draft.

Cheers

Dacheng

发件人: L3sm [mailto:l3sm-bounces@ietf.org] 代表 Qin Wu
发送时间: 2015年6月16日 21:39
收件人: l3sm@ietf.org
抄送: adrian@olddog.co.uk
主题: [L3sm] Poll for adoption of draft-ltsd-l3sm-l3vpn-service-model


Hello working group:



As you'll recall, our charter directs us to produce a single deliverable: a
YANG data model that describes a L3VPN service.



The charter says:

> The working group should consider draft-l3vpn-service-yang as a

> starting point.



The authors of that draft have just reposted it as
https://datatracker.ietf.org/doc/draft-ltsd-l3sm-l3vpn-service-model giving
it a name that associates it with the working group, and picking up a number
of review comments from the mailing list.



Obviously the document is not perfect yet, but the chairs believe it is
sufficiently stable that we should adopt it into the WG so that we can
polish it and work towards publication as an RFC. So this email starts a
two-week poll for adoption of the draft ending 30/06/2015.



Please indicate whether you support adoption for not, and if not why. If you
support adoption, have you read the document? do you think it meets our
needs? is it stable enough for adoption? If you oppose to adoption, can you
say why? what is your proposed alternative? what needs to be done before
adoption?



It's likely that as you review the document you will come up with issues and
concerns. We hope these will be fixed along the way, so please do raise them
on the mailing list. But please also try to understand the difference
between a critical issue that should block adoption, and smaller issues that
can be fixed better through discussion within the working group.



Thanks,

Qin and Adrian

v2.23.0 | Report a Bug | By Email