On Apr 27, 2011, at 10:22 AM, Sebastian Kiesel wrote:
Hi,
On Wed, Apr 27, 2011 at 09:15:11AM +0800, ?????? wrote:
hi, everyone:
have the ALTO considered the use cases of wireless, which means how
to make
the selection of the peers in the wireless environment?
the ALTO protocols and procedures feature mechanisms that can be
leveraged in a mobile / wireless scenario. IMO there are two issues:
1. When a client is moving between different sections of an access
network it may have to find a new ALTO server which is able
to give guidance that is useful at the new client position.
draft-kiesel-alto-3pdisc-05, sec. 1.3 states:
o A change of the IP address at an interface invalidates the result
of the ALTO server discovery procedure. For instance, if the IP
address assigned to a mobile host changes due to host mobility,
it
is required to run the ALTO server discovery procedure for the
new
IP address without relying on earlier gained information.
mobility is often at layer-2 and this mean you will need some other
mechanisms in order to enrich your maps/ecs with wireless-l2 derived
topology info.
I agree with you: not sure these mechanisms needs standardization.
s.
2. The actual strategy (algorithm) for selecting peers is out of scope
of the standardization process, as there are many different
scenarios
with different constraints and optimization goals (e.g., in a given
mobile access network, is the backhaul capacity an issue or not?).
The ALTO client protocol together with a procedure for defining new
Host Characteristics Attributes (cost types) is able to convey the
input for a variety of different selection algorithms.
does this make sense?
thanks
sebastian
_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto
_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto
