Subject: Re: [alto] interop test

From: Wendy Roome <[email-masked]>
Date: Tue, 02 Jun 2015 10:26:58 -0400

How about the following simplified outline of the interop test:

The interop test specifies:

* A default network map (PIDs & CIDRs).
* An alternate network map.
* Numerical values for routingcost & hopcount for both network maps.
* Values for a set of custom endpoint properties.

Each ALTO server MUST provide an IRD with the following resources:

* A full network map for the default network.
* A full cost map for routingcost for the default network, in either
numerical or ordinal mode; if ordinal mode, the values must be consistent
with the specified numerical values.
* An endpoint property service for the pid property for the default
network map.

Each ALTO server MAY provide additional resources, including:

* A full network map for the alternate network.
* Full cost maps for the routingcost & hopcount metrics, in numerical
and/or ordinal modes, for either or both network maps.
* Filtered network map(s) for either or both networks.
* Filtered cost map(s), which may or may not allow constraints.
* Endpoint cost service(s), which may or may not allow constraints.
* Endpoint property service(s) for the custom properties.

Each ALTO client MUST:

* Fetch the IRD.
* Locate & fetch the default network map, even if the server offers an
alternate network map, and verify the values.
* Locate & fetch the routingcost cost map for the default network map, in
whatever mode the server offers, and verify the values.
* Locate the EPS for the default network map's pid property, fetch the
PIDs for several endpoint addresses, and verify they are correct.

Each ALTO client MAY:

* Fetch & verify any resource it recognizes.

	- Wendy Roome