> I think my proposal keeps DELEXT itself simpler. Rather than > having the generic protocol decide, based on a type range, > whether NS is replaced, each Delegation Type defines its own > interaction with NS. Existing implementations automatically > have a well-defined compatibility behaviour for future Delegation > Types that they do not yet implement.
Maybe I misunderstand your proposal. It seems that what you are saying is the following: Suppose we have a secondary DNS server. It knows about DELEG but not anything else. It gets a zone transfer and the zone has a delegation type record that the server doesn't know about. Now the secondary cannot serve the zone because it doesn't know the interaction with NS. _______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
