CDNI

Summary

The CDNI Working Group held an interim meeting to discuss the status and progression of several active drafts. Key topics included the resolution of normative reference issues in the client access control metadata draft, a strategy for reviewing the voluminous logging extensions draft, and a detailed technical review of pending changes for the rfc8007bis (Control Interface/Triggers) document. The group also reviewed and aligned on milestones for the remainder of 2024 and beyond.

Key Discussion Points

1. Metadata Access Control

Alfonso Silóniz provided an update on draft-ietf-cdni-client-access-control-metadata.

Living Standards Issue: A primary concern from the IESG/Last Call process involves the normative reference to the "Fetch" specification (a WHATWG living standard).
Resolution: Following IETF precedents, the group discussed referencing a specific GitHub commit/snapshot of the Fetch standard to satisfy normative reference requirements while providing a link to the living version.
Next Steps: Alfonso Silóniz plans to reconcile various reviewer comments and publish a new version in approximately 1–2 weeks to unlock the Last Call process.

2. CDNI Logging Extensions

The group discussed how to approach the review of draft-ietf-cdni-logging-extensions, which is a large document.

Review Strategy: Ben Rosenblum and Alan Arolovitch agreed that line-by-line reviews during meetings are unproductive.
Process: The group decided to use upcoming interim meetings as hard deadlines for assigned reviewers to post comments to the mailing list. This "milestone-driven" approach is intended to ensure the document progresses toward its October 2026 target.

3. Control Interface and Triggers (rfc8007bis)

Alan Arolovitch detailed the changes pending for version 20 of draft-ietf-cdni-ci-triggers-rfc8007bis:

Error Handling: There is a need to align "legacy" asynchronous error codes (JSON-based) with modern RESTful HTTP error semantics. The document needs to provide clear guidance on when to return an immediate HTTP 400 vs. a 200 OK with an error object in the payload.
Labels (Section 4.4.2): Kevin Ma raised concerns regarding "opaque strings with semantic encoding" (key=value pairs). Alan Arolovitch explained that these are modeled after Kubernetes labels to facilitate monitoring and selection/filtering without requiring the dCDN to understand the underlying semantics unless specified by an extension.
Object List Flattening: A discussion occurred regarding the recommendation to flatten object lists in trigger responses to aid troubleshooting and debugging.

4. Working Group Milestones

Sanjay Mishra reviewed the current timeline for the following documents:

draft-ietf-cdni-ci-triggers-rfc8007bis: Target May 2024.
draft-ietf-cdni-delivery-metadata: Target July 2024. Sanjay Mishra to review.
draft-ietf-cdni-protected-secrets-metadata: Target July 2024 (Working Group Last Call goal). Requires SecDir review.
draft-ietf-cdni-metadata-expression-language: Target September 2026.
draft-ietf-cdni-logging-extensions: Target October 2026.
draft-ietf-cdni-processing-stages-metadata: Target December 2026.

Decisions and Action Items

Decision: The group will not move to a fortnightly meeting schedule. Instead, interims will be scheduled as needed (approximately every 4-6 weeks) to serve as deadlines for document reviews.
Action Item: Alfonso Silóniz to update draft-ietf-cdni-client-access-control-metadata with the Fetch snapshot reference and reconcile IESG/IANA comments.
Action Item: Alan Arolovitch to publish version 20 of draft-ietf-cdni-ci-triggers-rfc8007bis addressing error code alignment and label clarifications.
Action Item: Sanjay Mishra to review draft-ietf-cdni-delivery-metadata.
Action Item: Ben Rosenblum to prepare draft-ietf-cdni-protected-secrets-metadata for potential SecDir review and Working Group Last Call prior to the July cutoff (July 6).

Next Steps

Discussion on draft-ietf-cdni-metadata-expression-language was tabled until Glenn Goldstein is available.
The working group will continue technical discussions on the mailing list.
The next formal session is scheduled for IETF 126 in July 2024. No interim meetings are planned between now and the July meeting.

Automatic IETF Minutes