Petr,

On Thu, Jul 4, 2024 at 3:22 AM Petr Špaček <pspa...@isc.org> wrote:

> I've reviewed version 18 and it seems okay.
>
> I have only nit:
> Section C.1. BIND 9 is using somewhat confusing references to
> recommendations. Sometimes it says "recommendation 3" but it means
> something else than R3 in the preceding text.
>
> Some unification would be good, but that's really a nit. This section
> will become obsolete over time anyway :-)
>
>
Thanks for this and a good catch.  Initially I suggested the
recommendations be numbered 1, 2, 3, ... in each section, but then I
realized that was confusing and we moved to the R1, R2, ....  I also think
there has been some consolidation of recommendations.

Let me go back a few versions and figure out the changes and apply them to
Appendix C.1.

I will return with some suggested text.

tim



Petr Špaček
> Internet Systems Consortium
>
>
> On 02. 07. 24 21:49, Tim Wicinski 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: <internet-dra...@ietf.org <mailto:internet-dra...@ietf.org>>
> > Date: Fri, Jun 28, 2024 at 7:47 AM
> > Subject: New Version Notification -
> > draft-ietf-dnsop-avoid-fragmentation-18.txt
> > To: <be...@nlnetlabs.nl <mailto:be...@nlnetlabs.nl>>, <swo...@pir.org
> > <mailto:swo...@pir.org>>, <tjw.i...@gmail.com
> > <mailto:tjw.i...@gmail.com>>, <war...@kumari.net <mailto:
> war...@kumari.net>>
> >
> >
> >
> > 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
> <
> 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/
> > <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
> <
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-dnsop-avoid-fragmentation-18
> >
> >
> > IETF Secretariat.
> >
> >
> >
> > _______________________________________________
> > DNSOP mailing list -- dnsop@ietf.org
> > To unsubscribe send an email to dnsop-le...@ietf.org
>
> --
> Petr Špaček
>
> _______________________________________________
> DNSOP mailing list -- dnsop@ietf.org
> To unsubscribe send an email to dnsop-le...@ietf.org
>
_______________________________________________
DNSOP mailing list -- dnsop@ietf.org
To unsubscribe send an email to dnsop-le...@ietf.org

Reply via email to