Re: [rmcat] Roman Danyliw's Discuss on draft-ietf-rmcat-wireless-tests-09: (with DISCUSS and COMMENT)

"Xiaoqing Zhu (xiaoqzhu)" <xiaoqzhu@cisco.com> Fri, 13 March 2020 19:31 UTC

Return-Path: <xiaoqzhu@cisco.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE25C3A0C00; Fri, 13 Mar 2020 12:31:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.6
X-Spam-Level:
X-Spam-Status: No, score=-9.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=XJgriyeE; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=VEU6pcNY
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id boIxKoQTD7tP; Fri, 13 Mar 2020 12:31:27 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5BD793A0BB6; Fri, 13 Mar 2020 12:31:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10654; q=dns/txt; s=iport; t=1584127887; x=1585337487; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=atmc2KQwEB7cpXJtxQ+hPIYw+xGfXds430vmQA+OlcQ=; b=XJgriyeE0/c7j+dfj02mhlEQ6Ooq9Dv6I1PlDA3TYTsoz3r8WpGnQ5VF i9sUjuWCyjO2WrJtoSu9u6pbzBL+Jss5pfaLEm4zF8xEy5cfnenuTdAPt Ff93daPWxxcrDh68kCdYq2A1DumTgsjCd4Krm3lIlqEaxZOOcWrl6G6nD I=;
IronPort-PHdr: =?us-ascii?q?9a23=3AFhhp2xyLXU9LiiLXCy+N+z0EezQntrPoPwUc9p?= =?us-ascii?q?sgjfdUf7+++4j5YhWN/u1j2VnOW4iTq+lJjebbqejBYSQB+t7A1RJKa5lQT1?= =?us-ascii?q?kAgMQSkRYnBZuVCET8NezqcgQxHd9JUxlu+HToeUU=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CqBQDQ3mte/40NJK1mHAEBAQEBBwE?= =?us-ascii?q?BEQEEBAEBgXuBVFAFbFggBAsqhBWDRQOKcYI6mD2BQoEQA1QJAQEBDAEBJQg?= =?us-ascii?q?CBAEBhEMCF4IGJDgTAgMBAQsBAQUBAQECAQUEbYVWDIVkAgEDEhERDAEBJRI?= =?us-ascii?q?BDwIBBgIODAImAgICMBUQAgQBDQUigwQBgkoDLgEOkSKQZwKBOYhidYEygn8?= =?us-ascii?q?BAQWBMwIOQYMiGIIMAwaBDiqMLhqBQT+BOAwUghg1PoFJgRsBAQEBAQGBLAE?= =?us-ascii?q?SASGDETKCLI1UJCCCV59OCoI8h1aFA0qFF4Q1HYJKiCeQUI8CgU6HM5JaAgQ?= =?us-ascii?q?CBAUCDgEBBYFpImdYEQhwFWUBgkFQGA2OHSMVgzuFFIVBdAKBJ4poLYIUAQE?=
X-IronPort-AV: E=Sophos;i="5.70,549,1574121600"; d="scan'208";a="455489067"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 13 Mar 2020 19:31:25 +0000
Received: from XCH-ALN-002.cisco.com (xch-aln-002.cisco.com [173.36.7.12]) by alln-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id 02DJVOLS018452 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 13 Mar 2020 19:31:25 GMT
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by XCH-ALN-002.cisco.com (173.36.7.12) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 13 Mar 2020 14:31:24 -0500
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 13 Mar 2020 14:31:24 -0500
Received: from NAM10-BN7-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 13 Mar 2020 14:31:24 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; =?utf-8?q?b=3Da9wUofvRfZFpdrKHndWhcXdYo14Dj4W+WhuK7DurBlZlIxwbUaVlcpoKLNQo0?= =?utf-8?q?om2/GCStk0BggERcelTViBgL2rUDujAh/CmtpcIDmhulLtiJ9YHHfI9REc8m3WRPj?= =?utf-8?q?EILqjM7TBCl2DJ74MJuL8AqoL7C3GjXJu36Zn81SzDVrTUY/pbUD2TZwNDOuJyJvE?= =?utf-8?q?4CtOlZk9SOKAwb1fux5o4Vl4Z6JE34H1N/ck07VFBoNvpCPF0S+uMWlozRTUQ7aqe?= =?utf-8?q?LL4Dhox6zXO2wdXHSF3RmXKKwAvPJgC97QpqyvKbnVW0+fbriWK0qm7Wgcmofzak1?= =?utf-8?q?LtYk+/wVh3MPLad3uI8bQ=3D=3D?=
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; =?utf-8?q?h=3DFrom=3ADate=3ASubject=3AMessage-ID=3ACont?= =?utf-8?q?ent-Type=3AMIME-Version=3AX-MS-Exchange-SenderADCheck=3B?= =?utf-8?q?bh=3Datmc2KQwEB7cpXJtxQ+hPIYw+xGfXds430vmQA+OlcQ=3D=3B_b=3Dm0zNAc?= =?utf-8?q?vCPH/UX3Q/bhDc6XMq84KdUIXEUsHNISNMvCH71RSLKfpksSj1JeKp9o2ZL4trrGe?= =?utf-8?q?Sx7zhx1BJGVznzIIOGK0GN02YoAz/CNkSXbUO2WdyFfkFxv9FRKXWYWalSirzH4oC?= =?utf-8?q?i4RM6qQEAw9qRwACDe3bBA0Fcn6u9AKz/7dIWgt2IPMtf5NV4HrI6DXqFdYE+wxSh?= =?utf-8?q?g4qgK0fG6Kzt7YDCgLBSw5geW8NkG99kNfIX5qZ3RmkLvlTGFVt3CEI22TOq+2vLD?= =?utf-8?q?x0UloNnY/MkevhoUF4HtFOj5EbLJjWahp90g35Hb679WSXY9urI/p11K/panBEOaN?= =?utf-8?q?qP1F32HwCvA=3D=3D?=
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; =?utf-8?q?h=3DFrom=3ADate=3ASubject=3AM?= =?utf-8?q?essage-ID=3AContent-Type=3AMIME-Version=3AX-MS-Exchange-SenderADC?= =?utf-8?q?heck=3B_bh=3Datmc2KQwEB7cpXJtxQ+hPIYw+xGfXds430vmQA+OlcQ=3D=3B_b?= =?utf-8?q?=3DVEU6pcNYkVetWOZ0/7i3bC0B5QKIIV7Bc3OqGkyPhDwrMi1lQ6zTvQ8GykEzi3?= =?utf-8?q?bo6CVjEZZtv9gi9lpFScyZKvASvjxcQ3nlDKEm8lQUFOOFWo/KuNSqCW93TOV6Cm8?= =?utf-8?q?6TqJXjbtZLiRTnToVYu7EWR7ouSlu3EvU5BDcWAquUmk=3D?=
Received: from BYAPR11MB3158.namprd11.prod.outlook.com (2603:10b6:a03:1c::29) by BYAPR11MB2983.namprd11.prod.outlook.com (2603:10b6:a03:88::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2814.16; Fri, 13 Mar 2020 19:31:22 +0000
Received: from BYAPR11MB3158.namprd11.prod.outlook.com ([fe80::6cc3:855e:aaac:522f]) by BYAPR11MB3158.namprd11.prod.outlook.com ([fe80::6cc3:855e:aaac:522f%4]) with mapi id 15.20.2793.018; Fri, 13 Mar 2020 19:31:22 +0000
From: "Xiaoqing Zhu (xiaoqzhu)" <xiaoqzhu@cisco.com>
To: Roman Danyliw <rdd@cert.org>, The IESG <iesg@ietf.org>
CC: "draft-ietf-rmcat-wireless-tests@ietf.org" <draft-ietf-rmcat-wireless-tests@ietf.org>, "rmcat-chairs@ietf.org" <rmcat-chairs@ietf.org>, "rmcat@ietf.org" <rmcat@ietf.org>, Colin Perkins <csp@csperkins.org>
Thread-Topic: Roman Danyliw's Discuss on draft-ietf-rmcat-wireless-tests-09: (with DISCUSS and COMMENT)
Thread-Index: AQHV8jfqPBIHbvlayEmBhjvSQem0iqhGo7GA
Date: Fri, 13 Mar 2020 19:31:22 +0000
Message-ID: <298AEB88-956E-4E5C-9309-BBD77811A084@cisco.com>
References: <158333496772.29337.12478553941060973013@ietfa.amsl.com>
In-Reply-To: <158333496772.29337.12478553941060973013@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.35.20030802
authentication-results: spf=none (sender IP is ) smtp.mailfrom=xiaoqzhu@cisco.com;
x-originating-ip: [2001:420:1402:1250:9160:a3ca:335f:a3ce]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 4d95d88a-fab8-49dc-287f-08d7c7851d0b
x-ms-traffictypediagnostic: BYAPR11MB2983:
x-microsoft-antispam-prvs: =?utf-8?q?=3CBYAPR11MB29833E82B7735D5390E611C1C9F?= =?utf-8?q?A0=40BYAPR11MB2983=2Enamprd11=2Eprod=2Eoutlook=2Ecom=3E?=
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 034119E4F6
x-forefront-antispam-report: SFV:NSPM; =?utf-8?q?SFS=3A=2810009020=29=284636?= =?utf-8?b?MDA5KSgzOTg2MDQwMDAwMikoMzQ2MDAyKSgxMzYwMDMpKDM3NjAwMikoMzY2?= =?utf-8?b?MDA0KSgzOTYwMDMpKDE5OTAwNCkoMjkwNjAwMikoODY3NjAwMikoMTg2MDAzKSgz?= =?utf-8?q?3656002=29=284326008=29=2836756003=29=2886362001=29=288936002=29?= =?utf-8?q?=2866574012=29=286506007=29=282616005=29=2881166006=29=2881156014?= =?utf-8?q?=29=28110136005=29=2854906003=29=2871200400001=29=2866556008=29?= =?utf-8?q?=2866476007=29=2866946007=29=2864756008=29=2866446008=29=28761160?= =?utf-8?b?MDYpKDkxOTU2MDE3KSg0Nzg2MDAwMDEpKDk2NjAwNSkoMzE2MDAyKSg1NjYw?= =?utf-8?q?300002=29=286486002=29=286512007=29=3B?= DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB2983; H:BYAPR11MB3158.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: =?utf-8?q?oOjVf7Wk3g7d/AEp7sKpio0e1kal7/O?= =?utf-8?q?49A6vvHnuofNh16UEnhH0wM5Rh5YJLOgiS3Nh+zlNBwdwAMefKc/y4+PIzfhHg/q4?= =?utf-8?q?OTo8JOp6sM/hKja5x9Q47ueFEPnHsNR04HtSaNi5wnXR76U2vl9sDI8a5VELdOqJH?= =?utf-8?q?4MpgiSq4nhyhNMdGIlpDAWsNvlF110K2/jsB6BohOsha9Kgs/zzWpT3qA39vP7c9e?= =?utf-8?q?iPq2JUr31c2cMWb5pSp4HRC04MPPeyY76v9B6xbhLUa+Bl+cjR/wvu/pPyE0HfDH2?= =?utf-8?q?Zfk2D+uj5xXdipiMP7sQ6X226/JJgqTkwP/nOjr11bWq5eX51QAEeocMn/J3OtE3h?= =?utf-8?q?2TGSAvBGmbwDWgEBpgheZZbVKi6EQh7XBh+76QfYbeD714t7iJ9RAnn7w99SZyo/8?= =?utf-8?q?ENhnfVbhoVJFrx8dwoBhCBes6nvFPceDg3poYIrqEPW1145Ek7BxDIrNQbUPH/3NG?= =?utf-8?q?Gyxtn826ZmvnTd+SUGgRCRlRqDM45fKq4ek3qtKs03z5tF7g=3D=3D?=
x-ms-exchange-antispam-messagedata: =?utf-8?q?GD5ek+XG4X/eSxZz+fN5PZNhgKEtBU?= =?utf-8?q?HnpzEHxWkDIQCLXO1112FSfabeBCeDuShaMlHg+WZqH3KLlO6YHgrjRokJQNUuAZc?= =?utf-8?q?YqbfdIpd2oulkW/dKasvgNzAqYdWri5Zr1JjjuncIHDsl0DLtkL3AIwcFoYpHEGl+?= =?utf-8?q?XGG0Rxw8qWdvbyNWlar+3J9+VbXAZQz8L6eLwRvW98jvkBJb3kzGig=3D=3D?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <67B8A7B868799A40B47F2D74D3458B43@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 4d95d88a-fab8-49dc-287f-08d7c7851d0b
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Mar 2020 19:31:22.6263 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: =?utf-8?q?WX6aa8K1PYwxssBHwqCnp?= =?utf-8?q?jqDvQLLm75/KPhN3fIyTF4zrmDkqIb7qNTADa+K40aAK/vB8xGmFxwa5dIupjE9JA?= =?utf-8?q?=3D=3D?=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB2983
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.12, xch-aln-002.cisco.com
X-Outbound-Node: alln-core-8.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/LYpW_Aw6_Y8jlyeqCW_8QLtU5yo>
Subject: Re: [rmcat] Roman Danyliw's Discuss on draft-ietf-rmcat-wireless-tests-09: (with DISCUSS and COMMENT)
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "RTP Media Congestion Avoidance Techniques \(RMCAT\) Working Group discussion list." <rmcat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rmcat>, <mailto:rmcat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rmcat/>
List-Post: <mailto:rmcat@ietf.org>
List-Help: <mailto:rmcat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmcat>, <mailto:rmcat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Mar 2020 19:31:31 -0000

Hi Roman, 

Many thanks for your thorough review of this draft.  We have updated it to version -11: 
https://datatracker.ietf.org/doc/html/draft-ietf-rmcat-wireless-tests-11

Please also see our detailed responses, tagged [authors] inline below. 

Best regards,
Xiaoqing (on behalf of all authors)

On 3/4/20, 9:16 AM, "Roman Danyliw via Datatracker" <noreply@ietf.org> wrote:

    Roman Danyliw has entered the following ballot position for
    draft-ietf-rmcat-wireless-tests-09: Discuss
    
    When responding, please keep the subject line intact and reply to all
    email addresses included in the To and CC lines. (Feel free to cut this
    introductory paragraph, however.)
    
    
    Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
    for more information about IESG DISCUSS and COMMENT positions.
    
    
    The document, along with other ballot positions, can be found here:
    https://datatracker.ietf.org/doc/draft-ietf-rmcat-wireless-tests/
    
    
    
    ----------------------------------------------------------------------
    DISCUSS:
    ----------------------------------------------------------------------
    
    Please let me know if I've misunderstood the test execution protocol
    incorrectly:
    
    Section 6.  Per the paragraph “The evaluation of the test cases are intended to
    carry out in a controlled lab environment … It is important to take appropriate
    caution to avoid leaking non-responsive traffic from unproven congestion
    avoidance techniques onto the open Internet”, this is good guidance in general
    case.  However, in the case of this document how applicable is it?  Didn’t
    Section 3 (“We, therefore, recommend that a cellular network simulator is used
    for the test cases defined in this document …” and practically establish it
    can’t be done without simulation with the scenario of the underground mine) and
    Section 4 (“We recommend to carry out the test cases as defined in this
    document using a simulator, such as [NS-2] or [NS-3]).   If all the testing is
    supposed to be in a simulator how is it leaking out onto the internet?  As far
    as I can tell, this helpful text is common in RMCAT document, but in this case
    could it please be tailored for the proposed testing regime.
    
    Perhaps something on the order adding text on the order of “Given the
    difficulty of deterministic wireless testing, it is RECOMMENDED and expected
    that the tests described in this document would be done via simulation. 
    However, <in the case of not doing it that way> <leave the existing language>”

[authors] Thanks for the suggestion.  We have now revised the paragraph (now in Sec. 5)
to begin with: 

	Given the difficulty of deterministic wireless testing, it is
   	recommended and expected that the tests described in this document
	 would be done via simulations.  However, in the case where these test
   	cases are carried out in a testbed setting, the evaluation should
   	take place in a controlled lab environment.
    
   
    ----------------------------------------------------------------------
    COMMENT:
    ----------------------------------------------------------------------
    
    ** Section 3.1.  Per “In this test case, each of the user/UE in the media
    session is an RMCAT compliant endpoint”, what is a “RMCAT compliant endpoint”? 
    Could this be cited please.
   
[authors] We realize that the term RMCAT will no longer be relevant after all works of the 
WG are completed. We have therefore revised the sentence (now in Sec. 2.1 and 2.2) to:

	In this test case, each user/UE in the media session is an endpoint following RTP-based
   	congestion control.
 
    ** Section 3.1.  Per “At the beginning of the simulation, there should be
    enough time to warm-up the network”, intuitively the notion of “warm[ing]-up
    the network” makes sense.  However, is more precision required to side-by-side
    analysis of test runs of when the network is “warm enough”?

[authors] Good point. In the test case, the evaluation time is specified to be 30 seconds
after the start of the simulation. We've added the following as clarifications to the beginning
of both Sections 2.1 and 2.2 (previously 3.1 and 3.2):

	Typically, the evaluation period starts 30 seconds after test initialization.

    ** Section 4.  Per “Statistics collected from enterprise Wi-Fi networks show
    that the two dominant physical modes are 802.11n and 802.11ac, accounting for
    41% and 58% of connected devices”, it is would be valuable to cite this value
    and provide a timestamp.  This distribution will certainly change as this
    document ages.

[authors] These statistics are collected from our internal analytics dashboard
based from enterprise customer deployment. Unfortunately, we cannot provide
a public reference link to that data source. We have searched for alternative
sources of similar information (such as a white paper) but haven't yet found a
good substitute. If you are aware of any pointers that's very much welcome.


    
    ** Section 4.  Per “Unless otherwise mentioned, test cases in this section are
    described using the underlying PHY- and MAC-layer parameters based on the IEEE
    802.11n Standard.”, this focus on only 802.11n is surprising, since the next
    sentence establishes that 802.11.n is already less than half (41%) of the Wi-Fi
    traffic (and likely will continue to shrink).  Why not ac?

[authors] This draft was initially developed in 2015. At that time 11n was still the
dominant technology for endpoints and 11ac was not supported in ns-3.
We later updated the statistics on respective portions of 11n vs. 11ac clients in the draft.
On the other hand, since we haven't yet got the time/resource to update all ns3-based
test case implementations to be based on 11ac, our test case specifications are stuck
with the 11n mode.  Instead, we've added some text right after that sentence to encourage
practitioners to evaluate using up-to-date versions of Wi-Fi:

	As Wi-Fi standards evolve over time -- for instance, with the introduction of the
	emerging Wi-Fi 6 (based on IEEE 802.11ax) products -- the PHY- and MAC-layer
	test case specifications need to be updated accordingly to reflect such changes. 

    
    ** There appear to be some differences between the description of the Cellular
    (Section 3) and Wifi (Section 4) test. -- Section 4.1.2 and 4.2.2 are called
    “Test setup”, but Section 3.1.2 and 3.2.2. are called “Simulation setup”.  Was
    this intentional?

[authors] This is an artificat due to the merge of two separate drafts. Since
our validation efforts for cellular is in simulation only whereas for WiFi we've
implemented both simulation-based and testbed-based tests, we've updated the 
headings for Wi-Fi tests to be ' Test/simulation setup' instead. 


    
    -- Section 4.*.4 discusses the expected test behavior, but Section 3.* does
    not?  Was that explicit?
    
 [authors]. Again, this inconsistency in style is due to the draft merging. The draft originally
contained some inline texts on the expected behavior of cellular test cases.  Per your comment,
we have moved them out to be stand-along subsections (Sec. 2.1.3 and 2.2.3), which reads:

	The investigated congestion control algorithms should result in
   	maximum possible network utilization and stability in terms of rate
   	variations, lowest possible end to end frame latency, network latency
   	and Packet Loss Rate (PLR) at different cell load levels.