[rmcat] test cases for coupled cc [was: Re: Review of draft-ietf-rmcat-eval-test-02]

[Mirja Kühlewind <[e-mail]>]

Hi Zahed,

see below.

> Am 28.01.2016 um 14:29 schrieb Zaheduzzaman Sarker <[e-mail]>:
> 
>> * I would like to suggest the following two additional test-cases
>>    under section 6 (other potential test cases).
> 
> The test cases in the draft were designed for end-point adaptation algorithm without coupled congestion control in mind i.e. no need for shared bottleneck detection and flow priority. In the last IETF meeting we talked about the possibility of extending the test cases to include coupled congestion control algorithm.

I believe we decided already at the last meeting that we need to adapt this draft to include uses cases for coupled congestion (and that’s why we asked Safiqul to propose some).

> 
> Now if we extend the test cases then I don't think only adding the two proposed test cases will be sufficient.

Yes, that might be true but adding these use cases below would probably be a good starting point.

> We will need to identify all the test cases those are suitable for running with coupled congestion control.

Not sure, if you only have one flow that test case is simply not suitable and that’s fine.

> Like 5.2 can be run with priority per flow. By doing this we can mention (in each test case or in one place in the document) that one can run tests with flow priority and perhaps give some means to evaluate the available capacity distribution with some equation like the one mentioned here in the proposed test case 6.3.

Yes.

> However, then this document also needs to include description for shared bottleneck detection.

Why?

> In the simplest form, we can perhaps assume that the identified test cases have single bottleneck point.

Yes.

> 
> I think we need to discuss what is best possible way to extend the test cases if we agreed to do that.

As I said I think we agreed already. Please following with Safiqul on this!

> 
> But before that I would like to know if the WG is OK with extending the test cases for coupled congestion control.

Any further feedback on this from the group is of course welcome! Please speak up now!

> 
> And will it be a compulsory (candidate algorithms MUST present results) or optional (candidate algorithms MAY present results) part of the test case.

I guess only candidates that use coupled cc..?

Mirja


> 
>> 
>> 6.3 Prioritization test
>> 
>> In this test case, three RMCAT media flows started  out with a priority
>> of 1 each. At around 50 s, the priorities of flow 2 and flow 3 were
>> decreased to 1/3 and 2/3.  A flow i  is assigned the available capacity
>> based on its priority p_{i} as follows:
>> 
>> b_{i} = (p_{i} / Sum(p_{k}) ) * BW   ;  k = {1.. 3}
>> 
>> This test case ensures that flows are getting their assigned portions of
>> the available capacity based on their assigned priorities. It can be
>> useful for [I-D.ietf-rmcat-coupled-cc]. It addresses the requirement 3A
>> in  [I-D.ietf-rmcat-cc-requirements]
>> 
>> Testbed topology: Same as test case defined in section 5.4
>> 
>> Testbed Attribute:
>> 
>> The general description of the testbed parameters is same as Section 5.4
>> with changes in the test specific setup as  below-
>> 
>>   o  Other test specific setup:
>> 
>>       *  RMCAT media flow timeline:
>> 
>>          +  Flow ID: One (1)
>> 
>>          +  Start time: 0s
>> 
>>          +  Flow duration: 119s
>> 
>>          +  Priority: no change
>> 
>>      *  RMCAT media flow timeline:
>> 
>>          +  Flow ID: Two (2)
>> 
>>          +  Start time: 0s
>> 
>>          +  Flow duration: 119s
>> 
>>          +  Priority:  change to 1/3 after 50s
>> 
>>       *  RMCAT media flow timeline:
>> 
>>          +  Flow ID: Three (3)
>> 
>>          +  Start time: 0s
>> 
>>          +  Flow duration: 119s
>> 
>>          +  Priority: change to 2/3 after  50s
>> 
>> 
>> 6.4 RMCAT flows competing with one or more long TCP flows
>> 
>> This test case is an extension of the test case defined in section 5.6.
>> It is important for [I-D.ietf-rmcat-coupled-cc], where it requires more
>> than one RMCAT flows in order to couple them.
>> 
>> The general description of the testbed parameters is same as section 5.6.