MS basic connect extensions: 0d3a or 9d3a?

[Bjørn Mork]

Ben Chan <benchan at chromium.org> writes:

> 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.

Well, we can always look it up in the MBIM registry at
http://compliance.usb.org/mbim/

Oh, wait, I forgot - no one cares about maintaining that.  There's not a
single Intel entry for example, despite their role in the USB-IF.  So I
completely understand that Microsoft stopped bothering as well.  At
least they have the decency to document their stuff to the public.



Bjørn