RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 4 records.

Status: Verified (4)

RFC 8007, "Content Delivery Network Interconnection (CDNI) Control Interface / Triggers", December 2016

Source of RFC: cdni (art)

Errata ID: 5053
Status: Verified
Type: Technical
Publication Format(s) : TEXT

Reported By: Kevin J. Ma
Date Reported: 2017-06-27
Verifier Name: Barry Leiba
Date Verified: 2021-01-22

Section 5.2.3 says:

| canceling |
| canceled  |

It should say:

| cancelling |
| cancelled  |

Notes:

In the final editing phase, I believe it was agreed that text would use the American spelling with 1 "l", but that the actual status strings would use 2 "l"s. In sections 2.3, 4.3, 4.5, and Appendix A, the quoted status strings all use 2 "l"s. The first column of the table in section 5.2.3 is providing the JSON string values, which should match the quoted status strings in sections 2.3, 4.3, 4.5, and Appendix A and have 2 "l"s.

Errata ID: 5054
Status: Verified
Type: Technical
Publication Format(s) : TEXT

Reported By: Kevin J. Ma
Date Reported: 2017-06-27
Verifier Name: Barry Leiba
Date Verified: 2021-01-22

Section 5.2.7 says:

| ecanceled    |

It should say:

| ecancelled   |


Notes:

In the final editing phase, I believe it was agreed that text would use the American spelling with 1 "l", but that the status strings would use 2 "l"s. This should apply to the error codes as well. The first column of the table in section 5.2.7 is providing the Error Code values, which like the status code strings in sections 2.3, 4.3, 4.5, 5.2.3, and Appendix A, should have 2 "l"s. Note: The IANA registry has the error code as "ecancelled" with 2 "l"s. http://www.iana.org/assignments/cdni-parameters/cdni-parameters.xhtml#error-codes

Note: This errata also applies to Appendix A.

Errata ID: 6385
Status: Verified
Type: Technical
Publication Format(s) : TEXT

Reported By: Guillaume Bichot
Date Reported: 2021-01-12
Verifier Name: Barry Leiba
Date Verified: 2021-01-22

Section 4.1 says:

   When a CI/T Trigger Command is accepted, the uCDN MUST create a new
   Trigger Status Resource that will convey a specification of the CI/T
   Command and its current status.  The HTTP response to the dCDN MUST
   have status code 201 and MUST convey the URI of the Trigger Status
   Resource in the Location header field [RFC7231].

It should say:

   When a CI/T Trigger Command is accepted, the dCDN MUST create a new
   Trigger Status Resource that will convey a specification of the CI/T
   Command and its current status.  The HTTP response to the uCDN MUST
   have status code 201 and MUST convey the URI of the Trigger Status
   Resource in the Location header field [RFC7231].

Notes:

There has been an accidental switch between "uCDN" and "dCDN" terms in this statement. If my understanding is correct, when the uCDN post a CI/T command to the dCDN, the latter must create a trigger status resource and returns in the response (HTTP code 201) “Location” header the URI of that status resource.

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.

Report New Errata