On 6/23/15, 13:07, "DNSOP on behalf of Andrew Sullivan" <[email protected] on behalf of [email protected]> wrote:
>It seems to me that, for any domain name, there are three things that >are relevant: > >1. The namespace. >2. The registry for that name (in the old-fashioned, not ICANN, sense) >3. The zone at that name. I have to admit that this list isn't clear enough for me. When you same "name space" are you referring to a domain name space or a more general name space. I ask because the last entry "the zone" is specific to domain names. With "onion" as the root of a namespace for Tor (sorry, maybe the term is off), it has names in it that are in the "Tor name space". There's no "zone" in the DNS sense related to this, because this is not DNS. However, there is talk that the TLD "onion." ought to remain, forever, a non-existant name (as defined in RFC 4592 [The wildcard one]) and that then means there should be no zone for "onion." Just a bit confused. >At least some special-use names are in-band signals of a protocol >shift. >Some other possible special-use names are really names that are >expected to appear in DNS contexts _but_ that are not expected to >resolve in the global DNS context. These are two very different things. The first is that the name's look implies how it is resolved (mapped to an address, say). The latter is how the DNS is impacted by a domain name that looks similar to the name in question is treated. I don't know if this comment is related, and I think I've said this before (so guilty of repeating myself perhaps), the special-use domain-name registry isn't very useful unless it indicates what someone/something looking up the registry ought to do with the name besides not asking the DNS for it. In this case, "in-band signals" should be made explicit in the registry. But are the two things Andrew has really separate? I mean, isn't the registry saying "this" has a non-DNS purpose and DNS ought not make it exist? Yes, the the two are different (separated by the and in the previous sentence) but are related outcomes from the use of the name in some special way?
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
