This document describes the TAS3 Compliance Requirements for Deployments in a normative and prescriptive way. Any deployment claiming "TAS3" compliance MUST abide by this document as well as [TAS3ARCH], and [TAS3PROTO]. A deployment usually has to satisfy, as well, requirements of the Trust Guarantor's, see [TAS3GLOS], Governance Agreement and certification procedures, some of which concern the software implementation and others the organizational properties. Use of TAS3 Brand is governed by a separate TAS3 Brand Agreement.
This document uses the keywords (e.g. MUST, SHOULD) of [RFC2119]. All text is normative unless expressly identified as non-normative. Prose and specification has precedence over examples. In general the examples should not be assumed normative unless no normative specification for the subject matter is available.
This architecture, and related documents are copyrighted works of TAS3 Consortium, as dated. All Rights Reserved. This architecture, and related documents, are versioned and subject to change without notice. No warranty or guarantee is given. This architecture, and related specifications can be implemented on Royalty Free terms by anyone. However, no warranty regarding IPR infringement is given. For further details, please see [TAS3CONSOAGMT].
For a partner to operate in a TAS3 Trust Network, it must comply with certain software and protocol requirements described in [TAS3ARCH] and [TAS3PROTO]. However such software can often be configured in a variety of ways. This document incorporates by reference all the requirement described by the above documents, and then adds deployment and configuration specific requirements.
In addition to the present document, the Trust Guarantor of your Trust Network may have published additional policies and requirements. The Governing Agreement of the Trust Network can also specify more requirements.
Many compliance requirements that a Trust Guarantor will likely enforce to its Trust Network are described in the Identity Assurance Framework [IAF].