Download Network Working Group M. Vanderveen Request for Comments
Transcript
RFC 4763 EAP-SAKE November 2006 7. Acknowledgements ...............................................44 8. References .....................................................44 8.1. Normative References ......................................44 8.2. Informative References ....................................45 1. Introduction The Extensible Authentication Protocol (EAP), described in [EAP], provides a standard mechanism for support of multiple authentication methods. EAP is also used within IEEE 802 networks through the IEEE 802.11i [IEEE802.11i] framework. EAP supports several authentication schemes, including smart cards, Kerberos, Public Key, One Time Passwords, TLS, and others. This document defines an authentication scheme, called the EAP-SAKE. EAP-SAKE supports mutual authentication and session key derivation, based on a static pre-shared secret data. This RFC is published as documentation for the IANA assignment of an EAP Type for a vendor’s EAP method per RFC 3748. The specification has passed Designated Expert review for this IANA assignment. 2. Terminology In this document, several words are used to signify the requirements of the specification. These words are often capitalized. The key words "MUST", "MUST NOT", "REQUIRED", "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [KEYWORDS]. In addition to the terms used in [EAP], this document frequently uses the following terms and abbreviations: MIC Message Integrity Check SMS SAKE Master Secret NAI Network Access Identifier Vanderveen & Soliman Informational [Page 3]