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

"George, Wes" <wesley.george@twcable.com> Wed, 19 December 2012 16:08 UTC

Return-Path: <wesley.george@twcable.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 3993421F8598 for <sidr@ietfa.amsl.com>; Wed, 19 Dec 2012 08:08:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.548
X-Spam-Level:
X-Spam-Status: No, score=-0.548 tagged_above=-999 required=5 tests=[AWL=-0.085, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
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 y5x7jxSfiZB0 for <sidr@ietfa.amsl.com>; Wed, 19 Dec 2012 08:08:48 -0800 (PST)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id A22D621F8586 for <sidr@ietf.org>; Wed, 19 Dec 2012 08:08:48 -0800 (PST)
X-SENDER-IP: 10.136.163.11
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.84,318,1355115600"; d="scan'208";a="670053"
Received: from unknown (HELO PRVPEXHUB02.corp.twcable.com) ([10.136.163.11]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 19 Dec 2012 11:08:43 -0500
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.78]) by PRVPEXHUB02.corp.twcable.com ([10.136.163.11]) with mapi; Wed, 19 Dec 2012 11:08:47 -0500
From: "George, Wes" <wesley.george@twcable.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>, sidr wg <sidr@ietf.org>
Date: Wed, 19 Dec 2012 11:08:55 -0500
Thread-Topic: [sidr] Poll: WG acceptance of draft-ymbk-rpki-grandparenting-02
Thread-Index: Ac3YpKthvwn2V5zSS+2VimnbjmekHAFXOhZQ
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD5923033A3B3E2B@PRVPEXVS15.corp.twcable.com>
References: <50C8E17D.3090507@isode.com>
In-Reply-To: <50C8E17D.3090507@isode.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Wed, 19 Dec 2012 16:08:49 -0000

>
> 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.)
[WEG] yes, but I tend to agree that it's not a technical problem.
>
> 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
[WEG] b. The text itself is ok, but we need to resolve #3 before adoption.
>
>
> 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.
[WEG] It needs to be incorporated into an existing draft.
This text is covering a very specific gotcha with some helpful recommendations and no actual requirements. It currently reads like an orphaned section of another draft, probably the operational considerations (origin-ops) draft.


This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.