IETF Logo Mail Archive

Re: [sidr] WG acceptance call for draft-ymbk-rpki-grandparenting

Andy Newton <andy@arin.net> Thu, 08 November 2012 14:39 UTC

Return-Path: <andy@arin.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 5721E21F8ADD for <sidr@ietfa.amsl.com>; Thu, 8 Nov 2012 06:39:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 adsq8cq+CqEJ for <sidr@ietfa.amsl.com>; Thu, 8 Nov 2012 06:39:21 -0800 (PST)
Received: from smtp2.arin.net (smtp2.arin.net [IPv6:2001:500:4:13::32]) by ietfa.amsl.com (Postfix) with ESMTP id AE75A21F8A65 for <sidr@ietf.org>; Thu, 8 Nov 2012 06:39:21 -0800 (PST)
Received: by smtp2.arin.net (Postfix, from userid 323) id 30B8121366D; Thu, 8 Nov 2012 09:39:21 -0500 (EST)
Received: from CHAXCH05.corp.arin.net (chaxch05.corp.arin.net [192.149.252.94]) by smtp2.arin.net (Postfix) with ESMTP id A034D2135A0; Thu, 8 Nov 2012 09:39:20 -0500 (EST)
Received: from CHAXCH03.corp.arin.net (10.1.30.17) by CHAXCH05.corp.arin.net (192.149.252.94) with Microsoft SMTP Server (TLS) id 14.2.283.3; Thu, 8 Nov 2012 09:39:01 -0500
Received: from CHAXCH02.corp.arin.net ([169.254.2.182]) by CHAXCH03.corp.arin.net ([10.1.30.17]) with mapi id 14.02.0318.004; Thu, 8 Nov 2012 09:38:12 -0500
From: Andy Newton <andy@arin.net>
To: "Murphy, Sandra" <Sandra.Murphy@sparta.com>, Christopher Morrow <morrowc.lists@gmail.com>
Thread-Topic: [sidr] WG acceptance call for draft-ymbk-rpki-grandparenting
Thread-Index: AQHNcmy8FCcE8Dzhaka0MZcJTJP7npdxX+YAgAAMpICAAEYPAIBEvmMAgARaKACAJYJGAIAAG/SAgABtkoD//8GOgA==
Date: Thu, 08 Nov 2012 14:38:12 +0000
Message-ID: <CCC12BF9.E7AB%andy@arin.net>
In-Reply-To: <24B20D14B2CD29478C8D5D6E9CBB29F63B6E9BFB@Hermes.columbia.ads.sparta.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.2.4.120824
x-originating-ip: [192.149.252.97]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4916817E2423CE4689722A0597413FD8@corp.arin.net>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "sidr@ietf.org" <sidr@ietf.org>
Subject: Re: [sidr] WG acceptance call for draft-ymbk-rpki-grandparenting
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, 08 Nov 2012 14:39:22 -0000

On 11/8/12 8:21 AM, "Murphy, Sandra" <Sandra.Murphy@sparta.com> wrote:

>>the author of the document did not engage in the
>>discussion
>
>As Yakov was fond of saying, "send text".  Authors of wg drafts are
>supposed to represent consensus.

If this is true, then the current document should be blank since it does
not represent consensus.

Also are you now saying that the author does not need to participate in
the discussion since he can now only represent consensus decisions? If so,
that would mean the author of this draft has been able to completely avoid
addressing any of the issues raised. That strikes me as not being the IETF
way.

>
>A topic that generates a fire storm of discussion has a good chance.
>Nothing like actively working on a topic to demonstrate interest in
>working on the topic.

Thank you for clarifying this. For confirmation, in the future any draft
put forward to SIDR that generates "interest" but not necessarily rough
consensus will be admitted as a working group document. Is that correct?

-andy

v2.23.0 | Report a Bug | By Email