[PR] nimble/host: close l2cap channels with duplicate DCID [mynewt-nimble]

["piotrnarajowski (via GitHub)" <gi...@apache.org>]

piotrnarajowski opened a new pull request, #2324:
URL: https://github.com/apache/mynewt-nimble/pull/2324

   Previously, when receiving an L2CAP connection response with a duplicate DCID, Nimble invoked ble_l2cap_sig_disconnect_nolock() to negotiate channel termination ota. As a result, the channel kept active until timer has expired significantly prolonging L2CAP/ECFC/BV-29-C test execution.
   
   Per Code Spec Vol 3, Part A, Section 4.22 and 4.23: "If a device receives an L2CAP_CREDIT_BASED_CONNECTION_RSP packet with an already-assigned Destination CID, then both the original channel and the new channel shall not be used." This suggests discontinuing channel usage, but does not require issuing L2CAP Disconnection Request.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@mynewt.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org