rfc9808v2.txt | rfc9808.txt | |||
---|---|---|---|---|
skipping to change at line 167 ¶ | skipping to change at line 167 ¶ | |||
between the dCDN and uCDN. | between the dCDN and uCDN. | |||
2. CDNI Additional Capability Objects | 2. CDNI Additional Capability Objects | |||
Section 5 of [RFC8008] describes the FCI Capability Advertisement | Section 5 of [RFC8008] describes the FCI Capability Advertisement | |||
Object, which contains a CDNI Capability Object as well as the | Object, which contains a CDNI Capability Object as well as the | |||
capability-type (a CDNI Payload Type). The section also defines the | capability-type (a CDNI Payload Type). The section also defines the | |||
Capability Objects per such type. Below, we define two additional | Capability Objects per such type. Below, we define two additional | |||
Capability Objects. | Capability Objects. | |||
Note: In the following sections, the term "mandatory-to-specify" is | | Note: In the following sections, the term "mandatory-to- | |||
used to convey which properties MUST be included when serializing a | | specify" is used to convey which properties MUST be included | |||
given capability object. When mandatory-to-specify is defined as a | | when serializing a given capability object. When mandatory-to- | |||
"Yes" for an individual property, it means that if the object | | specify is defined as a "Yes" for an individual property, it | |||
containing that property is included in an FCI message, then the | | means that if the object containing that property is included | |||
mandatory-to-specify property MUST be included. | | in an FCI message, then the mandatory-to-specify property MUST | |||
| be included. | ||||
2.1. Telemetry Capability Object | 2.1. Telemetry Capability Object | |||
The Telemetry Capability Object advertises a list of Telemetry | The Telemetry Capability Object advertises a list of Telemetry | |||
Sources made available to the uCDN by the dCDN. In this document, | Sources made available to the uCDN by the dCDN. In this document, | |||
telemetry data is being defined as near real-time aggregated metrics | telemetry data is being defined as near real-time aggregated metrics | |||
of dCDN utilization, such as bits per second egress, and is specific | of dCDN utilization, such as bits per second egress, and is specific | |||
to the uCDN and dCDN traffic delegation relationship. | to the uCDN and dCDN traffic delegation relationship. | |||
Telemetry data is uniquely defined by a source ID, a metric name, and | Telemetry data is uniquely defined by a source ID, a metric name, and | |||
End of changes. 1 change blocks. | ||||
6 lines changed or deleted | 7 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. |