| RE: Issue 174: Mandatory to Implement | <– Date –> <– Thread –> |
|
From: Bernard Aboba (aboba |
|
| Date: Fri, 12 Sep 2003 12:14:13 -0500 (CDT) | |
> 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?
-
Issue 174: Mandatory to Implement Bernard Aboba, September 11 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
- RE: Issue 174: Mandatory to Implement Glen Zorn, September 12 2003
-
RE: Issue 174: Mandatory to Implement Glen Zorn, September 12 2003
- RE: Issue 174: Mandatory to Implement Walker, Jesse, September 14 2003
Results generated by Tiger Technologies using MHonArc.