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

[Miles Fidelman <[e-mail]>]

Seun,

Seun Ojedeji wrote:
>
> Miles, it think you are referencing that url as if the operating 
> systems services are syncing off the iana.org <http://iana.org> site.
>

I doubt that the o/s is syncing in real time.  I wouldn't be surprised 
though, if, at build/packaging time, the build system does a lookup 
against the iana.org site.  I wouldn't be surprised if other iana.org 
paramter registries are used in similar ways.

> If that domain changes today, it does not take anything other than a 
> update to reflect the new reference url does it?
>

If the URL changes, then auto-build systems will break - and people will 
end up having to figure out what happened, and fix it.  That's 
"disruptive" in my book.

> What would be disastrous is if there happens to be 2 authoritative 
> parameter source with different entries; as an example http referenced 
> as port 80 and as another port on the other site.
>

exactly!

> How to avoid that is not just by locking up the name iana.org 
> <http://iana.org> but by locking up to a single source of authority.
>

Currently, IETF is the source of policy and authority, iana.org, as run 
by ICANN is the single source of authoritative data. Seems to me that 
the simplest way to maintain a single source of authority is for the 
ownership of ietf.org to reside with IETF, to be delegated to whatever 
contractor is managing the data at any given time. Completely 
transparent to end-users of the registry.

Do you have an alternative, simpler solution to offer?

Cheers,

Miles

> Cheers!
>
> sent from Google nexus 4
> kindly excuse brevity and typos.
>
> On 7 Nov 2014 22:42, "Miles Fidelman" <[e-mail] 
> <mailto:[e-mail]>> wrote:
>
>     David Conrad wrote:
>
>         Miles,
>
>         On Nov 6, 2014, at 6:19 AM, Miles Fidelman
>         <[e-mail]
>         <mailto:[e-mail]>> 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
>     [e-mail] <mailto:[e-mail]>
>     https://www.ietf.org/mailman/listinfo/ianaplan
>


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