| Re: network discovery & selection: problem definition | <– Date –> <– Thread –> |
|
From: Jari Arkko (jari.arkko |
|
| Date: Thu, 11 Dec 2003 01:55:28 -0600 (CST) | |
Alper Yegin wrote:
--Jari
The primary network discovery and selection issue is routing within the AAA infrastructure, giving access to the user from the right home AAA and via the right AAA proxies.
I'd say network selection also impacts "data traffic routing", which should not have to be hard-bound to the AAA routing (or, my home AAA
Yes, this is a good point, thanks for bringing it up! Here's a question for you: do you expect some mechanism which allows you to control data traffic routing, or is the requirement simply that it is not hard-bound to the AAA routing? Currently, there is no user-level way to control routing (and probably shouldn't be). But access, intermediate, and home networks can control routing to an extent e.g. through mandatory tunneling.
server). For example, I might want to select ISPx among several, and let it charge my alper [at] visa.com account.
Hmm... wouldn't visa.com then be your home network, and the selected ISP just an access (or intermediate) network?
--Jari
- Re: network discovery & selection: problem definition, (continued)
- Re: network discovery & selection: problem definition Yoshihiro Ohba, December 1 2003
- Re: network discovery & selection: problem definition Jari Arkko, December 1 2003
- Re: network discovery & selection: problem definition Yoshihiro Ohba, December 1 2003
- Re: network discovery & selection: problem definition Jari Arkko, December 10 2003
- Re: network discovery & selection: problem definition Alper Yegin, December 11 2003
- Re: network discovery & selection: problem definition Michael Richardson, November 30 2003
Results generated by Tiger Technologies using MHonArc.