Re: [L4s-discuss] BBRv3 and L4S
Neal Cardwell <ncardwell@google.com> Tue, 16 January 2024 16:47 UTC
Return-Path: <ncardwell@google.com>
X-Original-To: l4s-discuss@ietfa.amsl.com
Delivered-To: l4s-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15581C14F71B for <l4s-discuss@ietfa.amsl.com>; Tue, 16 Jan 2024 08:47:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.607
X-Spam-Level:
X-Spam-Status: No, score=-17.607 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tap3WcfzBb7Z for <l4s-discuss@ietfa.amsl.com>; Tue, 16 Jan 2024 08:46:57 -0800 (PST)
Received: from mail-vs1-xe29.google.com (mail-vs1-xe29.google.com [IPv6:2607:f8b0:4864:20::e29]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 31D6BC14F713 for <l4s-discuss@ietf.org>; Tue, 16 Jan 2024 08:46:57 -0800 (PST)
Received: by mail-vs1-xe29.google.com with SMTP id ada2fe7eead31-466faf5846eso1771655137.0 for <l4s-discuss@ietf.org>; Tue, 16 Jan 2024 08:46:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20230601; t=1705423615; x=1706028415; darn=ietf.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=8hU3NPwsKw9k7294EpD72BLmUqdgUA5of4lrKt4T+10=; b=NqOr9VH/ZPZFh/4SctPTdrCFQY6S9yrP1xXrOkXziNoA+O6GDKzO5hSK9NExkeeq1d NVy/fzOY3ZILTkArhu1eXQn+4oJ5ELXp8w3sOy8I2cVlBGYurP9TSyS+JRR2ZrMegwm3 s+NLqHw7Lg9LelnEIACMXEwRj8Vq02G4sn/fBBTPZs5aJksw78ZFEDvUcSZkXioLzLV4 h/K/LCKY4TOVI95+QfJg2PzXG08yGD+bWBaOCFCAGA6bAmn/qApSZjZ/yF9mWuGnTuNU xtxEhjqMpOaQdR5CM4LOTTk2r6JN5AWoYd+WxlVscV/QnyhrCIudbB7FR1vHEoRwVNw8 Sdcg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705423615; x=1706028415; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=8hU3NPwsKw9k7294EpD72BLmUqdgUA5of4lrKt4T+10=; b=gBfdPuKw3kwTbV+YlzBza3sptp9SukoGUeuKT9chEo1O5AKuQLe3jcOl1lEKsgOczB hMfXKYiZkNFNnuJhzBjrl2AFhjjYS9N/KfXxp1pvNGVJh8/4Q8ABQxwTN4OHzhtwUVo9 hvrfTAWYGB/Sw59Rf+0my77OlMmohAfjygF/5h8OxUafQo9IWttNVp8GT+7XazzE0Iw2 EV/GBuwicns/D8GdmSyOr5N4/Ki39f7ifSVMkioGO5fNBZ46M8v8yfs+4042v9jeyGNT dlMITNvPQUCVGDSb5SaY/Li41OBdIi6EEmfP5bKFN/E8nsBI6F5aFq/1cVn4Eyy2BWpG zJFw==
X-Gm-Message-State: AOJu0YyS18WgoOw+3m9Lw0bn/5ukszqEsJPZ4ScHQ4QayafxUWmPhFBf x0kdUDcsqhuUljo9Bj1ojVqel7wq/tpp/eLjZ1DWSfxokiFgQ7J8tgzsC2etGbPD
X-Google-Smtp-Source: AGHT+IHXmDWBRqq+AbmPfZN+MnqqknEkmmM2bQYcINeaHxDGSeQ2cLBq/4OU+lvtSWW8/CejiF7a2q2aJ4gJKWoiGQ0=
X-Received: by 2002:a67:ffca:0:b0:468:ca4:2aab with SMTP id w10-20020a67ffca000000b004680ca42aabmr5418515vsq.14.1705423615345; Tue, 16 Jan 2024 08:46:55 -0800 (PST)
MIME-Version: 1.0
References: <AM8PR07MB8137FCFD1AB8A5123D85062BC2732@AM8PR07MB8137.eurprd07.prod.outlook.com> <CADVnQykPM1iMmKmf-Pip6UORQ_vFQfNf25RQpxtNhW5pr4JHsA@mail.gmail.com>
In-Reply-To: <CADVnQykPM1iMmKmf-Pip6UORQ_vFQfNf25RQpxtNhW5pr4JHsA@mail.gmail.com>
From: Neal Cardwell <ncardwell@google.com>
Date: Tue, 16 Jan 2024 11:46:37 -0500
Message-ID: <CADVnQymnY+UZHK9Pfm8RwGo2ri9gM7hwXR0kXB7fCQiRVJB8_w@mail.gmail.com>
To: l4s-discuss@ietf.org, Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
Content-Type: multipart/alternative; boundary="000000000000c95a8f060f12e033"
Archived-At: <https://mailarchive.ietf.org/arch/msg/l4s-discuss/H_sPMSEUDJwN0bKousTeYUmh6eU>
Subject: Re: [L4s-discuss] BBRv3 and L4S
X-BeenThere: l4s-discuss@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Low Latency, Low Loss, Scalable Throughput \(L4S\) " <l4s-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l4s-discuss>, <mailto:l4s-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/l4s-discuss/>
List-Post: <mailto:l4s-discuss@ietf.org>
List-Help: <mailto:l4s-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l4s-discuss>, <mailto:l4s-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jan 2024 16:47:01 -0000
Hi Ingemar, > Tried to figure out if BBRv3 supports L4S In principle one could use BBRv3 in an L4S environment. However, its ECN logic was designed for and is currently used only in datacenter environments, and is not yet designed/tuned for L4S environments. Specifically: (1) The ECN logic in BBRv3 has only been tuned/used in production in low-RTT datacenter environments, and is known to have shortcomings at longer RTTs. (2) The ECN logic in BBRv3 is not designed for good coexistence with Prague CC, and would tend to starve Prague CC. > and, if that is the case, does it use accurate ECN ? Linux TCP BBRv3 can use whatever ECN information the core TCP stack provides: that can either be (1) DCTCP-style ECN signals echoed in ACKs (that's how we use it internally within Google) or (2) Accurate ECN. best regards, neal On Tue, Jan 16, 2024 at 9:52 AM Ingemar Johansson S < ingemar.s.johansson@ericsson.com> wrote: > Hi > > > > I am trying to catch up on BBRv3, found a presenation from IETF 117 > > > https://datatracker.ietf.org/meeting/117/materials/slides-117-ccwg-bbrv3-algorithm-bug-fixes-and-public-internet-deployment-00 > > Tried to figure out if BBRv3 supports L4S and, if that is the case, does > it use accurate ECN ? > > > > Any information is greatly appreciated. > > > > /Ingemar > > ================================= > > Ingemar Johansson M.Sc. > > Master Researcher > > > > Ericsson AB > > GFTL ER Networks RNS Protocol & E2E Perf > > Labratoriegränd 11 > > 977 53, Luleå, Sweden > > Phone +46-1071 43042 > > SMS/MMS +46-73 078 3289 <+46%2073%20078%2032%2089> > > ingemar.s.johansson@ericsson.com > > www.ericsson.com > > > > *The right to be ridiculous is * > > *something I hold dear...* > U2 > > ================================= > > >
- Re: [L4s-discuss] BBRv3 and L4S Neal Cardwell