From 543c984c4614062c768708a2cfbb9e9cdb0039e8 Mon Sep 17 00:00:00 2001 From: Thomas Darimont Date: Sun, 18 Oct 2026 17:09:54 +0200 Subject: [PATCH] Revise Specification Version 2.3.1 section in CAEP IOP (#357) We now explicitly state that SSF 1.0+ configuration metadata is provided via the /.well-known/sssf-configuration endpoint and that the legacy SSE 1.0-ID1 configuration is provided via /.well-known/sse-configuration endpoint. This lets a single issuer serve both versions with separate endpoints, so streams are bound to a version by the endpoints that created them. It also keeps the certification check meaningful and helps with interop. Closes #357 Signed-off-by: Thomas Darimont --- openid-caep-interoperability-profile-1_0.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/openid-caep-interoperability-profile-1_0.md b/openid-caep-interoperability-profile-1_0.md index 20e2617..fdb799b 100644 --- a/openid-caep-interoperability-profile-1_0.md +++ b/openid-caep-interoperability-profile-1_0.md @@ -160,8 +160,9 @@ Transmitters MUST implement the following features. ### Specification Version {#spec-version} -The Transmitter Configuration Metadata MUST include a `spec_version` field, and -its value MUST be `1_0` or greater. +The Transmitter Configuration Metadata published at `/.well-known/ssf-configuration` MUST include a `spec_version` field, and its value MUST be `1_0` or greater. + +A Transmitter that additionally supports Receivers implementing `1_0-ID1` MUST publish the metadata for that version at `/.well-known/sse-configuration`, as defined in Section 6.2 of [SSE-1_0-ID1], and MUST NOT publish `1_0-ID1` metadata at `/.well-known/ssf-configuration`. ### Delivery Method {#delivery-method}