[rfc-dist] RFC 5216 on The EAP-TLS Authentication Protocol
rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Fri, 21 March 2008 23:34 UTC
From: "rfc-editor at rfc-editor.org"
Date: Fri, 21 Mar 2008 16:34:43 -0700
Subject: [rfc-dist] RFC 5216 on The EAP-TLS Authentication Protocol
Message-ID: <20080321233443.F0736120690@bosco.isi.edu>
A new Request for Comments is now available in online RFC libraries. RFC 5216 Title: The EAP-TLS Authentication Protocol Author: D. Simon, B. Aboba, R. Hurst Status: Standards Track Date: March 2008 Mailbox: dansimon at microsoft.com, bernarda at microsoft.com, rmh at microsoft.com Pages: 34 Characters: 71599 Obsoletes: RFC2716 I-D Tag: draft-simon-emu-rfc2716bis-13.txt URL: http://www.rfc-editor.org/rfc/rfc5216.txt The Extensible Authentication Protocol (EAP), defined in RFC 3748, provides support for multiple authentication methods. Transport Layer Security (TLS) provides for mutual authentication, integrity-protected ciphersuite negotiation, and key exchange between two endpoints. This document defines EAP-TLS, which includes support for certificate-based mutual authentication and key derivation. This document obsoletes RFC 2716. A summary of the changes between this document and RFC 2716 is available in Appendix A. [STANDARDS TRACK] This document is a product of the EAP Method Update Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ...
- [rfc-dist] RFC 5216 on The EAP-TLS Authentication… rfc-editor@rfc-editor.org