> On the other hand, there are many other cost types (or
> "rating criteria", as the ALTO requirements document RFC 6708
> calls them), where an exact specification how to compute and
> how to encode them makes sense, e.g.:
>
> - draft-scharf-alto-vpn-service-00 talks about publishing the
> geographical location of a data center using ALTO. How excatly
> do we encode longitude/latitude? This might fit into two lines
> of text directly in the IANA registry.
For what it is worth (slightly off-topic in this thread): Approximate
geographic location is already explicitly mentioned in the ALTO charter
("Initially the WG will consider: IP ranges to prefer and to avoid, ranked
lists of the peers requested by the client, information about topological
proximity and approximate geographic locations.").
IMHO, regarding geographical locations, draft-scharf-alto-vpn-service-00 just
suggests something that the charter already mentions.
Michael
_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto
