applicability statement also apply to this protocol because clients are required to use the Lists Web Service Protocol ([MS-LISTSWS]) to implement this protocol. This protocol is intended to transfer the data of the abstract data model (section 3.2.1) between the protocol server and the protocol client so that both agree on the state of the items after the protocol completes. Versioning and Capability Negotiation This document covers versioning issues in the following areas: Supported transports: This protocol uses multiple transports with SOAP as specified in Transport (section ). Protocol versions: This protocol is based on the Lists Web Service Protocol () and shares the same versioning. Security and authentication methods: This protocol supports the following authentication methods: LANMAN, , and . Capability negotiation: This protocol does explicit negotiation as specified in this section. If a protocol server implements GetListItemChanges and not GetListItemChangesSinceToken, the protocol client has to implement some way of detecting that. This is optional and a protocol client can choose to support only one of those . For an example of how a protocol client might do this, see GetList (section ). For information about those WSDL operations, see [MS-LISTSWS]. Vendor-Extensible Fields This protocol does not define any vendor-extensible fields, but because this protocol uses the Web Service Protocol (), any vendor extensible fields from that protocol can be used with this protocol. See [MS-LISTSWS] section 1.8. Standards Assignments None.
applicability statement also apply to this protocol because clients are required to use the Lists Web Service Protocol ([MS-LISTSWS]) to implement this protocol. This protocol is intended to transfer the data of the abstract data model (section 3.2.1) between the protocol server and the protocol client so that both agree on the state of the items after the protocol completes. Versioning and Capability Negotiation This document covers versioning issues in the following areas: Supported transports: This protocol uses multiple transports with SOAP as specified in Transport (section ). Protocol versions: This protocol is based on the Lists Web Service Protocol () and shares the same versioning. Security and authentication methods: This protocol supports the following authentication methods: LANMAN, , and . Capability negotiation: This protocol does explicit negotiation as specified in this section. If a protocol server implements GetListItemChanges and not GetListItemChangesSinceToken, the protocol client has to implement some way of detecting that. This is optional and a protocol client can choose to support only one of those . For an example of how a protocol client might do this, see GetList (section ). For information about those WSDL operations, see [MS-LISTSWS]. Vendor-Extensible Fields This protocol does not define any vendor-extensible fields, but because this protocol uses the Web Service Protocol (), any vendor extensible fields from that protocol can be used with this protocol. See [MS-LISTSWS] section 1.8. Standards Assignments None.