MS basic connect extensions: 0d3a or 9d3a?

[Ben Chan]

Looks like the UUID for basic connect extension is pretty messed up.  It
isn't listed in http://compliance.usb.org/mbim/.  I'm not sure what to
expect. majority wins?   Worst case, we will need to carry a quirk in
libmbim to treat them interchangeable, sigh :(

Service UUID = 3d01dcc5-fef5-4d05-9d3a-bef7058e9aaf
https://docs.microsoft.com/en-us/windows-hardware/drivers/network/mb-modem-reset-operations
https://docs.microsoft.com/en-us/windows-hardware/drivers/network/mb-protocol-configuration-operations--pco-

Service UUID = 3d01dcc5-fef5-4d05-0d3a-bef7058e9aaf
https://docs.microsoft.com/en-us/windows-hardware/drivers/network/mb-multi-sim-operations
https://docs.microsoft.com/en-us/windows-hardware/drivers/network/mb-network-blacklist-operations
https://docs.microsoft.com/en-us/windows-hardware/drivers/network/mb-base-stations-information-query-support
https://docs.microsoft.com/en-us/windows-hardware/drivers/network/mb-provisioned-context-operations
https://docs.microsoft.com/en-us/windows-hardware/drivers/network/mb-lte-attach-operations
:

On Mon, Sep 10, 2018 at 8:22 AM Ben Chan <benchan at chromium.org> wrote:
>
> Hi Aleksander,
>
> Looks like Microsoft uses inconsistent UUIDs for the same MS basic
connect extensions:
>
>
https://docs.microsoft.com/en-us/windows-hardware/drivers/network/mb-protocol-configuration-operations--pco-
:
> Service = MBB_UUID_BASIC_CONNECT_EXT_CONSTANT
> Service UUID = 3d01dcc5-fef5-4d05-9d3a-bef7058e9aaf
>
>
https://docs.microsoft.com/en-us/windows-hardware/drivers/network/mb-lte-attach-operations
:
> UUID = UUID_BASIC_CONNECT_EXTENSIONS
> UUID Value = 3d01dcc5-fef5-4d05-0d3a-bef7058e9aaf
>
> I added the extensions based on the PCO CID.   Given the close
resemblance of these two UUIDs, it looks more like a typo in their doc.  I
tested with Fibocom L850, which supports the PCO CID and uses the 9d3a
variant.   Unfortunately, I don't have another modem to compare with.
>
> Ben
>
> On Mon, Sep 10, 2018 at 6:59 AM Aleksander Morgado <
aleksander at aleksander.es> wrote:
>>
>> Hey Ben & all,
>>
>> In libmbim we have the MS basic connect extensions UUID defined as:
>>    3d01dcc5-fef5-4d05-9d3a-bef7058e9aaf
>>
>> Which is in line with e.g.
>>
https://docs.microsoft.com/en-us/windows-hardware/drivers/network/mb-modem-reset-operations
>>
>> But then I'm seeing devices reporting the basic connect extensions UUID
as:
>>   3d01dcc5-fef5-4d05-0d3a-bef7058e9aaf
>>
>> Which is actually in line with e.g.
>>
https://docs.microsoft.com/en-us/windows-hardware/drivers/network/mb-base-stations-information-query-support
>>
>> What is this mess...? Are both UUIDs used interchangeably?
>>
>> --
>> Aleksander
>> https://aleksander.es
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libmbim-devel/attachments/20180910/ae96d20f/attachment.html>