Re: [GROW] Adrian Farrel's Discuss on draft-ietf-grow-irr-routing-policy-considerations-05: (with DISCUSS)

"Osterweil, Eric" <eosterweil@verisign.com> Tue, 03 March 2015 17:43 UTC

Return-Path: <eosterweil@verisign.com>
X-Original-To: expand-draft-ietf-grow-irr-routing-policy-considerations.all@virtual.ietf.org
Delivered-To: grow@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id C8ED21A1B7D; Tue, 3 Mar 2015 09:43:36 -0800 (PST)
X-Original-To: xfilter-draft-ietf-grow-irr-routing-policy-considerations.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-grow-irr-routing-policy-considerations.all@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A66AE1A1B6D for <xfilter-draft-ietf-grow-irr-routing-policy-considerations.all@ietfa.amsl.com>; Tue, 3 Mar 2015 09:43:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EBkxguv1UfNf for <xfilter-draft-ietf-grow-irr-routing-policy-considerations.all@ietfa.amsl.com>; Tue, 3 Mar 2015 09:43:35 -0800 (PST)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 762801A036E for <draft-ietf-grow-irr-routing-policy-considerations.all@ietf.org>; Tue, 3 Mar 2015 09:43:34 -0800 (PST)
Received: from mail-qg0-f100.google.com ([209.85.192.100]:47817) by zinfandel.tools.ietf.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.82_1-5b7a7c0-XX) (envelope-from <eosterweil@verisign.com>) id 1YSqqy-0006Ay-QS for draft-ietf-grow-irr-routing-policy-considerations.all@tools.ietf.org; Tue, 03 Mar 2015 09:43:34 -0800
Received: by mail-qg0-f100.google.com with SMTP id a108so1529242qge.3 for <draft-ietf-grow-irr-routing-policy-considerations.all@tools.ietf.org>; Tue, 03 Mar 2015 09:43:26 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:thread-topic:thread-index :date:message-id:references:in-reply-to:accept-language :content-language:content-type:mime-version; bh=pKRnRAZFv450VZxaSsbkQ/85ljuGaz98I6nsEZnlGm4=; b=DlNgYlPeDXGvFtuBVfNuXXDRsTf8qZPfPf3auWmDo+MEctMdFZ/XfbnqcA4bgmmCjI lvF7m5stuYZuCWged6vFWoiiuL+4yqz1CwjI40G36xeV4i17P+GumOzMilZAflt9jHXT OqS5GsgCDQuhp9zL1ET7OPpDdklBOgJoJ01XYhn8wcZSNCZls8KWHQtLYSfKItsWRdeX /Tm4xNXEOwWfStMTNgRqARUqlZpqoMYI/fci7iR7lYXn2F6udTuuMDDIsKvOOHhobVDV ridQlup3C9VTBJuwjhixgk6p/3C5OrOTp19DHkNaKibXaw5xz1BDng0OkiuPET/CjVWN Js1A==
X-Gm-Message-State: ALoCoQlfIPlfUwLud1VeeKWoAzIfG0N4AerUFoU5KVgjX5Iq5NSlIPO4wJSWvZdy4PSKhqdm3y4FUSwxH54E3MIqFn9+yPv01A==
X-Received: by 10.140.85.9 with SMTP id m9mr57260046qgd.7.1425404239903; Tue, 03 Mar 2015 09:37:19 -0800 (PST)
Received: from brn1lxmailout01.verisign.com (brn1lxmailout01.verisign.com. [72.13.63.41]) by mx.google.com with ESMTPS id by3sm385879qcb.4.2015.03.03.09.37.19 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 03 Mar 2015 09:37:19 -0800 (PST)
X-Relaying-Domain: verisign.com
Received: from brn1wnexcas02.vcorp.ad.vrsn.com (brn1wnexcas02 [10.173.152.206]) by brn1lxmailout01.verisign.com (8.13.8/8.13.8) with ESMTP id t23HbIMD015740 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 3 Mar 2015 12:37:18 -0500
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Tue, 3 Mar 2015 12:37:18 -0500
From: "Osterweil, Eric" <eosterweil@verisign.com>
To: "McPherson, Danny" <dmcpherson@verisign.com>
Thread-Topic: Adrian Farrel's Discuss on draft-ietf-grow-irr-routing-policy-considerations-05: (with DISCUSS)
Thread-Index: AQHQRO+Yknj4an+MoE6fehQxrDn49p0JNHgAgACDRoCAABC8gIABh+eAgAAnPgCAAAQOgA==
Date: Tue, 03 Mar 2015 17:37:02 +0000
Message-ID: <769262C6-427C-4C65-8834-102EC5B13DD5@verisign.com>
References: <20141218153246.28132.26429.idtracker@ietfa.amsl.com> <088101d044ac$449d2f40$cdd78dc0$@olddog.co.uk> <54D99234.5020305@bogus.com> <54F4085C.1050307@bogus.com> <D119DF53.16ACD%dmcpherson@verisign.com> <54F48485.1060906@bogus.com> <002a01d055c3$3df82280$b9e86780$@olddog.co.uk> <D11B5572.16C5E%dmcpherson@verisign.com>
In-Reply-To: <D11B5572.16C5E%dmcpherson@verisign.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.173.152.4]
Content-Type: multipart/signed; boundary="Apple-Mail=_A3BF3C61-F4EE-4C00-A440-8FC1250579E7"; protocol="application/pkcs7-signature"; micalg="sha1"
MIME-Version: 1.0
X-SA-Exim-Connect-IP: 209.85.192.100
X-SA-Exim-Rcpt-To: draft-ietf-grow-irr-routing-policy-considerations.all@tools.ietf.org
X-SA-Exim-Mail-From: eosterweil@verisign.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
Resent-To: draft-ietf-grow-irr-routing-policy-considerations.all@ietf.org
Resent-Message-Id: <20150303174334.762801A036E@ietfa.amsl.com>
Resent-Date: Tue, 03 Mar 2015 09:43:34 -0800
Resent-From: eosterweil@verisign.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/draft-ietf-grow-irr-routing-policy-considerations.all@tools/lgj0E3a1Qh09BWkalZB_hmwrogA>
Archived-At: <http://mailarchive.ietf.org/arch/msg/grow/71d6EEuJ2sxMFgQcZwxAx7VFl80>
X-Mailman-Approved-At: Tue, 03 Mar 2015 09:58:57 -0800
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "draft-ietf-grow-irr-routing-policy-considerations.all@tools.ietf.org" <draft-ietf-grow-irr-routing-policy-considerations.all@tools.ietf.org>, "grow-chairs@tools.ietf.org" <grow-chairs@tools.ietf.org>
Subject: Re: [GROW] Adrian Farrel's Discuss on draft-ietf-grow-irr-routing-policy-considerations-05: (with DISCUSS)
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Mar 2015 17:43:36 -0000

On Mar 3, 2015, at 12:24 PM, McPherson, Danny <dmcpherson@verisign.com> wrote:

> 
> 
> On 3/3/15, 10:03 AM, "Adrian Farrel" <adrian@olddog.co.uk> wrote:
> 
>> To be clear, these comments arrived during IETF last call and were well
>> circulated.
>> My Discuss is that the comments were not addressed in the normal way of
>> IETF
>> review comments. However, I offered to adopt the comments as my own and
>> let you
>> discuss them with me if you prefer.
>> 
>> RFC 7282 provides some hints on addressing comments and, as Joel has
>> noted,
>> addressing comments does not necessarily imply changing the document.
> 
> Yep, understood.
> 
>> I am sure, however, that if none of the currently listed document authors
>> has
>> the bandwidth to run through this process (which is perfectly fine, and
>> reflects
>> the fact that the IETF is not the only activity for many of us), the WG
>> chairs
>> will find it simple to appoint an additional editor to run through the
>> final
>> piece of the process. So the statement (which I choose to not interpret
>> as a
>> threat :-) that this document might never see the RFC Editor, is just
>> nonsense.
> 
> It was most certainly NOT a ³threat² - whatever that would mean as I don¹t
> really have an alternative go forward plan, the comments need to be
> addressed.  It was more an indication that someone finding the cycles to
> dig back into this and circulate received comments with the WG for
> reconsideration.  
> 
> It was simply an indication to the folks involved that the timelines
> conveyed yesterday weren¹t realistic for an array of reasons ‹ and perhaps
> a nudge to the current pen holder to allocate some cycles for this as
> appropriate.

I will get on this in the next 1-2 days.  Sorry for the delay, no need to add pens. ;)

Eric