From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lj1-x236.google.com (mail-lj1-x236.google.com [IPv6:2a00:1450:4864:20::236]) (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 5F49F3B29E for ; Mon, 8 Oct 2018 01:16:37 -0400 (EDT) Received: by mail-lj1-x236.google.com with SMTP id z21-v6so16614852ljz.0 for ; Sun, 07 Oct 2018 22:16:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=eAhbR06Y1QfJkZLKeF6R0HY3QaF+KfGX395gphmINsw=; b=iVhLFzhdGG4lr7yPQqjq/dtDXFs7EJovAMTmluUtq/ZyiPqP+7Q4B4PiqAqEAxIq8K tguoa6iOmyF3iZC+FKsYP+LFNCLqF5ipbfwLG5ZX1sIv3VlnPwuluJ43F6rj+ynMzBJB eTLgq3z/XVfo33MlKfTF1EfVVAXAv8IYIPiWwCmr3tbTvsQU7kgVUv0XmHxzTivg61xr 1Q//7Y7iSZN3f3U8nZe/sKUP84aYOjBNzPTfndZSGfg8a9qYpIcZ/E6JacjhPmq4BoUS PDAZ36kNYiszrV0KkQoeWSnC9QoI1Fwvkoob/Sq4jIUfdxKDuwQBz3WMpg3IcIZbBujy 9GnA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=eAhbR06Y1QfJkZLKeF6R0HY3QaF+KfGX395gphmINsw=; b=faffYILpj+vX1+rY5ygZ+oU8g+mvE/7pevXLWztrDltI5u96HUnB1LkILkxE6M+jq+ b8wBNj9fMWtc52SY9RsW1TIDl9n/PUdxNPij1YbP8oQR5tB/+z2DWScMtfroafqFEh+Q X1inBIawix1D/kZ2MoaULykZ89StSw2H38/z63pZ6ec1anmt7NE+GDrSd/IsHRl407h0 rj9i7E/kSeftcsBJetsILpDFlvkt59qepOTw8NPLOoRMnetMvwBNNsMVeeqLZjEitLJU LqsNuEHs8cMbjEmJRrvsrfyJeL58UN7A3cyrbGeb87dXPY54pknb5zj71i4DI3bM/9VA N0zQ== X-Gm-Message-State: ABuFfoj7WxHGb9PRE9wi0walZyOLLKZlVegd5UYqIVrmfQ1LMYZO6dKq wJjFGKbN1K9GB4sNfXmdefs= X-Google-Smtp-Source: ACcGV60S0AEKlRmgjw85FYYovGXT8vJyKVeyqVlrRHHFq7UqxjQ4NCANH5bY+r4tCzbgWEsAKOHYDg== X-Received: by 2002:a2e:83d7:: with SMTP id s23-v6mr14518305ljh.0.1538975795826; Sun, 07 Oct 2018 22:16:35 -0700 (PDT) Received: from jonathartonsmbp.lan (83-245-238-10-nat-p.elisa-mobile.fi. [83.245.238.10]) by smtp.gmail.com with ESMTPSA id k19-v6sm3417136lfi.51.2018.10.07.22.16.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 07 Oct 2018 22:16:35 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) From: Jonathan Morton X-Priority: 3 In-Reply-To: Date: Mon, 8 Oct 2018 08:16:33 +0300 Cc: cake@lists.bufferbloat.net Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Ruben X-Mailer: Apple Mail (2.3445.9.1) Subject: Re: [Cake] Status of sch_cake and sctp with ECN X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Oct 2018 05:16:37 -0000 > On 7 Oct, 2018, at 11:45 am, Ruben wrote: >=20 > I googled this but I found no answers. RFC4960 (the sctp RFC) is = mentioning ECN, but just in the appendix. I was wondering if the Linux = library has ECN support, and how one might active it (as socket option = or as system setting?) and if this tags are currently supported to be = handled by sch_cake? ECN itself is an IP-level protocol, using two bits in the former TOS = byte. Cake will treat any packets advertising themselves as ECN-capable = in this way as supporting ECN. Additionally, Cake uses Linux' = packet-dissection mechanism (which I believe supports SCTP) to identify = and isolate traffic flows, so it doesn't need to understand every = possible transport protocol or encapsulation itself. Of course, it is the responsibility of the sender to set those bits, and = of the receiver to interpret them and echo their meaning back to the = sender, and of the transport-layer protocol as a whole to respond = appropriately to any congestion signal encoded in them. I don't = personally know how well SCTP does that. - Jonathan Morton