CDN Metrics

[Eric Dean <eric@crystalballinc.com>]

I'm not sure if there was conclusion whether we were goin top include
metrics within an advertisement or not and if so, which draft(s) we were
going to include it within.
 
One thing that had me confused is that with IP routing, a reachable 
network is advertised with a particular metric to it's peers.  Peered
networks then may deliver packets across that peering connection destined
for the advertised network.   

However, with CDN peering, I am not advertising content so that requests
can be delivered to me...that already works.  I am requesting permission
to map content requests to a peer's surrogates. In exchange I would like
to receive a metric from a CDN peer that reflects the QoS I can expect if
I decide to map content requests to their surrogates.
    
It would not make sense to advertise specific URI's and request
independent metrics for each.  A CDN/surrogate's performance should not be
URI dependent...though it may be dependent upon certain content
characteristics.

If anything, I would like to know the performance level of each surrogate
and whether they will accept if I map certain requests to it.  Again, I
certainly don't see why I would advertise URI's with metrics nor do I see
why I would want to receive a metric for every URI from every surrogate.
I just want to know:

a) Am I allowed to map URI A to surrogate B
b) If so, what performance metric can I associate with that mapping 

or better yet, send me the metrics of all your surrogates and let me know
what specific content types I'm allowed to map to them.  I'll then send
you the URI's that I'd like to map to your surrogates.

Maybe I'm way wrong in interpreting what has been discussed lately.