eap Mailing List: RE: Re: Issue 251

[Congdon, Paul T (ProCurve) (paul.congdon]

The 'canned' messages are only send when the 802.1X port is
administratively forced authorized or unauthorized.   This is basically
when management turns off 802.1X and forces the port open or closed.
These message are also discussed in the text.

Paul 

> -----Original Message-----
> From: eap-admin [at] frascone.com [mailto:eap-admin [at] frascone.com] 
> On Behalf Of Nick Petroni
> Sent: Tuesday, July 27, 2004 8:13 AM
> To: Bernard Aboba
> Cc: eap [at] frascone.com
> Subject: Re: [eap] Re: Issue 251
> 
> > 802.1X "canned" messages are encapsulated EAP packets.  So 
> an 802.1X 
> > packet containing an EAP Success is expressly forbidden under RFC 
> > 3748, even though I think it is still mentioned in IEEE 
> 802.1X-2004.  
> > Similarly, our discussion of whether "canned" EAP Failure 
> is illegal 
> > also applies to "canned" 802.1X packets.
> Ok, this was the source of my confusion. I guess I assumed 
> that since they were in another standard they were going to 
> be allowed for backwards compatibility or some other legacy 
> argument. They are, indeed, still in the latest version, 
> which was another source of my confusion. They are in the 
> 802.1X SM diagrams, not just the text.
> 
> Thanks,
> nick
> 
> >
> 
> _______________________________________________
> eap mailing list
> eap [at] frascone.com
> http://mail.frascone.com/mailman/listinfo/eap
>