Requirements for a Tunnel-Based Extensible Authentication Protocol (EAP) Method
Draft of message to be sent after approval:
From: The IESG <email@example.com> To: IETF-Announce <firstname.lastname@example.org> Cc: Internet Architecture Board <email@example.com>, RFC Editor <firstname.lastname@example.org>, emu mailing list <email@example.com>, emu chair <firstname.lastname@example.org> Subject: Document Action: 'Requirements for a Tunnel Based EAP Method' to Informational RFC (draft-ietf-emu-eaptunnel-req-09.txt) The IESG has approved the following document: - 'Requirements for a Tunnel Based EAP Method' (draft-ietf-emu-eaptunnel-req-09.txt) as an Informational RFC This document is the product of the EAP Method Update Working Group. The IESG contact persons are Sean Turner and Tim Polk. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-emu-eaptunnel-req/
Technical Summary This memo defines the requirements for a tunnel-based Extensible Authentication Protocol (EAP) Method. This 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. Working Group Summary The document has had substantial review from a number of working group participants. The working group is ready to start working on protocols. Document Quality The document is a requirements document that has had contributions from Working group participants from different vendors. Discussion in the Working group has resulted in improvements to the document. Personnel Alan DeKok (email@example.com) is the document shepherd. Sean Turner (firstname.lastname@example.org) is the responsible Area Director.