Clarify case sensitivity of parameter names and values

[eric-murray]

What type of PR is this?

• documentation

What this PR does / why we need it:

The CAMARA Security and Interoperability profile does not clarify whether parameter names and values are case sensitive.

It is proposed to adopt the RFC 6749 convention that parameter names and values are case sensitive unless otherwise stated.

Which issue(s) this PR fixes:

Fixes #

Special notes for reviewers:

None

Changelog input

 release-note
 - Add document convention that parameter names and values are case-sensitive unless otherwise stated

Additional documentation

None

[AxelNennker]

Specifications are specifications. If we define e.g. the "tel:" prefix for the login_hint format then that is the prefix.
No other interpretations. Neither "TEL:" nor "Tel:" nor "tEL:" are valid values because the spec specifies "tel:" and nothing else.

[eric-murray]

Specifications are specifications. If we define e.g. the "tel:" prefix for the login_hint format then that is the prefix. No other interpretations. Neither "TEL:" nor "Tel:" nor "tEL:" are valid values because the spec specifies "tel:" and nothing else.

Sure. And this statement, which other standards feel the need to include, unambiguously clarifies this.

[AxelNennker]

I am trying to avoid repeating standards.
I have no idea how anybody can interpret the specification of e.g. login_hint "tel:" prefix that e.g "Tel:" is conforming to that specification.

I think the "clarification" this PR provides is very unneeded. You do not have to be an "expert" to read our spec and conclude that e.g. only "tel:" is a valid prefix.

If we go there that we start stating the obvious we end up with documents that are harder to understand because now e.g. OpenId Provider implementers have to read the OIDC core standard plus our document.

But, of course, if the group feels it helps then we can add this one sentence.