IETF Logo Mail Archive

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

Byron Ellacott <bje@apnic.net> Wed, 12 December 2012 04:48 UTC

Return-Path: <bje@apnic.net>
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 2DD1521E80BE for <sidr@ietfa.amsl.com>; Tue, 11 Dec 2012 20:48:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.557
X-Spam-Level:
X-Spam-Status: No, score=0.557 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, RELAY_IS_203=0.994]
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 BMQjelS6Fnsn for <sidr@ietfa.amsl.com>; Tue, 11 Dec 2012 20:48:58 -0800 (PST)
Received: from ao-mailgw.apnic.net (ao-mailgw.apnic.net [IPv6:2001:dd8:b:98::120]) by ietfa.amsl.com (Postfix) with SMTP id 8455321E80BA for <sidr@ietf.org>; Tue, 11 Dec 2012 20:48:53 -0800 (PST)
Received: from IAMDA1.org.apnic.net (unknown [203.119.101.249]) by ao-mailgw.apnic.net (Halon Mail Gateway) with ESMTP; Wed, 12 Dec 2012 14:46:35 +1000 (EST)
Received: from NXMDA1.org.apnic.net ([fe80::c877:49c3:86f7:9d67]) by IAMDA1.org.apnic.net ([fe80::d35:7ac6:ff34:45a%19]) with mapi id 14.01.0421.002; Wed, 12 Dec 2012 14:48:42 +1000
From: Byron Ellacott <bje@apnic.net>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Thread-Topic: [sidr] Reboot: questions regarding WG acceptance of draft-ymbk-rpki-grandparenting-02
Thread-Index: AQHN1JuKCN3qJcxTsUiiFTXDmlj7rJgT9w+A
Date: Wed, 12 Dec 2012 04:48:42 +0000
Message-ID: <80B399CE-2539-43D5-832B-A5607BB23444@apnic.net>
References: <50C21F2E.6000708@isode.com>
In-Reply-To: <50C21F2E.6000708@isode.com>
Accept-Language: en-AU, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [2001:dc0:a000:4:6071:2e8e:1049:c42e]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <25618822EE705F4CAC5D8CCBD3844F13@apnic.net>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: sidr wg <sidr@ietf.org>
Subject: Re: [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: Wed, 12 Dec 2012 04:48:59 -0000

Hi Alexey,

These questions seem reasonable to me.  Did you want answers now, too?

  Byron

On 08/12/2012, at 2:54 AM, Alexey Melnikov <alexey.melnikov@isode.com> wrote:

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

v2.23.0 | Report a Bug | By Email