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

andy L <pop.andrew@gmail.com> Wed, 17 June 2015 08:40 UTC

Return-Path: <pop.andrew@gmail.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 5668E1A86F7 for <l3sm@ietfa.amsl.com>; Wed, 17 Jun 2015 01:40:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level:
X-Spam-Status: No, score=-1.399 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, J_CHICKENPOX_12=0.6, SPF_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 i9_UF7r5ftF4 for <l3sm@ietfa.amsl.com>; Wed, 17 Jun 2015 01:40:26 -0700 (PDT)
Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com [IPv6:2a00:1450:4010:c04::234]) (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 746251A86F3 for <l3sm@ietf.org>; Wed, 17 Jun 2015 01:40:26 -0700 (PDT)
Received: by lblr1 with SMTP id r1so26659302lbl.0 for <l3sm@ietf.org>; Wed, 17 Jun 2015 01:40:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=JMlks80i11q7H46SCVcyqAQlVyW76XLnhFtDVnLAd58=; b=hABdqOsm0txdyTW0qNRieKvR57d+siswUl2bpgq4bUwZDUC1zujSP2OwaDOUkloF6P TpWkUgzLmbyNsUudwOBwHI/GGmZow71XXaaBrz/Z98jWauCNzf5Es3stee/aGYq5GzQ+ CGMDVcRN8RB8Vi8sELldmQRzFz0f85909Q5uv74Ji4wjodIa8dYHZ1EpnMF7+Qr/A8at fKCgUcwhsRjwqZ6+Nfp6pErWU/r5Tsa0pyuT6ia932TsnJtZEXSL4tsNR8wLbaY0NkGV iOyw2DoxIO0Zp8mU79xmnpy18jV1/pNEYpgFVzz1+VdiT3tFCdMDqstLi78mbAtx3/hL HMew==
MIME-Version: 1.0
X-Received: by 10.152.7.65 with SMTP id h1mr6553109laa.33.1434530424747; Wed, 17 Jun 2015 01:40:24 -0700 (PDT)
Received: by 10.114.246.2 with HTTP; Wed, 17 Jun 2015 01:40:24 -0700 (PDT)
In-Reply-To: <B8F9A780D330094D99AF023C5877DABA8475E8DC@nkgeml501-mbs.china.huawei.com>
References: <B8F9A780D330094D99AF023C5877DABA8475E8DC@nkgeml501-mbs.china.huawei.com>
Date: Wed, 17 Jun 2015 16:40:24 +0800
Message-ID: <CAPsMJ7qp6w45J5qWP4ChDTn1NLg13QweqLAiEgu=KO+pNK2LBw@mail.gmail.com>
From: andy L <pop.andrew@gmail.com>
To: "l3sm@ietf.org" <l3sm@ietf.org>
Content-Type: multipart/alternative; boundary="001a11c27cf062fbd90518b2a46a"
Archived-At: <http://mailarchive.ietf.org/arch/msg/l3sm/aAz_MQBTEeb6V7WTVuBb-XrCal4>
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: Wed, 17 Jun 2015 08:40:28 -0000

it will be a good start, I support the suggestion.
Andy

2015-06-16 21:38 GMT+08:00 Qin Wu <bill.wu@huawei.com>:

>  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
>
>
>
> _______________________________________________
> L3sm mailing list
> L3sm@ietf.org
> https://www.ietf.org/mailman/listinfo/l3sm
>
>