W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2016

Re: draft-ietf-httpbis-header-structure-00, unicode range

From: Poul-Henning Kamp <phk@phk.freebsd.dk>
Date: Sun, 25 Dec 2016 14:31:28 +0000
To: Mark Nottingham <mnot@mnot.net>
cc: Ilari Liusvaara <ilariliusvaara@welho.com>, Kari Hurtta <hurtta-ietf@elmme-mailer.org>, HTTP working group mailing list <ietf-http-wg@w3.org>, Poul-Henning Kamp <phk@varnish-cache.org>
Message-ID: <63014.1482676288@critter.freebsd.dk>
--------
In message <6D8F0C71-BF83-438E-AF6E-4D7CA500F2B0@mnot.net>, Mark Nottingham wri
tes:

>> I see us having four options, in my order of preference:
>> 
>> 1) Forbid Unicode in headers.
>> 
>> 2) Take UTF8 out and leave all (non-ASCII) unicode to the \uxxxx
>>   escape mechanism.
>> 
>> 3) Leave UTF8 in, and make it clear that it may or may not work, so
>>   that people can use it in controlled environments.
>> 
>> 4) Leave UTF8 in, and specify how to indicate/negotiate if it can be 
>used.
>> 
>>> astral planes (and I hope the escape system there would be more sane
>>> than the one JSON has...)
>> 
>> Any suggestions ?
>
>When you say "take out / leave in" above, that's only in the context of 
>the HTTP/1 serialisation, correct?

Yes, sorry if that wasn't clear.


-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.
Received on Sunday, 25 December 2016 14:31:56 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 25 December 2016 14:31:59 UTC