On 6/4/15, 16:07, "[email protected]" <[email protected]> wrote:
>But if you have to be prepared for identifier >collisions anyway, what use is the registry? This is a good starting point for discussion. I've been passively reading messages without much time to put together a contribution based on my experience. The chief function of a registry, and this is core to all registries, is to map objects to entities. Objects could be domain names, IP address ranges, automobiles, plots of land. Entities can be people, family, organizations, corporations. And the mappings might be for owning, driving, taxation, maintenance, and so on. The mapping is for all purposes 1:1. (I suppose you could list multiple maintainers for a route object, but thats an extension of mapping on to a role account.) The goal is uniqueness of the mapping. The uniqueness may be relative, like there being multiple "743 Evergreen Terraces" in towns named "Springfield." Once within a locale though, the mapping is unique. (Registries also have other functions, but the mapping is what puts the "registry" in "registry".) This is what makes me scratch my head about ".alt". It might be a very useful idea. (Trying to avoid saying "it might not be a bad idea" which has a double negative in it.) It could be a sandbox where "there's no lifeguard." Trying to apply any sort of order in the area is like trying to add some of the features of TCP to UDP - the Internet's version of alchemy. The question I roll in my head is this - "are Internet Identifiers a subset of Domain Names -or- are Domain Names a subset of Internet Identifiers?" I think the the answer to that matters greatly before knowing whether reserving a branch of the Domain Name space for mayhem is useful. If Internet Identifiers are a subset of Domain Names, then declare a branch for mayhem. If it is the other way around, don't subjugate the identifiers under the DNS. As far as the cost - what's often missed is the cost of the lost opportunity to have "www.stadt.alt." be a website. ;)
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
