CDNI Private Features Metadata

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶

This Internet-Draft will expire on 5 September 2024.¶

Copyright Notice

Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved.¶

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶

Table of Contents

1. Introduction

There is a natural tension between standardization and differentiation - all CDNs and Open Caching systems are not identical, and not all content providers use the same methodologies for controlling access to their resources.¶

While [RFC8006] provides the GenericMetadata object as the basis for extensibility, creating a formal structure for private features as a distinct MI object conveys the explicit understanding of the usage context. This document details a private features mechanism that allows for custom configuration metadata to be easily added, enabling rapid development of new features, and allowing companies to mutually agree on a feature that may not be of general interest to the industry.¶

Through the CDNI Footprint & Capabilities Interface [RFC8008], dCDNs advertise their capabilities to uCDNs. This capabilities advertisement allows a dCDN to declare the private features that it supports.¶

Examples of private features include:¶

• Custom authentication schemes¶

• Definitions of custom scripts to be invoked on the CDN during request processing¶

2. Requirements

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].¶

3. MI.PrivateFeatureList

The dCDN MAY gather a certain number of private features (i.e., not [yet] adopted in a standard or considered marginal) that it MAY want to expose to the content provider and/or the uCDN. Although private, the announcement, selection, and configuration of this private feature can be done through the CDNI interfaces.¶

MI.PrivateFeatureList is a GenericMetadata configuration object used as a base generic object that permits the control of private features.¶

Property: features¶

• Description: The list of feature configuration objects.¶

• Type: Array of MI.PrivateFeature objects¶

• Mandatory-to-Specify: Yes¶

{
  "generic-metadata-type": "MI.PrivateFeatureList",
  "generic-metadata-value": {
    "features": [
      {
        "feature-oid": "Broadpeak",
        "feature-type": "S4Streaming",
        "feature-value": {
          "footprint": {
            "footprint-type": "ipv4cidr",
            "footprint-value": [
              "192.0.2.0/24",
              "198.51.100.0/24"
            ]
          },
          "activation": "ON",
          "mode": "transparent",
          "policy": "bandwidth-max"
        }
      }
    ]
  }
}

4. Named Private Features

Named private features provides an alternative for specifying private features inside the MI.PrivateFeatureList object, allowing them to be specified individually rather than as part of a group under the host match and path match inheritance/override hierarchy.A named private feature corresponding to a feature inside an MI.PrivateFeatureList object in the same generic metadata array, takes precedence and overrides the latter.¶

{
  "generic-metadata-type": "MI.PrivateFeatureList",
  "generic-metadata-value": {
    "features": [
      {
        "feature-oid": "ACME",
        "feature-type": "Hammer",
        "feature-value": {
          "enable": true
        }
      }
    ]
  }
}

{
  "generic-metadata-type": "MI.PrivateFeature.ACME.Hammer",
  "generic-metadata-value": {
    "enable": true
  }
}

5. FCI.PrivateFeatures

While the MI objects introduced in this document allow a uCDN to configure private features with any required configuration metadata, FCI.PrivateFeatures enables a dCDN to advertise the set of private features that it supports.¶

Property: features¶

• Description: The list of supported private features.¶

• Type: Array of nested objects of FCI.PrivateFeature¶

Example:¶

{
  "capabilities": [
    {
      "capability-type": "FCI.PrivateFeatures",
      "capability-value": {
        "features": [
          {
            "feature-oid": "Broadpeak",
            "feature-type": "S4Streaming"
                 }
        ]
      }
    }
  ]
}

6. Security Considerations

The FCI and MI objects defined in the present document are transferred via the interfaces defined in CDNI [RFC8006] which describes how to secure these interfaces protecting integrity and confidentiality while ensuring the authenticity of the dCDN and uCDN.¶

7. IANA Considerations

8. Acknowledgements

The authors would like to express their gratitude to the members of the Streaming Video Technology Alliance [SVTA] Open Caching Working Group for their guidance / contribution / reviews ...)¶

Particulary the following people contribute in one or other way to the content of this draft:¶

• Guillaume Bichot - Broadpeak¶
• Chris Lemmons - Comcast¶
• Pankaj Chaudhari - Disney Streaming Services¶
• Will Power - Lumen¶
• Rajeev RK - picoNETS¶
• Shmuel Asafi - Qwilt¶
• Yoav Gressel - Qwilt¶
• Nir Sopher - Qwilt¶
• Eric Klein - Sirius XM¶
• Alfonso Siloniz - Telefonica¶
• Ben Rosenblum - Vecima¶

Authors' Addresses