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

Eliot Lear <lear@cisco.com> Mon, 03 November 2014 22:45 UTC

Return-Path: <lear@cisco.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 2ACDC1A87AE for <ianaplan@ietfa.amsl.com>; Mon, 3 Nov 2014 14:45:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.095
X-Spam-Level:
X-Spam-Status: No, score=-15.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.594, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 ykgHPDBwB15m for <ianaplan@ietfa.amsl.com>; Mon, 3 Nov 2014 14:45:33 -0800 (PST)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1378F1A8782 for <ianaplan@ietf.org>; Mon, 3 Nov 2014 14:45:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2637; q=dns/txt; s=iport; t=1415054713; x=1416264313; h=message-id:date:from:mime-version:to:subject:references: in-reply-to; bh=H+0yms8xsA2lt8mF3y4EF1x3FHva6dxZvSY1TR8LS4o=; b=m47r4zSRA7qhyYJnMv8xbO6mj+8BvxIQI/FApTuM/NmD8N1yWJrm2mU1 lL5tFkLQ5+VbCI0kkYw3KLW22UiCTldEtv78PSJXMWokcI5ipKz8bB7/c PsKRHxajwJKRaVf7EvlGpAOK4wm6KgvXpoTKQyosknedxX1TjkhUc+6sd I=;
X-Files: signature.asc : 486
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArcEAEoEWFStJssW/2dsb2JhbABcg2JYgwbLE4dVAoE+AQEBAQF9hAMBAQQjVRELDgoJFgQHAgIJAwIBAgFFBgEMCAEBEIgttiWUcwEBAQEBAQEBAQEBAQEBAQEBARqRF4J3gVQBBIt2iDmBUmiHGIFuhgeOW4I0gWUcL4JLAQEB
X-IronPort-AV: E=Sophos;i="5.07,309,1413244800"; d="asc'?scan'208";a="230354920"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP; 03 Nov 2014 22:45:11 +0000
Received: from [10.154.176.54] ([10.154.176.54]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id sA3MjAkv025479; Mon, 3 Nov 2014 22:45:10 GMT
Message-ID: <54580575.3020804@cisco.com>
Date: Mon, 03 Nov 2014 14:45:09 -0800
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Andrew Sullivan <ajs@anvilwalrusden.com>, 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: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="RToW9Ba054ij4l1TDvaUsELPs2PSLVf3B"
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/hECpNpSKlczMxFEiKLfKrYgBisA
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:45:34 -0000

On 11/3/14, 2:26 PM, 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. 

There are two arguments to be made.  First, and perhaps most
importantly, it's not theirs..  It's the community's, and this is true
on its face.  How can it be said that IANA.ORG is not part and parcel of
the IANA functions? Second we have stated a legitimate requirement for
continuity of service that the NTIA is in a position to make clear is a
requirement; that is part of security and stability of the IANA
functions service.  For ICANN to say "no" would discredit them, given
the first argument.  Nor should they say "no".  It would be bad for
everyone.

As I wrote, I am not wedded, nor was I ever wedded, to the IETF Trust
having to have a role here.  I was satisfied with any successor taking
the name, as you and Milton agreed.  My sole issue is continuity of
service in the face of transition, including backward compatibility.

Finally, I expect that when we publish this document, we are not done. 
Rather there will be discussions about how to meet the legitimate
requirements we have laid out, such that the other parties are
satisfied.  That may require changes to the resulting response.  That is
already built into the ICG's timeline.

Eliot