RE: [Bluez-devel] Qualification Testing

["Daryl Van Vorst" <daryl@wideray.com>]

Max,

> If an application does not explicitly tell us that it 
> supports larger MTU then it does not support it. As simple as 
> that :). We don't play "guess what MTU I support" games ;-). 

Yup.

> Sure we can make a hack. Once we agree on how should we 
> handle it I'll make 
> the change. But if the hack affects general case we're not 
> going to put it 
> into official kernel.

Of course. :)

> >Apparently, in step 3 above, if we send a config request with no 
> >options it will also pass the test. How silly is that? (specially 
> >considering that's what we send by default in the first place!)
> I'm pretty sure that it's just because they use some dumb 
> tester implementation. It doesn't make sense to resend the 
> same config request.

It's actually written that way in the test case. Here's a quote from the
updated test case (errata correction ID 241):

"Pass Verdict: The IUT sends an L2CAP_ConfigReq with acceptable values
received in the L2CAP_ConfigRsp with Result = Failure - unacceptable
parameters, or the L2CAP_ConfigReq contains no options."

-Daryl.