Re: [Ianaplan] control and negotiation (was Re: draft-ietf-ianaplan-icg-response-02 working group last call)

Miles Fidelman <mfidelman@meetinghouse.net> Mon, 03 November 2014 22:44 UTC

Return-Path: <mfidelman@meetinghouse.net>
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 BE4B61A878C for <ianaplan@ietfa.amsl.com>; Mon, 3 Nov 2014 14:44:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.003
X-Spam-Level:
X-Spam-Status: No, score=-0.003 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, SPF_HELO_PASS=-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 SGC1YISWocvc for <ianaplan@ietfa.amsl.com>; Mon, 3 Nov 2014 14:44:14 -0800 (PST)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 3FDE51A8782 for <ianaplan@ietf.org>; Mon, 3 Nov 2014 14:44:14 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id C7140CC0D3 for <ianaplan@ietf.org>; Mon, 3 Nov 2014 17:44:13 -0500 (EST)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id LEaEkAUlu3T4 for <ianaplan@ietf.org>; Mon, 3 Nov 2014 17:44:09 -0500 (EST)
Received: from new-host-3.home (pool-96-237-159-213.bstnma.fios.verizon.net [96.237.159.213]) by server1.neighborhoods.net (Postfix) with ESMTPSA id AFD2ECC093 for <ianaplan@ietf.org>; Mon, 3 Nov 2014 17:43:57 -0500 (EST)
Message-ID: <5458052D.2030806@meetinghouse.net>
Date: Mon, 03 Nov 2014 17:43:57 -0500
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:33.0) Gecko/20100101 Firefox/33.0 SeaMonkey/2.30
MIME-Version: 1.0
To: ianaplan@ietf.org
References: <20141103183007.GP27751@mx1.yitter.info> <GLEAIDJPBJDOLEICCGMNEENBCNAA.rhill@hill-a.ch> <20141103212831.GF28565@mx1.yitter.info> <5457FBA7.6050908@cisco.com> <20141103222618.GB28757@mx1.yitter.info>
In-Reply-To: <20141103222618.GB28757@mx1.yitter.info>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/BHRydUODrCDPvrCtJgKs-ebqCRs
Subject: Re: [Ianaplan] control and negotiation (was Re: draft-ietf-ianaplan-icg-response-02 working group last call)
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: Mon, 03 Nov 2014 22:44:16 -0000

Andrew Sullivan wrote:
> On Mon, Nov 03, 2014 at 02:03:19PM -0800, Eliot Lear wrote:
>> How does that sound to you in principle?
> My objection to moving the relevant bits to the IETF Trust has never
> been one of principle.  It's been one of practicality: I don't see any
> incentive whatsoever for ICANN to give up that property without
> getting something in return, and I can't think of anything I want to
> give up more than iana.org in case there's more than one operator.
>
> Again, to be clear, I think that would be a very bad outcome.  I don't
> think it would be good to have to split the iana.org stuff, and I
> think we should avoid it.  But I think it is preposterous to imagine
> that ICANN is going to give away an asset just because we want it,
> without extracting some concession.  Therefore, it'd be fine to say to
> the IAOC, "Please ask for this."  But if they don't get it, what then?
>
> The burden of proof, IMO, is on those who claim that ICANN will simply
> have to give up control of that asset.  I've yet to see a good
> argument that they will, and I note it is somewhat unusual in the US
> for a government department to force a corporation to give up an asset
> without any compensation.

As far as the USG is concerned, ICANN is a contractor - nothing more, 
nothing less.  Generally, unless there are clear exceptions in law, 
regulation, or contract, work performed under contract is the property 
of the contractee (USG), not the contractor (ICANN).

By all rights, IMHO, iana.org should have been registered by either the 
USG, or SRI - back when John Postel was doing the work; and transferred 
to the USG when the work moved - with the USG delegating management to 
ICANN, as part of the contract.  Instead, ICANN unilaterally staked a 
claim to the domain, by registering it.

Yes, possession is nine 10ths of the law - but what we're talking about 
here is an oversight to be rectified, not an overstepping to be ratified.

Why NOT take the opportunity to at least attempt to fix this.  This is 
the best opportunity to do so, and perhaps the last that would not 
involve the potential for hostile litigation at some point down the line.

As to burden of proof re. whether or not ICANN will "simply give up 
control" - well.. seems to me that the best way to find out is to run 
the experiment.  Put it in our proposal, stand fast, and stand fast.  At 
the very least, it puts IETF in a stronger negotiating position for 
getting to compromise language.

Miles Fidelman

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra