Re: [p2pi] Charter and problem statement

[stefano previdi <sprevidi at cisco.com>]

> From: Reinaldo Penno <rpenno at juniper.net>
> 
> I agree. 
> 
> We seem to be stuck in caching as if it is something special but it seems to
> me this is a general problem with any piece of network/topology information
> an ALTO server wants to convey.

yes.

> The entities involved in this protocol (P2P clients, ALTO servers, etc) need
> to to be able to encode/decode and understand in a uniform fashion the
> notions of weight, distance, peer, etc. The notion of passing caching
> information is just one aspect of it.

I agree.

s.

> 
> Thanks,
> 
> Reinaldo
> 
> 
> On 7/16/08 1:08 AM, "songhaibin 64081" <melodysong at huawei.com> wrote:
> 
>> 
>> ----- Original Message -----
>> From: Stanislav Shalunov <shalunov at shlang.com>
>> Date: Wednesday, July 16, 2008 3:48 pm
>> Subject: Re: [p2pi] Charter and problem statement
>> 
>>> On Jul 16, 2008, at 12:33 AM, Song Haibin wrote:
>>>> If so, the ALTO
>>>> client must identify the "kind" of cache it wants to get from
>>> the ALTO
>>>> server's selection. I don't know if it violates the rule of
>>>> application
>>>> agnostic here.
>>> 
>>> 
>>> ALTO doesn't need to know anything about BitTorrent to make it
>>> possible to discover caches for a string "BitTorrent".  You could
>>> also  
>>> ask for "HTTP" or "gopher", and again, ALTO would not need to know
>>> how  
>>> these work.
>>> 
>>> To interoperate on the ALTO level, it is only necessary to
>>> standardize  
>>> these handles. 
>> 
>> 
>> Yes, that is the point.
>> 
>> BR
>> Song Haibin
>> 
>> 
>> 
>> _______________________________________________
>> p2pi mailing list
>> p2pi at ietf.org
>> https://www.ietf.org/mailman/listinfo/p2pi
> 
> _______________________________________________
> p2pi mailing list
> p2pi at ietf.org
> https://www.ietf.org/mailman/listinfo/p2pi


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