[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CRACK

At 05:41 PM 10/26/99 +0300, Tero Kivinen wrote: 
I think the BCP18 (RFC2277) states, that you MUST define charset for
all character data, and you MUST be able to use UTF-8 charset. So I
think it is against that RFC to say that CRACK_MESSAGE is an ASCII
string. Changing it to "ISO-10646 UTF-8 string" should fix this issue.

A better way is to just say UTF-8 and reference RFC 2279 (which is about to go from Proposed to Draft standard).

Also we may want to add "standard" warning about escape/control
characters (from the draft-ietf-secsh-architecture-04.txt).

There's a similar warning in RFC 2279 that is specific to UTF-8.

--Paul Hoffman, Director
--VPN Consortium