RE: [Bluez-devel] Qualification Testing

[Max Krasnyansky <maxk@qualcomm.com>]

At 04:37 PM 5/12/2003, Daryl Van Vorst wrote:
>Re: l2cap config stuff:
>
>We don't need any more logs or anything for that do we?  I think we're just
>trying to understand what it is exactly that we're supposed to do and why.
Yep. No need for logs.

>Max - You mentioned that the spec says that what the stack does with a
>config reject can be implementation specific. I just had a look at the spec
>and couldn't find it. Could you tell me where to look in the spec? 

section 6.1 
page 297

"Since all L2CAP implementations are capable to support a minimum L2CAP
packet size, see Section 4 on page 280, MTU is not really a negotiated value
but rather an informational parameter to the remote device that the local device
can accommodate in this channel an MTU larger than the minimum required. In
the unlikely case that the remote device is only willing to send L2CAP packets
in this channel that are larger than the MTU announced by the local device,
then this Configuration Request will receive a negative response in which the
remote device will include the value of MTU that is indented to transmit. In this
case, it is implementation specific on whether the local device will continue the
configuration process or even maintain this channel."

Max