I have some questions about this draft. How should responders populate the COUNT fields when one record answers multiple accompanying questions? For example, assume example.com has an MX record but no A or AAAA (the latter two thus being covered by an authority section SOA):
QUESTION example.com. IN MX AQ example.com. IN A AQ example.com. IN AAAA ANSWER example.com. 3600 IN MX 10 mail.example.net. AUTHORITY example.com. 3600 IN SOA … ADDITIONAL . 0 CLASS4096 OPT ??? In a more general sense, how are responders to generate—and how are initiators to interpret—responses in which it is not clear which question any given response record corresponds to? Section 3 defines the prefix field of an accompanying question as "a domain name with the form of a dot or a sequence of labels ending with a pointer"... could you clarify that "the form of a dot" refers to the root domain name (i.e., a single null label with wire format 0x00)? In section 4, what is meant by "the responder assembles the prefix with the main domain name"? Wire-format domain names are necessarily fully-qualified, whether or not they end with compression pointers. Is the operation to be interpreted as something like "if the prefix is the DNS root domain, treat it as the QNAME"? If so, I think such special processing is unnecessary, because it's already possible to reference the QNAME directly with a compression pointer. Why require accompanying question names to match or be subdomains of the QNAME? It precludes potentially useful queries like QNAME=www.example.com. accompanied by prefix=static.example.com., and prohibiting them doesn't prevent out-of-bailiwick queries anyway. Section 5 references a "not been implemented, too many accompanying-questions." response... what would that response look like? On Sun, Sep 17, 2017 at 11:19 PM, <internet-dra...@ietf.org> wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the Domain Name System Operations WG of the > IETF. > > Title : A DNS Query including A Main Question with > Accompanying Questions > Authors : Jiankang Yao > Paul Vixie > Ning Kong > Xiaodong Li > Filename : draft-yao-dnsop-accompanying-questions-04.txt > Pages : 11 > Date : 2017-09-17 > > Abstract: > This document enables DNS initiators to send a main question > accompanying with several related questions in a single DNS query, > and enables DNS responders to put the answers into a single DNS > response. This extension enables a range of initiators to look up > "X, or failing that, Y" in a better way than both current > alternatives. This mechanism can reduce the number of DNS round- > trips per application work-unit. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-yao-dnsop-accompanying-questions/ > > There are also htmlized versions available at: > https://tools.ietf.org/html/draft-yao-dnsop-accompanying-questions-04 > https://datatracker.ietf.org/doc/html/draft-yao-dnsop- > accompanying-questions-04 > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-yao-dnsop- > accompanying-questions-04 > > > Please note that it may take a couple of minutes from the time of > submission > until the htmlized version and diff are available at tools.ietf.org. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org > https://www.ietf.org/mailman/listinfo/dnsop >
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
