Dave Lawrence wrote:
Bob Harold writes:
I am a little concerned about yet another option that the client
might want to send with every query. Can the existence of *any*
EDNS option from the client be taken to mean that EDNS options are
understood in general, and the resolver is ok to respond with this
ENDS option, which the client might not understand but will not choke on?
I personally am of the belief that yes, if the request has an OPT then
a responder can include an option code that was not in the request.
At least I don't see anything in 6891 to prohibit it. This is
behaviour that draft-ietf-dnsop-extended-error is also expecting.
while i've seen every kind of misbehaviour from EDNS responders, i've
yet to suspect that an initiator who knows EDNS in any form will choke
on, or syslog about, unrecognized options in the response. so, +1 to tale.
--
P Vixie
_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop
