Subject: [eap] issue: jari's netsel-03 review, section 2 improvements

From: Jari Arkko <[email-masked]>
Date: Wed, 25 Jan 2006 15:58:45 +0200

>    The Access Network Discovery problem has been extensively studied,
>    see for instance the results of the IETF Seamoby WG, IEEE
>    specifications on 802.11 wireless LAN beaconing and probing process,
>    studies (such as [Fixingapsel]) on the effectiveness of these
>    mechanisms, and so on.

Maybe you could start with a reference to 802.11 as well as
some other (e.g. GSM cellular), then continue with the Seamoby
things; the main body of the work has been imho in the link
layers.

> 2.1  Access Network Discovery

This section is very 802.11 focused. It might make sense
to mention other link layers, too. For instance, cellular
link layers typically employ very network-centric mechanisms
for directing clients to the most suitable attachment point.

> While there
>    is Standards Track RFC specifying the interpretation of the field
>    beyond the NUL character, [I-D.adrangi-eap-network-discovery] is
>    widely expected to be used.

While there is NO Standards Track RFC?

Also, don't say anything about what usage expectations there
are. Just state that the spec exists.

> For instance, the Redirect feature could be used to provide
>    a centralized routing function for AAA, without having to know all
>    home network names in all access networks.

There should be some truth-in-advertising disclaimer
here. We don't know how to set the security up for
that in practice, and even if we did, it might not match
business practices.

_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/eap

Arhives: http://lists.frascone.com/pipermail/eap