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

"Richard Hill" <rhill@hill-a.ch> Fri, 28 November 2014 14:52 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 834CB1A0013 for <ianaplan@ietfa.amsl.com>; Fri, 28 Nov 2014 06:52:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.062
X-Spam-Level:
X-Spam-Status: No, score=-0.062 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, 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 SqMvUNdgSXP8 for <ianaplan@ietfa.amsl.com>; Fri, 28 Nov 2014 06:52:56 -0800 (PST)
Received: from smtp4.infomaniak.ch (smtp4.infomaniak.ch [IPv6:2001:1600:2:5:92b1:1cff:fe01:18cc]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 95EFF1A1ABF for <ianaplan@ietf.org>; Fri, 28 Nov 2014 06:52:53 -0800 (PST)
Received: from Timea ([193.239.221.248]) (authenticated bits=0) by smtp4.infomaniak.ch (8.14.5/8.14.5) with ESMTP id sASEqoiM009070; Fri, 28 Nov 2014 15:52:51 +0100
Message-ID: <4286E3466C7A45F89D5D1395B5222FF1@Timea>
From: "Richard Hill" <rhill@hill-a.ch>
To: "John Curran" <jcurran@istaff.org>
References: <GLEAIDJPBJDOLEICCGMNIEMOCOAA.rhill@hill-a.ch> <4A087055-EF5B-4BC7-BA25-3CBA7256BDC4@istaff.org>
Date: Fri, 28 Nov 2014 15:52:53 +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/hqS_ak8n4ySzPfw_hyvpUgKeGfA
Cc: Marc Blanchet <marc.blanchet@viagenie.ca>, Jari Arkko <jari.arkko@piuha.net>, ianaplan@ietf.org
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:52:57 -0000

Please see below.

Thanks and best,
Richard

----- Original Message ----- 
From: "John Curran" <jcurran@istaff.org>
To: <rhill@hill-a.ch>
Cc: "Marc Blanchet" <marc.blanchet@viagenie.ca>ca>; <ianaplan@ietf.org>rg>; "Jari 
Arkko" <jari.arkko@piuha.net>
Sent: Friday, November 28, 2014 12:39 AM
Subject: Re: [Ianaplan] draft-ietf-ianaplan-icg-response moving to next step


> On Nov 27, 2014, at 3:57 AM, Richard Hill <rhill@hill-a.ch> wrote:
>>
>> 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.
>
> There was one potentially significant concern raised in WG last call that
> was not accommodated - specifically adding a requirement for strengthened
> legal and contractual IANA arrangements for the post-NTIA period.

Yes.  And there was also another concern raised, namely a requirement that a 
legally binding document be developed, if, after legal analysis, it was 
found that the current MoU is not a legally binding document.

>The draft
> does doesn't preclude stronger legal/contractual measures, but it also 
> does
> not note such as a specific requirement for future IANA arrangements.
>
> Adding stronger legal/contractual arrangements as a requirement was 
> discussed
> at length, and it was apparent that accommodating that change in the 
> document
> would actually reduce the level of consensus due to the much higher 
> support
> for the current text as well as concerns that the change would run 
> contrary
> to existing IETF practices for handling of external agreements.
>
> One might argue that the resulting draft does not meet the ICG response
> requirements (i.e. “Description of any legal framework requirements in the
> absence of the NTIA contract” per 'Section V. Transition Implications'),
> but transition implications are only required to be per the viewpoint of
> the IETF community, and the proposed text already notes that "No major
> changes are required."
>
> All in all, the determination of rough consensus by the WG chairs seems
> quite appropriate.

I do appreciate your view (and that of others) that rough consensus was 
achieved, but I would still like to see the co-chairs justification for 
their decision.

>
> /John
>
> Disclaimer: My views alone.
>
>
>
>
>