RE: [Bluez-devel] Qualification Testing

[Max Krasnyansky <maxk@qualcomm.com>]

At 11:01 AM 5/16/2003, Daryl Van Vorst wrote:
>Max,
>
>> >> I sent the above quote to Cetecom last week. They responded
>> >> saying that MTU isn't the only negotiated parameter.
>> 
>> FlushTO _must_ be 0xffff for reliable ACL link. So far none 
>> of the profiles specified use of unreliable links. 
>> 
>> Support for QOS is totally optional. We're only required to 
>> support 'best effort'. Which means that even if they want 
>> something other than 'best effort' (i.e. they reject 
>> default settings) we won't be able to accept it simply 
>> because we don't support it.
>> 
>> So I'm not sure what can be negotiated there. 
>
>Ok. I'll see what they say about that too.
>
>> btw Can this fancy Merlin viewer export trace in plain text ? 
>> I'm too lazy to install that stuff. And it looks like I need to see 
>> what is it exactly that they request/reject.
>
>
>Before we start the test, we must specify to the tester the parameters that
>we'll accept. The tester will reject the first set of values, no matter what
>they are. In its response it will send new values (which we specify) that it
>expects to see in the next request from the IUT.

Any updates on this one ?

Max