On Mon, 2 Jul 2018, Eric Rescorla wrote:
https://tools.ietf.org/html/draft-rescorla-tls-esni-00
This is at a pretty early stage, so comments, questions, defect
reports welcome.
This structure is placed in the RRData section of a TXT record as a
base64-encoded string. If this encoding exceeds the 255 octet limit
of TXT strings, it must be split across multiple concatenated strings
as per Section 3.1.3 of [RFC4408].
It is strongly recommended not to use TXT records. Why not use a new
RRTYPE? Everything these days knows how to serve unknown record types
(see RFC 3597). The only possibly exception is provisioning tools of
small players, but this document starts of saying you basically need
to be on a bulk hosting provider anyway. They can properly provision.
I need to think more about the document to see if there is really not
something simpler or better possible.
Paul
_______________________________________________
TLS mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/tls
