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]
