From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ot1-x32b.google.com (mail-ot1-x32b.google.com [IPv6:2607:f8b0:4864:20::32b]) (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 6CADE3CB36 for ; Sat, 6 Apr 2019 07:56:23 -0400 (EDT) Received: by mail-ot1-x32b.google.com with SMTP id j10so8038021otq.0 for ; Sat, 06 Apr 2019 04:56:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Jry3Yt/SA1tvVLKwvnAOJF7G0WdLrurahVmQfYKklW0=; b=S/aQZaVmUb7+bPK8B9TQvXqDMLmSpgu7i7SOp+I7QE8x53Z63jfn/6yPTcNMbNoDD2 8kr+0DjluEEv/C8ilKpkzpuFGI7cWwn89iPBABUvkYn1k2AJuxNo+BdTNHo+nT2WuQBb tLDGGyHYUNIGyggqpew7tyP5U4xTM9wn0VFVXIUNuctnxbgCv4A/NWhjBAlzo4bgDLD2 arWI610/H2HiayZvTgu6duhqdgrEYULkG7wq/m5aNvF8NefKZo3rG90fgV971JSio6Yw OJAGXxpZY0nItgPgZw8EWswJX3izoYQjtbByfYVebL+gQREO330fbaLGGIaIrjaaGYLr NGzg== 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=Jry3Yt/SA1tvVLKwvnAOJF7G0WdLrurahVmQfYKklW0=; b=BTemurdLaSl1fEdxD89EDNeE58I3aDAYtHKOEwxCTx+vNTMUkMA4af/18psWacQsF6 ALQwkOoR27YkHThCEuBZlTmWuddzPQvXuin9QZod7iCIKlvKXdfFQ43U6MsLpb7/dx6P QpAQlYsP25s7icCXlmIRStaaQMMeo+8cryrEYmhQl6H3ZuHF15Ie/aU1BeNZYKfgxhYf HKU+ud9JWe/n7ZctjnP5h4a7o2VtpV0xbwgQ8SjZr4h2s18I/b7ZAaLYVv7GIqDWA6q9 zOzcZFruRv/GzWIEP1/J0L3UNdQ/qc5IgKbBvRwzDTnY77iHZ0fGsJRqU048CHArbHcd +mMw== X-Gm-Message-State: APjAAAUGzpgjOTSCCeJbn5JqpWEqYTHt0tJWqEQjn469/A5PtqVlqIhQ BGNaO8uNQzFMe31iuMccYOfyywIpDXdwKDV3cSXHdQ== X-Google-Smtp-Source: APXvYqwC8iQWn/KQTFRaczP2wfByaUXNsJXDXMaJWGJEn71AEr2CixH+FTJWY8/GSSp4LOJcg2pkqzjWoxsU4srm+Gg= X-Received: by 2002:a9d:dc4:: with SMTP id 62mr12229113ots.211.1554551782670; Sat, 06 Apr 2019 04:56:22 -0700 (PDT) MIME-Version: 1.0 References: <3EDC8EAC-1EB2-4E64-8973-8AE177D8789C@gmail.com> In-Reply-To: <3EDC8EAC-1EB2-4E64-8973-8AE177D8789C@gmail.com> From: Neal Cardwell Date: Sat, 6 Apr 2019 07:56:06 -0400 Message-ID: To: Jonathan Morton Cc: Dave Taht , ECN-Sane , BBR Development , flent-users Content-Type: multipart/alternative; boundary="000000000000cafa290585db4ad0" Subject: Re: [Ecn-sane] [bbr-dev] duplicating the BBRv2 tests at iccrg in flent? 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, 06 Apr 2019 11:56:23 -0000 --000000000000cafa290585db4ad0 Content-Type: text/plain; charset="UTF-8" On Fri, Apr 5, 2019 at 12:20 PM Jonathan Morton wrote: > > On 5 Apr, 2019, at 6:10 pm, 'Neal Cardwell' via BBR Development < > bbr-dev@googlegroups.com> wrote: > > > > Right. I didn't mean setting the codel target to 242us. Where the slide > says "Linux codel with ECN ce_threshold at 242us sojourn time" I literally > mean a Linux machine with a codel qdisc configured as: > > > > codel ce_threshold 242us > > I infer from this that BBR's new ECN support won't work properly with > standard CE marking behaviour, only with the sort of signal that DCTCP > requires. Is that accurate? > Yes, that's correct. Thus far BBR v2 is targeting only DCTCP/L4S-style ECN. > SCE allows providing that sort of high-fidelity congestion signal without > losing interoperability with RFC-3168 compliant flows. > Noted, thanks. neal --000000000000cafa290585db4ad0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Fri, Apr 5, 2019 at 12:20 PM Jonathan = Morton <chromatix99@gmail.com> wrote:
> On 5 Apr, 2019, at 6:10 pm, 'Neal Cardwel= l' via BBR Development <bbr-dev@googlegroups.com> wrote:
>
> Right. I didn't mean setting the codel target to 242us. Where the = slide says "Linux codel with ECN ce_threshold at 242us sojourn time&qu= ot; I literally mean a Linux machine with a codel qdisc configured as:
>
>=C2=A0 =C2=A0codel ce_threshold 242us

I infer from this that BBR's new ECN support won't work properly wi= th standard CE marking behaviour, only with the sort of signal that DCTCP r= equires.=C2=A0 Is that accurate?

Yes, t= hat's correct. Thus far BBR v2 is targeting only DCTCP/L4S-style ECN.
=C2=A0
SCE allows providing that sort of high-fidelity congestion signal without l= osing interoperability with RFC-3168 compliant flows.
=
Noted, thanks.

neal

<= /div>
--000000000000cafa290585db4ad0--