[tsvwg] David Black's Review of draft-finzi-priority-switching-scheduler

"Black, David" <David.Black@dell.com> Mon, 07 May 2018 19:53 UTC

Return-Path: <David.Black@dell.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 6E79E12783A for <tsvwg@ietfa.amsl.com>; Mon, 7 May 2018 12:53:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.71
X-Spam-Status: No, score=-2.71 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dell.com header.b=Yd3IYOJN; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=emc.com header.b=rkABAqhX
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id p8VvSjVBZSau for <tsvwg@ietfa.amsl.com>; Mon, 7 May 2018 12:53:40 -0700 (PDT)
Received: from esa6.dell-outbound.iphmx.com (esa6.dell-outbound.iphmx.com []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D1479124C27 for <tsvwg@ietf.org>; Mon, 7 May 2018 12:53:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dell.com; i=@dell.com; q=dns/txt; s=smtpout; t=1525722819; x=1557258819; h=from:to:subject:date:message-id:mime-version; bh=mqQg8T3Aw3l4yiXCV4Ri7EmaAck/XQllJZKqY+iOAjo=; b=Yd3IYOJNylZ6tNbozLhfw0kWCg7OBKnmhSMo7+f0WTetVu29ZMjDzNLX DT+IKY62cVqVp4ikHY83+3KqiQp2Di24t4/HNTddAUG8dd3t7NASsZvrm 9TW0hihdAkOFR5Hsclp63HDzJIYA0aicvA7JFNhZMszCNpYFlFxN/ZqQr 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2HFAABIrfBamGOa6ERaAx+CXyIqfg4XY?= =?us-ascii?q?ygKmFuDCJMmgT07CycHhD4CglQhNBgBAgEBAQEBAQIBAQIQAQEBAQEICwsGKCM?= =?us-ascii?q?BC4I1IhFLIQgzAQEBAQEBAQEBAQEBAQEBAQEBFwJDARIBRwYTHxsRARoQHTkUA?= =?us-ascii?q?w8BBAoJCBOEImQBDqlnM4J2hVCCQAMFiCWBVT6DG4NuIgEBAwGBOSUfDBqCaYI?= =?us-ascii?q?khziQdAMFAoVjglKHS4Ngh02JRoZfAgQCBAUCFIElHIILcIMTgi6BAwEHCAeBL?= =?us-ascii?q?YEHhRSFPm8wjnyBGAEB?=
Received: from esa6.dell-outbound2.iphmx.com ([]) by esa6.dell-outbound.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 May 2018 14:53:37 -0500
From: "Black, David" <David.Black@dell.com>
Received: from mailuogwhop.emc.com ([]) by esa6.dell-outbound2.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 May 2018 01:53:36 +0600
Received: from maildlpprd06.lss.emc.com (maildlpprd06.lss.emc.com []) by mailuogwprd01.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id w47JrZtx029005 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <tsvwg@ietf.org>; Mon, 7 May 2018 15:53:36 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com w47JrZtx029005
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1525722816; bh=dhmSL7PXm3CsdX91BRlTP9d/0bg=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=rkABAqhXtWzcyhfJtv31o4OEDwXETZfYIaH36zcfnPhjsg9rJXwKgMkgy5B+OXEnF bonFxi0EbcSwFSY+uGZtcJ4YiUXnIu/CNXs1Gys4ZFTnRyKNPvgO/I1OdyAb+bY57B EZlN9LSNLy8r5Hy/K7WH0Ed8V2+t3qa/2R18KkXg=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com w47JrZtx029005
Received: from mailusrhubprd04.lss.emc.com (mailusrhubprd04.lss.emc.com []) by maildlpprd06.lss.emc.com (RSA Interceptor) for <tsvwg@ietf.org>; Mon, 7 May 2018 15:53:20 -0400
Received: from MXHUB305.corp.emc.com (MXHUB305.corp.emc.com []) by mailusrhubprd04.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id w47JrLVa000419 (version=TLSv1.2 cipher=AES128-SHA256 bits=128 verify=FAIL) for <tsvwg@ietf.org>; Mon, 7 May 2018 15:53:21 -0400
Received: from MX307CL04.corp.emc.com ([fe80::849f:5da2:11b:4385]) by MXHUB305.corp.emc.com ([]) with mapi id 14.03.0382.000; Mon, 7 May 2018 15:53:20 -0400
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: David Black's Review of draft-finzi-priority-switching-scheduler
Thread-Index: AdPmN8RfNwWa7gzLR+mcdFJjPmJ5DQ==
Date: Mon, 7 May 2018 19:53:20 +0000
Message-ID: <CE03DB3D7B45C245BCA0D243277949363010D3D6@MX307CL04.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_CE03DB3D7B45C245BCA0D243277949363010D3D6MX307CL04corpem_"
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd04.lss.emc.com
X-RSA-Classifications: public, GIS Solicitation
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/XOmOa2ecJ8uJDK3__VsK1b0Suvw>
Subject: [tsvwg] David Black's Review of draft-finzi-priority-switching-scheduler
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 May 2018 19:53:42 -0000

I write as an individual, not as WG co-chair.  I appreciate the effort that the authors have made to bring this draft to the IETF.

Draft status page:
Slides from London tsvwg meeting (March 2018):

I like the slides much more than I like the draft.   My initial thought on reading the draft was to suggest switching the order of Sections 2 and 3 so that discussion of the problem in Diffserv context (important for IETF) would precede explanation of the solution.  After looking at the slides, I realized that what's really wanted is a shorter up-front summary of how this scheduling technique can benefit a Diffserv router implementation, as slide 3 concisely explains.  Sections 2 and 3 should then be fine in their current order if an analogous (to slide 3) explanation of how this scheduler benefits a Diffserv router implementation is added to Section 1, perhaps to follow the current Section 1.1.

As this draft is not intended to be standards track, I strongly suggest that the authors submit a PDF version in addition to the text version, as the PDF diagrams should be much more comprehensible by comparison to ASCII graphics, and it should be possible to include more detailed graphs.

The implementation pseudo-code and discussion in Section 2.2 might be better moved to an Appendix.

Are there any results from simulated or actual traffic?

Section 3.2's pointer to the Globecom paper for the results of the scheduler scenario described in Section 3.1 is unsatisfying - please include content analogous to slide 14.

Obviously, Section 4 (Security Considerations) needs to be written ;-).  At a minimum, I suggest comparing this scheduler to others that it might replace on opportunities for theft or denial of service - e.g., is one of the schedulers more prone to starvation of a class of traffic than another?

Finally, this text on p.7 bothered me:

   the Assured Forwarding

   (AF) class deals with elastic traffic as defined in [RFC4594<https://tools.ietf.org/html/rfc4594>] (data

   transfer, updating process, ...) while all other remaining traffic is

   classified inside the default (DE) best-effort class.

I traced my concern back to this text in Section 1.5 of RFC 4594 ...

   While Differentiated Services is a general architecture that may be

   used to implement a variety of services, three fundamental forwarding

   behaviors have been defined and characterized for general use.  These

   are basic Default Forwarding (DF) behavior for elastic traffic, the

   Assured Forwarding (AF) behavior, and the Expedited Forwarding (EF)

   behavior for real-time (inelastic) traffic.

In other words, a lot of the best-effort traffic is elastic, so it's not correct to imply that all elastic traffic would use AF.   For AF, I'd suggest instead picking a relevant service class or two from RFC 4594, perhaps High-Throughput Data or Low-Latency Data.  Also, "(DE)" -> "(DF)".

I think another version of this draft would be a good idea.

Thanks, --David
David L. Black, Distinguished Engineer
Dell EMC, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953    Mobile: +1 (978) 394-7754