Subject: [CDNi] FW: New Version Notification for draft-murray-cdni-triggers-02.txt

From: Rob Murray <[email-masked]>
Date: Sun, 24 Feb 2013 11:46:07 +0000

Hi all, we've uploaded a new version of the triggers draft.

Changes in this version are ...

  - we've made it uCDN's responsibility to schedule preposition
    and invalidate/purge requests affecting the same URLs so that
    they do not interact badly, and went back to a single trigger
    operation per request
  - added error reporting
  - allow dCDN implementations not to track and report status of
    triggered activity (they can accept requests as 'best-effort'
    and estimate a completion time without having to confirm
    completion)
  - aligned content references with the metadata draft
  - note that dCDN may ignore 'scheme' (http/https) when
    matching content urls for invalidate/purge

Cheers,
Rob.

On 24/02/2013 11:33, "[email-masked]" <[email-masked]>
wrote:

>
>A new version of I-D, draft-murray-cdni-triggers-02.txt
>has been successfully submitted by Rob Murray and posted to the
>IETF repository.
>
>Filename:	 draft-murray-cdni-triggers
>Revision:	 02
>Title:		 CDN Interconnect Triggers
>Creation date:	 2013-02-24
>Group:		 Individual Submission
>Number of pages: 36
>URL:             
>http://www.ietf.org/internet-drafts/draft-murray-cdni-triggers-02.txt
>Status:          
>http://datatracker.ietf.org/doc/draft-murray-cdni-triggers
>Htmlized:        http://tools.ietf.org/html/draft-murray-cdni-triggers-02
>Diff:            
>http://www.ietf.org/rfcdiff?url2=draft-murray-cdni-triggers-02
>
>Abstract:
>   This document proposes a mechanism for a CDN to trigger activity in
>   an interconnected CDN that is configured to deliver content on its
>   behalf.  The upstream CDN can use this mechanism to request that the
>   downstream CDN pre-positions metadata or content, or that it re-
>   validate or purge metadata or content.  The upstream CDN can monitor
>   the status of activity that it has triggered in the downstream CDN.
>
>
>                  
>        
>
>
>The IETF Secretariat
>