CDNi Administration

CDNi specifications define the standards for interoperability within the CDN and open caching ecosystems set forth by the IETF. This integration utilizes the APIs defined by the SVA.

See also

For complete details on CDNi and the related API specifications see RFC 8006, RFC 8007, RFC 8008, and the SVA documents titled Footprint and Capabilities Interface: Open Caching API, Open Caching API Implementation Guidelines, Configuration Interface: Part 1 Specification - Overview & Architecture, Configuration Interface: Part 2 Specification – CDNi Metadata Model Extensions, and Configuration Interface: Part 3 Specification – Publishing Layer APIs.

In short, these documents describe the CDNi metadata interface that enables interconnected CDNs to exchange content distribution metadata to enable content acquisition and delivery. These define the interfaces through which a uCDN and a dCDN can communicate configuration and capacity information.

For our use case, it is assumed that ATC is the dCDN.

Note

This is currently under construction and will be for a while. This document will be updated as new features are supported.

/OC/FCI/advertisement

The advertisement response is unique for the uCDN and contains the complete footprint and capabilities information structure the dCDN wants to expose. This endpoint will return an array of generic FCI base objects, including type, value, and footprint for each. Currently supported base object types are FCI.Capacitiy and FCI.Telemetry but these will be expanded in the future.

/OC/CI/configuration

An endpoint that is used to push (PUT), fetch (GET), or delete (DELETE) the entire metadata set for a given uCDN from a JWT. This puts the requested change into a queue to be reviewed later and returns an endpoint to view the asynchronous status updates.

Note

This is under construction. Currently only PUT is supported and in a very limited sense.

/OC/CI/configuration/{{host}}

An endpoint that is used to push (PUT), fetch (GET), or delete (DELETE) the metadata set that is attached to host name for a given uCDN from a JWT. This puts the requested change into a queue to be reviewed later and returns an endpoint to view the asynchronous status updates.

Note

This is under construction. Currently only PUT is supported and in a very limited sense.

/OC/CI/configuration/request/{{id}}/{{approved}}

This endpoint allows a user to approve or deny a queued update request from the previous endpoints. A denial will result in the removal from the queue and a FAILED status update. An approval will result in the changes being made to the configuration and a SUCCEEDED status update.

Note

This is under construction and only supports very limited metadata field and limited configuration updates.