Original text:
value of specific Claims if it knew that only certain values were accepted by the Relying Party. <del> Conceptual messages carrying sensitive or confidential information are expected to be integrity protected (i.e., either via signing or a secure channel) and optionally might be confidentiality protected via encryption.  If there isn't confidentiality protection of conceptual messages themselves, the underlying conveyance protocol should provide these protections. </del>  As Evidence might contain sensitive or confidential information, Attesters are responsible for only sending such Evidence to trusted 12.2. <del> Any solution that conveys information used for security purposes, whether such information is in the form of Evidence, Attestation Results, Endorsements, or appraisal policy must support end-to-end integrity protection and replay attack prevention, and often also needs to support additional security properties, including: </del>  end-to-end encryption, Security protections in RATS may be applied at different layers, whether by a conveyance protocol, or an information encoding format. <del> This architecture expects conceptual messages (see messages) to be end-to-end protected based on the role interaction context.  For example, if an Attester produces Evidence that is relayed through some other entity that doesn't implement the Attester or the intended Verifier roles, then the relaying entity should not expect to have access to the Evidence. </del>  12.3.

Reviewer comments:
Signed-off-by: Dave Thaler
** Section 12.2 Any solution that conveys information used for security purposes, whether such information is in the form of Evidence, Attestation Results, Endorsements, or appraisal policy ... Should reference values be included?
same changes, conceptual messages

Revised text:
value of specific Claims if it knew that only certain values were accepted by the Relying Party.  <ins> Conceptual messages (see messages) carrying sensitive or confidential information are expected to be integrity protected (i.e., either via signing or a secure channel) and optionally might be confidentiality protected via encryption.  If there isn't confidentiality protection of conceptual messages themselves, the underlying conveyance protocol should provide these protections. </ins> As Evidence might contain sensitive or confidential information, Attesters are responsible for only sending such Evidence to trusted 12.2.  <ins> Any solution that conveys information in any conceptual message (see messages) must support end-to-end integrity protection and replay attack prevention, and often also needs to support additional security properties, including: </ins> end-to-end encryption, Security protections in RATS may be applied at different layers, whether by a conveyance protocol, or an information encoding format.  <ins> This architecture expects conceptual messages to be end-to-end protected based on the role interaction context.  For example, if an Attester produces Evidence that is relayed through some other entity that doesn't implement the Attester or the intended Verifier roles, then the relaying entity should not expect to have access to the Evidence. </ins> 12.3.