[CDNi] [Errata Verified] RFC8007 (5064)

RFC Errata System <rfc-editor@rfc-editor.org> Fri, 22 January 2021 15:13 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: cdni@ietfa.amsl.com
Delivered-To: cdni@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4278A3A0E27; Fri, 22 Jan 2021 07:13:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VIB7r-3hGIP4; Fri, 22 Jan 2021 07:13:23 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8FD23A0DEC; Fri, 22 Jan 2021 07:13:23 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 2AD5EF40745; Fri, 22 Jan 2021 07:13:05 -0800 (PST)
To: kevin.j.ma@ericsson.com, rob.murray@nokia.com, ben.niven-jenkins@nokia.com
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: barryleiba@computer.org, iesg@ietf.org, cdni@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20210122151305.2AD5EF40745@rfc-editor.org>
Date: Fri, 22 Jan 2021 07:13:05 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/cdni/kg4rNXiZsW6iqn9MwtPJ54DVpQ0>
Subject: [CDNi] [Errata Verified] RFC8007 (5064)
X-BeenThere: cdni@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This list is to discuss issues associated with the Interconnection of Content Delivery Networks \(CDNs\)" <cdni.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cdni>, <mailto:cdni-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cdni/>
List-Post: <mailto:cdni@ietf.org>
List-Help: <mailto:cdni-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cdni>, <mailto:cdni-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jan 2021 15:13:25 -0000

The following errata report has been verified for RFC8007,
"Content Delivery Network Interconnection (CDNI) Control Interface / Triggers". 

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid5064

--------------------------------------
Status: Verified
Type: Editorial

Reported by: Kevin J. Ma <kevin.j.ma@ericsson.com>
Date Reported: 2017-07-07
Verified by: Barry Leiba (IESG)

Section: 6.2.5

Original Text
-------------
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:


Corrected Text
--------------
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.

--------------------------------------
RFC8007 (draft-ietf-cdni-control-triggers-15)
--------------------------------------
Title               : Content Delivery Network Interconnection (CDNI) Control Interface / Triggers
Publication Date    : December 2016
Author(s)           : R. Murray, B. Niven-Jenkins
Category            : PROPOSED STANDARD
Source              : Content Delivery Networks Interconnection
Area                : Applications and Real-Time
Stream              : IETF
Verifying Party     : IESG