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

Miles Fidelman <mfidelman@meetinghouse.net> Sat, 08 November 2014 13:35 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 0AE4D1A7D84 for <ianaplan@ietfa.amsl.com>; Sat, 8 Nov 2014 05:35:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.881
X-Spam-Level:
X-Spam-Status: No, score=-0.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 Y9F6rPwVLylk for <ianaplan@ietfa.amsl.com>; Sat, 8 Nov 2014 05:35:56 -0800 (PST)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 2BD491A7D83 for <ianaplan@ietf.org>; Sat, 8 Nov 2014 05:35:56 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 5C530CC137 for <ianaplan@ietf.org>; Sat, 8 Nov 2014 08:35:55 -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 0hK1knu7KUUc for <ianaplan@ietf.org>; Sat, 8 Nov 2014 08:35:51 -0500 (EST)
Received: from new-host-3.home (pool-72-93-213-216.bstnma.fios.verizon.net [72.93.213.216]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 1AAF1CC136 for <ianaplan@ietf.org>; Sat, 8 Nov 2014 08:35:51 -0500 (EST)
Message-ID: <545E1C36.6030500@meetinghouse.net>
Date: Sat, 08 Nov 2014 08:35:50 -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
CC: "ianaplan@ietf.org" <ianaplan@ietf.org>
References: <GLEAIDJPBJDOLEICCGMNIEOJCNAA.rhill@hill-a.ch> <54594A50.4090305@meetinghouse.net> <20141105001731.GA30186@mx1.yitter.info> <54597BDB.7040305@meetinghouse.net> <5459BA98.1070006@gmail.com> <545A208A.7040304@meetinghouse.net> <631e3e3d29c843bd9c23151c63612989@EX13-MBX-13.ad.syr.edu> <20141105154903.GI30379@mx1.yitter.info> <498a39b81b774192bd2d609b3feab35f@EX13-MBX-13.ad.syr.edu> <20141105234444.GM31320@crankycanuck.ca> <545ABCB0.5080206@meetinghouse.net> <8f3dcda6c3db4cd8be1b77444f987d59@EX13-MBX-13.ad.syr.edu> <D0805C27.136BE7%jon.peterson@neustar.biz> <7F52A930-DD6F-4D0D-8278-A021CF8A466C@istaff.org> <D080D78C.136C6E%jon.peterson@neustar.biz> <545B9F8A.6090502@meetinghouse.net> <FB588096-E8EF-4D2D-A504-3B6AE2D591BB@virtualized.org> <545D3CB2.6080905@meetinghouse.net> <CAD_dc6i=yOoAvky-OQ17EcmojeTnQD4bOO5Vx=qkSatp116rrg@mail.gmail.com>
In-Reply-To: <CAD_dc6i=yOoAvky-OQ17EcmojeTnQD4bOO5Vx=qkSatp116rrg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/8YMKxTwt6ZxfHIsghZBw6GFHiCA
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: Sat, 08 Nov 2014 13:35:58 -0000

I agree.  Though the issue is really whether people use conflicting 
sources of information - whether they are authoritative or not.

Which breaks down into two separate issues:
- what constitutes an "authoritative source," and,
- what do users perceive to be an authoritative source

My major take is that clear control and delegation of iana.org is a way 
of avoiding the potential for conflicting sources of information - by 
taking pains to make sure that iana.org is, and remains to be the 
well-publicized "official" and hence "authoritative" source of 
information, and that the data in it is managed by the party(ies) 
responsible for maintaining he authoritative data.

That's the current situation.  Let's craft a transition that makes an 
effort to keep it the situation in the event of a transition of iana.org 
contractor.

(note: I agree with those who seem to think we're spending way too much 
time on what seems to be a simple matter.  I honestly don't understand 
why this should be such an issue.)

Miles

Seun Ojedeji wrote:
> I responded to this mail but it seem my response did not get through. 
> I will try this again below:
>
> @Miles i think you may be referring to iana.org <http://iana.org> as 
> if operating systems services sync information off it in reatime which 
> is not necessarily the case. I would expect that a change in the 
> domain name will only require a normal OS update to reflect the 
> appropriate new url...No?
>
> What i would term disruptive is when there exist 2 sources of 
> authoritative information and when the information on the each source 
> is not the same. For example it would not be helpful if a source 
> reflects http being port 80 and another reflects it as another port. 
> So i would think being authoritative goes beyond a mere ownership of 
> iana.org <http://iana.org> but extend to the content itself.
>
> Cheers!
>
>
> On Fri, Nov 7, 2014 at 10:42 PM, Miles Fidelman 
> <mfidelman@meetinghouse.net <mailto:mfidelman@meetinghouse.net>> wrote:
>
>     David Conrad wrote:
>
>         Miles,
>
>         On Nov 6, 2014, at 6:19 AM, Miles Fidelman
>         <mfidelman@meetinghouse.net
>         <mailto:mfidelman@meetinghouse.net>> wrote:
>
>             More specifically, I'm concerned with avoiding any
>             confusion or operational disruption in the event of future
>             conflicts among the parties involved in oversight,
>             management, and/or performance of the IANA functions -
>             particularly in the case where a transition of contractor
>             might occur on less then friendly terms.
>
>             Under such situations, it seems at least possible, if not
>             likely, that litigation might ensue and/or that parties
>             might operate competing registries - causing operational
>             confusion at a minimum, and possibly more serious
>             disruptions to smooth operation of the net.
>
>         We're talking about the protocol parameter registries, right?
>
>         I'm honestly curious: could you describe the "serious
>         disruptions to smooth operation of the net" or "operational
>         confusion" that would occur in the event of future conflicts
>         relating to the IANA trademark and/or IANA.ORG
>         <http://IANA.ORG> domain?
>
>
>
>     Kind of depends on the degree to which various developers depend
>     on the various registries published under iana.org
>     <http://iana.org>, and perhaps on the degree to which anybody
>     relies on automatic download of registry contents.
>
>     For example, the /etc/services file in Debian includes this statement:
>     #Updated from http://www.iana.org/assignments/port-numbers
>
>     I expect other operating systems do similar things.  A lot of
>     systems could break, rather precipitously, if iana.org
>     <http://iana.org> went offline, or the file were moved somewhere
>     else, or the file were corrupted - particularly if it happened
>     just before a major release cycle.
>
>     To me, that would be a "serious disruption" or at the very least
>     "operational confusion"
>
>
>
>     Miles Fidelman
>
>     -- 
>     In theory, there is no difference between theory and practice.
>     In practice, there is.   .... Yogi Berra
>
>     _______________________________________________
>     Ianaplan mailing list
>     Ianaplan@ietf.org <mailto:Ianaplan@ietf.org>
>     https://www.ietf.org/mailman/listinfo/ianaplan
>
>
>
>
> -- 
> ------------------------------------------------------------------------
>
>     /Seun Ojedeji,
>     Federal University Oye-Ekiti
>     web: http://www.fuoye.edu.ng
>     Mobile: +2348035233535
>     //alt email:<http://goog_1872880453>seun.ojedeji@fuoye.edu.ng
>     <mailto:seun.ojedeji@fuoye.edu.ng>/
>
>         The key to understanding is humility - my view !
>
>


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