eap Mailing List: Re: PKMv2 EAP Authenctication

[Rengith Thomas (Rengith.Thomas]

Dear Bernard,

We need to implement a pass through
authenticator. RFC 4137 explains the state machine implementation of RFC
3748.  So while designing Gateway/EAP_Authenticator, Whether we have
to stick to IEE 802.1X state machines with some changes or RFC
4137 state machine (decision = PASSTHROUGH). 

The  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 

Your views will be very helpful for
our design. Thanks in advance


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