In article <04dea363-80f3-46e2-9f22-1d6fa3d31...@gmail.com> you write: >IETF is making a request of ICANN. It seems to me homenet-dot should be >revised: > >* take the relevant text out of the IANA considerations section >* add a section that > - motivates and explicitly defines the desired entry in the root zone > - suggests that a request be made directly to ICANN > - explicitly points out that no process for such a request exists, and it > might be necessary for IETF and ICANN to develop a mutually >acceptable process before the request from .homenet can be considered > - asks for IETF advice on this plan
Don't forget - waits many, many years while ICANN does what ICANN does about anything new At this point I see the only plausible options as choose .homenet and require all validating resolvers to special-case it, or choose .homenet.arpa and put whatever DNSSEC magic we need into .arpa. While I don't think that the technical issues are particularly complex around changing the rules to put a .homenet stub or opt-out in the root, I can absolutely guarantee that if ICANN considers it, there will be a long queue of opportunists insisting that their particular awful root hacks are just like .homenet and ICANN has to do them, too. They are wrong, but ICANN is poorly defended against people with a mission and a lot of free time. R's, John _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
