[sidr] Reboot: questions regarding WG acceptance of draft-ymbk-rpki-grandparenting-02

Alexey Melnikov <alexey.melnikov@isode.com> Fri, 07 December 2012 16:53 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 80CCD21F86F7 for <sidr@ietfa.amsl.com>; Fri, 7 Dec 2012 08:53:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.504
X-Spam-Level:
X-Spam-Status: No, score=-102.504 tagged_above=-999 required=5 tests=[AWL=0.095, 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 kVdaI3v+ubCL for <sidr@ietfa.amsl.com>; Fri, 7 Dec 2012 08:53:49 -0800 (PST)
Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id AA3F221F86CD for <sidr@ietf.org>; Fri, 7 Dec 2012 08:53:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1354899228; d=isode.com; s=selector; i=@isode.com; bh=X8cK9yDZ0fI03v9A0meIhbpMN4/mup0J3bQjmCpDUm8=; 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=v+rzUCm+SPoR6c+XMtfFfdTIV7Wgnrjjqw0as+9L0z2uZKRvKR2GV8nm5WqUB3IapT8UcU qXFXkXbAZyoxiOqmd0HZjwZMe54efJn9s5XAJPsga1cQo9TJnk3siV/ipaRvPOnjjkizu2 tOyguDV7PfX+opT4p+Ez5uAbhQzL0os=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250]) by statler.isode.com (submission channel) via TCP with ESMTPA id <UMIfGwBEKEdp@statler.isode.com>; Fri, 7 Dec 2012 16:53:48 +0000
Message-ID: <50C21F2E.6000708@isode.com>
Date: Fri, 07 Dec 2012 16:54:06 +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>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [sidr] Reboot: questions regarding 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: Fri, 07 Dec 2012 16:53:50 -0000

Hi,
Sorry for procrastinating on this for so long.

Here are questions I would like to ask WG participants. At this point I 
would like to ask people to review the questions and let me know if you 
think they are contradictory. If they are clear, I will poll the WG 
early next week. Comments on the mailing list or sent directly to WG 
chairs <sidr-chairs@tools.ietf.org> are welcome.

----------------

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.