| RE: Issue 174: Mandatory to Implement | <– Date –> <– Thread –> |
|
From: Walker, Jesse (jesse.walker |
|
| Date: Sun, 14 Sep 2003 04:18:24 -0500 (CDT) | |
Ill advised. EAP methods are outside the scope of the 802.11i PAR. > -----Original Message----- > From: Glen Zorn [mailto:gwz [at] cisco.com] > Sent: Friday, September 12, 2003 10:24 AM > To: 'Bernard Aboba' > Cc: eap [at] frascone.com > Subject: RE: [eap] Issue 174: Mandatory to Implement > > > Bernard Aboba <mailto:aboba [at] internaut.com> writes: > > >> The obvious problem is that this leaves EAP as essentially an empty > >> framework, removing the basis for any but purely formal > >> interoperability. In addition, since AFAIK 802.11i doesn't specify > >> any EAP method as mandatory (relying instead upon RFC 2284), it > >> leaves them in the same boat. Is this really desirable? > > > > Since EAP MD5-Challenge is already illegal for use with > IEEE 802.11i, > > they are already in this predicament, no? > > Is the use of EAP MD5-Challenge actually illegal or just ill-advised? > > ~gwz > > "They that can give up essential liberty to obtain a little temporary > safety deserve neither..." > -- Benjamin Franklin, 1759 > > "It is forbidden to kill; therefore all murderers are punished unless > they kill in large numbers and to the sound of trumpets." > -- Voltaire > > > _______________________________________________ > eap mailing list > eap [at] frascone.com > http://mail.frascone.com/mailman/listinfo/eap >
- RE: Issue 174: Mandatory to Implement, (continued)
-
RE: Issue 174: Mandatory to Implement Bernard Aboba, September 12 2003
- RE: Issue 174: Mandatory to Implement Glen Zorn, September 12 2003
- RE: Issue 174: Mandatory to Implement Bernard Aboba, September 12 2003
- RE: Issue 174: Mandatory to Implement Glen Zorn, September 12 2003
-
RE: Issue 174: Mandatory to Implement Bernard Aboba, September 12 2003
Results generated by Tiger Technologies using MHonArc.