Since this seems to be of at least some interest again I've resurrected this draft from its expired state.
The main comment I had first time around was that it appeared to be unnecessary to include the count of the QTYPEs within the OPT wire format since that can be intuited from the overall length of the RDATA. It was also suggested that the QTD bit could be replaced with using one OPT code point for requests and another for responses. I do not favour this approach, since no other OPT RR uses it. Arguably there should be a better way in EDNS to differentiate a true response from a dumb echo... Ray -------- Forwarded Message -------- Subject: New Version Notification for draft-bellis-dnsext-multi-qtypes-02.txt Date: Thu, 14 Apr 2016 10:09:47 -0700 From: [email protected] To: Ray Bellis <[email protected]> A new version of I-D, draft-bellis-dnsext-multi-qtypes-02.txt has been successfully submitted by Ray Bellis and posted to the IETF repository. Name: draft-bellis-dnsext-multi-qtypes Revision: 02 Title: DNS Multiple QTYPEs Document date: 2016-04-13 Group: Individual Submission Pages: 6 URL: https://www.ietf.org/internet-drafts/draft-bellis-dnsext-multi-qtypes-02.txt Status: https://datatracker.ietf.org/doc/draft-bellis-dnsext-multi-qtypes/ Htmlized: https://tools.ietf.org/html/draft-bellis-dnsext-multi-qtypes-02 Diff: https://www.ietf.org/rfcdiff?url2=draft-bellis-dnsext-multi-qtypes-02 Abstract: This document specifies a method for a DNS client to request additional DNS record types to be delivered alongside the primary record type specified in the question section of a DNS query. _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
