Hi a few comments opjn this draft....
1. RFC7766 ("All general-purpose DNS implementations MUST support both UDP and
TCP transport." should also be
noted at this point in the document, as avoiding fragmentation relies on a
working TCP fallback
2. (minor) change "Guidelines for Authoritative DNS Configuration" to
"Guidelines for Authoritative DNS Server Configuration"
3. "every iterative name server should be dual stack" - whats an "iterative
name server"? Do you mean a recursive resolver?
thanks
Geoff
> On 8 May 2024, at 5:20 PM, Momoka Yamamoto <momoka....@gmail.com> wrote:
>
> Hi dnsop wg.
> We have submitted an update to our rfc3901bis draft "DNS IPv6 Transport
> Operational Guidelines."
>
> The changes can be seen below.
> Diff from v3 to v5(current):
> https://author-tools.ietf.org/iddiff?url1=draft-momoka-dnsop-3901bis-03&url2=draft-momoka-dnsop-3901bis-05&difftype=--html
>
> The main difference from the previous version is the addition of the
> following, after Geoff's comments on DNS over UDP/IPv6 not working properly
> on large responses.
> We added a reference to I-D.ietf-dnsop-avoid-fragmentation to address the
> problem of IP fragmentation with IPv6.
>
> ```
> Avoiding Fragmentation:
> IP fragmentation has been reported to be fragile [RFC8900].
> Therefore, IP fragmentation should be avoided in order to treat
> both IPv4/IPv6 equally [I-D.ietf-dnsop-avoid-fragmentation].
> ```
>
> I hope to hear from the community about how this document can be improved.
>
> Momoka
>
> ---------- Forwarded message ---------
> From: <internet-dra...@ietf.org>
> Date: Tue, Apr 30, 2024 at 3:10 PM
> Subject: New Version Notification for draft-momoka-dnsop-3901bis-05.txt
> To: Momoka Yamamoto <momoka....@gmail.com>, Tobias Fiebig
> <tfie...@mpi-inf.mpg.de>
>
>
> A new version of Internet-Draft draft-momoka-dnsop-3901bis-05.txt has been
> successfully submitted by Momoka Yamamoto and posted to the
> IETF repository.
>
> Name: draft-momoka-dnsop-3901bis
> Revision: 05
> Title: DNS IPv6 Transport Operational Guidelines
> Date: 2024-04-30
> Group: Individual Submission
> Pages: 9
> URL: https://www.ietf.org/archive/id/draft-momoka-dnsop-3901bis-05.txt
> Status: https://datatracker.ietf.org/doc/draft-momoka-dnsop-3901bis/
> HTML: https://www.ietf.org/archive/id/draft-momoka-dnsop-3901bis-05.html
> HTMLized: https://datatracker.ietf.org/doc/html/draft-momoka-dnsop-3901bis
> Diff:
> https://author-tools.ietf.org/iddiff?url2=draft-momoka-dnsop-3901bis-05
>
> Abstract:
>
> This memo provides guidelines and documents Best Current Practice for
> operating authoritative and recursive DNS servers, given that queries
> and responses are carried in a mixed environment of IPv4 and IPv6
> networks. It expands on RFC 3901 by now suggesting authoritative and
> iterative resolvers to operate on both IPv4 and IPv6.
>
> This document obsoletes RFC3901. (if approved)
>
> Discussion Venues
>
> This note is to be removed before publishing as an RFC.
>
> Source for this draft and an issue tracker can be found at
> https://github.com/momoka0122y/draft-dnsop-3901bis.
>
>
>
> The IETF Secretariat
>
>
> _______________________________________________
> DNSOP mailing list -- dnsop@ietf.org
> To unsubscribe send an email to dnsop-le...@ietf.org
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ DNSOP mailing list -- dnsop@ietf.org To unsubscribe send an email to dnsop-le...@ietf.org
