Subject: [eap] displayable message

From: [email-masked] (Jari Arkko)
Date: Sun, 11 May 2003 14:36:39 +0300

From the terms section:

>    Displayable Message
>              This is interpreted to be a human readable string of
>              characters, and MUST NOT affect operation of the protocol.
>              The message encoding MUST follow the UTF-8 transformation
>              format [RFC2279].

First, I'm not too happy to have keyword behaviour in the terms
section. Secondly, in Section 5.5 this term is used
for the OTP challenge, which I believe contains machine
readable sequence numbers and seeds. That would seem
to affect the behaviour of the protocol! Suggested rewrite:
move the MUST-NOT-affect-operation requirement to the
relevant sections where the term is referred to. Keep the
UTF-8 requirement here. Consider replacing 5.5 "displayable
message" with simply a reference to the OTP RFC format.

--Jari