2 Conformance

This Standard defines two conformance classes: TEA server and TEA client. An implementation may conform to either or both.

A conformant TEA server shall:

• Implement the operations defined in The TEA API, except those that this Standard makes optional for it.
• Support the discovery of its API as defined in the Discovery chapter.
• Either require no authentication, following the rules for such servers in the Discovery chapter, or require authentication for some or all of its objects and conform to the Authentication chapter, which is normative optional.
• Assign TEA UUIDs with the uniqueness and stability defined in the UUID Scope and Stability chapter.
• Return payloads that conform to Data model.

A conformant TEA client shall:

• Resolve Transparency Exchange Identifiers as defined in the Discovery chapter.
• Authenticate, where a TEA server requires it, as defined in the Authentication chapter.
• Send requests that conform to The TEA API.

The verbal forms in this Standard follow ISO/IEC Directives, Part 2: shall and shall not indicate requirements; should and should not indicate recommendations; may and need not indicate permission; and can and cannot indicate possibility or capability. The verbal form must is used only for external constraints and does not express a requirement of this Standard.