At 11:20 +0100 3/8/05, Bruce Campbell wrote:
From a Registry POV, allowing in-bailiwick glue adds the requirement of keeping track of the IP addresses used; whilst it is clearly the responsibility of the child to keep the parent informed about changes, most people simple do not think about these things until breakage occurs, with the finger of blame being pointed at the parent for not supporting the do-what-I-want-not-what-I-say interface correctly.
It's true that the RIR's don't have to worry about glue maintenance, don't fret - the registrants already do. ;) The glue is somewhere...
I don't mean to push for the RIR's to maintain glue, just to point out that if they do, it isn't "new pain" just "moved pain." ;)
The downside of the RIR's not maintaining glue is an arguable (arguable) performance hit of having an iterating name server chase down so many name server addresses (independent of old BIND problems). Also, because of old BIND, .net servers (where most of the /8 in-addr name servers are) have to give out "extra glue" because old BIND got "lost" on the way. ("Old" BIND.)
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis +1-571-434-5468
NeuStar
Achieving total enlightenment has taught me that ignorance is bliss. . dnsop resources:_____________________________________________________ web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html
