IETF Logo Mail Archive

Re: [tsvwg] per-flow scheduling

Kyle Rose <krose@krose.org> Wed, 19 June 2019 14:20 UTC

Return-Path: <krose@krose.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 618891204BF for <tsvwg@ietfa.amsl.com>; Wed, 19 Jun 2019 07:20:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=krose.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 sIiWfeILxsSS for <tsvwg@ietfa.amsl.com>; Wed, 19 Jun 2019 07:20:41 -0700 (PDT)
Received: from mail-yw1-xc2e.google.com (mail-yw1-xc2e.google.com [IPv6:2607:f8b0:4864:20::c2e]) (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 44FCD12051F for <tsvwg@ietf.org>; Wed, 19 Jun 2019 07:20:41 -0700 (PDT)
Received: by mail-yw1-xc2e.google.com with SMTP id k128so8363130ywf.2 for <tsvwg@ietf.org>; Wed, 19 Jun 2019 07:20:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=krose.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=jrraZmcYVwTr5HgBSAhZ/QgjnAiFLJZNqtG/aCbMRkQ=; b=QrMBKQlI1S9r93PpuTmnOIpX12Xt71ZU+nnpocx/s6PaU8++YA37r3s3qX8hMgJc4E mtTW7K+Nt98XxggCyWC8kq7QHVWhF9LpQHo9I0CXjnAedJceVLCyj3w5Ps0U4ovTle77 j7Pfcr/d/pQgIzNI8tZZeneSiTQKN637cUSfM=
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=jrraZmcYVwTr5HgBSAhZ/QgjnAiFLJZNqtG/aCbMRkQ=; b=ko/YRNs8b2NmtKlePoMwkobrUjkLnBWmaic/1nVIMfVccyf5mZTj+J5rIqbwWZmr6/ ABEutH+AiQbiR2oCm3jelgU4S/heHVEzURtv36+6o7X2sVxQ5H7MyDs1sJmF3y8RcVOH BYCGzhezd/fRpW7IF88aneeNbF/w1OYz+pVc6RTqGVp/gMbEVWiU+DOIT3D58Ys3XV6d qGdLtEtdsfVBRDIUzNgGXRLbf3q+1pNdSQRqaNmk2JrEeTjoixQ1oLvYIVre7syUjTyb 8hKRU2ey42sVfhoFM2MMF8+m9Fhhn7GoRdcsY+a8ktgDlGM+Z+TMbTeJ1j2TiriP6Q+b tNQg==
X-Gm-Message-State: APjAAAWx+XVQwPXzjuWCnPaF+XG/yFEJWpJ9TckX1kEyeaoVEtgdJxvW gHWgLpszeZOxHiKIZsgbBS1KJDotpSZaNVTrbiYeRRPVO7k=
X-Google-Smtp-Source: APXvYqyW4hQLZ1UsARObQmFPnvq4kCYhBYTfq9Ib37qZhqFJ3gShF4UHTOorRz2jur8aBX/s6SFTy3fpLpcF31eCdeI=
X-Received: by 2002:a81:4786:: with SMTP id u128mr69408265ywa.43.1560954040156; Wed, 19 Jun 2019 07:20:40 -0700 (PDT)
MIME-Version: 1.0
References: <350f8dd5-65d4-d2f3-4d65-784c0379f58c@bobbriscoe.net>
In-Reply-To: <350f8dd5-65d4-d2f3-4d65-784c0379f58c@bobbriscoe.net>
From: Kyle Rose <krose@krose.org>
Date: Wed, 19 Jun 2019 10:20:29 -0400
Message-ID: <CAJU8_nUmQgbRcpKchjLN_N+QhLtiPmTZDP6c-D1K899SsAtQLQ@mail.gmail.com>
To: Bob Briscoe <ietf@bobbriscoe.net>
Cc: "Holland, Jake" <jholland@akamai.com>, "ecn-sane@lists.bufferbloat.net" <ecn-sane@lists.bufferbloat.net>, tsvwg IETF list <tsvwg@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000131831058badefe1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/iONSCE3CBo7Z45V7b9VVRhQO2lc>
Subject: Re: [tsvwg] per-flow scheduling
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: Wed, 19 Jun 2019 14:20:43 -0000

On Wed, Jun 19, 2019 at 10:13 AM Bob Briscoe <ietf@bobbriscoe.net> wrote:

> Jake, all,
>
> You may not be aware of my long history of concern about how per-flow
> scheduling within endpoints and networks will limit the Internet in
> future. I find per-flow scheduling a violation of the e2e principle in
> such a profound way - the dynamic choice of the spacing between packets
> - that most people don't even associate it with the e2e principle.
>
> I detected that you were talking about FQ in a way that might have
> assumed my concern with it was just about implementation complexity. If
> you (or anyone watching) is not aware of the architectural concerns with
> per-flow scheduling, I can enumerate them.
>

I would certainly be interested in reading more about these concerns. Even
a reference that I can read out-of-band would be fine. Thanks, Bob.

Kyle

v2.23.0 | Report a Bug | By Email