XML Schema change for the eap-metadata format

[restena-sw]

Issue type

• Defect - Crash/memory corruption.
• Defect - Non-compliance with a standards document or incorrect OS API usage.
• Defect - Unexpected behaviour (obvious or has been verified by a project member).
• New feature request.

Defect/Feature description

Changed semantics of an option to enforce username correctness checking in #187 means the current name of the option in XML Schema ("InnerIdentityHint") is not telling any more.

If Schema is to be changed, a better name for it could be "InnerIdentityExactRealm" (to accompany "InnerIdentitySuffix").

A second possible change relates to the issue raised in #189 where the CAT admin UI has a possiblity to define "Remove/Disable SSID" but there is no space in the schema to express that.

[restena-sw]

@twoln @majagw @jornane This is the new issue regarding the requested XML Schema changes.

[restena-sw]

The IETF document describing (an initial version of) the eap-metadata format can be found on the IETF's document graveyard: https://datatracker.ietf.org/doc/html/draft-winter-opsec-netconfig-metadata-00

The draft, along with the schema, did not resonate with much interest in the IETF back in the day, so it simply expired.

Today, the schema as contained in source code is the only authoritative place and reference.

There are multiple known consumers of this: the eduroam CAT Android App, and an ongoing implementation effort inside HP Inc.

That doesn't mean changes are impossible; but it's best to be conscious of possible breakage if we do change something.