I don't have any objections with leaving this as an extension. Sabine - are you still intending to fill out the details in draft-randriamasy-alto-multi-cost? Perhaps that could be the first ALTO protocol extension :)
I could imagine a couple of ways the extension could go: (1) Design a new service such as the multicost map service. This is easy within the current protocol (adding new services to the IRD is easy without breaking existing clients). (2) Treat queries for multiple cost types the same as a query for a cost type that is vector (I think this was basically the way we were heading in the design discussion previously on the list). I think this requires a bit of a change to the base protocol, but one that we proposed a while back (in particular, opaque cost types). I'll ping that thread to see if there are any objections to adding that in this revision and we can discuss on that thread if there are. Thanks Rich On Sat, Aug 27, 2011 at 12:29 PM, Reinaldo Penno <[email protected]> wrote: > I prefer 1. > > > On 8/26/11 11:01 PM, "Enrico Marocco" <[email protected]> > wrote: > >> The current specification allows cost maps to convey only one type of >> cost information at a time. It has been pointed out that, in some cases, >> applications may benefit from the presence of multiple cost-type values >> in a single cost map (see draft-randriamasy-alto-multi-cost for a >> detailed description of such use cases) and an extension for allowing >> that has been proposed. >> >> Possible options (please express and possibly motivate your preference): >> >> 1. allow only one type per cost map in the core protocol >> specification and define the syntax and usage of multi-cost maps >> as an extension; >> >> 2. extend the core protocol specification to allow multi-cost >> information to be queried and provided in base responses; >> >> 3. other. > > _______________________________________________ > alto mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/alto > _______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
