This is a call for vendors and authors of existing,
deployed EAP methods to document their
protocols. The IESG, the RFC Editor, and a
number of volunteer reviewers want to
help this process and make it as smooth
Extensible Authentication Protocol (EAP -- RFC
3748) is used for network access control in
various link layers and protocols, including 802.11,
802.16, IKEv2, etc. Being extensible, EAP allows
different authentication methods. Unfortunately,
many of the real-world EAP methods are either
undocumented or poorly documented, particularly
those methods that were developed prior to
RFC 3748 and its IANA considerations being
The IETF is and has been addressing methods in the
EMU WG, as well as in some individual submissions.
For instance, there are currently four methods
in the RFC Editor's queue. However, these activities
are mostly about creating new methods that
can be used in future networks.
In addition, the IESG would like to see some commonly
used current EAP methods to be published as RFCs.
The intention would be to document current practice
and focus on accurate descriptions (as opposed to
improving the protocols or attempting to fix bugs in
them). We believe this improves overall interoperability
and makes it easier for anyone to implement equipment
that employs EAP.
More information available from an e-mail sent to the
EMU and EAP WG lists, archives at:
Please contact me if you are interested in this.
Ietf mailing list