On Fri, 17 Nov 2023, Ray Bellis wrote:
Last time this came around I also suggested instead of n times QT
entries, to use the same method as NSEC does for conveying which RRtypes
are covered using a single bitmap:
https://datatracker.ietf.org/doc/html/rfc3845#section-2.1.2
Speaking personally, I am not a fan of NSEC bitmaps when used to encode a
small and possibly sparse list of QTYPES. It's relatively complicated to
encode / decode and is often inefficient.
I think it would be unwise to make assumptions on how people will use
this feature. They might want to ask for many more records along with
A/AAAA records. If we change a core DNS feature, it should not designed
for a specific DNSSD use case of HTTPS.
Paul
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop