[DNSOP] Re: [v6ops] Fwd: New Version Notification - draft-ietf-dnsop-avoid-fragmentation-18.txt

[Tim Wicinski <[e-mail]>]

David

Thanks for the comments.

On Tue, Jul 2, 2024 at 9:26 PM David Farmer <[e-mail]> wrote:

> A couple of issues I noticed;
>
> 1. The text added to R2 in section 3.1 refers to Appendix C, but it
> includes an Editor's Note that it will be removed, leaving this as a
> dangling reference. The Editor's Note should probably be removed.
>

That's a good point to remove the reference.  There has been much back and
forth on keeping or not keeping Appendix C.  The appendix was added to
collect information from Implementers describing which recommendations they
support (or not).


> 2. Also, maybe R5 should have text similar to R3 with "...the minimum
> of...the interface MTU, the network MTU...and 1400 bytes..." Instead of "It
> should use a limit of 1400 bytes, but a smaller limit MAY be used."
>

Something like this:

"UDP requestors should limit the requestor's maximum UDP payload size  to
use the RECOMMENDED size of 1400 bytes, but a smaller limit MAY be used."


tim


> Thanks
>
> On Tue, Jul 2, 2024 at 2:52 PM Tim Wicinski <[e-mail]> wrote:
>
>>
>> (please note I'm sending this to DNSOP and V6OPS)
>>
>> All
>>
>> The authors have addressed the comments made during the IESG process and
>> feedback from DNS implementers, and have published version 18.
>> The links for the diff are mentioned below.   I will point out the
>> additional introduction paragraph added in this version:
>>
>>     This document was originally intended to be a BCP, but due to
>>     operating system and socket option limitations, some of the
>>     recommendations have not yet gained real-world experience and
>>     therefore the document is published as Informational.  It is hoped
>>     and expected that, as operating systems and implementations evolve,
>>     we will gain more experience with the recommendations, and plan to
>>     publish an updated document as a Best Current Practice.
>>
>>
>> Speaking as one who wears many hats, I am OK with this and feel this
>> document is the first step in documenting best practices on fragmentation
>> with DNS.
>> I am always hoping to be proven incorrect.
>>
>> We will elicit feedback on this latest and we feel the final update.   We
>> will discuss with Mr Warren tomorrow during our Chairs call if he has other
>> concerns.
>>
>> thanks
>> tim
>>
>> ---------- Forwarded message ---------
>> From: <[e-mail]>
>> Date: Fri, Jun 28, 2024 at 7:47 AM
>> Subject: New Version Notification -
>> draft-ietf-dnsop-avoid-fragmentation-18.txt
>> To: <[e-mail]>, <[e-mail]>, <[e-mail]>, <
>> [e-mail]>
>>
>>
>>
>> A new version (-18) has been submitted for
>> draft-ietf-dnsop-avoid-fragmentation:
>>
>> https://www.ietf.org/archive/id/draft-ietf-dnsop-avoid-fragmentation-18.txt
>>
>>
>> The IETF datatracker page for this Internet-Draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-dnsop-avoid-fragmentation/
>>
>> Diff from previous version:
>>
>> https://author-tools.ietf.org/iddiff?url2=draft-ietf-dnsop-avoid-fragmentation-18
>>
>> IETF Secretariat.
>>
>>
>> _______________________________________________
>> v6ops mailing list -- [e-mail]
>> To unsubscribe send an email to [e-mail]
>>
>
>
> --
> ===============================================
> David Farmer               Email:[e-mail]
> Networking & Telecommunication Services
> Office of Information Technology
> University of Minnesota
> 2218 University Ave SE        Phone: [phone]
> Minneapolis, MN 55414-3029   Cell: 612-812-9952
> ===============================================
>