Does it need to recharter? Best regards, Badra
On 3/28/07, Bernard Aboba <[EMAIL PROTECTED]> wrote:
The latest EAP-TTLSv0 draft is available here: http://www.watersprings.org/pub/id/draft-funk-eap-ttls-v0-00.txt In terms of publication interest, back in the fall Jari Arkko had announced a program to encourage widely implemented EAP methods to publish their specifications as RFCs. As I recall, there was interest to publish EAP-FAST (in the RFC Editor queue), PEAPv0 (documentation currently being revised for submission as an Internet Draft). I don't know the current status of the EAP-TTLSv0 publication effort (e.g. whether publication has been requested or not). Steve Hanna might know. In terms of history, EAP-TTLSv0 was accepted as a Standards Track work item of the PPPEXT WG prior to the formation of the EAP WG. It has been implemented on a wide variety of platforms including open source versions for Windows (http://www.securew2.com/) and Linux (http://open1x.sourceforge.net/). Interoperability of EAP-TTLSv0 implementations is currently certified by the WFA. In terms of features that would be needed to meet EMU WG requirements, I think we are probably talking about crypto-binding and channel binding. It is possible that there may be other features needed for some scenarios ( e.g. mutual certificate authentication for a device/machine plus user auth for scenarios currently discussed within WiMAX Forum and 3GPP2).
_______________________________________________ Emu mailing list [email protected] https://www1.ietf.org/mailman/listinfo/emu
