Re: [dispatch] Initial version of draft-hoffman-dispatch-dns-over-https

Hi Paul,

Thanks for the heads-up.

"""
   A DNS API Client encodes the DNS query into the HTTP request using
   either the HTTP GET or POST methods.

   When using the POST method, the DNS query is included as the message
   body of the HTTP request and the Content-Type request header
   indicates the media type of the message.  POST-ed requests are
   smaller than their GET equivalents.
"""

I think it's a mistake to bifurcate the request style so fundamentally; it's HTTP tunnelling at its worst. 

The GET-style request in your example (which I think is pretty representative) uses 44 octets to encode the body; the POST serialisation is 33 octets. However, with HPACK's huffman encoding (remember, you're requiring HTTP/2), that goes down to 34 bytes.

Are we really that sensitive to on-the-wire size? To me, the cache efficiency gains as well as simplicity more than make up for a 3% difference. The statement that "POST-ed requests are smaller" isn't going to be true, in pathological cases.

"""
  The media type is "application/dns-udpwireformat"
"""

That's needlessly long; suggest "application/dns-uwf".

There's a laundry list of questions about what HTTP functionality the client needs to support. I'm hoping a draft will emerge shortly that will help with this.

Why shouldn't DNS API servers be able to generate ETags based upon their internal state, to reduce outbound bandwidth?

Cheers,

> On 27 Jun 2017, at 12:38 pm, Paul Hoffman <paul.hoffman@icann.org> wrote:
> 
> [[ Any comments on the -00 that we should incorporate into a -01 before the cutoff in a week? ]]
> 
> Greetings. Based on the advice from the chairs, we have given a new filename to our dns-over-https draft. This will hopefully get the draft picked up in the DISPATCH WG tracker page.
> 
> --Paul and Patrick
> 
> 
> A new version of I-D, draft-hoffman-dispatch-dns-over-https-00.txt
> has been successfully submitted by Paul Hoffman and posted to the
> IETF repository.
> 
> Name:		draft-hoffman-dispatch-dns-over-https
> Revision:	00
> Title:		DNS Queries over HTTPS
> Document date:	2017-06-17
> Group:		Individual Submission
> Pages:		12
> URL:            https://www.ietf.org/id/draft-hoffman-dispatch-dns-over-https-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-hoffman-dispatch-dns-over-https/
> Htmlized:       https://tools.ietf.org/html/draft-hoffman-dispatch-dns-over-https-00
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-hoffman-dispatch-dns-over-https-00
> 
> 
> Abstract:
>  DNS queries sometimes experience problems with end to end
>  connectivity at times and places where HTTPS flows freely.
> 
>  HTTPS provides the most practical mechanism for reliable end to end
>  communication.  Its use of TLS provides integrity and confidentiality
>  guarantees and its use of HTTP allows it to interoperate with
>  proxies, firewalls, and authentication systems where required for
>  transit.
> 
>  This document describes how to run DNS service over HTTP using
>  https:// URIs.
> 
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch

--
Mark Nottingham   https://www.mnot.net/