1.4 Relationship to Other Protocols

The ActiveSync commands described in this document are sent and received over a Hypertext Transfer Protocol (HTTP) connection, as described in [RFC2616] in an HTTP POST method. The information contained in the HTTP POST header is described in [MS-ASHTTP]. The information contained in the HTTP message is sent and received in Wireless Application Protocol (WAP) Binary XML (WBXML) format, as described in [MS-ASWBXML], where the content of the WBXML adheres to the commands described in this document.

Some of the ActiveSync commands described in this document are used to synchronize or retrieve more than one class of content. For example, the Ping command (section can be used to monitor changes to the email, note, contact, calendar, or task classes. The elements included in the Ping command change depending on which content class is being monitored. Because each content class is used by multiple commands, each content class is described by an individual protocol. The content class protocols are described in [MS-ASEMAIL], [MS-ASCNTC], [MS-ASDOC], [MS-ASCAL], [MS-ASNOTE], [MS-ASMS], and [MS-ASTASK].

Another protocol that contains elements used by multiple commands is [MS-ASAIRS]. [MS-ASAIRS] describes the AirSyncBase namespace, which is used by multiple commands to specify the formatting preference of body content, truncation sizes, and other commonly used elements.

This document describes all of the ActiveSync commands except for the Provision command, which is described in [MS-ASPROV] section

The Autodiscover command (section is described in this document, but more information about Autodiscover publishing and lookup are available in [MS-OXDSCLI].

All simple data types in this document conform to the data type definitions in [MS-ASDTYPE].

For information about how to control the view of related email messages or conversations, see [MS-ASCON].

For information about how outbound Short Message Service (SMS) email messages are sent from mobile devices, see [MS-ASMS].

For conceptual background information and overviews of the relationships and interactions between this and other protocols, see [MS-OXPROTO].