Hi Roy,
Change 2) There was an observation by developers that some
authoritative servers do not parse (unknown) EDNS0 options correctly,
leading to an additional roundtrip by the resolver. It was suggested
that authoritative servers could return the new EDNS0 option
“unsolicited”. This is already the case for Extended DNS errors. We
have adopted this suggestion. It was also pointed out that this kind
of unsolicited behaviour can be surveyed. We believe that one such
effort is underway.
Let me express my personal opinion here.
While sending unsolicited EDE seems fine for me as it's just few bytes,
the error-reporting address might be usually roughly 100 bytes long, so
sending it with very every response may lead to perceptible increase in
traffic, including increase in TCP fallbacks.
This may be tolerable, if there were some better reason for it. But I
don't like argumenting with broken implementations. Always dodging
broken implementation only leads to more broken implementations (see DNS
Flag Day etc). In ideal case, we should aim for the state where broken
implementation are failing constantly.
Libor
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
