Re: [Ianaplan] it's more than that

Olivier MJ Crepin-Leblond <ocl@gih.com> Tue, 05 May 2015 10:30 UTC

Return-Path: <ocl@gih.com>
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 78AA91A8895 for <ianaplan@ietfa.amsl.com>; Tue, 5 May 2015 03:30:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 TSTB_93orQK2 for <ianaplan@ietfa.amsl.com>; Tue, 5 May 2015 03:30:28 -0700 (PDT)
Received: from waikiki.gih.co.uk (salsa.gih.co.uk [IPv6:2a00:19e8:10:5::b]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D3461A8894 for <ianaplan@ietf.org>; Tue, 5 May 2015 03:30:25 -0700 (PDT)
Received: from waikiki.gih.co.uk (localhost6.localdomain6 [IPv6:::1]) by waikiki.gih.co.uk (Postfix) with ESMTP id 0EF6918F3B5; Tue, 5 May 2015 11:30:11 +0100 (BST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gih.com; h=message-id:date :from:mime-version:to:subject:references:in-reply-to :content-type; s=mahalo1; bh=S1CuZ/N5QrpwcrWhhcACI7Z26CY=; b=wml 1HnmQTtLA/j2UhCeMQQSdTX+FHpQSdwMTtFrsQY5HoRVuBfonodk44b1kOjIKCkx ghPijxUGjRUwQAOL54M1K7txIDcEKasGlIujFqgMq/YWWWsaAXWDh2Y0biYb2tTN C5oFW60SjZWhu8qzYZXTWSp1VNmA6MaWq+bviTtw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gih.com; h=message-id:date :from:mime-version:to:subject:references:in-reply-to :content-type; q=dns; s=mahalo1; b=DC/NMroYrUtIxgJjbEoXPq8sQJDsG PKyo1DkBWE6NMLx5DxP6/VgNwGoGbUq/jRkhlo5514Q5eTEGh71sqbtVpjz653dl a5StLEVQ0eOT0A1+j5KXuhxfnoqm6NHxmCz87n43giWd9ulVSCQgIbsjwpQSlQgX lHk+qjOXOJuEuA=
Received: from [192.168.1.18] (ANice-651-1-252-37.w86-205.abo.wanadoo.fr [86.205.36.37]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by waikiki.gih.co.uk (Postfix) with ESMTPSA id 328EC18F3AF; Tue, 5 May 2015 11:30:10 +0100 (BST)
Message-ID: <55489BBD.1060000@gih.com>
Date: Tue, 05 May 2015 12:30:21 +0200
From: Olivier MJ Crepin-Leblond <ocl@gih.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Eliot Lear <lear@cisco.com>, ianaplan@ietf.org
References: <20150503214102.33356.qmail@ary.lan> <55474334.50208@gih.com> <8e2e7aa8c7cf4241ba399c6febaf1226@EX13-MBX-13.ad.syr.edu> <5547EB42.2080904@gih.com> <55484B68.7000808@cisco.com>
In-Reply-To: <55484B68.7000808@cisco.com>
Content-Type: multipart/alternative; boundary="------------030601030405080205020507"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/h6QuLa9KAfn4qduqgz1UIFUCHuY>
Subject: Re: [Ianaplan] it's more than that
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: Tue, 05 May 2015 10:30:31 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
Dear Eliot,
Everyone,

again -- I am in full agreement with you. I also wish that everyone here
stopped being so defensive.

As a representative of Internet End Users, I would like this Stewardship
transition to happen smoothly and to serve the public interest above
everything else. When I hear allegations of a "problem", I want to bring
this up to colleagues in the ICANN Community and for the Chairs of the
Naming Issues WG to query ICANN Management's alleged actions, especially
in a process which is sitting firmly in the hands of the ICANN
Community, as NTIA has asked.

Everything else is just, IMHO, interference. So unless I know the origin
of the "problem", how do you want me to ask the ICANN Community -
members of the CWG IANA - to reach and ask ICANN Management for an
explanation?

I am not interested in tabloid style articles that are there to put
ICANN down as an organisation or to entertain the polemic about ICANN
being rogue or whatever other allegation designed to leverage political
influence. Likewise, I also think that the multistakeholder model which
we have in ICANN is a very unique animal that needs to be both preserved
and improved and that will not happen by kicking it to the ground. The
only thing that could be achieved right now if we start to kick any
component part of the IANA Stewardship transition process, whether
within ICANN, CRISP, IETF, is that it will discredit everyone; it will
discredit the multistakeholder model of governance on the Internet. It
will play in favour of governments who want full control of the
Internet. It will play in favour of supporters of a top down model of
governance that wants to kill what we have today - and I am not ready to
let that go. (if you think this is FUD, think again - the reality is
that this is what is on our doorstep)

So instead of bickering about who said what and making a lot of noise
about it, why don't we work together to fix things? The ICANN community
in charge of building a Stewardship Transition proposal has the ability
to complain to ICANN about ICANN management actions, but it can only do
that if information like "who said what", "in what context", and "under
what authority" --- and then we'll all be able to operate according to
the principles of transparency set promoted by ARIN in
<https://www.arin.net/participate/meetings/reports/ARIN_35/PDF/wednesday/curran_transition.pdf>

Kind regards,

Olivier
(own views)

On 05/05/2015 06:47, Eliot Lear wrote:
> Olivier,
>
> On 5/4/15 11:57 PM, Olivier MJ Crepin-Leblond wrote:
>> Unsubstantiated. Again - I'd like to see the note. This has all of the
>> favours of crying wolf without the actual note.
>
> When the many people that consists of the IAOC, IAB, IESG, and ARIN
> boards and at least some of the ICG and CRISP teams speak up, that tells
> you that this is not a person crying wolf, but a chorus of concern.
>
>>  If substantiated, then
>> it's another matter, but how do you want *any* progress to be made if
>> we're discussing allegations out of a presentation without an actual
>> source as to who said what. Was that meeting conducted under Chatham
>> House rules? If so, why? Why not an open, transparent meeting, in which
>> case someone could publicly say who said what?
>> I would appreciate the clarification either way.
>
> What I want is something simpler: going forward, ICANN and the IANA
> customers bring forth questions to the communities before they rise to
> the level of even a concern.  I'd also hope that NTIA monitors these
> discussions so that when their name is used, especially by responsible
> people at ICANN, they can provide clarification where necessary.  Here
> (at least to me) it seems it would be helpful.
>
>     Eliot
>
>
>
>

- -- 
Olivier MJ Crépin-Leblond, PhD
http://www.gih.com/ocl.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
 
iQIcBAEBAgAGBQJVSJu9AAoJEFTSJAeQq33t1goQALRDNrosEdJExyb3Uiyua/gN
mQ5oai4e2vw0wSARqkC0mJ5MWZq5M4b7aael8kSTF+tQtRTuhfUQOaSKj6tsaL6v
bz8IgvUybmCqhjTTRnllxjMJT55zeGMB8IbAEgT150EohfrWtfMI+xJytOdWpcgX
pik+2Rv8ME1K33XJWjYl0QP0+LmzTTMSMVRsNkJ6mXeJd7GYAXfBvRQDE0rBO2l8
VJLqcVCcOpmbAU6H8S3zG5aWwS1N3vdd3kqQ1iLJWQ/pioekrlvnWV8xY1T/17/i
z8MeS7PvFoBc5m/Lf7h0q6tzXVXTTxVfwsB5TH2STuNVc9lCI9SFnvg26wZ1nlFg
v2I34vsV+0QZCALwdp7nLBCnXSzVGCR5s7ESYcwTDGrh3mKGbUMmg32q0RFQG16w
V2IMzkQU9Deq2A1ZRuwWzPyTtZZmKP3zFP7zvfDC6XeprRw7VDhez7Oj10cAZ5hi
tE2sqi0iR8IcI2t1REvCfSlKDsBfTP4DIfBc6sE/aC1QbBnAcDvOd8wYRi+35PHh
aDQ0QUNvkvU+xWi6gOPliJ7//Yo9DlpJUJ6XcSyY+ik5TlwxnTVEre6PKM+4ZQeO
hH2JQfIXB5dHigy6CICDkqvqxTKKcAjynFN4rrOg8IUH/yuuvFB6D7pSiJgD+Rbx
En1RXHLNCNAocP1cBXd0
=hzZg
-----END PGP SIGNATURE-----