On 15. 08. 22 12:18, Kazunori Fujiwara wrote:
I assume section 3.2 means the EDNS bufsize in the request when it says
"their payload size", but I am not sure. The text could be clearer on
that.
* UDP requestors MAY probe to discover the real MTU value per
destination.
How?
For example, recent BIND 9 starts small EDNS requestors maxiumum
DNS/UDP payload size (512), and increases gradually.
Correction:
Recent BIND starts with EDNS buffer size 1232 bytes, and it does not
rise the value to "probe" the destination address by to "probe".
FTR I'm testing on 9.19.5-dev commit b13d973, but I believe it is like
that for a long time already.
I think the draft as it is currently does not have enough information
for implementers to be followed in safe way.
I'm against publication as it is.
There should be running code, experiments, and measurements to back up
data in this draft. I can't see them at the moment.
--
Petr Špaček
Internet Systems Consortium
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
