Sebastian,
I agree with that 100%. I think that¹s the only practical deployment
scenario, for precisely the reasons you outlined.
However, over the last year, a number of folks have asked me, ³I¹ve heard
you¹re working on something called ALTO that¹s supposed to help me select
the best server. How does that work?² While learning about their
application, I¹ve discovered that almost every newbie expects an ALTO
server will have detailed cost information between any pair of endpoints
anywhere in the world. I¹ve tried to gently explain that your scenario is
more likely -- there won¹t be one global ALTO server. Instead there will
be a bunch of ALTO servers, each with local knowledge, and their
application will have to select the right ALTO server.
Of course, I haven¹t pushed that point too hard. I don¹t want to
discourage them from using ALTO!
But I am afraid that our customers may expect more from ALTO than ALTO can
deliver.
- Wendy
On 07/14/2014, 08:02, "Sebastian Kiesel" <[email protected]> wrote:
>My vision of a deployment scenario with distributed ALTO knowledge is:
>
>Every operator of an access network can publish (e.g., via the DNS) for
>each of their prefixes, which ALTO Server (i.e. IRD URI) is in charge.
>These ALTO servers will deliver very sparse cost maps, which are
>de-facto only a "cost from us to anywhere"-vector.
>
>If I am a network operator in, say Europe, I know the costs from my
>access networks to the rest of the Internet (both in terms of routing
>protocol costs and other traffic engineering parameters as well as
>monetary costs for network interconnections). But from where would I
>know the cost from, say, Tokyo to New York City (or, to be more precise,
>from a sepecific access network in Tokyo to a specific access network in
>New York City)? And even if I knew, why should I bother publishing it?
>I might even run into legal liabilities if I gave bad advice?! That's
>why I would only publish a "from us to anywhere"-vector (or a sparse
>"from our prefixes to anywhere"-matrix). This vector would
>be rather detailed about possible destinations in my vicinity and less
>detailed about other continents or difficult-to-reach networks.
_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto
