eap Mailing List: RFC-2284bis-07 Identity request

[nagi reddy jonnala (Nagi_Reddy.Jonnala]

I understand that RFC2284bis-07 Section 5.1 conflicts with the RFC2284
Section 3.1

See the text from 2284-bis.

"
      This field MAY contain a displayable message in the Request,
      containing UTF-8 encoded ISO 10646 characters [RFC2279].  Where
      the Request contains a null, only the portion of the field prior
      to the null is displayed.  If the Identity is unknown, the
      Identity Response field should be zero bytes in length.  The
      Identity Response field MUST NOT be null terminated.  In all
      cases, the length of the Type-Data field is derived from the
      Length field of the Request/Response packet.
"

See the text from 2284 Section 3.1 - Identity Type-Data field.

   "This field MAY contain a displayable message in the Request.  The
      Response uses this field to return the Identity.  If the Identity
      is unknown, this field should be zero bytes in length.  The field
      MUST NOT be null terminated.  The length of this field is derived
      from the Length field of the Request/Response packet and hence a
      null is not required."

Particularly, the last sentence (of 2284)  means that the Request cannot
have a NULL. I guess the intention was to recommend the use of length
rather than a NULL.

Though I don't have any objections to use the space after NULL,  I would
like to know if that causes any issues. At the same time, I propose to
explicitly mention the same thing in the 2284-bis.

Regards
Nagi.