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

Seun Ojedeji <seun.ojedeji@gmail.com> Sat, 10 October 2015 20:21 UTC

Return-Path: <seun.ojedeji@gmail.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 327431B4711 for <ianaplan@ietfa.amsl.com>; Sat, 10 Oct 2015 13:21:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 nWO16cgJVAJr for <ianaplan@ietfa.amsl.com>; Sat, 10 Oct 2015 13:21:41 -0700 (PDT)
Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 460531B4716 for <ianaplan@ietf.org>; Sat, 10 Oct 2015 13:21:39 -0700 (PDT)
Received: by wicgb1 with SMTP id gb1so9104362wic.1 for <ianaplan@ietf.org>; Sat, 10 Oct 2015 13:21:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=eLpkE9QtbJB1/jW7N9Qlx2+Cd7cezNjHSQfp8In2t28=; b=JwcwPVvMtOFjXbJPQndmF9IVRvKLqKLhTLl2Z2vh0gkReos89QezVP4lSEEsyD0A6v s5JFW9TQiJ6kGy9mqg2DabSRPISRNawQ1V844kWTYmULpJmh3qlOiYZAaXEhAxzheFZ7 qVGKvWBuOQJSTR089+LAWltcuU3R/EAF+I+6HEjs1tNTxsQIJ1SmbALIP7zv1FnRv8Fi TrabGxF5m70PHiEi/uWuhj6+4j0OkX0ncY/OECQVtF15ftG6Too+puf1KTdrYpw8JaQ5 tMhWvhLB3VQgwbdGuT551+qaMe1QDc9vob8RY8unznAyd9jrbLIoZ1smIjYZcho4s2VE 6bOA==
MIME-Version: 1.0
X-Received: by 10.180.81.228 with SMTP id d4mr6406010wiy.38.1444508497872; Sat, 10 Oct 2015 13:21:37 -0700 (PDT)
Received: by 10.194.171.170 with HTTP; Sat, 10 Oct 2015 13:21:36 -0700 (PDT)
Received: by 10.194.171.170 with HTTP; Sat, 10 Oct 2015 13:21:36 -0700 (PDT)
In-Reply-To: <56196F4D.3080801@gmail.com>
References: <56181181.50002@gmail.com> <D23F19BE.27A31A%Jonne.soininen@nsn.com> <56196F4D.3080801@gmail.com>
Date: Sat, 10 Oct 2015 21:21:36 +0100
Message-ID: <CAD_dc6h8NNZNqLLJLQEK85uL--Jz6vNKzkdrYrYixXXbXX_xJw@mail.gmail.com>
From: Seun Ojedeji <seun.ojedeji@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=f46d043bdb0ee40d8f0521c5d7b7
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/Fh1mvSc5CobuqqiH6e3iPXI2P08>
Cc: ianaplan@ietf.org, "Soininen, Jonne \(Nokia - FI/Espoo\)" <jonne.soininen@nokia.com>
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 20:21:43 -0000

+1 to that as well, with some caveat. Considering that ICANN board acts in
the interest of the entire organisation and considering that some board
seats are filled by the entire community (nomcom). It's therefore important
that board member removal be completed by the entire community (even though
SO/AC appointed member removal process can only be triggered by the
appointing SO/AC)

Regards
Sent from my Asus Zenfone2
Kindly excuse brevity and typos.
On 10 Oct 2015 21:04, "Brian E Carpenter" <brian.e.carpenter@gmail.com>;
wrote:

> Thanks Jonne. Yes, it helps to have a calm overview rather than a
> seemingly biased media story.
>
> I do believe that the communities that put Board members in place
> should be able to remove them, with some sort of due process.
>
> Regards
>    Brian
>
> On 11/10/2015 05:57, Soininen, Jonne (Nokia - FI/Espoo) wrote:
> > 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.
> >
>
> _______________________________________________
> Ianaplan mailing list
> Ianaplan@ietf.org
> https://www.ietf.org/mailman/listinfo/ianaplan
>