- From: Alexey Melnikov <alexey.melnikov@isode.com>
- Date: Mon, 28 Oct 2013 17:51:39 +0000
- To: Martin Thomson <martin.thomson@gmail.com>
- CC: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>, Andrei Popov <Andrei.Popov@microsoft.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
On 28/10/2013 17:29, Martin Thomson wrote: > On 28 October 2013 04:32, Alexey Melnikov <alexey.melnikov@isode.com> wrote: >> So I would also like to see use cases for UTF-8 data which is not US-ASCII. > How about a use case that is neither ASCII nor UTF-8? > > There was concern raised about the overall size of the option when > there are multiple strings in the set. Aside from changing from > 16-bit lengths to 8-bit lengths (something I'd prefer, but am not > going to jump up and down over), the following was suggested. > > >From any set of strings, you can create another string that acts as a > stand-in for all of the set. That string is the output of a hash of > some canonical form of the input set (maybe sort, encode, hash). I am not yet sure about the hash idea yet, but if this is something that needs to be supported, then it is either binary or can be hex- or base64 encoded (and then it is ASCII). Either way, the binary case needs to have some text in the ALPN draft.
Received on Monday, 28 October 2013 17:52:06 UTC