Paul Vixie <p...@redbarn.org> wrote: > > for QTYPE=A, add AAAA as a desired additional data type. > > for QTYPE=AAAA, add A as a desired additional data type.
How does the server signal to a client that made an A query that there are no AAAA records so the client does not need to make a followup AAAA query? My answer: use DNSSEC :-) What are the incentives to implement this? The current state of the art is happy eyeballs version 2, which specifies concurrent AAAA and A queries; the client has already made both queries before it finds out it only needed to make one. I'm not sure how a client could know in advance that it only needs to make one query. I think there would be some benefit to this between auth and recursive, provided the recursive server eagerly validates additional records and promotes them to the authoritative answer level of RFC 2181 trust. Tony. -- f.anthony.n.finch <d...@dotat.at> http://dotat.at/ partnership and community in all areas of life _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
