Re: [tsvwg] Requesting TSVWG adoption of SCE draft-morton-tsvwg-sce

Luca Muscariello <muscariello@ieee.org> Mon, 18 November 2019 08:37 UTC

Return-Path: <muscariello@ieee.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F25C12092E for <tsvwg@ietfa.amsl.com>; Mon, 18 Nov 2019 00:37:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ieee.org
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 LxB_xswieXBu for <tsvwg@ietfa.amsl.com>; Mon, 18 Nov 2019 00:37:15 -0800 (PST)
Received: from mail-wm1-x336.google.com (mail-wm1-x336.google.com [IPv6:2a00:1450:4864:20::336]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46E14120926 for <tsvwg@ietf.org>; Mon, 18 Nov 2019 00:37:15 -0800 (PST)
Received: by mail-wm1-x336.google.com with SMTP id t26so17720878wmi.4 for <tsvwg@ietf.org>; Mon, 18 Nov 2019 00:37:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ieee.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=VO+uzqRiVvwxcKeL3t7Sqs/2zIqK5cBHwnGho+7Rzsw=; b=C6z8PniIX1IN/hrrY4UhIH0Ix+pj8tLcbYAhuwacs6jvU1A8yBWCKHRTWsMbNIWwfU EPysouRMPvixMZs0c6a3089GQFOS6Rvd6Lx5p8ewsXNnEPZr8w8iY48Q9ZMm/D/iH9jn JHyx/YduIbUCY6Q3FF21vhMzGhDhUm3zR7pHg=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=VO+uzqRiVvwxcKeL3t7Sqs/2zIqK5cBHwnGho+7Rzsw=; b=Y3Yk4Gt/3rWRkr+DTeUHTIlPl+Mw8vbd03olaJ74wfugB/GOTUzcv8CBAgzgOA1K0b 2vWYDp1yb1KOjqbxAN9jr6DByywGD9gux4xDtzNjwO7ecqKcvL/4BXuXeXNtctuo2DVT cf/cUh79Cma05tKO25o8JqBpsPGkc1P3on9tQZwPn4yiHDe6yR9BH5S2krz/TotRhkgc LKUXFoHx38wPdbomKGuZU+4NSvDw0M46lk1YCREY/TijSAKLoCADCOV/XKzZrha1Xqaf J+HOFPIJsLtEWteDFQauqvwPLRyLinPkJ+Nq9zQjC/UtwHnB1k1eTiJoAMvzD/FILzkl 49Ag==
X-Gm-Message-State: APjAAAUCr4PYQLGFveWKUhzYlT1T5jFNQjA/6rKtg7MjA3FpdkQeQEN8 FgM6dT9zXDtUWPXoRhbcgGqvUxCR+L5QPwhrLBQnnUq2gv/EKg==
X-Google-Smtp-Source: APXvYqzYxUaobL8bQzXY1kbiTGFAa4ozGidd0Z/PXiYM70XONrLqxfZUVncqGlkMmMEOftynFkGEYGPo8k7ZnMsRSo0=
X-Received: by 2002:a05:600c:22c3:: with SMTP id 3mr26651543wmg.139.1574066233680; Mon, 18 Nov 2019 00:37:13 -0800 (PST)
MIME-Version: 1.0
References: <201911141350.xAEDo99J048928@gndrsh.dnsmgr.net>
In-Reply-To: <201911141350.xAEDo99J048928@gndrsh.dnsmgr.net>
From: Luca Muscariello <muscariello@ieee.org>
Date: Mon, 18 Nov 2019 09:37:02 +0100
Message-ID: <CAH8sseRYcY3QAWe95OxjbhWfE+KL0qDdeA664zFZKdFNnCKc8g@mail.gmail.com>
To: "Rodney W. Grimes" <4bone@gndrsh.dnsmgr.net>
Cc: tsvwg IETF list <tsvwg@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b65a2c05979ada35"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/gdDSWX4Ujek105U_x3Cyevt5Q44>
Subject: Re: [tsvwg] Requesting TSVWG adoption of SCE draft-morton-tsvwg-sce
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
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, 18 Nov 2019 08:37:23 -0000

Hi,

I've followed the different discussions on the list on this topic and, IMHO,
it would be highly desirable to let the SCE proposal move forward in the WG.

The effects of the coexistence of different classes of applications in the
same traffic mix
seem not explored very well so far, and answers based on DSCP or coupled
queueing systems
with non predictable performance raised even more questions and worries.

Traffic isolation is an important topic in this whole discussion and I
noticed
different proposals have been recently proposed with announced running code
for testing such
as

https://tools.ietf.org/html/draft-morton-tsvwg-cheap-nasty-queueing-01

It would make sense to know more about the different solutions in terms of
isolation
and see if they can provide predictable performance and at which
implementation
and operational cost.
Nonetheless, it would be important to also know what happens when isolation
is not in place.

IMHO, It would be difficult to understand why the WG would refuse fresh
energies
coming from people willing to do actual work on the topic.

I'm not doing any work on SCE but I'd be ready to spend some time to review
results and documents,
if that helps.

Regards
Luca
:wq


On Thu, Nov 14, 2019 at 2:50 PM Rodney W. Grimes <4bone@gndrsh.dnsmgr.net>
wrote:

> Hello tsvwg list members,
>
> It is our intent to ask for adoption by the TSVWG of
> draft-morton-tsvwg-sce (
> https://tools.ietf.org/html/draft-morton-tsvwg-sce-01) during the
> IETF/106 Singapore TSVWG session.
>
>
> The TSVWG chairs have provided the following guidelines for this adoption
> request:
>
> (1) The WG chairs want to see interest in SCE technology beyond the draft
> authors in order to adopt the SCE draft.   This will include surveying the
> room in Singapore (e.g., who has read this
>  draft?).
>
> (2) Coexistence of the L4S and SCE experiments is a concern that will need
> to be addressed by the WG if the SCE draft is adopted, and hence is in
> scope for discussion of this adoption request
> ..  In particular, absence of a coexistence plan (e.g., to deal with the
> different uses of the ECT(1) codepoint by L4S and SCE) is not an automatic
> barrier to WG adoption of the SCE draft.
>
> (3) The TCPM WG chairs have indicated TCPM WG willingness to consider
> complementary TCP work needed to complete SCE functionality.  In
> particular, draft-grimes-tcpm-tcpsce is likely to be inc
> luded in the TCPM Singapore agenda for Friday morning.
>
>
> Regards,
> --
> Rod Grimes
> rgrimes@freebsd.org
>
>