In article <[email protected]> you write: >today it was proposed that NS2 be added as a new record-set type that >could exist in either the parent or the child, similar to NS, and >reminding several of us about the DS debacle. ...
>so instead of example.com DS, it should have been example._dnssec.com DS. I take your point but I have a question and a half. The plan in this draft is that NS2 would eventually replace NS records. Hence a zone could have a zone cut at a name that has no NS records, so the server has to do something like scan the zone when loaded or updated for NS2 records at names like example._ns2.com and remember that means that example.com is a zone cut. Adding to the excitement, NS2 in its current kitchen-sink form replaces both NS and DS, so the name at the zone cut would not exist at all. The server would presumably have to synthesize an ENT there. Does that seems feasible? Sensible? R's, John _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
