Jan,

On 14 Apr 2011, at 00:54, Jan Medved wrote:
> On 4/13/11 4:32 AM, "Ben Niven-Jenkins" <[email protected]> wrote:
>> * Extracting network topology is not an interoperability issue between
>> ALTO servers. Each ALTO server can extract the network topology
>> independently and if the topology needs to be distributed between ALTO
>> servers then it is an ALTO Server-Server API that needs standardising
>> *not* an ALTO Server-Network API.
> 
> Actually, extracting network topology and generating the abstracted
> network topology (maps) is an interoperability issue between ALTO Servers,
> and it can not be completely separated from the exchange of topology
> between ALTO servers. For ALTO Servers to be able to exchange (and
> reconcile) their respective abstracted topologies (maps) with each other,
> the topologies need to be equivalent. This then drives the need for a
> common set of data from which the topology is created and a normalized way
> to generate the topology from the data (which we mentioned in the draft,
> but did not attempt to specify).

I think this is the crucial bit for me. If you want two ALTO servers to produce 
the same result you need to identify the key bits of information they need to 
obtain from the network and how they will translate that into a ALTO 
representation of the network.

How they extract that information from the network is an orthogonal problem. 
Throwing the entire IGP into BGP (or for that matter specifying that an ALTO 
server must listen to both BGP and the IGP) doesn't help you with 
interoperability as you haven't specified what information the ALTO server 
needs know and what it needs to do with that data to generate the network and 
cost maps, you've just specified one possible way to import the raw data into 
the ALTO server.

<snip>

> Standardizing the way to get network topology through ALTO will extend
> ALTO's applicability rather than limit it. If ALTO does not define a
> standardized way to generate maps from topology data, people will simply
> use BGP (eventually with extensions that will convey the TE / IGP topology
> information), and bypass an ALTO Service that a provider may offer.

But your draft (and any ALTO Server - Network API) doesn't address how to 
standardise the way to get topology through ALTO. It just proposes one possible 
way to get topology *into* an ALTO server.

Ben


_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto

Reply via email to