[MS-CDP]: Connected Devices Platform Protocol Version 3

2023/01/30

In Section 2.2.2.1.1, "Common Header," changed "inner buffer" to "Payload field" in the descriptions of deserialization.

Changed from:

Message deserialization is split into two phases. The first phase consists of parsing the header, validating authenticity, deduping, and decryption. The inner buffer is sent to the owner to manage the second part of the deserialization.

Changed to:

Message deserialization is split into two phases. The first phase consists of parsing the header, validating authenticity, deduping, and decryption. The Payload field is sent to the owner to manage the second part of the deserialization.

Changed from:

Message deserialization will therefore be split into two phases. With the first phase consisting of the parsing header, validating authenticity, deduping, and decryption. The inner buffer will be passed up to the owner to manage the second part of the deserialization.

Changed to:

Message deserialization will therefore be split into two phases. With the first phase consisting of the parsing header, validating authenticity, deduping, and decryption. The Payload field will be passed up to the owner to manage the second part of the deserialization.

2022/11/29

In section 2.2.2.2.3, "Bluetooth Advertising Beacon," added flag values and provided additional details about packet field structure and length.

Changed from:

Beacon Data (24 bytes): The beacon data section is further broken down. Note that the Scenario and Subtype Specific Data section requirements will differ based on the Scenario and Subtype.

Scenario Type (1 byte): Set to 1

Version and Device Type (1 byte): The high two bits are set to 00 for the version number; the lower6 bits are set to Device Type values as in section 2.2.2.2.2:

Changed to:

Beacon Data (24 bytes): The beacon data section is further broken down. Note that the Scenario and Subtype Specific Data section requirements will differ based on the Scenario and Subtype.

Scenario_Type (1 byte): Set to 1 (Bluetooth scenario).

Version_and_Device_Type (1 byte): The high three bits are set to 001 for the version number; the lower 5 bits are set to Device Type values as in section 2.2.2.2.2:

Changed from:

Version and Flags (1 byte): The high 3 bits are set to 001; the lower 3 bits to 00000.

Reserved (1 byte): Currently set to zero.

Salt (4 bytes): Four random bytes.

Device Hash (16 bytes): SHA256 Hash of Salt plus Device Thumbprint. Truncated to 16 bytes.

Changed to:

Version_and_Flags (1 byte): The high 3 bits are set to 001; the lower 5 bits are set to 00000 or 00001. Setting the lower 5 bits to 00001 indicates that the NearBy share setting is everyone rather than only my devices.

Flags_and_Device_Status (1 byte): The field has the following structure:

A (2 bits): Unused.

B - Bluetooth_Address_As_Device_ID (1 bit): When set, indicates that the Bluetooth address can be used as the device ID.

C (1 bit): Unused.

D - ExtendedDeviceStatus (4 bits):

One of the values in the following table. Values may be ORed.

Salt (4 bytes): Four random bytes.

Device_Hash (19 bytes): SHA256 Hash of Salt plus Device Thumbprint.