- From: Poul-Henning Kamp <phk@phk.freebsd.dk>
- Date: Tue, 13 Dec 2016 21:28:47 +0000
- To: Kari Hurtta <hurtta-ietf@elmme-mailer.org>
- cc: HTTP working group mailing list <ietf-http-wg@w3.org>, Poul-Henning Kamp <phk@varnish-cache.org>
-------- In message <20161213173327.C1F7D1714B@welho-filter2.welho.com>, Kari Hurtta wri tes: >2. Definition of HTTP Header Common Structure >https://tools.ietf.org/html/draft-ietf-httpbis-header-structure-00#section-2 > >| unicode_string = * unicode_codepoint >| # XXX: Is there a place to import this from ? >| # Unrestricted unicode, because there is no sane >| # way to restrict or otherwise make unicode "safe". > >What is range of unicode_codepoint ? As far as I know, UNICODE does not have a firm upper end, but everybody _expects_ 32 bits to be enough for everybody. Since section two is the abstract datamodel, that's the best we can do there. >3. HTTP/1 Serialization of HTTP Header Common Structure >https://tools.ietf.org/html/draft-ietf-httpbis-header-structure-00#section-3 >[...] >Or is unicode values > 0xFFFF >encoded with surrogates (values 0xd8000 - 0xdffff) ? >( UCS-2 or UTF-16 is used ) That was the plan. Not a particular good plan, as evindenced by the fact that I forgot to write that, and that JSON has seen interop issues with parsers missing that detail. I will add text about it. -- 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 Tuesday, 13 December 2016 21:29:21 UTC