Re: Poll for adoption: draft-fang-l3vpn-end-system-requirements
Loa Andersson <loa@pi.nu> Mon, 08 September 2014 08:48 UTC
Return-Path: <loa@pi.nu>
X-Original-To: l3vpn@ietfa.amsl.com
Delivered-To: l3vpn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BA361A016E for <l3vpn@ietfa.amsl.com>; Mon, 8 Sep 2014 01:48:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.552
X-Spam-Level:
X-Spam-Status: No, score=-3.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.652] autolearn=ham
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 hKssQviByX38 for <l3vpn@ietfa.amsl.com>; Mon, 8 Sep 2014 01:47:59 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E645C1A0421 for <l3vpn@ietf.org>; Mon, 8 Sep 2014 01:47:58 -0700 (PDT)
Received: from [192.168.0.102] (81-236-221-144-no93.tbcn.telia.com [81.236.221.144]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 56AF91801487; Mon, 8 Sep 2014 10:47:57 +0200 (CEST)
Message-ID: <540D6D43.5030303@pi.nu>
Date: Mon, 08 Sep 2014 10:48:03 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Thomas Morin <thomas.morin@orange.com>, l3vpn@ietf.org
Subject: Re: Poll for adoption: draft-fang-l3vpn-end-system-requirements
References: <5409BFC1.1000301@orange.com>
In-Reply-To: <5409BFC1.1000301@orange.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/l3vpn/K91nsYG7vckyLnMcnLFimpeSJf4
Cc: draft-fang-l3vpn-end-system-requirements@tools.ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn/>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Sep 2014 08:48:00 -0000
Folks, I read the draft and think it is a good start to address a real problem. I support making this a working group document. There are some things that can be addressed during the normal wg process, e.g. I would like to make the requirements easily identifiable (e.g. RFC 5654 number the requirements), 5654 also clearly separate explanatory text and requirement text. The structure of the document need to be reviewed, at least updating the section numbering. I think RFC 2119 needs to be a normative reference. /Loa On 2014-09-05 15:50, Thomas Morin wrote: > Hello working group, > > This email starts a two-week poll on adopting > draft-fang-l3vpn-end-system-requirements [1] as a working group item. > > Please send comments to the list and state if you support adoption or > not (in the later case, please also state the reasons). > > This poll runs until **September 19th**. > > > *Coincidentally*, we are also polling for knowledge of any IPR that > applies to this draft, to ensure that IPR has been disclosed in > compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 > and 5378 for more details). > > ==> *If you are listed as a document author or contributor* please > respond to this email and indicate whether or not you are aware of any > relevant IPR. > > The draft will not be adopted until a response has been received from > each author and contributor. > > If you are on the L3VPN WG mailing list but are not listed as an author > or contributor, then please explicitly respond only if you are aware of > any IPR that has not yet been disclosed in conformance with IETF rules. > > Thank you, > > Martin & Thomas > l3vpn chairs > > [1] https://tools.ietf.org/html/draft-fang-l3vpn-end-system-requirements-03 > -- Loa Andersson email: loa@mail01.huawei.com Senior MPLS Expert loa@pi.nu Huawei Technologies (consultant) phone: +46 739 81 21 64
- Poll for adoption: draft-fang-l3vpn-end-system-re… Thomas Morin
- RE: Poll for adoption: draft-fang-l3vpn-end-syste… NAPIERALA, MARIA H
- RE: Poll for adoption: draft-fang-l3vpn-end-syste… NAPIERALA, MARIA H
- RE: Poll for adoption: draft-fang-l3vpn-end-syste… Luyuan Fang
- Re: Poll for adoption: draft-fang-l3vpn-end-syste… Jeff Tantsura
- Re: Poll for adoption: draft-fang-l3vpn-end-syste… Andrew G. Malis
- Re: Poll for adoption: draft-fang-l3vpn-end-syste… Robert Raszuk
- RE: Poll for adoption: draft-fang-l3vpn-end-syste… Lucy yong
- RE: Poll for adoption: draft-fang-l3vpn-end-syste… Ronald Bonica
- RE: Poll for adoption: draft-fang-l3vpn-end-syste… Richard Li
- Re: Poll for adoption: draft-fang-l3vpn-end-syste… Marco Rodrigues
- Re: Poll for adoption: draft-fang-l3vpn-end-syste… Loa Andersson
- Re: Poll for adoption: draft-fang-l3vpn-end-syste… Kireeti Kompella
- RE: Poll for adoption: draft-fang-l3vpn-end-syste… Jeffrey (Zhaohui) Zhang
- RE: Poll for adoption: draft-fang-l3vpn-end-syste… Xuxiaohu
- Re: Poll for adoption: draft-fang-l3vpn-end-syste… ningso
- RE: Poll for adoption: draft-fang-l3vpn-end-syste… Mach Chen
- RE: Poll for adoption: draft-fang-l3vpn-end-syste… Bitar, Nabil N
- 答复: Poll for adoption: draft-fang-l3vpn-end-syste… Haoweiguo
- Re: Poll for adoption: draft-fang-l3vpn-end-syste… Thomas Morin
- Re: Poll for adoption: draft-fang-l3vpn-end-syste… Luyuan Fang
- RE: Poll for adoption: draft-fang-l3vpn-end-syste… Luyuan Fang