[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Advertisement Protocol -- more thoughts
- To: cdn@ops.ietf.org
- Subject: Re: Advertisement Protocol -- more thoughts
- From: Stephen Thomas <stephen.thomas@transnexus.com>
- Date: Tue, 09 Jan 2001 14:08:36 -0500
- Delivery-date: Tue, 09 Jan 2001 11:21:08 -0800
- Envelope-to: cdn-data@psg.com
At 10:44 AM 2001-01-09 -0500, brad cain wrote:
> > >URL Exchange Protocol (proxy case)
> > >----------------------------------
> > >This protocol exchanges a list of urls and a set of metrics with
> > >each set. This protocol is used to communicate metrics to proxies or
> > >transparent proxies. An example would be a CDN advertising
> > >
> > >"Content AS": 2
> > >url: http://www.blah.com/images
> > >nexthop: surrogate 1
> > >metric: 10
> >
> > Can Brad (or anyone else) help me understand what nexthop and metric are in
> > this case?
>
>The next hop would be a useful for either layer-7 switches or
>proxies... it would work very much like a BGP next hop which would
>specify the specific surrogate that had the content (in cases
>where the advertisement wasn't coming directly from the
>surrogate itself).
Sorry to be so confused, but I'm still a little lost. I thought we were
talking about a content provider advertising its content to a CDN. So, the
content provider doesn't own surrogates, right?
>The metric is a "generic metric" which is negotiated between
>cdns... I personally don't believe we can come to agreement
>on a set of metrics (e.g. delay, etc) at this point both
>because it is extremely hard (just look at layer-3 qos)
>and because nobody would ever agree anyway...
Same question here, I guess. What does the metric purport to measure?
____________________________________________________________________
Stephen Thomas +1 770 671 1888
TransNexus, Chief Technical Officer stephen.thomas@transnexus.com