30 likes | 158 Views
“draft-urien-eap-smartcard-type-01.txt”. EAP Smart Card Protocol (EAP-SC) Pascal.Urien@enst.fr. Why do we need a type for smartcard ?. Why not?. Existing types relative to tokens or smartcards (according to www.IANA.org)
E N D
“draft-urien-eap-smartcard-type-01.txt” EAP Smart Card Protocol (EAP-SC) Pascal.Urien@enst.fr
Why do we need a type for smartcard ? • Why not?. • Existing types relative to tokens or smartcards (according to www.IANA.org) • 6 Generic Token Card (RFC3748) , 14 Defender Token, 15 RSA Security SecurID EAP, 18 Nokia IP smart card authentication, 28 CRYPTOCard, 30 DynamID, 32 SecurID EAP, … • Prerequisite • Method is clearly defined and standardized. • Method may be implemented by other means than smartcards. • Smartcard interface, associated with a particular method is clearly defined and standardized. • Benefits • Standardization of smartcards use with EAP scenario. • Avoid conflicts when the host supports multiple instances of a given type (EAP-TLS, …). Smartcard may be removed from the supplicant host, it’s clearly linked to terminal user. • Proposed mechanism • EAP in EAP encapsulation
Messages Structures code Idt Length+8 Vendor-Id=0 Type = EAP-SC EAP-SC Message Vendor-Type = type Payload type EAP Message received/sent from/to smartcard handler code Idt Length Payload type