David Conrad wrote: > ... > > With an exclusive registry: > > Them: "Hey IANA, we're using .PAUL and here's the docs describing who we are > and how." > IANA: "Um, sorry. Someone else is already using that label." > Them: "But we really like .PAUL and we have deployed a zillion instances that > make use of .PAUL" > IANA: "That's fine, but you're potentially creating an interoperability > problem." > Them: "So tell the other guys to stop, since we've been using .PAUL since the > early 1700s." > etc. > > This smells like a hoop to me.
it would be .PAUL.EXTERNAL, which noone in their right mind would "really like" or deploy a zillion instances of. granted, being in one's right mind has never been a requirement for developers of distributed systems technology, but still, the fact that it's a registry of 2LD rather than TLD changes how we should interpret the impact of a collision. someone could, as you say, deploy a zillion instances of an app that pirates .PAUL (or .DAVID) within the context of a local application or end system. this will not happen with .PAUL.ALT (or .DAVID.EXTERNAL). >> so: offering someone a chance to register that a conflict exists does >> not serve the purpose of advancing interoperability. > > It doesn't address the interoperability of non-interoperable domain name > overlays. It does advance interoperability in the sense of improving the > state of knowledge that the non-interoperable domain name overlays exist, how > they operate, who runs them, etc. since the IETF gives guidance to implementers, i think it's wise to guide non-DNS naming implementers toward non-colliding names, and to guide end-system library and application implementers toward a dictionary of non-DNS exit gateways within the DNS "namespace" that mean the same thing for all of their users. > It seems to me that by making the registry exclusive, you're trying to put > the IESG/IETF/IANA in the role of gatekeeper of the non-interoperable domain > name overlays. since we're now talking about what i'm trying to do, i'll tell you, because it isn't what you said. i'm trying to create a new IANA registry of 2LD's beneath an exit-gateway reserved TLD. and like all other IANA registries i know of, i'd like IANA to only register the use of a given code point for one use, and i'd like that use to be defined by some public document. -- Paul Vixie _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
