Re: [Ianaplan] A draft for your review

Miles Fidelman <mfidelman@meetinghouse.net> Tue, 02 September 2014 14:17 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 07CBD1A03FA for <ianaplan@ietfa.amsl.com>; Tue, 2 Sep 2014 07:17:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 uID1HCpj2pEZ for <ianaplan@ietfa.amsl.com>; Tue, 2 Sep 2014 07:17:23 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 7A3081A0410 for <ianaplan@ietf.org>; Tue, 2 Sep 2014 07:17:23 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 100B7CC06B; Tue, 2 Sep 2014 10:17:22 -0400 (EDT)
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 Gr3yXeJYCIzw; Tue, 2 Sep 2014 10:17:13 -0400 (EDT)
Received: from [172.18.2.126] (unknown [69.27.252.130]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 493ACCC06F; Tue, 2 Sep 2014 10:17:13 -0400 (EDT)
Message-ID: <5405D188.5070508@meetinghouse.net>
Date: Tue, 02 Sep 2014 10:17:44 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 SeaMonkey/2.26.1
MIME-Version: 1.0
To: Eliot Lear <lear@cisco.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, rhill@hill-a.ch, Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <GLEAIDJPBJDOLEICCGMNOEGHCKAA.rhill@hill-a.ch> <54059FA9.50107@meetinghouse.net> <5405A18B.2060604@cs.tcd.ie> <5405CDEF.6040302@meetinghouse.net> <5405CF6B.3050704@cisco.com>
In-Reply-To: <5405CF6B.3050704@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/k4qJ_Lc-wPUmDqFDhfuDguegIP4
Cc: ianaplan@ietf.org
Subject: Re: [Ianaplan] A draft for your review
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: Tue, 02 Sep 2014 14:17:25 -0000

Eliot Lear wrote:
> Miles,
>
> On 9/2/14, 4:02 PM, Miles Fidelman wrote:
>> Yes, but the MOU can be withdrawn from.  Right now, the NTIA contract
>> "backstops" the MOU.  The question becomes: what, if anything replaces
>> that backstop?  If I were NTIA, I'd sure like to see that answered
>> before stepping away.
> Yes, but what does that mean in this case?  If the IETF were to
> terminate the arrangement, would ICANN still review our documents, and
> if so, would we not take them seriously?  The worst case would be
> ICANN's copy of protocol parameters didn't match our own, and at that
> point, developers would have to decide who to believe.  This would not
> be a good state to be in, but realistically anyone else can do the same
> thing.  And truly it would serve nobody's interest for this to happen,
> not ours, not ICANN's and certainly not implementers'.
>

It's awfully important (IMHO) to have a definitive registry for protocol 
parameters.  Right now ICANN provides the registry, under the aegis of 
both the NTIA contract and the MOU.  What will be the process if IETF 
decides that the job isn't being done well and wants to replace ICANN as 
the registry operator?  What if ICANN decides it wants to levy fees?  
Who makes such decisions, and how?  Etc.

Miles Fidelman