[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Distribution CPG Protocol
> ----- Original Message -----
> From: "Alex French" <afrench@vianetworks.com>
>
> > I don't know if CDN operators would want to advertise their total
> available
> > space. In any case, this is likely to be governed by offline policy
> > decisions, e.g. a contractual agreement that I will provide you with
> 3G
> per
> > site for 10 sites. The protocol would need to know what the sites were
> > before it could advertise the space available to them, which is
> similar to
> > what I suggested.
> >
>
> I think asking for a specific space during the request stage should
> solve
> this problem
We should start to define the information we want to exchange at each
time. What are the initial capabilities, what will be exchanged during
the request stage (content advertisment)?
I agree with Paul that the space request should be done during
the request stage. Initial capabilities for me are more like
- served footprint (a list of served networks might be not sufficient)
- supported content types
optional, or to be discussed:
- offered service levels (first-class, business, economy service?)
- aggregate load metric
- some kind of generic metric (not yet defined)
- surrogate connectivity (a cache server connected with OC-3 is different
from a DSL connected server,...)
- ...
During the request stage we must exchange the information about
the content that will be distributed
- disk space required
- bandwidth requirements (e.g., for streaming...)
- maximum cost (I don't like to talk about that either but somewhere
we have to take case about that)
- ...
We should start pinning that down for the requirement drafts!
Martin
>
>
> abbie
>
> I agree, the CP should be burdened with understanding the resource
> requirements of their content, as well as the way in which the content is
> served to their clients. (As Kobus van der Merwe mentioned earlier.)
>
> Paul Scanlon