RFC Errata
RFC 8007, "Content Delivery Network Interconnection (CDNI) Control Interface / Triggers", December 2016
Source of RFC: cdni (wit)See Also: RFC 8007 w/ inline errata
Errata ID: 5064
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Kevin J. Ma
Date Reported: 2017-07-07
Verifier Name: Barry Leiba
Date Verified: 2021-01-22
Section 6.2.5 says:
6.2.5. Deleting Trigger Status Resources The uCDN can delete completed and failed Trigger Status Resources to reduce the size of the collections, as described in Section 4.4. For example, to delete the "preposition" request from earlier examples:
It should say:
6.2.5. Canceling or Deleting Trigger Status Resources The uCDN can cancel pending or active Trigger Status Resource processing, as described in Section 4.3. For example, to cancel the "preposition" request from earlier examples: REQUEST: POST /triggers HTTP/1.1 User-Agent: example-user-agent/0.1 Host: dcdn.example.com Accept: */* Content-Type: application/cdni; ptype=ci-trigger-command Content-Length: 91 { "cancel" : [ "https://dcdn.example.com/triggers/0" ], "cdn-path" : [ "AS64496:1" ] } RESPONSE: HTTP/1.1 200 OK Content-Length: 0 Server: example-server/0.1 Date: Wed, 04 May 2016 08:50:00 GMT The uCDN can also delete completed and/or failed Trigger Status Resources to reduce the size of the collections, as described in Section 4.4. For example, to delete the "preposition" request from earlier examples:
Notes:
There is no example for canceling a trigger. Section 4.3 does not specify what the response payload should be for cancel responses. An explicit example would help clarify the intent of an empty response. A cancel example probably warrants its own section, but for the purposes of simplifying this errata, it has been combined with the delete example.