Matthijs Mekking <matth...@pletterpet.nl> wrote: > > 1. In case of a DNS responder selecting one or a subset of the RRsets at the > QNAME, The draft does not give clear guidance on which RRset(s) to pick.
The code in BIND just picks an arbitrary RRset, without making any effort to be clever. It makes an ANY query to the back end, then adds the first RRset to the response. The data from the back end doesn't have a deterministic order. Doing better than this would (I think) require additional methods in the rdataset API to get the size of the RRset. Unless we use a dumb heuristic like smallest RR TYPE number :-) > 2. People expressed that they would like to see ANY over TCP stick to the > original (undefined) behavior, that is to return all RRsets at the QNAME. BIND does this. > One more nit comment, I would like to see explicitly called out in section 7 > that "DNS implementations are free to not return all RRSIGS *in case > QTYPE=RRSIG*". BIND also does this. Tony. -- f.anthony.n.finch <d...@dotat.at> http://dotat.at/ - I xn--zr8h punycode Bailey, Fair Isle, Faeroes, Southeast Iceland: Southerly or southwesterly veering westerly, 5 or 6, increasing 7 or gale 8. Moderate or rough, becoming very rough. Occasional rain, then showers later, wintry in Faeroes and Southeast Iceland. Good, occasionally poor. _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
