Requirements for a Tunnel-Based Extensible Authentication Protocol Method
RFC 6678, “Requirements for a Tunnel-Based Extensible Authentication Protocol Method”, is an Informational document published in July 2012 by K. Hoeper, S. Hanna, H. Zhou, J. Salowey. The canonical text is published by the RFC Editor.
Abstract
This memo defines the requirements for a tunnel-based Extensible Authentication Protocol (EAP) Method. This tunnel method will use Transport Layer Security (TLS) to establish a secure tunnel. The tunnel will provide support for password authentication, EAP authentication, and the transport of additional data for other purposes. This document is not an Internet Standards Track specification; it is published for informational purposes.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 6678 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6677 Channel-Binding Support for Extensible Authentication Protocol Methods
- RFC 6679 Explicit Congestion Notification for RTP over UDP
- RFC 6676 Multicast Addresses for Documentation
- RFC 6680 Generic Security Service Application Programming Interface Naming Extensions
- RFC 6675 A Conservative Loss Recovery Algorithm Based on Selective Acknowledgment for TCP
- RFC 6681 Raptor Forward Error Correction Schemes for FECFRAME
- RFC 6674 Gateway-Initiated Dual-Stack Lite Deployment
- RFC 6682 RTP Payload Format for Raptor Forward Error Correction