On 18. 08. 23 17:33, Peter van Dijk wrote:
Hello Tim,
On Wed, 2023-08-16 at 15:45 -0700, Tim Wicinski via Datatracker wrote:
Tim Wicinski has requested publication of
draft-ietf-dnsop-avoid-fragmentation-14 as Best Current Practice on behalf of
the DNSOP working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-dnsop-avoid-fragmentation/
In
https://mailarchive.ietf.org/arch/msg/dnsop/lrPbp6B8Mkz2S7HBXlxSPoIhTOw/
I pointed out that zero of the implementers honour item 2 in section 3.1.
In
https://mailarchive.ietf.org/arch/msg/dnsop/QOxTZHG03UVLom9E-y6iYG5s6po/
you said "good point, we need to address this".
After that I have seen no communication on the list about addressing
this, so I'm very surprised to see this publication request.
FTR I agree that this document does not describe Best _Current_
Practice, and to underline the point I add that
> D.1. BIND 9
> BIND 9 does implement recommendation 2 of Section 3.2.
... does not seem to be correct. None of the values is used, and none of
the MAY methods is employed by BIND (in current versions).
--
Petr Špaček
Internet Systems Consortium
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
