eap Mailing List: Re: PKMv2 EAP Authenctication

[Rengith Thomas (Rengith.Thomas]

Dear Bernard,

          Thanks
for the prompt reply.
           Can
you please give some  more input for the Authenticator Key handling
part.
           The
whole n/w is like this ( MS <--> BS <-->Authenticator<-->AAA)
           

           
AKA                    
                     
                     
                     
                     
                     
   AKA
            EAP        
                  EAP  
EAP                    
  EAP   EAP              
                     
    EAP 
            PKMv2        
             PKMv2 ???    
                 ??? RADIUS
                     
              RADIUS
            ------------      
             ------------    
                   -------------------------
                     
           -----------
          MSS/EAP_peer      BS/EAP_Proxy
        Gateway/EAP_Authenticator      
    AAA server 

        From  Wimax forum studies of PKMv2
, during initial network entry sequence , it says about 
      the  generation
of keys.The  PMK(Pairwise Master key) key generated  using
MSK(Master Session key)
        and AK(authorization
key) generated in authenticator and MS using PMK key.

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


Regards,
Rengith Thomas

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

03/07/2007 09:34 PM

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

IEEE 802.16e does not support IEEE 802.1X authentication,
because with 
802.16 (like PPP), authentication is required prior to bringing the link
up. 
  Therefore EAP packets encapsulated in a dataframe prior to "link
up" will 
be dropped.

>I was seeing the feasiblity of using IEEE 802.1x  EAPOL code for
handling
>the PKMv2 Eap authentication.





***********************  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."