Re: [p2pi] Charter and problem statement

[Laird Popkin <laird at pando.com>]

We should minimize the amount of caching metadata and logic are exposed in ALTO. As long as ALTO can introduce the p2p cache server to the p2p clients, and tell them that they are caches rather than normal peers, the rest (specific content assignment to specific caches, preferential use of caches over normal peers, etc.) can be negotiated between the p2p clients and the caches using the p2p protocols, without ALTO's involvement.

- Laird Popkin, CTO, Pando Networks
  mobile: 646/465-0570

----- Original Message -----
From: "stefano previdi" <sprevidi at cisco.com>
To: "Laird Popkin" <laird at pando.com>, "Stanislav Shalunov" <shalunov at shlang.com>
Cc: p2pi at ietf.org, "Enrico Marocco" <enrico.marocco at telecomitalia.it>
Sent: Wednesday, July 16, 2008 10:08:26 AM (GMT-0500) America/New_York
Subject: Re: [p2pi] Charter and problem statement

> From: Laird Popkin <laird at pando.com>
> 
> Stefano,
> 
>    Yes, I am suggesting that ALTO should make cache entities explicit to ALTO
> clients. And the means of doing so should be standardized so that there is
> interoperability. It could be expressed in the ALTO specification itself, or
> via the extension mechanism, of course.

now we'll have to explore what kind of cache-specific bits we want to
standardize in the ALTO protocol... I have the feeling is going to be quite
vast...

My point was to keep the ALTO protocol agnostic enough in order to provide a
generic protocol between ALTO providers/consumers. Having some bits in the
request/response related to a cache entity/object, it's fine but I'm not
sure how far we can go without significantly impacting the protocol engine.

s.
 
> 
> - Laird Popkin, CTO, Pando Networks
>   mobile: 646/465-0570
> 
> ----- Original Message -----
> From: "Stanislav Shalunov" <shalunov at shlang.com>
> To: "stefano previdi" <sprevidi at cisco.com>, "Laird Popkin" <laird at pando.com>,
> "Enrico Marocco" <enrico.marocco at telecomitalia.it>
> Cc: p2pi at ietf.org
> Sent: Tuesday, July 15, 2008 7:36:34 PM (GMT-0500) America/New_York
> Subject: RE: [p2pi] Charter and problem statement
> 
> The information conveyed to the client needs to enable the client to find a
> nearby cache (or three).  Whether this information blob can be called opaque
> then is a semantic question, but to me, calling it opaque is misleading.
> 
> Anything opaque is transparent to something higher up the stack. For example,
> should we use DNS to find the cache, the information is opaque on DNS layer.
> It is no longer opaque when it is used.
> 
> If it is to allow any client to find the cache, it's not opaque to ALTO.
> 
> 
> 
> -----Original Message-----
> From: "stefano previdi" <sprevidi at cisco.com>
> To: "Laird Popkin" <laird at pando.com>; "Enrico Marocco"
> <enrico.marocco at telecomitalia.it>
> Cc: p2pi at ietf.org
> Sent: 7/15/08 6:41 AM
> Subject: Re: [p2pi] Charter and problem statement
> 
> Laird,
> 
> do you suggest to make the cache entity explicit in the ALTO protocol
> semantic ? 
> 
> Or is it just part of the opaque protocol data the algorithm (not under
> standardization at this point) will work with ?
> 
> I'd vote for the latter...
> 



_______________________________________________
p2pi mailing list
p2pi at ietf.org
https://www.ietf.org/mailman/listinfo/p2pi