Re: [dnsoverhttp] [Ext] DNS over HTTP: next steps?

[Erik Kline <[e-mail]>]

Shane,

Can you clarify something for me about the wireformat draft, section 3.4?

I believe that a client proxy does not include the DNS-over-TCP 2 byte
length toward the server, instead relying on the HTTP content-length.
Is it fair (and would be more clear) to simply say that the
DNS-over-TCP 2 byte length is *never* included when encapsulating over
HTTP regardless of role and query vs. response status?

I'm also a tad confused about how things look if one was, for example,
doing a zone transfer via DNS-over-HTTP and the server wanted to send
things with Transfer-Encoding of type chunked?

Actually, re-reading RFC 7230 sections 3.3.1 and 3.3.2, I believe that
if it's a requirement to include a Content-Length header then that
means Transfer-Encoding MUST NOT be used.  Is this fair to say, and is
it true of all DNS-over-HTTP data streams, regardless of role and
direction (i.e. it doesn't just apply to client requests)?

My apologies if I'm focusing on minutiae too early in the process.

Thanks.
-ek