Re: [sidr] Poll: WG acceptance of draft-ymbk-rpki-grandparenting-02

Alexey Melnikov <alexey.melnikov@isode.com> Thu, 10 January 2013 17:05 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 218D821F89CB for <sidr@ietfa.amsl.com>; Thu, 10 Jan 2013 09:05:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.289
X-Spam-Level:
X-Spam-Status: No, score=-102.289 tagged_above=-999 required=5 tests=[AWL=0.310, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gUXKtclZ+r4V for <sidr@ietfa.amsl.com>; Thu, 10 Jan 2013 09:05:34 -0800 (PST)
Received: from waldorf.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id 208FB21F8945 for <sidr@ietf.org>; Thu, 10 Jan 2013 09:05:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1357837530; d=isode.com; s=selector; i=@isode.com; bh=GsPMkuj/HvRFuRBBnRVX/1Echp2W6epGS6yfDSfZeeU=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=vxZawFUkCVAoJSLmq+QvCPboXSJHq7YtCMrFjZYtnR/a2jLInyMvQH56A44W3SzusuXM6f WffOB42Dm0SK6+UXzGXRZnQtBnbcBeSEzeYocoqH6omtlGW9ZcGzKzKbAH7VouQOTsHkUX pqrpk+bW6gX42k09CU7wPYut2lnmIEs=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250]) by waldorf.isode.com (submission channel) via TCP with ESMTPA id <UO702gB1sFZA@waldorf.isode.com>; Thu, 10 Jan 2013 17:05:30 +0000
Message-ID: <50EEF4F6.4070903@isode.com>
Date: Thu, 10 Jan 2013 17:05:58 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
To: sidr wg <sidr@ietf.org>
References: <50C8E17D.3090507@isode.com>
In-Reply-To: <50C8E17D.3090507@isode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [sidr] Poll: WG acceptance of draft-ymbk-rpki-grandparenting-02
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sidr>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Jan 2013 17:05:35 -0000

On 12/12/2012 19:56, Alexey Melnikov wrote:
> Dear WG participants,
>
> I would like to initiate 2+ weeks poll (ending on December 31st 2012)
Although the poll has ended last year, there was a suggestion to extend 
it. If you want to express your opinion, but haven't done so yet, can 
you please do that by the end of Sunday, January 13th. Or at least email 
me directly if you think you need more time.

Thanks,
Alexey
> regarding acceptance of draft-ymbk-rpki-grandparenting-02.txt. Please 
> reply to questions listed below. Send your replies to the mailing list 
> or directly to WG chairs <sidr-chairs@tools.ietf.org>. I would like to 
> avoid extended discussions of technical issues at this time, as I 
> think people already made up their minds. However including pointers 
> to earlier discussions is fine.
>
> Alexey,
> on behald of SIDR chairs.
>
> ----------------
>
> 1) Is the problem described/solved by 
> draft-ymbk-rpki-grandparenting-02 actually a problem that the WG needs 
> to address? (Answer: yes or no. Additional information is welcomed, 
> but I don't want people to repeat the whole discussion.)
>
> 2) If you answered "yes" to the question #1, please also answer the 
> following question:
>
> Is draft-ymbk-rpki-grandparenting-02 a reasonable starting point to 
> become a WG document? Please choose one of the following:
>
>
> a) Ready for Adoption (whether or not you have some specific issues 
> with it. Also, this answer is unrelated to whether this should be a 
> separate draft or a part of an existing draft).
>
> b) Needs more work BEFORE Adoption
>
> c) Should not be adopted. In particular this mean that you don't 
> believe any amount of work on the proposed draft will address your 
> issues. So any solution to this problem should be a new draft written 
> from scratch.
>
> d) Abstain/don't care
>
>
> 3) If you answered "a" or "b" above, please also answer the following 
> question:
>
> Does this need to be in a standalone draft, or can it be incorporated 
> into another existing WG draft? When answering this question please 
> only base your answer on technical reasons, in particular please leave 
> the decision on who is going to edit the document (if it is 
> standalone) to WG chairs.