What about exchanges of arbitrary data in the protected tunnel (may include channel binding), optional server side authentication with inner method support for weak password. Would it make sense to create a single TLS based tunneling method instead of two separate ones, one for enhanced TLS, and another one for tunneling method support for weak password?
> -----Original Message----- > From: Joseph Salowey (jsalowey) > Sent: Thursday, June 08, 2006 4:01 PM > To: emu@ietf.org > Subject: [Emu] Enhanced EAP-TLS > > One of our charter items is to develop an enhanced EAP-TLS > that can support features that are not possible to support in > a manner that is backward compatible with RFC2716. > > Some of the potential features on the list include: > > 1. Additional cipher suites (PSK, Kerberos, ECC) 2. TLS > extensions 3. Channel Bindings 4. Identity protection > > Are there additional features that should be supported by an > enhanced TLS? > > _______________________________________________ > Emu mailing list > Emu@ietf.org > https://www1.ietf.org/mailman/listinfo/emu > _______________________________________________ Emu mailing list Emu@ietf.org https://www1.ietf.org/mailman/listinfo/emu
