Re: [p2pi] Charter and problem statement

[stefano previdi <sprevidi at cisco.com>]

> From: Stanislav Shalunov <shalunov at shlang.com>
> 
> 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.

ok, I agree that "opaque" may be an overstatement...

But I understand that the ALTO protocol shouldn't have a specific state
machinery or behavior because it conveys cache based information.

> 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.

ok.

s.

> 
> 
> 
> -----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