Hi Sebastian, On Wed, Jul 24, 2013 at 3:16 PM, Sebastian Kiesel <[email protected]>wrote:
> Hi Richard, > > On Wed, Jul 24, 2013 at 03:00:57PM -0400, Y. Richard Yang wrote: > > On Wed, Jul 24, 2013 at 2:48 PM, Sebastian Kiesel <[email protected] > >wrote: > > > > > Speaking of dynamically generated IRDs: how would the ALTO server > > > identify the client in order to generate an IRD specifically for it? > > > > > > This could be done based on the source IP address of the HTTP > > > connection, or based on an X-Forwarded-For header in HTTP. > > > > > > For requests originated from end users, the preceding can serve > > as the customization parameter. > > > > > > > But how > > > would we do that in the third-party use case, e.g., if a P2P tracker > > > issues ALTO queries on behalf of (topologically distant) resource > > > consumers? Is there a way to explicitly tell the resource consumer's > > > ID/IPaddress when requesting an IRD? > > > > > > > Third party is a more challenging case. It is interesting that you appear > > to suggest that the requestor of the IRD can indicate the end user that > > the request is for, > > "yes" up to here ... > > > say in X-Forwarded-For. > > ... this seems too much of a hack to me. > In addition to a reaction of it being a hack, some other reactions that I can "hear" include that this creates cross-layer issues (against); we should use existing mechanisms whenever possible (for). maybe GET http://altoserver.example/ird&rc=192.0.2.55 > (RC=ressource consumer) or what would be a RESTful solution approach? > > > > This will require that the ALTO > > Server check the field, and the (third-party) requestor set the field. > > Interesting > > idea. I am not sure if we want to take on this in the base protocol. But > it > > is quite interesting, and I never thought about this possibility. > > if we cannot find a very simple solution that still can be added to the > base protocol without the risk of side effects, I could imagine a future > extension that uses POST to request the IRD and give more information > about the client and its expectations wrt. the ALTO guidance. > > The idea of introducing parameters in the request for IRD (i.e., filtered IRD) is an interesting one. I will think more about it. Thanks! Richard > > thanks > Sebastian >
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
