[rfc-i] How lack of Unicode support in IDs is detrimental to design

Martin Rex mrex at sap.com
Fri Jul 27 14:05:56 PDT 2012

Phillip Hallam-Baker wrote:
> And in point of fact, the specification does specify both the PIN as
> it would be presented to the human user and the UTF8 byte code.
> But it is rather difficult to write a spec that says the bytecode
> value of "????	?-???Z-?" is [21 01 21 03 ...] without being able to
> give the PIN code in the form that it is intended to be presented to
> the human user. Just giving the bytecode says absolutely nothing of
> value as the spec already says that the bytes are fed into the MAC
> function.

Except that the presentation is completely garbled and useless,
and the hex dump is clear and umabiguous.


More information about the rfc-interest mailing list