IETF Logo Mail Archive

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

赵婧 <zhaojing@sttri.com.cn> Thu, 18 June 2015 11:13 UTC

Return-Path: <zhaojing@sttri.com.cn>
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 7E5641B30E1 for <l3sm@ietfa.amsl.com>; Thu, 18 Jun 2015 04:13:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.1
X-Spam-Level: *
X-Spam-Status: No, score=1.1 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-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 8T7cqac3ZkNM for <l3sm@ietfa.amsl.com>; Thu, 18 Jun 2015 04:13:13 -0700 (PDT)
Received: from corp.21cn.com (corp.forptr.21cn.com [121.14.133.8]) by ietfa.amsl.com (Postfix) with ESMTP id 30EF11A6EDC for <l3sm@ietf.org>; Thu, 18 Jun 2015 04:13:11 -0700 (PDT)
HMM_SOURCE_IP: 10.28.101.9:33335.484959675
HMM_ATTACHE_NUM: 0000
HMM_SOURCE_TYPE: SMTP
Received: from zhaojing-PC (unknown [10.28.101.9]) by corp.21cn.com (HERMES) with ESMTP id 4EDBBD6806A; Thu, 18 Jun 2015 19:13:05 +0800 (CST)
Received: from zhaojing-PC ([116.227.144.171]) by 21CN-entas9-3(MEDUSA 10.28.101.9) with ESMTP id 1434625984.5390 for bill.wu@huawei.com ; Thu Jun 18 19:13:07 2015
0/X-Total-Score: -120:
X-FILTER-SCORE: to=<838a8d8d4f98966189968298868a4f84908e>, score=<1434625987im0DXXXXXzXXVXXoXzVoYF0nqvEEEEE1EEMEEsE1MsQD>
X-REAL-FROM: zhaojing@sttri.com.cn
X-Receive-IP: 116.227.144.171 zhaojing@sttri.com.cn
Date: Thu, 18 Jun 2015 19:13:29 +0800
From: 赵婧 <zhaojing@sttri.com.cn>
To: "bill.wu" <bill.wu@huawei.com>, "l3sm@ietf.org" <l3sm@ietf.org>
References: <B8F9A780D330094D99AF023C5877DABA8475E8DC@nkgeml501-mbs.china.huawei.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7, 2, 6, 40[cn]
Mime-Version: 1.0
Message-ID: <201506181913285349886@sttri.com.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart006085015531_=----"
Archived-At: <http://mailarchive.ietf.org/arch/msg/l3sm/tf18Dvaz1oAA_3meFS_JoaZ4Q84>
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>
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: <http://www.ietf.org/mail-archive/web/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: Thu, 18 Jun 2015 11:13:16 -0000

Hi, all, 
    It makes sense to adopt the model. I support the draft. 
BR.
JING ZHAO
CHINA TELECOM

 



 
From: Qin Wu
Date: 2015-06-16 21:38
To: l3sm@ietf.org
CC: adrian@olddog.co.uk
Subject: [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