From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-x232.google.com (mail-lf0-x232.google.com [IPv6:2a00:1450:4010:c07::232]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id B976821F649 for ; Fri, 23 Oct 2015 06:32:28 -0700 (PDT) Received: by lfaz124 with SMTP id z124so83759033lfa.1 for ; Fri, 23 Oct 2015 06:32:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=3gjUNHQDUH3yLDFB3z11m6JH7VW5SUjWLoudeJuvFpg=; b=tcqOzQ3BVE8g+8LAhj4UuZjU95c32mXGc4CvgJAG648P2cQmeQc42tj8Pd/DOlXXBy zNCXEPE2qtJaV1/gCn9V275bToFoENoxu01942yjuv9bwPzccnyHbLgE5uEo4EzulDB/ VQvC9sSib+udn0VXJz96VrivuKmKiV4ACady9Y3lhzh0xZyf+FLIpjtRrKbg0CZJ679K 97X4b0OQDFIa00vVcBKnjm/NxD1io76KwLVGe4626vlZegTzuaZQZhlA7xL4FcHwgtj3 xlIRPYkZW38uM7yTit/UfqTemHN2SxmnVvd9si6K2/BGZmGKB/Dx/tdo8ywa2W0hxSj4 Yh7w== X-Received: by 10.112.141.7 with SMTP id rk7mr10658965lbb.82.1445607146234; Fri, 23 Oct 2015 06:32:26 -0700 (PDT) Received: from bass.home.chromatix.fi (87-95-20-216.bb.dnainternet.fi. [87.95.20.216]) by smtp.gmail.com with ESMTPSA id ut10sm3255918lbc.31.2015.10.23.06.32.18 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 23 Oct 2015 06:32:25 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) From: Jonathan Morton In-Reply-To: <81564C0D7D4D2A4B9A86C8C7404A13DA34C0AE3A@ESESSMB205.ericsson.se> Date: Fri, 23 Oct 2015 16:31:55 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: References: <81564C0D7D4D2A4B9A86C8C7404A13DA34C0AE3A@ESESSMB205.ericsson.se> To: Ingemar Johansson S X-Mailer: Apple Mail (2.2104) Cc: "Pal Martinsen \(palmarti\)" , "aqm@ietf.org" , "cake@lists.bufferbloat.net" , "rmcat@ietf.org" , "rtcweb@ietf.org" , Colin Perkins Subject: Re: [Cake] [aqm] ECN support for UDP (was RE: [rmcat] [rtcweb] Catching up on diffserv markings) X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Oct 2015 13:32:51 -0000 > On 23 Oct, 2015, at 11:40, Ingemar Johansson S = wrote: >=20 > Network wise, I guess the support for ECN for UDP is a matter of = configuration, but if one look from strict radio (LTE) perspective it = does not really matter if it is UDP or TCP over IP, it is treated the = same, thus the strategy for ECN marking should be the same and should = preferably follow the guidelines in RFC7567. All the Linux qdiscs I=E2=80=99m aware of that support ECN are agnostic = to the transport layer in this respect. If ECN capability is advertised = in a packet=E2=80=99s IP header, it=E2=80=99s eligible for ECN CE = marking. - Jonathan Morton