eap Mailing List: Re: PKMv2 EAP Authenctication

[Rengith Thomas (Rengith.Thomas]

Dear Bernard,

Thank you  for the valuable information.One
more doubt i have related to the Link Status. 
 If I am making Link state UP explicitly
while creating the port , then can i use  the   IEEE 802.1X
state machine.(some time constraints i have 
force full to use  802.1x code).
Whether this change will  affect any  authentication procedure
in PKMv2 based authentication.
  

>I have doubts whether the IEEE 802.1X
state machine is applicable, because 16e begins 
>the interaction with EAP before
dataframes can be sent. If you are looking for a place to start, 
>the PPP state machine might be closer,
since in both 16e and PPP,
> EAP authentication occurs prior
to "Link Up", not after, as it does with IEEE 802.1X.


Regards,
Rengith Thomas

"Bernard Aboba" <bernard_aboba [at] hotmail.com>

03/08/2007 12:05 PM

To	Rengith Thomas/CHE/HSS [at] HSS
cc	eap [at] frascone.com
Subject	Re: [eap] PKMv2 EAP Authenctication

>So can you please provide some information about
the Key handling part in 
>each network entity.

I believe this is covered in the IEEE 802.16e-2005 specification, which
is 
available for download here:
http://standards.ieee.org/getieee802/802.16.html


_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/eap

Arhives: http://lists.frascone.com/pipermail/eap



***********************  Aricent-Private   ***********************

"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of 
the individual to whom it is addressed. It may contain privileged or confidential information and should not be 
circulated or used for any purpose other than for what it is intended. If you have received this message in error, 
please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly
prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for 
loss or damage arising from the use of the information transmitted by this email including damage from virus."