Verifying, identifying and ack-ing requests ....

[Abhi Deshmukh <Abhi.Deshmukh@apogeenet.com>]

I have a set of questions on Identification, Verification and
Acknowledgement of requests, that would help me understand the current or
proposed working of peered CDNs. Here goes.

Assume that CDN-A and CDN-B peer with each other. 
Assume that CDN-A forwards an end-user request R to CDN-B.

0. How does CDN-A know that CDN-B has succesfully (or un-successfully) 
received the request R ?

1. How does CDN-A know that CDN-B has succesfully (or un-successfully) 
serviced the request R ?

2. Does CDN-B send a real-time or batched response back to CDN-A after the
request R is serviced ?

3. How does CDN-A verify the work (including QoS, SLA, etc) done by CDN-B
while trying to service request R ?  
	3.a  Do CDN-A and CDN-B share common/neutral monitoring apps at each
service points ?

4. Is each request between CDN-A and CDN-B identified uniquely ? Is it as
simple as a combination of timestamp and a rolling counter ?

Thanks
----------------------------
Abhi Deshmukh
mailto:abhi@apogeenet.com
+1-(201)-3688800 x266