[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Review of draft-adrangi-eap-network-selection-07.txt
- To: aaa-doctors@ops.ietf.org
- Subject: Review of draft-adrangi-eap-network-selection-07.txt
- From: Bernard Aboba <aboba@internaut.com>
- Date: Sun, 13 Feb 2005 10:45:29 -0800 (PST)
- In-reply-to: <Pine.LNX.4.56.0406230824200.26064@internaut.com>
- References: <Pine.LNX.4.56.0406230824200.26064@internaut.com>
"Identity Selection Hints for EAP" is an individual submission to the
RFC Editor that has recently gone to IETF Last Call:
http://www1.ietf.org/mail-archive/web/ietf-announce/current/msg00832.html
The document is available for inspection here:
http://www.ietf.org/internet-drafts/draft-adrangi-eap-network-discovery-07.txt
Prior to last call expiration, an issue was raised about the security of
the mechanisms described in the draft, as well as their compatibility with
existing AAA servers:
http://mail.frascone.com/pipermail/eap/2005-February/003113.html
Since this document has impact on AAA as well as on EAP, I would like to
request a review of the document by the AAA doctors.
Some things to think about:
o Is the document consistent with behavior described in existing
AAA/EAP documents, such as RFC 3579 and draft-ietf-aaa-eap-10.txt?
o Does the document introduce significant new security issues?
o Is the document a reasonable basis on which to build interoperable
roaming?
Since this is a document in IETF Last Call, please send comments not only
to this list, but also CC: them to eap@frascone.com and iesg@ietf.org.