Re: [Ianaplan] One more attempt at text (Re: Updated text Re: Please keep context in mind Re: Consensus call -- text reply for ICG proposal review)

"Patrik Fältström " <paf@frobbit.se> Tue, 25 August 2015 15:37 UTC

Return-Path: <paf@frobbit.se>
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 E4CCE1B2FAD for <ianaplan@ietfa.amsl.com>; Tue, 25 Aug 2015 08:37:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.961
X-Spam-Level:
X-Spam-Status: No, score=-1.961 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, 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 vUL4RHjvzT7t for <ianaplan@ietfa.amsl.com>; Tue, 25 Aug 2015 08:37:35 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.185]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 349A91B2F81 for <ianaplan@ietf.org>; Tue, 25 Aug 2015 08:37:35 -0700 (PDT)
Received: from [172.18.241.222] (w193-11-200-249.eduroam.sunet.se [193.11.200.249]) by mail.frobbit.se (Postfix) with ESMTPSA id AE1D120703 for <ianaplan@ietf.org>; Tue, 25 Aug 2015 17:37:33 +0200 (CEST)
From: Patrik Fältström <paf@frobbit.se>
To: Org <ianaplan@ietf.org>
Date: Tue, 25 Aug 2015 17:37:32 +0200
Message-ID: <5330B563-BA17-4574-AB6C-226FEC40F2F1@frobbit.se>
In-Reply-To: <A619F46842E0B3A5C0C9A9D4@JcK-HP8200.jck.com>
References: <A619F46842E0B3A5C0C9A9D4@JcK-HP8200.jck.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_D7BD9EE8-2B6A-488A-8995-554A109157A4_="; micalg="pgp-sha1"; protocol="application/pgp-signature"
X-Mailer: MailMate (1.9.2r5107)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/dOQgug5wCiOT1Kz1NQztzSkDmNs>
Subject: Re: [Ianaplan] One more attempt at text (Re: Updated text Re: Please keep context in mind Re: Consensus call -- text reply for ICG proposal review)
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 25 Aug 2015 15:37:37 -0000

All,

On top of what has been said let me urge the IETF to think carefully about the situation.

It is correct that the open consultation is something ICG has requested, the consultation include a number of specific questions, which all are related to the principles NTIA has put on the transition. Principles that are I think well founded in the multistakeholder environment we all live in. See paper from ISOC on the matter <http://www.internetsociety.org/doc/perspectives-iana-stewardship-transition-principles>. People can of course also in general make general comments on the proposal.

The proposal itself is built upon responses to an RFP that ICG did send to the three operational communities and each one have used whatever process they used to come up with the proposal. They have reached consensus and have submitted their portion of the combined proposal that now ICG have on the table.

Various pieces of the proposal of course matter to various degrees to the various operational communities and of course it is interesting to know, if it is possible to get, the view of the communities if the ICG compilation of the proposals are correct.

But there is a slippery slope here which I think make the situation difficult, which is where maybe this discussion is. It includes everything from difficulties from separating feedback and thoughts on each one of the OC's portion of the combined proposal to the actual combination action that ICG did. From whether the consensus reached in each one of the groups do or not impact the OC that comments to the question on whether the different view brought up was in the rough side of consensus of some other OC.

You can, as mr Hill notes, see his objections to the CWG proposal and the process that lead to it. You can also see the response from the chairs of the CWG. I am not to interpret what has been written by mr Hill and the chairs.

The response from the CWG chairs can be found here:

<http://mm.ianacg.org/pipermail/internal-cg_ianacg.org/2015-August/001334.html>

What I can say is that I urge people to be careful in this, as in all similar situations, where there might be a question whether one consensus process is investigating consensus in another consensus process. There is a difference between individuals/organisations having a view and consensus processes having a view. Should IETF have a view on the CWG process itself?

And as I think more than one person have written, regardless what is said by the IANAPLAN Operational Community (from ICG perspective), or IETF or...it is important to be careful with wording so that the processes still are as independent from each other as they are intended to be.

   Patrik Fältström
   Speaking personally
   But for disclosure: co-chair of ICG