Re: [Ianaplan] draft-ietf-ianaplan-icg-response moving to next step

"Richard Hill" <rhill@hill-a.ch> Fri, 28 November 2014 14:49 UTC

Return-Path: <rhill@hill-a.ch>
X-Original-To: ianaplan@ietfa.amsl.com
Delivered-To: ianaplan@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79D401A1ABE for <ianaplan@ietfa.amsl.com>; Fri, 28 Nov 2014 06:49:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.462
X-Spam-Level:
X-Spam-Status: No, score=-1.462 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, STOX_REPLY_TYPE=0.439] autolearn=no
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 BomTkcPpgcZn for <ianaplan@ietfa.amsl.com>; Fri, 28 Nov 2014 06:49:03 -0800 (PST)
Received: from smtp3.infomaniak.ch (smtp3.infomaniak.ch [IPv6:2001:1600:2:5:92b1:1cff:fe01:147]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE4CE1A1A6F for <ianaplan@ietf.org>; Fri, 28 Nov 2014 06:49:02 -0800 (PST)
Received: from Timea ([193.239.221.248]) (authenticated bits=0) by smtp3.infomaniak.ch (8.14.5/8.14.5) with ESMTP id sASEmqdH030184; Fri, 28 Nov 2014 15:48:52 +0100
Message-ID: <6AA8B855E1914295849E10F7E5410795@Timea>
From: "Richard Hill" <rhill@hill-a.ch>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>, "Marc Blanchet" <marc.blanchet@viagenie.ca>
References: <GLEAIDJPBJDOLEICCGMNIEMOCOAA.rhill@hill-a.ch> <99539C37-B970-490F-A7ED-9952CFDF1716@viagenie.ca> <547778AE.50302@gmail.com>
Date: Fri, 28 Nov 2014 15:48:56 +0100
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=original
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/XvsPQWGGaoeYkg_d4NMDeLHUtNI
Cc: "Ianaplan@Ietf. Org" <ianaplan@ietf.org>, "Leslie Daigle \(TCE\)" <ldaigle@thinkingcat.com>, Jari Arrko <jari.arkko@piuha.net>
Subject: Re: [Ianaplan] draft-ietf-ianaplan-icg-response moving to next step
X-BeenThere: ianaplan@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IANA Plan <ianaplan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ianaplan>, <mailto:ianaplan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ianaplan/>
List-Post: <mailto:ianaplan@ietf.org>
List-Help: <mailto:ianaplan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ianaplan>, <mailto:ianaplan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Nov 2014 14:49:05 -0000

Please see below.

Thanks and best,
Richard

----- Original Message ----- 
From: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
To: "Marc Blanchet" <marc.blanchet@viagenie.ca>
Cc: <rhill@hill-a.ch>ch>; "Ianaplan@Ietf. Org" <ianaplan@ietf.org>rg>; "Leslie 
Daigle (TCE)" <ldaigle@thinkingcat.com>om>; "Jari Arrko" <jari.arkko@piuha.net>
Sent: Thursday, November 27, 2014 8:17 PM
Subject: Re: [Ianaplan] draft-ietf-ianaplan-icg-response moving to next step


> On 28/11/2014 05:51, Marc Blanchet wrote:
>> Le 2014-11-27 à 03:57, Richard Hill <rhill@hill-a.ch> a écrit :
>>> I note that section 3 of RFC 7282 states:
>>>
>>> "The chair of a working group who is about to find that there is only 
>>> rough
>>> consensus is going to have to decide that not only has the working group
>>> taken the objection seriously, but that it has fully examined the
>>> ramifications of not making a change to accommodate it, and that the 
>>> outcome
>>> does not constitute a failure to meet the technical requirements of the
>>> work. ... A valid justification needs to me [sic] made."
>>>
>>> Therefore, I would request that the co-chairs provide a justification 
>>> for
>>> the conclusion that rough consensus has been achieved.
>>
>> While the shepherd writeup is not to justify, the writeup that was 
>> recently submitted summarize it.
>>
>> https://datatracker.ietf.org/doc/draft-ietf-ianaplan-icg-response/shepherdwriteup/
>
> Speaking as a process pedant, I would like to point out that
> RFC 7282 is Informational, so that use of "needs" is not actually
> a normative requirement of the standards process.

Yes, the status of the RFC is Informational, and, as far as I can tell, that 
reflects its content, which is not normative.

However, I presume that the RFC does correctly describe best practices and 
so it does describe the process that should be followed.

>
> Also, the text Richard elided ends thus:
>
> "...the chair must use their judgement in these cases.  What can't happen
>   is that the chair bases their decision solely on hearing a large
>   number of voices simply saying, "The objection isn't valid."  That
>   would simply be to take a vote.  A valid justification needs to [be]
>   made."
>
> Now, that passive tense is a bit confusing, but to my eyes it refers
> to the fact that the chair(s) should make a judgement about validity 
> rather
> than counting votes.

That is also my understanding.

>Anyway, I believe that the paragraph in the writeup
> that starts "There was a broad suggestion..." does justify the chairs'
> judgement.

>From my point of view, that is a description of what happened, not a 
justification for the decision.

I will be sending separately my comments on the writeup, but, again, it does 
not appear to me to be a justification.

>
>   Brian
>
>
>