EAP-TLS is also in Win2k (for PPP) but 802.1X is not.
You can always ask the IETF to move RFC2716 to standards track but you
need a second implementation.
In terms of 802.1X I know of people working on client implementations
for other OSs and it is capable of being independent of the client card,
as long as you have the right support in the card driver and firmware
(you need to be able to set the WEP key among other things). Cisco,
Agere and Symbol all work with WinXP against Cisco 802.1X APs as well as
other 802.1X APs.

-----Original Message-----
From: Scott Dier [mailto:diemanringworld.org]
Sent: Wednesday, August 29, 2001 6:27 PM
To: Jim Veneskey
Cc: hideyuki suzuki; aironetenkidu.cse.ucsc.edu
Subject: Re: [Aironet] A Complete Security Solution and WE

> (EAP-TLS = Windows XP)

EAP-TLS is detailed in rfc 2716, http://www.faqs.org/rfcs/rfc2716.html

Its 'Experimental' right now, so its not really a 'standard' but
something out there for the cause of interop.

EAP-TLS, IMO, would be a preferable thing to see implemented in Unix
based Radius Servers and Cisco Linux client software. Many places are
implementing a PKI and this would tie in nicely into existing
infrastructures. (And with x.509, not that f&*$#ing entrust stuff)

(We recently deployed about 16 350 APs. We are buying more. We really
like the product. We want to beable to go to 802.1x and be cross
platform and somewhat vendor agnostic for client cards.)

-- 
Scott Dier <diemanringworld.org> <sdierdebian.org>
http://www.ringworld.org/  #linuxosirc.openprojects.net
_______________________________________________
Aironet mailing list  -  Aironetcsl.cse.ucsc.edu
http://csl.cse.ucsc.edu/mailman/listinfo/aironet
_______________________________________________
Aironet mailing list  -  Aironetcsl.cse.ucsc.edu
http://csl.cse.ucsc.edu/mailman/listinfo/aironet

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]