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

In message <>, Kari Hurtta wri

>2.  Definition of HTTP Header Common Structure
>|     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
>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