[Ianaplan] Quibbling about origins (was Re: draft-ietf-ianaplan-icg-response-02 working group last call)

Dave Crocker <dhc@dcrocker.net> Mon, 03 November 2014 20:57 UTC

Return-Path: <dhc@dcrocker.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 229201A026A for <ianaplan@ietfa.amsl.com>; Mon, 3 Nov 2014 12:57:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 Z5Nf25PpVTph for <ianaplan@ietfa.amsl.com>; Mon, 3 Nov 2014 12:57:22 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E95131A026E for <ianaplan@ietf.org>; Mon, 3 Nov 2014 12:57:21 -0800 (PST)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id sA3KvIY5025434 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <ianaplan@ietf.org>; Mon, 3 Nov 2014 12:57:21 -0800
Message-ID: <5457EC2B.8010200@dcrocker.net>
Date: Mon, 03 Nov 2014 12:57:15 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: ianaplan@ietf.org
References: <GLEAIDJPBJDOLEICCGMNEENBCNAA.rhill@hill-a.ch>
In-Reply-To: <GLEAIDJPBJDOLEICCGMNEENBCNAA.rhill@hill-a.ch>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Mon, 03 Nov 2014 12:57:21 -0800 (PST)
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/ouPpWrwoPy78CazL49PX-cjEzCI
Subject: [Ianaplan] Quibbling about origins (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
Reply-To: dcrocker@bbiw.net
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 20:57:25 -0000

As Andrew notes, this has nothing to do with current concerns, so I've
changed the Subject.


On 11/3/2014 12:30 PM, Richard Hill wrote:
>> -----Original Message-----
>> From: Ianaplan [mailto:ianaplan-bounces@ietf.org]On Behalf Of Andrew
>> Sullivan
>> On Mon, Nov 03, 2014 at 07:14:19PM +0100, Richard Hill wrote:
>>> So, since the IANA function was originally an emanation of the IETF
>>
>> No, it was not.  It was an emanation of someone to whom various
>> interested parties deferred. 
...
> As that E-Mail says, the  first formal reference to "IANA" seems to be in
> RFC 1060, of 1990.
> 
> So the IANA function was an emanation of the IETF.

This confuses nomenclature with function.  In this case, the
nomenclature came long after the function had been in continuous operation.

The Wikipedia entry on IANA's history matches my understanding of things
-- which matches what I usually hear others from that early timeframe cite:

   http://en.wikipedia.org/wiki/Internet_Assigned_Numbers_Authority#History

 -- and it notes that the /function/ dates back to the early 70s. This
also matches IANA's own reporting of its history:


https://www.iana.org/about/presentations/davies-berlin-domainpulse-060208.pdf


>> In general, I think foundational arguments in this area are likely to
>> get us into a dark and very wet swamp.  It seems to me that we need to
>> concentrate on what outcome we want ("stuff stays the same"),
> 
> Yes.  But we differ on what "staying the same" means.

Independent of an origins debate, we have had a stable operation of
IETF/ICANN/IANA/USG for something like 17 years.  That provides a pretty
reasonable baseline for assessing what it means to have things "stay the
same".

This, of course, is entirely distinct from determining what constitutes
reasonable components of the next agreement with ICANN...

One would think that removal of the USG from the equation would be
considered as a significant environmental change.



d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net