Re: [Ianaplan] comments on draft-ietf-ianaplan-icg-response-01

Andrew Sullivan <ajs@anvilwalrusden.com> Fri, 24 October 2014 13:23 UTC

Return-Path: <ajs@anvilwalrusden.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 48A511A000F for <ianaplan@ietfa.amsl.com>; Fri, 24 Oct 2014 06:23:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level:
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] 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 yKX0XwjcGOsT for <ianaplan@ietfa.amsl.com>; Fri, 24 Oct 2014 06:23:45 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2DAF1A0097 for <ianaplan@ietf.org>; Fri, 24 Oct 2014 06:23:13 -0700 (PDT)
Received: from mx1.yitter.info (nat-07-mht.dyndns.com [216.146.45.246]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 7CF8C8A031 for <ianaplan@ietf.org>; Fri, 24 Oct 2014 13:23:12 +0000 (UTC)
Date: Fri, 24 Oct 2014 09:23:08 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ianaplan@ietf.org
Message-ID: <20141024132307.GA2240@mx1.yitter.info>
References: <5449EF98.70701@cisco.com> <GLEAIDJPBJDOLEICCGMNAEACCNAA.rhill@hill-a.ch>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <GLEAIDJPBJDOLEICCGMNAEACCNAA.rhill@hill-a.ch>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/G7Ou0LajhLT3BWiKbt7Fga3-ILM
Subject: Re: [Ianaplan] comments on draft-ietf-ianaplan-icg-response-01
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, 24 Oct 2014 13:23:46 -0000

On Fri, Oct 24, 2014 at 08:59:35AM +0200, Richard Hill wrote:
> 
> I was under the impression that that text reflected our discussions during the audio conference.  But perhaps my impression is not correct.
> 

It certainly reflects what some people wanted at the interim.  I
argued then, and I argue now, that this level of specification isn't
something we want.  I am prepared to be in the rough, of course, like
anyone else.  So,

> substantive about jurisdiction. So, if the above text is not
> acceptable to all

we don't need text acceptable to all.  We need text that's achieves
rough consensus.

> "The IAOC is asked to conclude a supplemental agreement regarding
> jurisdiction and any necessary dispute resolution mechanisms, taking
> into account that it may be preferable to specify a neutral
> jurisdiction such as arbitration in Switzerland."

It may be preferable also to specify jurisdictions where any of the
bodies are incorporated, to the extent they are, also.  So if we're
going to include instructions to get an agreement about jurisdiction
and dispute resolution, then I am very strongly opposed to specifying
what jurisdiction that ought to be.  I don't think the WG should get
into that kind of instructing of the IAOC.  Also, see below.

>  "Further, the IAOC is asked to consider whether it would be
> appropriate for the IANA function to be legally domiciled in a
> neutral jurisdiction such as Switzerland, possibily with immunity of
> jurisdiction."

I think that's completely off-topic for this, and it's also clearly
outside our charter since it would be a major change to the existing
arrangements and our charter tells us not to do that: "This working
group is chartered solely with respect to the planning needed for the
transition, and is not meant to cover other topics related to
IANA. Possible improvements outside that scope will be set aside for
future consideration."  The recommendation of jurisdiction in the
first proposal also seems to me to be in violation of that term.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com