1 / 3

CDNI Triggers draft-murray-cdni-triggers- 01

CDNI Triggers draft-murray-cdni-triggers- 01. Rob Murray Ben Niven -Jenkins IETF 85 Atlanta – Nov 2012. Changes between ’ 00’ & ’ 01 ’. Addressed comments from the list, including… Multiple triggers in a request For requests to invalidate/purge then prepopulate

hadar
Télécharger la présentation

CDNI Triggers draft-murray-cdni-triggers- 01

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CDNI Triggersdraft-murray-cdni-triggers-01 Rob Murray Ben Niven-Jenkins IETF 85 Atlanta – Nov 2012

  2. Changes between ’00’ & ’01’ Addressed comments from the list, including… • Multiple triggers in a request • For requests to invalidate/purge then prepopulate • Timing of requests is under dCDN control, but it must not invalidate/purge data prepopulated as part of the same request • Trigger results • Report failure if any part of the operation failed • Only report results when dCDNs in a cascade have reported

  3. Next steps • Define references to Metadata • Its URL, as supplied to dCDN by uCDN • Patterns allowed for invalidate/purge, use mechanism from metadata interface • Define error reporting • Come up with a set of failure reasons, and a way to tie those to each action in the request • Align encoding with metadata interface • Aim for adoption before IETF 86

More Related