From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm1-x32e.google.com (mail-wm1-x32e.google.com [IPv6:2a00:1450:4864:20::32e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 42F783B29E for ; Sat, 27 Jul 2019 15:42:25 -0400 (EDT) Received: by mail-wm1-x32e.google.com with SMTP id v15so50590523wml.0 for ; Sat, 27 Jul 2019 12:42:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=kJWMXxR4ZhrFXGE0yE40CmzVb/3YbseUq3j7wnyHT4M=; b=A+5rSJNm8KdpqkXop0CJgt51+q0klWT7MmhwzOImDygk/cOVZd00CUenax5/vUPabd tQJEKjvwXgirDXLLHGt51s+kOY1rZRre8kik9VdsDEDGzj3ZOrfV7dH1TOPBI7re7x35 hq/+USrdln35voz8zGJTjTXVEumxbA9YYxeGFSvVq7FnvaOq1QTjv1mYTZBKCFLEUw4j pJaT6QYgAAJSAtP3qHfs4lP3zLr+Hzuc7DGn6Gp91ilyYjIzYVi3Jw59dz1d4BQgA4Ca Qyen/HYxEsixBuVN0rnXvqFm1fANz/ChebNplfJcCXBMAROxAJ71fbJEYOIR+ICr1T3i seYw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=kJWMXxR4ZhrFXGE0yE40CmzVb/3YbseUq3j7wnyHT4M=; b=XwhMI20ZF4S7ZrNxRU+Z6Kcs5GlwgQ87tXrecEYXWyryCgJ9ilB+RRp8+QnDF4IcfB mDPgn47RYbOnWFj+KAFVn6IuKY25VDrQPQcEZ2LgrQkRYVKX1A67wAY4uElYTEt4Iru/ rXDND2BsF6YJRvmy3gCjHndLaJPOcZclK1ox+x/2i3vsl9Ao3bv2sVwKufUstGl6tMT7 w19RjeN2lwY+eRCu0xI97tYWSjIt1BfNUh7vSbIASPYn7fuknaxb6GFhA9WssxsDJk1y TvYgqh8bxEMuBkJU3wSakIcpzF+ZUJo0coRoWae0kKuaFw1y19Ly9DfPdQ0V5K2dfXhX fVvw== X-Gm-Message-State: APjAAAU5ErE2AvWdHvTtdWSzxBpnZCNUZ9kg9NW2NAw1RNQqL0kR80FX vwvZPV1fyyf3P4jY/qx5580ehsQ10IGoDHzHcm0= X-Google-Smtp-Source: APXvYqxdS9u0YqTG5EgV5PwBfetALs5+Ek7A/rx1bHKtvZ3fEmZIaSDfjzZVeoK0ImDjUxiEBTBfJ6zxOt8pstRTh7E= X-Received: by 2002:a1c:988a:: with SMTP id a132mr88833180wme.165.1564256544411; Sat, 27 Jul 2019 12:42:24 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a1c:9e09:0:0:0:0:0 with HTTP; Sat, 27 Jul 2019 12:42:22 -0700 (PDT) Received: by 2002:a1c:9e09:0:0:0:0:0 with HTTP; Sat, 27 Jul 2019 12:42:22 -0700 (PDT) In-Reply-To: References: <350f8dd5-65d4-d2f3-4d65-784c0379f58c@bobbriscoe.net> <40605F1F-A6F5-4402-9944-238F92926EA6@gmx.de> <1563401917.00951412@apps.rackspace.com> <4833615D-4D68-4C95-A35D-BCF9702CEF69@akamai.com> From: Jonathan Morton Date: Sat, 27 Jul 2019 22:42:22 +0300 Message-ID: To: Kyle Rose Cc: "Holland, Jake" , tsvwg IETF list , Bob Briscoe , "ecn-sane@lists.bufferbloat.net" Content-Type: multipart/alternative; boundary="000000000000aad693058eaedb74" Subject: Re: [Ecn-sane] [tsvwg] per-flow scheduling X-BeenThere: ecn-sane@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion of explicit congestion notification's impact on the Internet List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jul 2019 19:42:25 -0000 --000000000000aad693058eaedb74 Content-Type: text/plain; charset="UTF-8" RFC compliant traffic finding its way into the L4S queue is one thing - it obviously results in a performance degradation to one or the other, depending on other factors - but I'm more concerned about L4S traffic entering the classic queue, which would have a severe impact on general traffic throughout. By default this always occurs when a single queue AQM that is not L4S aware is encountered. --000000000000aad693058eaedb74 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

RFC compliant traffic finding its way into the L4S queue is = one thing - it obviously results in a performance degradation to one or the= other, depending on other factors - but I'm more concerned about L4S t= raffic entering the classic queue, which would have a severe impact on gene= ral traffic throughout.=C2=A0 By default this always occurs when a single q= ueue AQM that is not L4S aware is encountered.

--000000000000aad693058eaedb74--