Hi Ben, Endpoint cost service calculates the cost of the client sending the message to one or more clients. The client's IP address is used in order to generate the appropriate answer.
The endpoint property lookup service provides a way to find a list of properties about a endpoint. The IP address of the client sending the query has no bearing on the answer. Or does it? Or you are talking about a client finding properties for itself? Thanks, Reinaldo On 6/24/11 10:48 AM, "Ben Niven-Jenkins" <[email protected]> wrote: > Colleagues, > > Section 10.3 of draft-ietf-alto-protocol-08 states: > > The protocol specified in this document provides a mode of operation > where the source network location is computed by the ALTO Server (via > the Endpoint Property Lookup interface) from the source IP address > found in the ALTO Client query packets. This is similar to how some > P2P Trackers (e.g., BitTorrent Trackers - see "Tracker HTTP/HTTPS > Protocol" in [BitTorrent]) operate. > > However, although section 7.7.5.1.3 (for the Endpoint Cost service) allows the > source address to be inferred from the client's IP address, section 7.7.4.1.3 > (for the Endpoint Property Lookup service) doesn't allow the source address to > be optional or inferred from the client's IP address. > > Is this an oversight in the description of the Endpoint Property Lookup > service or should the example in section 10.3 point to the Endpoint Property > Cost service? > > Thanks > Ben > > _______________________________________________ > alto mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/alto _______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
