fix: Check Commonalities and ICM scope definition to assess API impact

[Kevsy]

Problem description

Per M0, check Commonalities and ICM scope definition to assess API impact

Expected behavior

1. Look for Scope of Fall25 issues raised by Commonalities and ICM
2. Add any relevant issues to the SED repository

Alternative solution

Additional context

[Kevsy]

Commonalities scope M1 PR 451 covers the issues listed in 423

Issues to be checked if relevant for SimpleEdgeDiscovery Fall 25 (an X in the box indicates 'checked and issue raised if relevant'

error definitions

• Clarification required on usage of UNAUTHENTICATED and AUTHENTICATION_REQUIRED error codes Commonalities#368

• Remove AUTHENTICATION_REQUIRED error code Commonalities#429

• Remove 422 IDENTIFIER_MISMATCH error code as this can allow PII leakage Commonalities#431

• Remove IDENTIFIER_MISMATCH error and introduce DeviceResponse object Commonalities#455

• Adding a section in API info.description to provide rationale for not documented Error responses and a reference for their format Commonalities#438

• Not Documented Error Responses info.description section Commonalities#457

• Proposal for x-correlator format change Commonalities#436

• Enhancements for CAMARA Subscription/Notification Architecture Commonalities#437

• Update types property of Subscription schema in event-subscription-template.yaml Commonalities#432

pending issues

• Proposal to add a standard for defining durations for API Design guidelines Commonalities#137
• Text description aligment for duration format fields Commonalities#459
• Include Reference Link to CAMARA API Design Guidelines in Notification Cloud Events Artifact Commonalities#290
• Links to CAMARA API Event Subscription and Notification Guide in artifacts Commonalities#453
• Follow the principle of data minimization for events based on explicit subscriptions Commonalities#295
• Guidelines for asynchronous response in callback Commonalities#297
• Synchronization Status for initialEvent = true notifications Commonalities#299

[Kevsy]

I&CM scope M1 PR 292 covers the issues listed in 275

Issues to check if relevant for Simple Edge Discovery Fall 25:

• Clarification on which device is authenticated in authorization code flow IdentityAndConsentManagement#255
• Document when FE flow is applicable with regards to involved devices IdentityAndConsentManagement#256
• CIBA Privacy IdentityAndConsentManagement#258
• CIBA MUST not become two-legged IdentityAndConsentManagement#268
• Create OAuth2 two-legged flow with user identifier associated with the access token IdentityAndConsentManagement#277
• JWT Bearer Flow IdentityAndConsentManagement#290
• Further alignment of CAMARA-API-access-and-user-consent.md with API consumer and API provider terms IdentityAndConsentManagement#279
• Further alignment of CAMARA-API-access-and-user-consent.md with CAMARA terms and definitions IdentityAndConsentManagement#280
• Clarify protocols for CAMARA API access IdentityAndConsentManagement#281
• Claims in signed authentication requests IdentityAndConsentManagement#283
• mandatory fields in signed ACF request objects IdentityAndConsentManagement#285
• Update request object errors IdentityAndConsentManagement#287

[Kevsy]

Following check the required updates for Simple Edge Discovery are:

• fix: remove '401 AUTHENTICATION_REQUIRED' #84
• fix: remove 422 IDENTIFIER MISMATCH #85
• fix: add section on non-documented errors #87
• fix: update x-correlator pattern #88
• fix: update x-camara-commonalities to 0.6 #99

These are now included as sub-issues of #77 , so this issue can now be closed.