[tsvwg] L4S CC-signaling and tunneling

Sebastian Moeller <moeller0@gmx.de> Mon, 27 April 2020 08:58 UTC

Return-Path: <moeller0@gmx.de>
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 C7AF53A133C for <tsvwg@ietfa.amsl.com>; Mon, 27 Apr 2020 01:58:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.648
X-Spam-Level:
X-Spam-Status: No, score=-1.648 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 axcW1nP9pjCk for <tsvwg@ietfa.amsl.com>; Mon, 27 Apr 2020 01:58:33 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (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 AC8EE3A133B for <tsvwg@ietf.org>; Mon, 27 Apr 2020 01:58:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1587977910; bh=j1ShHlhKsdhsTvjpDz/NcojpFs3E+skDNoky83orh9I=; h=X-UI-Sender-Class:From:Subject:Date:To; b=M1Uw0cRQraM+2/82Y5usrYEXa0cUr1bqyESbCPTiSv48Owg3ZYqLq331RxeF24cam rS5ZFYK007IRQaSj2E3HnPMcmePqJxRzYlXRw7BzypdJiLH3MP2tTMWNNN32uGFwsW OSbJcNi/n0DcdQZVlU6iiwTDIwkuqHvXyPlDCR6c=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [10.11.12.16] ([134.76.241.253]) by mail.gmx.com (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MdNY8-1itemE1tuS-00ZN02 for <tsvwg@ietf.org>; Mon, 27 Apr 2020 10:58:30 +0200
From: Sebastian Moeller <moeller0@gmx.de>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.14\))
Message-Id: <0A6CE22E-B0CB-43CD-9989-9D6339A3B5FE@gmx.de>
Date: Mon, 27 Apr 2020 10:58:29 +0200
To: tsvwg IETF list <tsvwg@ietf.org>
X-Mailer: Apple Mail (2.3445.104.14)
X-Provags-ID: V03:K1:oI2oKyogXruj0myibf5R6HZ+ty57pIeVZ1cuTf8u6/+HS1cNZ3z IE5Yp0t+QB5K+t3t8eTIuo/AJW11HbQbJPsoebfw+1/NJ8GgzzloIETlovGKzqjn5m1ZOXy n7ATxmuxeoTh1IPqgAL9YDL2JRiR865+vI7ptE+m41ZKDdB21+dXWISd0FGZLaUhmnYxx1V pnIB2qQ7flqHCtGD7EhiQ==
X-UI-Out-Filterresults: notjunk:1;V03:K0:X2Kt64nDb8U=:3fAr/siVHqnH2+byAaD8gJ q+zi3/mpiR5X5DZASH66a6ibTskUCBIvOdRXRLhdw464eVUs4GhyHXkNKTUKu/rJLQRNIvtNr qjZNUDRwwOlT/KBP1yZDjHTJsfHgspyOzNallCKz66N9k7ghKILOXCxWiszq2TQuUSqDcByuD to0TG4b1KwYYNw3R5Oy9/PurRqZNXmAMjuAaz9+QPcoHDWZKGljDMU6MHuaHzfQf0Rpv4fYcr 5FQXyvi7mWSl8KHpnDK4+HTHK0lhhMaa4VPekFb/+4qHChwZixzrFDSHxFqFIZ+2q8g7DPd7F tYrLfyRHbwfYkewRRKeuSgKxvQAL4Mno+8jHc5hBFMaLvMAH8NuaWundtyP9q5u7vSiYaOpkY mmv65RQ0mDEsDpxBm1dg2Ij9SKPFbuNoP/hpYYDJSKy/Nc1NGg0UxHWSHcFCGp7//U2h7hvLi I4xNpJMg79CG0CuThS+lZRNoCAJuWmmOPZHMZLqGgpNbaWxmZEINN/uL6oEUGEdbF2kf9JaWm 9T17MUFmKNkD5E1M+CIhRZ0rOtJCLuaXpvIMJpntgIYrmYboOzZ+8+nGGow0QLETBVk7swnam xObpKKa6FVhElV5UOUCjLu70u4rG5A5LkRKBki368ory0oPzUKfGgt2nXD7+VYePTc+XSHMs0 qCNNeoBKmoUPnIHJgJXtpwazeReZnjGyBuemJYaeGXHfnk0drxCzunSo/0iIzjWffbemVnHYN sCOKww2v/ZWeHwzoKfUZxCzMD0TDg7i2Cg51iGn4cwcILiFJlcDayW1gtLxRctjrRMk4dOx3v FINhkKM/V80OkPzEFAWoebCN4tO0M+2dg2Nhqdn7DS8ddMk7fa5hpq9aijDvGJTVM1DT+ks78 1zKzUZCeIdQkwOPeVCZ1s/XUZ6ePZ6ZaVbnM4spObSKVSLM9xE+RvlSu+C/0JKnqkIuFluGbx ykdWsP15tgtOlx2Jqe2kMz+uxcfLqGfA6xsaT1g9B6II43Gsp2hul5AihAZWJOMlS6DPcHtp1 RTXV4bluvRn+xM3w3OsYyXwELl4B9sNwS7a/x8uk7F/fwagKf127BvT1IWpcb5+DznbkrHws5 2DdZBrYHRw/UVm6yWCzP/z42qANxnK6fPW/yzbK1Ec59fuFoeIHBNaHVFu3w/iDFKpewSX539 +Mn/HSdm7EmDbZ6SxXf5DUCN8mORaJB/yb+TfdmWVUYOmOy3NkRK7e5Ta3AGOX8cVkLBcKjfP xO6H8l/tFkwBBStd9kHz0+CsX2KEOzeq59hdGfA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/q_MABPCAvm7_t8OVw49Z8OzV4oE>
Subject: [tsvwg] L4S CC-signaling and tunneling
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, 27 Apr 2020 08:58:35 -0000

Dear List,

after Bob's recent emphasis on L4S's conscious design to be operable with its AQM operating on tunneled traffic, I took the liberty to actually look at the three currently discussed L4S RFC drafts. All I found when searching for tunnel and/or encap* was the following in https://tools.ietf.org/html/draft-ietf-tsvwg-l4s-arch-06:

"6.3.4.  Other Potential Deployment Issues


   An L4S AQM uses the ECN field to signal congestion.  So, in common
   with Classic ECN, if the AQM is within a tunnel or at a lower layer,
   correct functioning of ECN signalling requires correct propagation of
   the ECN field up the layers [RFC6040],   [I-D.ietf-tsvwg-ecn-encap-guidelines]."


I am a bit puzzled how terse this description is given how much emphasis there seems to have been on making L4S congestion signaling work properly with tunnel layers. While I am loath to propose to inflate the L4S drafts any further, maybe some fat could be trimmed at other places to make some room for a more detailed description of the desired/required tunnel transition properties.


Best Regards
	Sebastian