Re: [p2pi] Refining the ALTO problem statement [Was: Re: discussing P2PI-related standardization in Dublin]

>>
>>  the RSVP TSpec. Alternatively, a protocol such as GIST could
>> discover
>>  the cost of particular destination.  The service classes may change
>>  over time. For example, a network may offer "midnight specials" when
>>  the network is idle during off-hours, encouraging bulk downloads
>>  during that time.
>
> thanks - that does make it clearer. I agree that it's interesting to
> think through the possibilities here, but I don't see anything we
> could immediately think about standardizing here.
>

I do see a need for standardization here, namely conveying the current  
bandwidth price or total usage. (More complicated models are feasible,  
but I think something pretty simple would do the job and avoid getting  
into business models.)

You'd want to get something like

"Your current charge for priority X is Y currency units/byte, valid  
until time T."

"You have used B bytes out of L bytes for priority X."

"Your max. rate for priority X is S bits/second."

This covers the major knobs that a provider can turn (quotas, rate  
limits and metering).

> That is definitely possible. For example, low-RTT peers may be behind
> other DSL boxes within your ISP, whereas the university with the big
> pipe is a bit further away in RTT terms than those peers - who'd you
> like to transfer from? I'd expect the correlation between RTT and
> transmission time to be pretty weak (but have no data to back this  
> up.)

Given that TCP throughput is inversely proportional to RTT, one would  
indeed expect a correlation. See

http://www.slac.stanford.edu/comp/net/wan-mon/thru-vs-loss.html

for a random related page. Obviously, capacity matters where a single  
flow is likely to occupy the whole pipe.

Henning
>
>
> Lars
> _______________________________________________
> p2pi mailing list
> p2pi@ietf.org
> https://www.ietf.org/mailman/listinfo/p2pi

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