If HTTPs acts as a transport for DNS even with dns-udpwireformat MIME type, it should not be treated as a datagram encapsulted in a HTTPs header but a new byte stream over HTTPs(similar with DNS TCP). No truncation loop is needed. It is different from DNS wire-format over HTTP.
I'm wondering is it worthwhile differenciating the term "DNS HTTPs" with "DNS over HTTP(s)", in which the former means HTTPs transport usage, the later means DNS in a HTTP(s) tunnel.
If HTTPs acts as a transport for DNS even with dns-udpwireformat MIME type, it should not be treated as a datagram encapsulted in a HTTPs header but a new byte stream over HTTPs(similar with DNS TCP). No truncation loop is needed. It is different from DNS wire-format over HTTP.
I'm wondering is it worthwhile differenciating the term "DNS HTTPs" with "DNS over HTTP(s)", in which the former means HTTPs transport usage, the later means DNS in a HTTP(s) tunnel.
Davey