Original text:
cases.  Also, this document uses terminology defined in I-D.ietf- sacm-terminology.  2. This document defines requirements based on the SACM use cases models must adhere to and comply with the SACM information model. The requirements for the SACM information model include: <del> Extensible Attribute Vocabulary: the information model MUST define </del>  a minimum set of attributes for communicating Posture Information, to ensure interoperability between data models.  (Individual data models may define attributes beyond the mandatory-to-implement structure, and the ability to search based on patterns ("wildcard searches") as well as specific data elements. <del> Full Vs.  Partial Updates: The data model SHOULD include the </del>  ability to allow providers of data to provide the data as a whole, or when updates occur.  For example, a consumer can request a full update on initial engagement, then request to receive deltas Either or both confidentiality and integrity at the data layer.  5. 5.1.

Reviewer comments:
Updates to address 3 of four open issues
Version -09 The document is not consistent if the character following the pithy title is capitalized. A pass needs to be made to fix this.
Hi Jim, I only found 1 straggler in IM-URL there are others please let me know so I can fold it into the -10 draft. Thanks, Nancy
Fixed in Pull request
-version 09 There are two nits that needs to be resolved. Missing 2119 boilerplate Reference to RFC 3444 exists, but is not referred to.
Hi Jim, Will fix in -10 draft..... Thanks, Nancy
Fixed in Pull request

Revised text:
cases.  Also, this document uses terminology defined in I-D.ietf- sacm-terminology. <ins> 1.1. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC2119. When the words appear in lower case, their natural language meaning is used. </ins> 2. This document defines requirements based on the SACM use cases models must adhere to and comply with the SACM information model. The requirements for the SACM information model include:  <ins> Extensible Attribute Vocabulary: The information model MUST define </ins> a minimum set of attributes for communicating Posture Information, to ensure interoperability between data models.  (Individual data models may define attributes beyond the mandatory-to-implement structure, and the ability to search based on patterns ("wildcard searches") as well as specific data elements.  <ins> Full vs. Partial Updates: The data model SHOULD include the </ins> ability to allow providers of data to provide the data as a whole, or when updates occur.  For example, a consumer can request a full update on initial engagement, then request to receive deltas Either or both confidentiality and integrity at the data layer. <ins> 4.2. SACM information may contain sensitive information about the target endpoint as well as revealing identity information of the producer or consumer of such information.  Similarly, as part of the SACM discovery mechanism, the advertised capabilities (and roles, e.g. SACM components enabled) by the endpoint may be construed as private information.  There may be applications as well as business and regulatory practicess that require that aspects of such information be hidden from any parties that do not need to know it. Data confidentiality can provide some level of privacy but may fall short where unecessary data is still transmitted.  In those cases, filtering requirements at the data model such as OP-005 must be applied to ensure that such data is not disclosed.  RFC6973 provides guidelines for which SACM protocols and information and data models should follow. </ins> 5. 5.1.