Re: Revised ID Needed for draft-ietf-opes-iab-04?

Alex Rousskov wrote:

> 	Please review soon and I will publish the polished version to
> be resubmitted for IESG review. 

Looks good to me. At the end of the day, please go ahead ab request 
publication of the updated draft. I'll then notify ted that this draft 
has been modified to address the IESG comments.

>    Another environment where efficient and meaningful notification using
>    OPES tracing is possible are Content Delivery Networks (CDNs).  A CDN
>    node may use multiple content adaptation services to customize
>    generic content supplied by the content producer (a web site). For
>    example, the node may insert advertisements for client-local events
>    or services.  The node itself may not understand specifics of the ad
>    insertion algorithm implemented in OPES callout servers.  However, it
>    may use OPES trace to notify content producer about the number of
>    certain advertisements inserted (i.e., the number of "impressions"
>    delivered to the customer) or even the number of ad "clicks" the
>    customer made (e.g., if the node hosts content linked from the ads).
>    OPES services doing ad insertion may lack details (e.g., a customer
>    ID/address or a web server authentication token) to contact the
>    content producer directly in this case.

Just for clarification - this example implies that an OPES processor 
could use trace information to determine where to send notifications 
to. The destination of such notifications could be either the content 
producer or another (upstream) OPES processor. In the former case, 
there would be an OPES trace entry for the content producer?

Thanks,
   Makrus