metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 8008: Content Delivery Network Interconnection (CDNI) Request Routing: Footprint and Capabilities Semantics

Still current, but amended. Parts of this document are changed or extended by RFC 9388. Read both.

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID
RFC8008
Published
December 2016
Authors
J. Seedorf; J. Peterson; S. Previdi; R. van Brandenburg; K. Ma
Status
PROPOSED STANDARD
Stream
IETF
Area
wit
Pages
31
Also known as
—
Updated by:
RFC 9388

Topics

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/8008-content-delivery-network-interconnection-cdni-request-routing-footprint-and-capa