Document Shepherd: Sanjay Mishra
Responsible AD: Francesca Palombini
This document defines a framework for information exchange to facilitate
traffic delegation decisions between an upstream CDN (uCDN) and a downstream
CDN (dCDN) specifically about acceptable levels of traffic to delegate. The
framework establishes limits that are specific to delegation relationship and
defines limits in unambiguous and mutually understood units. To achieve this
goal, the document defines two new payload types:
1. FCI.CapacityLimits to specify the limit of traffic that should be delegated
in units, such as Bits per Second called limit-types (also references a
specific Telemetry source which outlines current usage of a particular
limit-type
2. FCI.Telemetry that allows the advertisement of what types of Telemetry
sources are supported. This is Initially scoped to generic Telemetry sources,
but paves the way for a formal Telemetry interface integration
The above two payload types are defined as per Section 5 of [RFC8008] that
describes the FCI Capability Advertisement Object, which contains a CDNI
Capability Object as well as the capability object type (a CDNI Payload Type).
This document was first submitted in July 2021 and since then has been
extensively discussed and reviewed within the CDNI working group and there was
no disagreement about its usage and the proposed changes. This document allows
a downstream CDN to expose its capacity limit and potentially the current usage
and avoid being overloaded by the upstream CDN.
The draft has gone through many rounds of review and I feel confident that the
document and is ready for the AD. The draft creates two new IANA payload
registries as mentioned earlier.
The draft is being submitted as a proposed standard. The draft is clear of any
nits.
There is also currently one CDN provider that has implemented and other has
indicated plans to implement.
The authors have confirmed that there is no undisclosed IPR to their knowledge.
The normative references are all freely available and normative.
There are no downrefs or unpublished RFC references.
Publication of this draft does not change the status of any other RFCs.