]> Cloudflare

ietf@englishm.net

Web and Internet Transport Media Over QUIC moq cdn provisioning relay This document describes concepts related to provisioning MoQ relay scopes on CDN infrastructure, including scope creation, credential-to-scope mapping, and origin fallback configuration. It uses a provisioning API as a vehicle for describing these concepts and identifying areas where common semantics across CDN providers may be needed for multi-CDN compatibility. About This Document The latest revision of this draft can be found at . Status information for this document may be found at . Discussion of this document takes place on the Media Over QUIC Working Group mailing list (), which is archived at . Subscribe at . Source for this draft and an issue tracker can be found at .

Introduction Media over QUIC Transport (MoQT) defines a pub/sub protocol for media delivery through relays. CDN providers that deploy MoQ relays need to configure them in ways that are roughly analogous to the rewrite rules, origin selection, and routing configuration associated with HTTP reverse proxies and CDNs. Some of these configurations will need common semantics across providers to support multi-CDN deployments. This document uses a provisioning API as a vehicle for describing these concepts. A customer creates a scope on a CDN relay, gets back connection credentials, and hands those credentials to their publishers and subscribers. The relay uses the credentials to map incoming connections to the right scope. The API itself is part of the picture, but the more important contribution here is describing the underlying concepts (scopes, credential-to-scope mapping, origin fallback) in a way that could be consistent across CDN providers. A machine-readable OpenAPI description of the API described here is maintained alongside this document in the source repository (see openapi.yaml).

Conventions and Definitions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

Scope:

An isolated MoQ delivery context on a relay, as defined in . All namespaces and tracks within a scope are isolated from other scopes on the same relay. A scope is the resource created by the provisioning API.

Scope Provisioning A CDN provider exposes an HTTP API endpoint for creating scopes: The request MAY include configuration (see ). The response includes a server-generated scope identifier and connection credentials: The url is the base URL of the relay service. The token is a credential that grants access to this scope.

Connecting to a Scope Clients connect to a provisioned scope by combining the URL and token returned at creation time: The relay extracts the token from the URL path, validates it, and maps the connection to the corresponding MoQT scope. Within that scope, all MoQT operations (SUBSCRIBE, ANNOUNCE, etc.) are isolated. Publishers and subscribers in one scope cannot see namespaces or tracks from another scope.

Origin Fallback A scope MAY be configured with an upstream origin URL. When a subscriber requests content that isn't available on the relay, the relay connects to the origin to fetch it. This is configured at provisioning time: The relay establishes a MoQT connection to the origin URL and forwards the subscription. The origin could be another relay (at a different CDN provider, or a customer's own infrastructure), or any MoQT-speaking endpoint.

Security Considerations TODO

IANA Considerations This document has no IANA actions.

Normative References Cisco Google Google Meta This document defines the core behavior for Media over QUIC Transport (MOQT), a media transport protocol designed to operate over QUIC and WebTransport, which have similar functionality. MOQT allows a producer of media to publish data and have it consumed via subscription by a multiplicity of endpoints. It supports intermediate content distribution networks and is designed for high scale and low latency distribution. In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.

Acknowledgments Thanks to Lucas Pardue and Jacob Curtis for design input.