Re: Unicode escape sequence | Re: draft-ietf-httpbis-header-structure-00, unicode range

In message <>, Julian Reschke writes

>> There is -- RFC5987 encoding. Not pretty or efficient, but
>> implemented and interoperable. Used in Content-Disposition, Link
>> (although not much), and not much else AFAIK (Julian?).
>It's used in the new Digest spec, but I don't believe it's implemented yet.

(RFC5987 uses %XX and UTF-8)

BCP137 doesn't really say anything about that, except a mild scorn for
UTF8 in general in preference for 'human readable' unicode points, and
I unless we want to incorporate RFC5987 into header-structure, we should
probably lean more on BCP137.

I asked previously if header-structure should incorporate RFC5987,
but I understodd the answer as "don't bother" ?

(The main problem in absorbing RFC5987 is that a trailing '*' on a
dictionary key gets a special meaning, and '*' is a valid character
in a RFC7230::token on which I based header-structure's identifier.)

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 Saturday, 24 December 2016 09:05:14 UTC