Greetings, answer section fans, See below, as previously discussed in 2015 (!) and earlier this year. You might recall the various threads along the lines of
- we shouldn't have to do this, people should fix their software - we understand some of this software will never be fixed though - Arrgh ok FINE, let's hold our nose though I understand I gave a small slot on the agenda in San Francisco to remind people about this with spoken word. Here is the text for those who like to read ahead. Joe Begin forwarded message: > From: [email protected] > Date: 5 November 2026 at 20:00:51 CET > To: Joe Abley <[email protected]>, Sebastiaan Neuteboom > <[email protected]> > Subject: New Version Notification for > draft-jabley-dnsop-ordered-answer-section-02.txt > > A new version of Internet-Draft > draft-jabley-dnsop-ordered-answer-section-02.txt has been successfully > submitted by Joe Abley and posted to the > IETF repository. > > Name: draft-jabley-dnsop-ordered-answer-section > Revision: 02 > Title: Ordering of RRSets in CNAME Responses in the DNS > Date: 2026-11-05 > Group: Individual Submission > Pages: 9 > URL: > https://www.ietf.org/archive/id/draft-jabley-dnsop-ordered-answer-section-02.txt > Status: > https://datatracker.ietf.org/doc/draft-jabley-dnsop-ordered-answer-section/ > HTML: > https://www.ietf.org/archive/id/draft-jabley-dnsop-ordered-answer-section-02.html > HTMLized: > https://datatracker.ietf.org/doc/html/draft-jabley-dnsop-ordered-answer-section > Diff: > https://author-tools.ietf.org/iddiff?url2=draft-jabley-dnsop-ordered-answer-section-02 > > Abstract: > > In the DNS, recursive resolvers receive queries and formulate > corresponding responses by reference to data obtained from > authoritative servers. In the case where the query name (QNAME) and > class (QCLASS) in the query matches an owner name in the DNS where a > canonical name (CNAME) resource record is published, the response > includes both the CNAME record and the resource record set > corresponding to the request's query type (QTYPE) published at the > CNAME target. The ordering of these two different RRSets has not > previously been clearly specified, but operational experience based > on real-world client implementations confirms that the order is > important. This document updates RFC 1034 1035 to provide a clearer > specification, consistent with deployed implementations. > > > > The IETF Secretariat > >
_______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
