Re: [rmcat] Genart last call review of draft-ietf-rmcat-wireless-tests-08

"Xiaoqing Zhu (xiaoqzhu)" <xiaoqzhu@cisco.com> Thu, 27 February 2020 17:37 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 A2C213A0DC0; Thu, 27 Feb 2020 09:37:00 -0800 (PST)
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=Jb7PWyXW; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=ulU+stZO
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 8VKPXuRO9eEi; Thu, 27 Feb 2020 09:36:57 -0800 (PST)
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 72D0B3A0DBD; Thu, 27 Feb 2020 09:36:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12390; q=dns/txt; s=iport; t=1582825017; x=1584034617; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=x7sVdIqRbzR7Wk36mASCudiqgQabydaW1Z3WUKfUEJw=; b=Jb7PWyXWiPrVhqz4OmO/y75SdbHF/mPlhO9BvzTTsimQkYwLUU39uXkZ wiKr2Z4JkJ6SlRgCCPDFp/4C8Du4adOab+XQMkaXUtZtf10TB6/L5yMKl h9W3he+3Vv1pWi2ApPDXDFCWpWJiAqDsYk33wHLiJiDxngc1YEtbqlWtm U=;
IronPort-PHdr: =?us-ascii?q?9a23=3AOktKlBNPXVTrDs3WI88l6mtXPHoupqn0MwgJ65?= =?us-ascii?q?Eul7NJdOG58o//OFDEu6w/l0fHCIPc7f8My/HbtaztQyQh2d6AqzhDFf4ETB?= =?us-ascii?q?oZkYMTlg0kDtSCDBjrLfftdj46AexJVURu+DewNk0GUMs=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CqBQCw/Vde/5hdJa1mHAEBAQEBBwE?= =?us-ascii?q?BEQEEBAEBgXuBVCQsBWxYIAQLKoQUg0YDimeCOiWBAZcTgUKBEANUCQEBAQw?= =?us-ascii?q?BARgLCgIEAQGEQAIXgXEkOBMCAw0BAQUBAQECAQUEbYU3DIVkAgEDAQEQERE?= =?us-ascii?q?MAQEsCwEPAgEGAg4GBgImAgICJQsVEAIEAQ0FIoMEAYJKAy4BDpQYkGcCgTm?= =?us-ascii?q?IYnWBMoJ/AQEFhQcYggwDBoEOKowlGoFBP4ERJwwUgU5JNT6CZAEBgScVKYM?= =?us-ascii?q?RMoIsjUxRgkifNQqCPIdRimKEMhyCSYgbjmOBZ45wgU2HL5JLAgQCBAUCDgE?= =?us-ascii?q?BBYFpIoFYcBU7KgGCQVAYDY4dDBeDUIUUhUF0gSmLR4JDAQE?=
X-IronPort-AV: E=Sophos;i="5.70,492,1574121600"; d="scan'208";a="446304370"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 27 Feb 2020 17:36:56 +0000
Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by rcdn-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id 01RHasUA006690 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 27 Feb 2020 17:36:54 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 27 Feb 2020 11:36:51 -0600
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 27 Feb 2020 12:36:48 -0500
Received: from NAM12-BN8-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 27 Feb 2020 12:36:47 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=MGygDyZ4CmagXosCxOMv1umh3G9Tyws8H6yVe8e7EgLqocuA6MWv5t8kcItWXsMmBv7ffNQGYSLzKddM7ZZIyL1mzpihOykfuuoRTzI5kZJlugDUMgoyDPLuMrbDvtTAlzK35ohjFqXpbvhHuUjUQAT/PoQzzKMFRepufFQCOixnPWCOLChjt90n3svJp2n33cOy0SrnNvLZkmSy1JY/+exNJMXUsmOVKzEdZk2mHFkCbGSrH+/g0vUOrOaM7cCynO9oaPv2aCQzn9W2EbR/P624s1U2MTo3tVioJqWYWTuSCXtDr0HDjC92wu2tKByt4zXqL8Xv8yMQwdLHmKuIgQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=x7sVdIqRbzR7Wk36mASCudiqgQabydaW1Z3WUKfUEJw=; b=PtyG4kHBhHcmI5MXdcpz9/or90ckivs28m3IU6oFpe5ARjaTmonXwvLbUgif7w+XVBCejdYkjwKbT+jHJZGNE69nv2PqgYZiYZH6tKK2N3KpOhjRm2Y79hELkTBgAU43GYPBh4ogqGRb43QLNzTHIxNp2olOZ9TsCA9XBChN/Ji6XaWUYiM04ZqSIK9JKUaeWI7URuPJqv1fNlI9W+WqpCP0QolFnQPf9NwtiPmTM2wJppATkSLi8mCv3znfKDDjtklLg4YAa7BsZVr61tNkWcoRmbZPqohvSBlOmgwQ2se5EBACDTH7Eik+WgP+ERjNnHQzebW9xLzOeO8FPNoiSA==
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; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=x7sVdIqRbzR7Wk36mASCudiqgQabydaW1Z3WUKfUEJw=; b=ulU+stZOnqfumB8NhtMqol1AEQpJM3grPFEFv9kqVAr5aYjyAkvtzTXeAagYzUyLekdteFoiZyMi31ver5UAzgGoW3lrP1BBTGkD4LsTA4bhjRb3MjyDiBWP2JkETWeDtaAhXyMFg0uq/cl4sXVExuKgmftLoh5fWSStaUO3ESM=
Received: from SN6PR11MB3166.namprd11.prod.outlook.com (2603:10b6:805:c5::17) by SN6PR11MB2590.namprd11.prod.outlook.com (2603:10b6:805:54::29) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2750.22; Thu, 27 Feb 2020 17:36:47 +0000
Received: from SN6PR11MB3166.namprd11.prod.outlook.com ([fe80::450f:d0ec:d45c:fa20]) by SN6PR11MB3166.namprd11.prod.outlook.com ([fe80::450f:d0ec:d45c:fa20%7]) with mapi id 15.20.2772.012; Thu, 27 Feb 2020 17:36:47 +0000
From: "Xiaoqing Zhu (xiaoqzhu)" <xiaoqzhu@cisco.com>
To: Gyan Mishra <hayabusagsm@gmail.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "last-call@ietf.org" <last-call@ietf.org>, "draft-ietf-rmcat-wireless-tests.all@ietf.org" <draft-ietf-rmcat-wireless-tests.all@ietf.org>, "rmcat@ietf.org" <rmcat@ietf.org>
Thread-Topic: Genart last call review of draft-ietf-rmcat-wireless-tests-08
Thread-Index: AQHV0LTyNmbuQvhAAk2l3lvzd3IfUqgvAW+A
Date: Thu, 27 Feb 2020 17:36:46 +0000
Message-ID: <D86FE41A-2260-47C3-97F9-B72ACC1C5886@cisco.com>
References: <157965034086.28971.6105777873164080956@ietfa.amsl.com>
In-Reply-To: <157965034086.28971.6105777873164080956@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.22.0.200209
authentication-results: spf=none (sender IP is ) smtp.mailfrom=xiaoqzhu@cisco.com;
x-originating-ip: [2001:420:30a:4e01:6008:3de4:5275:5a4c]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 1a5385ed-9d67-4c8d-2e27-08d7bbab9eb0
x-ms-traffictypediagnostic: SN6PR11MB2590:
x-microsoft-antispam-prvs: <SN6PR11MB2590EFD2A077D403735B1107C9EB0@SN6PR11MB2590.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 03264AEA72
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(366004)(346002)(136003)(376002)(396003)(39860400002)(189003)(199004)(64756008)(8936002)(91956017)(66556008)(66446008)(76116006)(66476007)(71200400001)(5660300002)(66946007)(36756003)(966005)(186003)(6512007)(66574012)(478600001)(81156014)(81166006)(4326008)(2906002)(86362001)(316002)(6506007)(6486002)(8676002)(33656002)(110136005)(54906003)(2616005); DIR:OUT; SFP:1101; SCL:1; SRVR:SN6PR11MB2590; H:SN6PR11MB3166.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; 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: 5DzHH1yTZmc+n22egl+BmmnXWU3sXBPErKRY3nJvyNfiv3D8yozMzlUo9eUnzAJ59ZDPR9BhpxQuDf5LNAKJxzj0HKl2PenttKZrEbJmZK6wNftfmt4prmYiTNZFRjYukKPkGCPPvNy6LNxAPwrk+7nk/3Laih6OIEzU7g61lCxN1N3xdMxEiSiWuNoLWe+xK6GE0YIVxXvvekVnNN4EeEJLYXzf638T0ypxMa+xSU6Jubebwf1EWYcUIS9YN145HQ3dr6osBLWaWBzE7UUevQmtJBHglpW33WFjHQS2b9LtN+oBuPVnw085E0x9vxgHM5pp0qs4ILqojJ5qVHgpy2nh88zSDN/zWdcK6loy/YTmtHyBvdSltzJgAmdZKlFjvycYGKufOPz12Iw6fjoMU+xkMfXdGN/fODsjnPCaMoNDXiiMtOyz0VdJxsYQ4aVZtBqiprcpmbXmi7YW4JqmIc/gNincFSSDoR16dIWcViAEA1Ny7hofgVpbF3nyw8hXZYLUGejiSP+yrfpqDuVKDQ==
x-ms-exchange-antispam-messagedata: ++DMcM4GcPGvBqHGL5hh/zhYwqPeAAtndg6m1vHwQ+lCxCd6uDHAEKN3efKrmrzHB2Zp8fSPAbgUaU0yzUXYX+irH1bP5baWaIxQnEXPhlqEnQxXhv96Ffbr+QAw8CwmEKZWlR3+BAPq8Qrz9FcRNnOUrghj8xdGTyO+N4Z3/UdoGHbBwN6EnrEl/Trx9PsA21UZCJHHTSQ7MhROzN7yEQ==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <4E3CE6BFF921484DA4AE6964371283E0@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 1a5385ed-9d67-4c8d-2e27-08d7bbab9eb0
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Feb 2020 17:36:46.9694 (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: lKlbRuXbHPR+PaFb0JSObnqeWAeRmA6WjHDkje+mLehmFVJ0RUZKyDB86iGNOSUuxkMZi+NnGgp7kz7TiP4p4g==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN6PR11MB2590
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.15, xch-aln-005.cisco.com
X-Outbound-Node: rcdn-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/KQwBnakWsBpTsPgBCjpOU5HJY94>
Subject: Re: [rmcat] Genart last call review of draft-ietf-rmcat-wireless-tests-08
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: Thu, 27 Feb 2020 17:37:01 -0000

Hi Gyan, 

Thanks a lot for your very thorough review of this draft, and for your valuable comments. We have uploaded the revised version (-09) to address some of the concerns and suggestions you've raised. 

Please also see our replies below inline, tagged [authors].  Let us know if you have any further thoughts or comments __ 

Best Regards,
Xiaoqing, on behalf of all authors.


On 1/21/20, 3:46 PM, "Gyan Mishra via Datatracker" <noreply@ietf.org> wrote:

    Reviewer: Gyan Mishra
    Review result: Ready with Issues
    
    I am the assigned Gen-ART reviewer for this draft. The General Area
    Review Team (Gen-ART) reviews all IETF documents being processed
    by the IESG for the IETF Chair.  Please treat these comments just
    like any other last call comments.
    
    For more information, please see the FAQ at
    
    <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
    
    Reviewer: Gyan Mishra
    Review result: Ready with Minor Issues
    
    Document: draft-ietf-rmcat-wireless-tests-08
    Reviewer: Gyan Mishra
    Review Date: 2020-01-17
    IETF LC End Date: 2020-01-21
    IESG Telechat date: Not scheduled for a telechat
    
    Summary: Ready, but with nits and minor issues that should be addressed.
    
    Major issues: None
    
    Minor issues:  This document describes test cases for evaluating performance of
    RTP congestion control algorithms over LTE & WIFI networks.
    
    Section 1 It is mentioned a number of instance where “wired” is mentioned where
    I believe “wireless” or “WIFI” is what is meant to be stated.  Please check.
    
[authors] Thanks for raising this concern. We’ve doubled checked on the usage of “wired” in all three instances in the introduction section, and believe it is intended as such.  Our intention was to contrast the characteristics of wireless networks from those of wired networks, as a motivation of the need for this draft.   We have, however, taken the opportunity to revise those sentences to make them less wordy.

    I would recommend  to use WIFI to refer to local LAN WIFI and use cellular to
    refer to a mobile handset, and not use the term “wireless” as that could be
    confusing.
  
[authors] We agree with the suggestion that it is preferable to refer specifically to WiFi or cellular whenever possible and have mostly edited out the word “wireless”. In a few places, however, it is rather cumbersome to always say “cellular and WiFi networks” when our intention is to simply contrast the difference between wireless and wired communication. We have therefore stuck with the term “wireless” in those cases.

    I would recommend not using LTE to refer to Cellular from a general mobile
    handset point of view, since LTE refers to 4G and Cellular could be any -
    2G,3G,4G,5G etc

[authors]  We agree with this proposed change. The text has been updated accordingly with a few exceptions: a) mentioning LTE/5G as an example of operational cellular network; b) pointing to the LTE simulator in NS-3; and c) referencing the corresponding 3GPP standard documents.
    
    Section 3 This section also mentioned “wired” where I think the goal of the
    document is test cases of WIFI & Cellular and adding in wired does confuse the
    reader as we are talking about quality degradation issues with wireless
    technologies - WIFI & Cellular.  Please check the verbiage.

[authors] Thanks for pointing this out. We have checked all three previous usage of the word in this section and have eliminated the mention of it in the introductory discussions. The remaining two uses, however, are needed for describing the proposed test case topology so we left them as is.
    
    Section 3 In this sentence you mention 3G support of high bandwidth.  My
    experience with 3G has not been very slow page loading and that multimedia
    would suffer.

[authors] This is a fair complaint. To avoid controversy, we have revised the sentence to now state: “… it is evident that only the more recent radio technologies can support the high bandwidth requirements  …”

    
    Section 3 Bottom of page 5 it is mentioned that the combination of multiple
    access technologies such as one user has LTE connection and another has Wi-Fi
    connection is kept out of the scope of this document.  Please explain why as
    the reader would believe it would be in scope as that is the main topic.
    
[authors]  When some of the users are on LTE and some of the users are on Wi-Fi, it is only interesting to investigate the test case when the bottleneck of the system is on the wired hop.  Whereas the main focus of this draft is to evaluate how congestion control schemes interactive over the wireless interface. We have added the following statement in the draft to explain why it is out of scope:

	“It should be noted that the goal of the following test cases is to evaluate the performance
	of candidate algorithms over the radio interface of the cellular network. Hence it is assumed
	that the radio interface is the bottleneck link between the communicating peers and that the core
	network does not introduce any extra congestion along the path. Consequently, this draft has kept
	as out of scope the combination of multiple access technologies involving both cellular and Wi-Fi users.”

    Section 3 Top of page 6 - I am wondering if there is a better explanation of
    why you need a test simulator due to unpredictable nature or cellular other
    than underground mines.

[authors]  The unpredictable nature of the cellular networks makes test results unrepeatable. Therefore our recommendation of carrying out tests using simulators.
    
    Section 3.1.1 Here the fixed user is on a wired LAN connected to mobile user. 
    You mention wireless interface which makes me wonder is the fixed user actually
    a WIFI user connected to broadband WIFI router wired to the internet. See in
    quotes which makes me wonder "The fixed user is connected to the Internet via
    wired connection with sufficiently high bandwidth, for instance, 10 Gbps, so
    that the system is resource limited on the {wireless?} interface"


[authors]  Thanks for raising this point of confusion. The proposed test case comprise of both cellular users and fixed users. They share the wired backhaul link with sufficiently high bandwidth.  As such, the bottleneck of the system is over the cellular radio access link.  We have revised the sentence as below to avoid further confusion:

“… so that the system bottleneck is on the cellular radio access interface … “

    
    Section 4.1 Please explain in why the home access link represents a bottleneck
    due to its bandwidth. It is not obvious as these days Gigabit and above
    broadband speeds are available at home.
    

[authors] We agree that the scenario where the wired hop remains the bottleneck is becoming less common. This subsection describes test cases to reflect DSL-like home Internet access that's less common but still present especially in other parts of the world.   As acknowledged in this section, these test cases are proposed mainly as a sanity check. Over time, we can perhaps get rid of this section completely.

    Nits/editorial comments:
    
    Draft Date should to be updated.

[authors] Done
    
    Section 3.1.2  1-B Antenna- [2D, 3D] should be defined

[authors]  The cited reference of the 3GPP test plan contains information for the above terminology.  For this round of revision we have not gathered input from authors familiar with the cellular technology terminologies. We will try to update the definition directly in the text in a later revision. 

    Section 3.1.2 RTT [40, 150] , should define a unit millisecond

[authors] Done.
    Section 3.1.2 4. User Intensity, should define what the values in brackets mean
    and unit of measure.

[authors]  The cited reference of the 3GPP test plan contains information for the above terminology.  For this round of revision we have not gathered input from authors familiar with the cellular technology terminologies. We will try to update the definition directly in the text in a later revision.

 Section 3.1.2 7.2.a Media direction: Uplink and Downlink,   should define what is meant by Uplink and Downlink 

[authors] The definition has been provided in the second paragraph of Section 3.1.1 as well as in the illustration in Fig. 1.

Section 4.2.3 g N= [4, 8,  12, 16, 20], should define what N is and any unit of measure

[authors] The variables N and M indicate the number of real-time media flows and competing TCP streams, respectively, as illustrated in Fig. 2. We added a sentence in Sec. 4.1.1 to explicitly explain this
    
    _______________________________________________

    Gen-art mailing list
    Gen-art@ietf.org
    https://www.ietf.org/mailman/listinfo/gen-art