Couple notes: -- In Section 3.1.
> Missing GLUE: You might want to reference RFC 9471 here[1]. -- Nit: > Note: To prevent name space fragmentation zone validation processes > SHOULD ensure that: replace with > To prevent name space fragmentation, zone validation processes > SHOULD ensure that: -- Consider adding Implementation Section - at least BIND 9 has dual-stack-servers option (https://bind9.readthedocs.io/en/v9.20.15/reference.html#namedconf-statement-dual-stack-servers) that provides means for a DNS resolver to reach the other family by falling back to the configure upstream resolver. I am pretty sure nobody except Mark knows about this :), so it might be useful to mention this (otherwise it is just a dead code). 1. although the document itself needs to be updated because of CVE-2025-40778[2] which basically limits glue to in-domain 2. https://kb.isc.org/docs/cve-2025-40778 and https://gitlab.isc.org/isc-projects/bind9/-/issues/5414 -- Ondřej Surý (He/Him) [email protected] > On 2. 11. 2025, at 14:02, Tobias Fiebig <[email protected]> > wrote: > > Moin, > > we just submitted an updated -05 of the document, which includes some > typo fixes, as well as the changes to the BCP14 language on address > synth. discussed on the list. > > With best regards, > Tobias > > On Sun, 2025-11-02 at 10:59 -0800, [email protected] wrote: >> A new version of Internet-Draft draft-ietf-dnsop-3901bis-05.txt has >> been >> successfully submitted by Momoka Yamamoto and posted to the >> IETF repository. >> >> Name: draft-ietf-dnsop-3901bis >> Revision: 05 >> Title: DNS IPv6 Transport Operational Guidelines >> Date: 2025-11-02 >> Group: dnsop >> Pages: 14 >> URL: >> https://www.ietf.org/archive/id/draft-ietf-dnsop-3901bis-05.txt >> Status: https://datatracker.ietf.org/doc/draft-ietf-dnsop-3901bis/ >> HTML: >> https://www.ietf.org/archive/id/draft-ietf-dnsop-3901bis-05.html >> HTMLized: >> https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-3901bis >> Diff: >> https://author-tools.ietf.org/iddiff?url2=draft-ietf-dnsop-3901bis-05 >> >> Abstract: >> >> This memo provides guidelines and documents Best Current Practice >> for >> operating authoritative DNS servers as well as recursive and stub >> DNS >> resolvers, given that queries and responses are carried in a mixed >> environment of IPv4 and IPv6 networks. This document expands on >> RFC >> 3901 by recommending that authoritative DNS servers as well as >> recursive DNS resolvers support both IPv4 and IPv6. It >> furthermore >> provides guidance for how recursive DNS resolver should select >> upstream DNS servers, if synthesized and non-synthesized IPv6 >> addresses are available. >> >> This document obsoletes RFC3901. (if approved) >> >> >> >> The IETF Secretariat >> > > -- > Dr.-Ing. Tobias Fiebig > T +31 616 80 98 99 > M [email protected] > > _______________________________________________ > DNSOP mailing list -- [email protected] > To unsubscribe send an email to [email protected] _______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
