- From: Judd via GitHub <noreply@w3.org>
- Date: Mon, 08 Jun 2026 03:11:30 +0000
- To: public-web-bluetooth-log@w3.org
Glad to hear some updates in 2026! Here I would like to clarify the terminology "negotiation" and "exchange". What is happening in Bluetooth is _exchanging_: Inform the peer the maximum size of Attribute Protocol PDU that **I** (the Host) can receive. After the exchanging procedure is done, both parties know the maximum size of PDU that the peer can receive. "Negotiation" usually means coming to an agreement between two parties. This is not the case in Bluetooth. What developers need to know is the maximum size supported in Host APIs. This size is the minimum of the two sizes below: * The maximum size of Attribute Protocol PDU the Host can transmit (if the peer is an embedding device, this value is likely to be larger), * The maximum size of Attribute Protocol PDU the peer can receive. So, what we need is something like `getMTU()` which reflects the minimum of the two sizes above, but not `getNeogitatedMTU()` or `getExchangedMTU()`. P.S. According to Bluetooth Core Spec, when sending some Attribute Protocol PDUs, data will just be truncated by Host without complain when exceeding MTU. -- GitHub Notification of comment by foldl Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/issues/383#issuecomment-4645119585 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 8 June 2026 03:11:31 UTC