[CDNi] [Errata Verified] RFC8007 (6385)
RFC Errata System <rfc-editor@rfc-editor.org> Fri, 22 January 2021 15:14 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 7E7393A0E6D; Fri, 22 Jan 2021 07:14:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.922
X-Spam-Level:
X-Spam-Status: No, score=-0.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.998, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 wXujmw95d3rX; Fri, 22 Jan 2021 07:14:45 -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 5C0813A0E29; Fri, 22 Jan 2021 07:14:45 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 87592F40745; Fri, 22 Jan 2021 07:14:26 -0800 (PST)
To: guillaume.bichot@broadpeak.tv, 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: <20210122151426.87592F40745@rfc-editor.org>
Date: Fri, 22 Jan 2021 07:14:26 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/cdni/hW9tBVbLDeEEc4HY-3tVGh0gmrE>
Subject: [CDNi] [Errata Verified] RFC8007 (6385)
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:14:47 -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/eid6385 -------------------------------------- Status: Verified Type: Technical Reported by: Guillaume Bichot <guillaume.bichot@broadpeak.tv> Date Reported: 2021-01-12 Verified by: Barry Leiba (IESG) Section: 4.1 Original Text ------------- 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]. Corrected Text -------------- 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. -------------------------------------- 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
- [CDNi] [Errata Verified] RFC8007 (6385) RFC Errata System