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

[Henrik Levkowetz (henrik]

Jari, Nagi,

A version of the document (-08.a) updated according to the text below is
available at http://ietf.levkowetz.com/drafts/eap/rfc2284bis/. 

Jari,

I guess that formally we'll supply this as an RFC editor note during the
Author's 48 hours?

        Regards,
                Henrik


On Tuesday,  9 Dec 2003, nagi wrote:

> Jari,
> 
> Yes, it is perfect if you add the text to Appendix A.
> 
> Thanks
> Nagi
> 
> 
> 
> Jari Arkko wrote:
> 
> > We discussed this in issue 142, see
> >
> >    http://www.drizzle.com/~aboba/EAP/eapissues.html#Issue%20142
> >
> > and the mail archives. The working group agreed at that time,
> > do we have some new information at this time that would make
> > us reconsider this? I'm not sure there is.
> >
> > Having said that, I think Appendix A of RFC 2284bis is misleading
> > because it just talks about the ISO character set clarifications
> > in 5.1 and 5.2, but does not mention this issue. Perhaps we should
> > add the following text to Appendix A, right after the item that
> > talks about 5.1:
> >
> >     o  The null character is forbidden in the Type-Data field of an
> >        Identity Response message, as it is in RFC 2284. But the this rule
> >        has been relaxed for Identity Requests, and it is now required
> >        that if the Type-Data field of an Identity Request contains a
> >        null character, only the part before the null is displayed.
> >
> > Would this work for you?
> >
> > --Jari
> 
> _______________________________________________
> eap mailing list
> eap [at] frascone.com
> http://mail.frascone.com/mailman/listinfo/eap

Attachment: pgp00008.pgp
Description: PGP signature