Re: [Ianaplan] What's happening at ICANN?

"Soininen, Jonne (Nokia - FI/Espoo)" <jonne.soininen@nokia.com> Sat, 10 October 2015 16:57 UTC

Return-Path: <jonne.soininen@nokia.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 1E4AE1B412C for <ianaplan@ietfa.amsl.com>; Sat, 10 Oct 2015 09:57:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_HI=-5, 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 73AgA8CKX3qA for <ianaplan@ietfa.amsl.com>; Sat, 10 Oct 2015 09:57:24 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A0AA1B412B for <ianaplan@ietf.org>; Sat, 10 Oct 2015 09:57:24 -0700 (PDT)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd001.nsn-inter.net (8.15.2/8.15.2) with ESMTPS id t9AGvL1f012525 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 10 Oct 2015 16:57:22 GMT
Received: from DEMUHTC003.nsn-intra.net ([10.159.42.34]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id t9AGvLAu002550 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 10 Oct 2015 18:57:21 +0200
Received: from DEMUHTC010.nsn-intra.net (10.159.42.41) by DEMUHTC003.nsn-intra.net (10.159.42.34) with Microsoft SMTP Server (TLS) id 14.3.248.2; Sat, 10 Oct 2015 18:57:21 +0200
Received: from DEMUMBX010.nsn-intra.net ([169.254.10.102]) by DEMUHTC010.nsn-intra.net ([10.159.42.41]) with mapi id 14.03.0248.002; Sat, 10 Oct 2015 18:57:21 +0200
From: "Soininen, Jonne (Nokia - FI/Espoo)" <jonne.soininen@nokia.com>
To: EXT Brian E Carpenter <brian.e.carpenter@gmail.com>, "ianaplan@ietf.org" <ianaplan@ietf.org>
Thread-Topic: [Ianaplan] What's happening at ICANN?
Thread-Index: AQHRAsZmnoFx0L28rU+8CjdG/JPz5J5lBKgA
Date: Sat, 10 Oct 2015 16:57:20 +0000
Message-ID: <D23F19BE.27A31A%Jonne.soininen@nsn.com>
References: <56181181.50002@gmail.com>
In-Reply-To: <56181181.50002@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.159.42.104]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <842555D7298B684BA9D3105FDD86344D@internal.nsn.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 2294
X-purgate-ID: 151667::1444496242-0000047E-D3E9B6EB/0/0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/ZISdc_sz21wgZLm5UluQlae5omU>
X-Mailman-Approved-At: Tue, 13 Oct 2015 08:12:32 -0700
Subject: Re: [Ianaplan] What's happening at ICANN?
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: Sat, 10 Oct 2015 16:57:26 -0000

Hi Brian,

like Bernard and Dave said, part of the story is the press tries to spin
an interesting story. Partly the story is that there are strong emotions
in play at the ICANN in this topic.

So, the topic is ICANN accountability. The claim is that as long as there
was the NTIA contract on IANA there has been a backstop on ICANN's
decisions, especially the board's. The theory is that if ICANN (the staff
and the board, not the community) would do something silly NTIA could at
least threaten to take IANA away and pressure ICANN to reconsider the
decision get to the right path. However, with the IANA stewardship
transition there would be no backstop anymore and potentially a future
board could go rogue and do whatever they want disregarding the community.
Therefore, there needs to be new accountability mechanisms.

The main accountability mechanisms discussed have been spilling the
complete board, removing a board member and control/veto the ICANN budget
and bylaws changes. There is pretty much consensus that in some form or
another these are reasonable requirements. However, the discussion is
about what is the right enforceability mechanism. Enforcement means how
can you legally enforce ICANN/board do something - basically, how can you
sue ICANN if the board/staff doesn't do what the community expects it to
do.

In the IETF, we have a bit different approach to these things. I wouldn't
think we would have ever the discussion the IETF community should be able
to take the IESG or IAB to court. Interesting thought, though... ;)

I hope this helps.

Cheers,

Jonne.
-- 
Jonne Soininen
Nokia Networks


Tel: +358 40 527 4634
E-mail: jonne.soininen@nokia.com





On 09/10/15 22:12, "Ianaplan on behalf of EXT Brian E Carpenter"
<ianaplan-bounces@ietf.org on behalf of brian.e.carpenter@gmail.com>; wrote:

>Could this WG, or the IETF as a whole, please get an update from our
>liaisons
>to the ICANN Board? The press stories are getting rather alarming, e.g.
>http://www.theregister.co.uk/2015/10/08/icann_fires_fear_fuzzy_logic_iana_
>transition/
>
>Thanks
>   Brian
>
>_______________________________________________
>Ianaplan mailing list
>Ianaplan@ietf.org
>https://www.ietf.org/mailman/listinfo/ianaplan