[Openid-specs-ab] Issue #2152: Consistently apply "if not understood MUST be ignored" language at potential extension points (openid/connect)

mbj issues-reply at bitbucket.org
Wed May 8 19:09:14 UTC 2024


New issue 2152: Consistently apply "if not understood MUST be ignored" language at potential extension points
https://bitbucket.org/openid/connect/issues/2152/consistently-apply-if-not-understood-must

Michael Jones:

We use this and similar language at [https://openid.net/specs/openid-federation-1\_0-34.html#name-constraints](https://openid.net/specs/openid-federation-1_0-34.html#name-constraints) and other places:

> Other constraint parameters MAY be defined and used. If they are not understood, they MUST be ignored.[¶](https://openid.net/specs/openid-federation-1_0-34.html#section-6.2-4)

But we’re not consistently applying this extension principle throughout the specification.  For instance, this language is missing from the list endpoint description.

We should include this language, where applicable.

‌

Responsible: Michael Jones



More information about the Openid-specs-ab mailing list