eap Mailing List: Re: Re: network discovery & selection: problem definition

[Michael Richardson (mcr]

-----BEGIN PGP SIGNED MESSAGE-----


So, I have another network selection problem/challenge. Feel free
to tell me I'm out of scope, but don't ask what I'm smoking, because
you can't have any :-)

It involves interactions between layers. I would like to be able to move
around from place to place, and have things "just work". (vs how things
went at the last IETF...)

At one colleague's office there is wireless. It happens to be a non-WEP
(we use IPsec, wavesec.org), with an unannounced ESSID. The DHCP will give
out public IP addresses, and also include other options that I want to
recognize. The next office over has a totally open network, NAT'ed. I won't
want to be on that network.

Naively, if you don't do the right thing, you wind up on the wrong network,
because the thing that knows what network I want to be one is the DHCP,
while the 802.11 stuff has already happened.

Meanwhile, at a different location, I want to recognize that I'm being
offered a for-pay EAP system. 

So, ideally, I'd like to have only one system. I'd like to have EAP,
DHCP and PPPoE discovery state machines all integrated together. Frankly,
I rather wish that we did EAP and PPPoE inside of DHCP.

]       ON HUMILITY: to err is human. To moo, bovine.           |  firewalls  [
]   Michael Richardson,    Xelerance Corporation, Ottawa, ON    |net architect[
] mcr [at] xelerance.com      http://www.sandelman.ottawa.on.ca/mcr/ |device 
driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Finger me for keys

iQCVAwUBP9T8YYqHRg3pndX9AQEczAP/bt69Jk3WWYewaVJWoptPbwTqYWva0mgp
2goECNPBPaE5PLTkXQkU2L1tB167ERZga+hw/MxWwRjkggkMd0GnNdpGZs0dSSWd
K8ANyD83zOoR66MsvG0o5bz2nemcUrMmtMYyDTT4BF9R+H5XLab4zFDxaA87Tkz4
6pMYZSl7HJg=
=mGLn
-----END PGP SIGNATURE-----