Gervase Markham wrote: > We've had this basic problem in the domain of cookies for years. I don't > expect another solution to pop out of the woodwork now. But I'm open to > being surprised :-) >
Surprise! If you want grouping, there is a simple-to-code, reliable, and authoritative way to do so. Zone cuts (in DNS). (Note well - a zone is not semantically identical to a domain, although they can at times seem that way. In particular, if a child domain is served by the same server(s) as the parent, there will not be a zone cut. This, I believe, will generally do a good job of permitting grouping automagically.) Where there is a delegation of authority, via a zone cut, that is *exactly* where you want to group. And in the absence of a zone cut, you do not want separation by grouping. That (among other things) is what distinguishes "foo.co.uk" from "myprivatesubdomain.foo.com". Perhaps examining other aspects of DNS responses may further inform the device needing to determine grouping. Things like presence/absence of glue (at particular places, e.g. root/TLD), commonality of NS instances between parent/child, etc. Whether this gets done by the end-user's client, or by some more-centralized box, is an implementation issue (but one that should be given lots of thought!!). But, it is better to trust information already published, which is required for proper operation of DNS, than to look for additional information that may become stale or inconsistent. Brian Dickson _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
