Re: IDN administrative bundling
Andrew Sullivan <[email protected]>
| Newsgroups | gmane.ietf.provreg |
|---|---|
| Message-ID | <[email protected]> |
On Fri, Mar 30, 2012 at 02:24:24PM +0000, Gould, James wrote: > objects. The concept of bundling could apply to domain names in a single > TLD, domain names across TLD's, and objects of different kinds within or > across TLD's. I don't care what we call them, but I do not see how anyone can claim that "bundling" in the same sense can cross domain (I'm almost tempted to say "zone") boundaries and also be the narrow meaning often intended by the word. Bundling(n) [n for narrow] is a case where, within the same domain, two subordinate labels are somehow treated as basically linked in some way. This is the meaning of bundling (and one of the meanings of "variant") that has most traditionally been seen in the RFCs. The links may be purely administrative, by which we mean that the administrative details of the name are required to be the same; or they may be technically tighter, such as a requirement for mirroring (either via aliasing or administrative fiat of parallel delegation). An example of this case is example.com and éxample.com: these are both names in the same domain (and zone). Bundling(w) [w for wide], which I would prefer to call "domain linking" or something like that, is where two names in different parts of the DNS namespace are somehow treated in ways that link them together. As above, these links may be stronger or weaker, but the key is that they be in different domains. If example.com and example.net are somehow linked together, for instance, it would be a case of this. best, A -- Andrew Sullivan [email protected] _______________________________________________ provreg mailing list [email protected] https://www.ietf.org/mailman/listinfo/provreg