[CDNi] RFC 8008 on Content Delivery Network Interconnection (CDNI) Request Routing: Footprint and Capabilities Semantics
rfc-editor@rfc-editor.org Wed, 14 December 2016 02:12 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 600491297EE; Tue, 13 Dec 2016 18:12:10 -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 Qha7YX1Hr6vu; Tue, 13 Dec 2016 18:12:08 -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 52525129801; Tue, 13 Dec 2016 18:11:55 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 4693DB817D8; Tue, 13 Dec 2016 18:11:55 -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: <20161214021155.4693DB817D8@rfc-editor.org>
Date: Tue, 13 Dec 2016 18:11:55 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/cdni/l3tI4SQ9TuqJiefQ2P4iFRnbzLg>
Cc: drafts-update-ref@iana.org, cdni@ietf.org, rfc-editor@rfc-editor.org
Subject: [CDNi] RFC 8008 on Content Delivery Network Interconnection (CDNI) Request Routing: Footprint and Capabilities Semantics
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:12:10 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8008
Title: Content Delivery Network Interconnection (CDNI)
Request Routing: Footprint and Capabilities Semantics
Author: J. Seedorf,
J. Peterson,
S. Previdi,
R. van Brandenburg,
K. Ma
Status: Standards Track
Stream: IETF
Date: December 2016
Mailbox: jan.seedorf@hft-stuttgart.de,
jon.peterson@neustar.biz,
sprevidi@cisco.com,
ray.vanbrandenburg@tno.nl,
kevin.j.ma@ericsson.com
Pages: 31
Characters: 61956
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-cdni-footprint-capabilities-semantics-20.txt
URL: https://www.rfc-editor.org/info/rfc8008
DOI: 10.17487/RFC8008
This document captures the semantics of the "Footprint and
Capabilities Advertisement" part of the Content Delivery Network
Interconnection (CDNI) Request Routing interface, i.e., the desired
meaning of "Footprint" and "Capabilities" in the CDNI context and
what the "Footprint & Capabilities Advertisement interface (FCI)"
offers within CDNI. The document also provides guidelines for the
CDNI FCI protocol. It further defines a Base Advertisement Object,
the necessary registries for capabilities and footprints, and
guidelines on how these registries can be extended in the future.
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