On Mar 5, 2013, at 9:45 AM, Joe Abley <jab...@hopcount.ca> wrote: > > On 2013-03-05, at 12:09, Paul Hoffman <paul.hoff...@vpnc.org> wrote: > >> On Mar 5, 2013, at 9:05 AM, Joe Abley <jab...@hopcount.ca> wrote: >> >>> I presume this has already come up, and there are good reasons why the >>> apparent lexical flexibility in what I'm about to suggest are swamped by a >>> sea of vicious snakes, but if the goal is "transmitting general information >>> to the parent which in some cases they might care about" why not think >>> about a more general RRType of the form >>> >>> ; zone cut >>> example.com. IN SOA ... >>> ; >>> example.com. IN PARENT SOMERRTYPE rrtype-specific-data... >>> . . . >> >> +1 > > I thought of that approach too, but it seems inadequate for the purposes of > signalling candidate glue to a parent (there's no obvious way to encode an > owner name, and the owner name is necessary with glue, unlike NS or DS > RRSets). > > I guess another approach for that particular problem is to note the child's > desired NS set and then use local policy to acquire secure answers for glue > records where needed.
That seems sufficient. That is, the child doesn't get to say "this is the glue", but the parent can decide where to look for glue. --Paul Hoffman _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
