[CDNi] RFC 8007 on Content Delivery Network Interconnection (CDNI) Control Interface / Triggers
rfc-editor@rfc-editor.org Wed, 14 December 2016 02:11 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 770EB129BA1; Tue, 13 Dec 2016 18:11:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.098
X-Spam-Level:
X-Spam-Status: No, score=-107.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.896, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 MN0KwW9lCt4P; Tue, 13 Dec 2016 18:11:44 -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 CEE75129801; Tue, 13 Dec 2016 18:11:40 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id B86E3B817CF; Tue, 13 Dec 2016 18:11:40 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20161214021140.B86E3B817CF@rfc-editor.org>
Date: Tue, 13 Dec 2016 18:11:40 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/cdni/NWTu0lSVlD8axiql2D7Gq-fMkw4>
Cc: drafts-update-ref@iana.org, cdni@ietf.org, rfc-editor@rfc-editor.org
Subject: [CDNi] RFC 8007 on Content Delivery Network Interconnection (CDNI) Control Interface / Triggers
X-BeenThere: cdni@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 14 Dec 2016 02:11:52 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8007
Title: Content Delivery Network Interconnection (CDNI)
Control Interface / Triggers
Author: R. Murray,
B. Niven-Jenkins
Status: Standards Track
Stream: IETF
Date: December 2016
Mailbox: rob.murray@nokia.com,
ben.niven-jenkins@nokia.com
Pages: 49
Characters: 90108
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-cdni-control-triggers-15.txt
URL: https://www.rfc-editor.org/info/rfc8007
DOI: 10.17487/RFC8007
This document describes the part of the Content Delivery Network
Interconnection (CDNI) Control interface that allows a CDN to trigger
activity in an interconnected CDN that is configured to deliver
content on its behalf. The upstream CDN can use this mechanism to
request that the downstream CDN pre-position metadata or content or
to request that it invalidate or purge metadata or content. The
upstream CDN can monitor the status of activity that it has triggered
in the downstream CDN.
This document is a product of the Content Delivery Networks Interconnection Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC