Skip to content

Conversation

@thomasdarimont
Copy link
Contributor

@thomasdarimont thomasdarimont commented Sep 16, 2025

Use SSF 1.0, CAEP 1.0, RFC9728, FAPI 2.0 Security Profile

Fixes #291

@thomasdarimont thomasdarimont changed the title Fixes issue #291 Remove draft and align with final spec references SSF 1.0, CAEP 1.0, RFC9728, FAPI 2.0 Security Profile Fixes issue #291 Update draft and align with final spec references SSF 1.0, CAEP 1.0, RFC9728, FAPI 2.0 Security Profile Sep 16, 2025
@thomasdarimont thomasdarimont changed the title Fixes issue #291 Update draft and align with final spec references SSF 1.0, CAEP 1.0, RFC9728, FAPI 2.0 Security Profile Fixes issue #291 Update draft and align with final spec references Sep 16, 2025
@FragLegs
Copy link
Contributor

FragLegs commented Sep 16, 2025

Section 2.3.1 says

The Transmitter Configuration Metadata MUST have a spec_version field, and its value MUST be 1_0-ID2 or greater

Should we update that to be 1_0 (the final version)?

…ces SSF 1.0, CAEP 1.0, RFC9728, FAPI 2.0 Security Profile

Signed-off-by: Thomas Darimont <[email protected]>
@thomasdarimont thomasdarimont force-pushed the gh-291-align-caep-interop-specs branch from b79aacf to 03fe2d5 Compare September 16, 2025 18:15
Signed-off-by: Thomas Darimont <[email protected]>
@thomasdarimont
Copy link
Contributor Author

I think it makes sense to update the required spec version to 1_0. I adjusted the PR.

@thomasdarimont thomasdarimont changed the title Fixes issue #291 Update draft and align with final spec references Update draft and align with final spec references Sep 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Align CAEP Interop profile with finalized specs

3 participants