Re: [Ianaplan] last call and IESG processing summary for draft-ietf-ianaplan-icg-response

Jari Arkko <jari.arkko@piuha.net> Tue, 30 December 2014 23:01 UTC

Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A2A71A897D; Tue, 30 Dec 2014 15:01:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.79
X-Spam-Level:
X-Spam-Status: No, score=0.79 tagged_above=-999 required=5 tests=[BAYES_50=0.8, T_RP_MATCHES_RCVD=-0.01] 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 8rlNbrx6fIg1; Tue, 30 Dec 2014 15:01:29 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2a00:1d50:2::130]) by ietfa.amsl.com (Postfix) with ESMTP id 9DED11A8979; Tue, 30 Dec 2014 15:01:28 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 220102CC61; Wed, 31 Dec 2014 01:01:26 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 77B_rBlaLgzJ; Wed, 31 Dec 2014 01:01:23 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id CF9C82CC4D; Wed, 31 Dec 2014 01:01:22 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Subject: Re: [Ianaplan] last call and IESG processing summary for draft-ietf-ianaplan-icg-response
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_7C8D7483-33C4-4A4F-902E-BF24A5457434"; protocol="application/pgp-signature"; micalg=pgp-sha512
From: Jari Arkko <jari.arkko@piuha.net>
X-Priority: 3 (Normal)
In-Reply-To: <GLEAIDJPBJDOLEICCGMNEEICCPAA.rhill@hill-a.ch>
Date: Wed, 31 Dec 2014 00:01:19 +0100
Message-Id: <32BF2478-B707-47BF-9A6F-C55FB4BEFF6E@piuha.net>
References: <GLEAIDJPBJDOLEICCGMNEEICCPAA.rhill@hill-a.ch>
To: rhill@hill-a.ch
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/mrowdKIjSZGPovYV1nK03wgLL2w
Cc: "Ianaplan@Ietf. Org" <ianaplan@ietf.org>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Dec 2014 23:01:33 -0000

Richard,

(I am copying once again your e-mail at the end, in case
it didn’t  otherwise make it to the list archives.)

First, I wanted to say that I agree with Andrew said. 

Secondly, I wanted to assure you that your opinion
and comments are on record, have been noted and 
thought about, even in those cases where we did not 
say anything specific about them. Your specific
issue in this case was brought up in the IESG
discussion, for instance. Thanks for the feedback.

The summary that I sent (or any other similar
messages) should not be taken as a detailed list 
of everything that went on. They are high-level 
summaries, and written in my words, characterising
the situation as I see it. They are beneficial as
brief explanations, but the real record is the detailed 
discussions, e.g, on the list.

But I can change my summary to read:

"Discussion of the rationale for concluding rough 
consensus from Richard Hill (responses from Marc 
Blanchet, Andrew Sullivan, Milton Muller, Jari Arkko, 
Brian Carpenter, John Curran, and Jefsey). Richard 
was requesting a justification (beyond information
already available) for why the conclusion was what
it was, and deferring the IESG decision."

For what it is worth, I think there was certainly 
enough information in the thread labeled 
"draft-ietf-ianaplan-icg-response moving to next step”,
the shepherd writeup, and of course as well in the 
overall process that the working group went through.

Jari

---

Original message from Richard:

>> Thanks for your note. (Reproduced at the end of this e-mail for
>> the benefit of
>> others, just in case we still have an issue with the list not
>> accepting your
>> e-mails. I apologize for the trouble on that, by the way.)
>> 
>> I wanted to acknowledge the reception of your note, and the
>> reception of the
>> earlier requests, including the one requesting the co-chairs to
>> provide (further)
>> justification for their conclusions.
> 
> Since you say "further justification", it seems that I missed something,
> because I don't recall seeing the justification from the co-chairs for the
> rough consensus call.  Perhaps you could point me to it?
> 
>> I also wanted to say that those were
>> considered as a part of the process. A big part of the IESG’s role in
>> approving output from the IETF is making sure that the community
>> has been heard and that there’s broad backing for the particular output.
>> In this case the IESG has been comfortable with the making the decision
>> it has made, having considered the community discussions, including
>> your request.
> 
> I don't recall seeing any statement from any IESG member to the effect that
> he or she had considered my request not to proceed to approve the draft
> until the co-chairs had provided a justification for the rough consensus
> call.  Perhaps I missed some relevant statements explaining why my request
> was considered but rejected.
> 
>> Personally, I am quite comfortable with the decisions in
>> the WG and IESG stages, and believe that they reflect community
>> (rough) consensus.
>> 
>> Hope this helps,
> 
> See above.
> 
> And please note that the changes I requested to the sheperd write-up with
> respect to my statements have not been made (see below), so that write-up
> does not correctly reflect what I said during the disussions.
> 
>> 
>> Jari
>> 
>>>> At the end of the working group process, although there was not
>>>> unanimous support for the results, the working group chairs
>>>> concluded that rough consensus existed in the working group. The
>>>> document shepherd’s summary of the WG consensus for this document
>>>> can be found here:
>>>> 
>>>> 
>>>> https://datatracker.ietf.org/doc/draft-ietf-ianaplan-icg-response/
>>>> shepherdwriteup/
>>> 
>>> Please add that I requested that changes be made to that
>> writeup so as to
>>> reflect correctly my statements.
>>> 
>>> SNIP
>>> 
>>>> 
>>>> 	• Discussion of the rationale for concluding rough
>>>> consensus from Richard Hill (responses from Marc Blanchet, Andrew
>>>> Sullivan, Milton Muller, Jari Arkko, Brian Carpenter, John
>>>> Curran, and Jefsey).
>>> 
>>> Please correct that to state that I requested that the
>> co-chairs provide a
>>> justification for the rough consensus call.  Unless I missed
>> something, the
>>> co-chairs did not provide that justification.
>>> 
>>>> Richard was requesting a rationale for why
>>>> the conclusion was what it was, or perhaps rather disagreeing
>>>> with the rationale that was provided.
>>> 
>>> No, I was requesting a justification of the rough consensus call.
>>> 
>>> SNIP
>>> 
>>>> 
>>>> 	• The IAOC has indicated that they are comfortable with the
>>>> direction the document gives for the IAOC.
>>> 
>>> Please add here (or wherever else you think it would fit):
>>> 
>>> * Richard Hill requested that the IESG defer its decision on this draft
>>> until the submission by the co-chairs of their justification
>> for the rough
>>> consensus call.
>> 
>> 
>> 
> 
> _______________________________________________
> Ianaplan mailing list
> Ianaplan@ietf.org
> https://www.ietf.org/mailman/listinfo/ianaplan