Re: [ippm] [tsvwg] [CCWG] [iccrg] New Internet Draft: Congestion Signaling (CSIG)

Abhiram Ravi <abhiramr@google.com> Wed, 25 October 2023 17:33 UTC

Return-Path: <abhiramr@google.com>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17F89C17C526 for <ippm@ietfa.amsl.com>; Wed, 25 Oct 2023 10:33:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -22.597
X-Spam-Level:
X-Spam-Status: No, score=-22.597 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, 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 We9T62Vtp8Sy for <ippm@ietfa.amsl.com>; Wed, 25 Oct 2023 10:33:05 -0700 (PDT)
Received: from mail-lj1-x22c.google.com (mail-lj1-x22c.google.com [IPv6:2a00:1450:4864:20::22c]) (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 25FDAC1705FE for <ippm@ietf.org>; Wed, 25 Oct 2023 10:33:05 -0700 (PDT)
Received: by mail-lj1-x22c.google.com with SMTP id 38308e7fff4ca-2c51388ccebso87441151fa.3 for <ippm@ietf.org>; Wed, 25 Oct 2023 10:33:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20230601; t=1698255183; x=1698859983; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=TZKQ2DTSFqfGa0kRQDpUVEyRXjQxzMA69w6BaoMcPgg=; b=jMh5GIe1BCoVEa8pJtKmtny9WSqCdIyxW/AdRipkK0QWlnzJPUCYLEdrKgYNBKZmU+ Wg+wqmiLlM4hI6LhCFZhUg9WA9k+2GVrrEXweLgAloQMRGxgQV5telc0tLUW99JNot/9 3lPNGLMv0HyUyuP3gIoX62DJ7HO0IcMkk3NBnl8t1haGXjYkcNPbrGVJcsHUDu3BpKZS ODN0E8DN+oGBlge7kTl2whH/UXjV+Wb0yhwVpbQ8pJlHWgDOyv0SuWtOmsJv/lqnn7Xg TW/ixQ7bu0MhTk0XxHSkb+hNawNzsNQBnGPr47nu79SmHWOzBQ2Rt84dl82OriXFHKiY oIXg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698255183; x=1698859983; h=cc: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=TZKQ2DTSFqfGa0kRQDpUVEyRXjQxzMA69w6BaoMcPgg=; b=ArxsyHlwOiwNokaPLITkUtk/LX94XrVEcTlJjiS/5ERzqJPomW715XFep4JsjbMEuO jVNA/XysyxeofNWEdpbQVglw7tHf2qJradLkPXbWxI3VS5UQ8Z0bJ0NxyrpeICNIYQ/k DciWcxbwkr6hEnuPVeaMVNzzvawa6C/TrhKs3pfWKRikRlrQxCgZTrWNX8OztNfutMYw n7MYn/yipfI0ORAa4+V9deOd/aFy5O9RHiASn2EHSG+IktpR0UyHYxwJhwPV2eY4lTrr Rv31hn+f2lyKtPx4DBCbx3hSWg6wenoYIMoc1B/hlQydQTiLzEzncUsPMmWNmFPYmujM A5Gw==
X-Gm-Message-State: AOJu0YyIc0qxvN339Vu2MYwlq8Llw4UIdfx4XxTJOJnRPBWUoW26eS1c 7uJEb8Bq20OoRjvr432NXkp6ErNYJXCWkHm1n+xU9WXkkeLR+w4PPZs=
X-Google-Smtp-Source: AGHT+IG1AupFx1dteux0hitwL9lrnFHobKJvdHQHYoD+JtpOkYygIjQnz6bZyJz86fYl4ehC5mJAK+tog741gCxPMbE=
X-Received: by 2002:a05:651c:1986:b0:2c0:afd:e7ed with SMTP id bx6-20020a05651c198600b002c00afde7edmr13791163ljb.10.1698255182171; Wed, 25 Oct 2023 10:33:02 -0700 (PDT)
MIME-Version: 1.0
References: <CAFvDQ9rz5A8Gng_HZEA_YDnrORY+7uMBbZ2DSvyAgoyicSrXGw@mail.gmail.com> <202309171914.38HJE7Le097504@gndrsh.dnsmgr.net>
In-Reply-To: <202309171914.38HJE7Le097504@gndrsh.dnsmgr.net>
From: Abhiram Ravi <abhiramr@google.com>
Date: Wed, 25 Oct 2023 10:32:24 -0700
Message-ID: <CAF0+TDDBysH017PbAY1c9xxQCjQp9p_bbBbPvCt+3UOLdi+ONA@mail.gmail.com>
To: ippm@ietf.org, iccrg IRTF list <iccrg@irtf.org>
Cc: jai.kumar@broadcom.com, nanditad@google.com, Naoshad Mehta <naoshad@google.com>
Content-Type: multipart/alternative; boundary="000000000000dfe9a106088dd8ba"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/5lYADHwhBqAWIW-ZYG-EYOqzdYI>
Subject: Re: [ippm] [tsvwg] [CCWG] [iccrg] New Internet Draft: Congestion Signaling (CSIG)
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Oct 2023 17:33:10 -0000

[ippm, iccrg only]


Thanks for all the comments and discussion. Here are a few more responses
inline.

> Tom: I'm not seeing how pushing this into layer 2 is a simplification for

deployment. When you say that you want to deploy in a heterogeneous

network, is this a network with different L2s but still IP over it, or

is it a network where there are non-IP links? If it's the former, then

if you put the information in the network layer then the fact that

it's a "heterogeneous network" is irrelevant-- there is immense value

in leveraging a common network layer across heterogeneous link layer

technologies, that's fundamental to the architecture of the Internet

“heterogeneous network” in this context of data center deployments
primarily refers to the diverse set of NICs and switches across generations
with different capabilities, that any new technology needs to continue to
interoperate across.

> Tom: I'm skeptical that this is any easier to implement than Hop-by-Hop

Options. HBH is at a fixed location in packets, this can be

implemented as the first option for cut through. A programmable

device, switch or NIC, would have no problem with this.

Note that “programmable” is the key word here. Most legacy devices deployed
in data centers are not programmable, and many new devices continue to be
fixed-function for performance. In addition, HBH only applies to IPv6, so
IPv4 and tunnels that do IPv6-in-IPv4 encaps will not be supported with
that approach.

> Tom: How does IP-IP carry CSIG tags if they're not part of the network

layer. It seems like it would only work if the L2 packet is tunneled.

Any L3+ encapsulation / decapsulation in the network does not touch the
location of the CSIG-tag in the header. CSIG-tags are updated by devices on
the packet at this fixed offset independent of tunneling at upper layers.

> Tom: RIght, what you're describing is an end to end protocol that can
cross

and be forwarded across multiple links and the data can be consumed or

modified in flight by intermediate nodes. I think that pretty much

fits the definition of network layer information.

> Tom: I  don't understand how that could be the only possible solution. As

already mentioned, IOAM is already providing similar functionality,

and AFAIK, it works perfectly well with legacy devices. Please provide

more explanation why this protocol MUST be L2 and can't be in the

network layer.

“works perfectly well with legacy devices” - This is not true for data
center deployments. Many devices don’t support processing ipv6 extension
headers in the fast path, for packet performance in data centers. Packets
with ip options are discarded by many legacy devices, or in some devices
can be processed only in the slow path (punt to cpu), which is a big hit to
packet latency and cpu usage. It is not feasible to achieve line rate
performance with any network layer implementation in such devices. However,
almost all devices have good support for L2 processing including VLAN tag
updates, which can be repurposed for CSIG and interoperate at line rate.
This is one of the observations that CSIG draws on to design a practical
solution.

>  [SM]: Well the proposal at hand has found a place, and the authors
probably would not complain if ratification would short and sweet. IMHO
given that I can see no side-effects on non-particiating flows, I think
worst case this could be made an informational RFC pretty quickly (look,
this is what ${BIG_TECH_CO} does in its data centers). I do however agree?
in that it would be better to make this actually usable over the internet.
> Greg: It seems like the question of the SDO driving this work requires
careful consideration. It is not a mere coincidence that the applicability
of IOAM is defined at IETF WGs for data planes based on specifications
developed at IETF. AFAICS, which is not exactly the case for CSIG. Could
the liaison from IETF to IEEE, specifically to 802.3 and 802.1, be drafted
before deciding where in IETF this work is anchored?

Thanks for the suggestions. We will address these.


On Sun, Sep 17, 2023 at 12:14 PM Rodney W. Grimes <ietf@gndrsh.dnsmgr.net>
wrote:

> Hesahm,
>         I think you missed my point, indeed there are lots of
> vendors and equipment around that has support for 802.1Qau, that
> is not hard to find.  What is hard to find is anyone who has ever
> actually deployed this or anyone who even has test lab data
> showing how it behaves when put to the test.
>
>
> > I think Broadcom Thor ASIC supports 802.1Qau [
> > https://docs.broadcom.com/doc/NCC-WP1XX] which is used by Arista [
> >
> https://www.arista.com/assets/data/pdf/Broadcom-RoCE-Deployment-Guide.pdf]
> The QCN in this guide is NOT IEEE 802.11Qua.
>
> >
> > NVIDIA uses QCN [
> >
> https://docs.nvidia.com/networking/plugins/servlet/mobile?contentId=12013417#content/view/12013417
> > ]
> >
> > Cisco used 802.1Qau in their earlier data center switches [
> >
> https://www.cisco.com/c/dam/global/en_sg/training-events/datacentertechbyte/assets/pdfs/data_center_ethernet_qa.pdf
> > ]
> > I am not sure about their current ones. It is worth noting that Cisco was
> > the main contributor to the standardization of IEEE 802.1Qau in the DCB
> TG.
> >
> > Marvell FastLinQ 41000 Series support 802.1Qau [
> >
> https://www.marvell.com/content/dam/marvell/en/public-collateral/ethernet-adaptersandcontrollers/marvell-ethernet-controllers-fastlinq-41000-product-brief.pdf
> ].
> > FastLinQ is used by HPE servers [
> >
> https://www.marvell.com/content/dam/marvell/en/public-collateral/hpe/hpe-marvell-pb-fastlinq-41000-series-adapters.pdf
> > ]
> >
> > To address congestion due to incast problem in DC IEEE 802.1 TSN TG
> > recently standardized IEEE 802.1Qcz [https://1.ieee802.org/tsn/802-1qcz/
> ].
> >
> > Although it is useful to know about products which use QCN, the main
> issue
> > which I want to discuss is how we compare the new congestion signaling
> > proposal with QCN.
>
> That would be greatly assisted by actual DATA showing how 802.11Qua
> behaves under various test conditions, which I can find NO data on.
>
> Regards,
> Rod Grimes
>
> > Hesham
> >
> > On Sat, Sep 16, 2023, 10:22 AM Rodney W. Grimes <ietf@gndrsh.dnsmgr.net>
> > wrote:
> >
> > > Hesham,
> > >         While I found a read of some of the IEEE 802.1Qau papers
> > > interesting, I have NOT been able to find anyone who has real
> > > world deployment data.  In a datacenter or otherwise.
> > >
> > >         Do you know of any or does anyone here have data to
> > > point at?
> > >
> > > Regards,
> > > Rod Grimes
> > >
> > > > Hi Abhiram,
> > > > IEEE 802.1 had a data center bridging TG which developed sometime
> ago the
> > > > spec for quantized congestion control (QCN). The spec is IEEE
> 802.1Qau
> > > > which is now part of 802.1Q.
> > > >
> > > > QCN provide a means for a bridge to notify a source of congestion
> causing
> > > > the source to reduce the flow rate.
> > > >
> > > > QCN is independent of upper layer protocol. It coexists with TCP
> (there
> > > is
> > > > a nested control loops of QCN and TCP flow control).
> > > >
> > > > QCN only works for unicast traffic, and operates over a domain where
> all
> > > > bridges and end stations support it.
> > > >
> > > > QCN does not require per flow state or per flow queuing in bridge.
> > > >
> > > > Over the years there have been proposals to enhance it, but the basic
> > > idea
> > > > stayed the same.
> > > >
> > > > How you compare your congestion signaling proposal with QCN. One
> obvious
> > > > difference is that yours is end-2end while QCN is not. But is end-end
> > > > congestion control the best way to go?
> > > >
> > > > Comments?
> > > >
> > > > Hesham
> > > > PS. I removed IPPM but kept other WG who may have an opinion on this
> > > issue.
> > > >
> > > >
> > > > On Wed, Sep 13, 2023, 5:09 PM Abhiram Ravi <abhiramr=
> > > > 40google.com@dmarc.ietf.org> wrote:
> > > >
> > > > > Thank you for your comments. Responses inline.
> > > > >
> > > > > > Tom: The signaling being described in the draft is network layer
> > > > > information, and hence IMO should be conveyed in network layer
> headers.
> > > > > That's is L3 which conveniently is the average of L2+L4 :-)
> > > > > > Rachel:  Implementing in L2 may be difficult to be used in e2e
> > > transport.
> > > > > > Hang: I agree L2 may not be the best choice to carry the
> congestion
> > > > > signaling end-to-end and more bits are needed.
> > > > >
> > > > > The choice of using L2+L4 is an intentional and important design
> > > choice,
> > > > > one that is driven by need, for practicality and ease of
> deployment in
> > > data
> > > > > center networks. We acknowledge that previous approaches have
> > > attempted to
> > > > > extend L3 or L4, but these approaches do not meet the requirements
> for
> > > > > deployability in a heterogeneous network, including
> interoperability
> > > and
> > > > > backward compatibility. CSIG targets specific yet important use
> cases
> > > while
> > > > > meeting these requirements.
> > > > >
> > > > > Section 7.1
> > > > > <
> > >
> https://datatracker.ietf.org/doc/html/draft-ravi-ippm-csig-00#name-choice-of-layer-2
> > > >
> > > > > of the draft explicitly addresses why such a design was chosen.
> > > > >
> > > > > The key reasons are:
> > > > >
> > > > >    -
> > > > >
> > > > >    Simplicity of device implementations of CSIG (both at NICs and
> > > > >    switches), given the location of the CSIG-tag in the packet
> header
> > > is not
> > > > >    affected by any header at layer 3 and above. CSIG-tag being the
> > > last tag
> > > > >    before the ethertype also makes it simple for ASICs to
> implement it
> > > inside
> > > > >    the L2 header.
> > > > >    -
> > > > >
> > > > >    Support for delivering congestion signals even in the presence
> of
> > > > >    in-network tunneling and encryption, which are commonly used in
> data
> > > > >    centers, especially for Cloud traffic and in Traffic engineered
> > > domains.
> > > > >    CSIG tags are carried through Layer 3 tunnels e.g., IP-in-IP,
> VxLAN,
> > > > >    Geneve, at a fixed offset in the packet header. This avoids the
> > > need to
> > > > >    copy and relocate CSIG tags across inner / outer headers during
> > > > >    encapsulation and decapsulation of packets, which is a complex
> > > hardware
> > > > >    operation and would be necessary if implemented instead at
> layers 3
> > > or
> > > > >    higher.
> > > > >
> > > > > > Tom: The signaling being described in the draft is network layer
> > > > > information, and hence IMO should be conveyed in network layer
> headers.
> > > > >
> > > > > The information carried in L2 CSIG-tags are device signals or port
> > > signals
> > > > > from the bottleneck, and should not be viewed as network-layer
> signals.
> > > > > Although the bottleneck signal is also a property of the packet
> path in
> > > > > aggregate, the signal carried on the tag has a scope of one hop
> i.e.,
> > > the
> > > > > measurement on one specific link or device on the path. The tag
> gets
> > > > > conditionally swapped on each device in a compare-and-replace
> manner as
> > > > > described in Section 4.3
> > > > > <
> > >
> https://datatracker.ietf.org/doc/html/draft-ravi-ippm-csig-00#name-csig-operation-life-of-a-pa
> > > >
> > > > >
> > > > > Reflection is a property of the transport as described in Section
> 4.2,
> > > and
> > > > > hence CSIG reflection is implemented at layer 4 and is specific to
> the
> > > > > transport. This allows a clean separation of the mechanism used to
> > > collect
> > > > > signals from the network from the mechanism used for leveraging
> those
> > > > > signals at the transport.
> > > > >
> > > > > > Tom: Also, L2 is not really an end-to-end protocol (would legacy
> > > > > switches in the path also forward the header)
> > > > >
> > > > > Legacy devices can not only forward the packet, but also
> participate in
> > > > > the CSIG protocol via a software-assisted approach by treating
> > > CSIG-tags as
> > > > > VLAN-tags and leveraging VLAN resources to perform CSIG updates.
> This
> > > L2
> > > > > approach is the only solution we?ve found which allows immediate
> > > deployment
> > > > > for certain signals with legacy devices in data centers, while
> native
> > > > > support for CSIG is easily achievable in future devices. CSIG
> > > stripping can
> > > > > also be exercised for interop when needed - see Section 6
> > > > > <
> > >
> https://datatracker.ietf.org/doc/html/draft-ravi-ippm-csig-00#name-incremental-deployment-of-c
> > > >
> > > > > for interoperability.
> > > > >
> > > > > > Tom: As the draft describes, this would entail having to support
> the
> > > > > protocol in multiple L2 and multiple L4 protocols
> > > > >
> > > > > Section 4.1
> > > > > <
> > >
> https://datatracker.ietf.org/doc/html/draft-ravi-ippm-csig-00#name-csig-tag-header-format
> > > >
> > > > > lists how CSIG-tag operates with each relevant L2 encapsulation and
> > > Section
> > > > > 4.2
> > > > > <
> > >
> https://datatracker.ietf.org/doc/html/draft-ravi-ippm-csig-00#name-csig-reflection-header-form
> > > >
> > > > > addresses implementation of reflection in relevant transports.
> > > > >
> > > > > > Tom: IMO, the proper carrier of the signal data is Hop-by-Hop
> > > Options.
> > > > > IOAM seems pretty extensible, so maybe it could be adapted to
> carry the
> > > > > signals of this draft?
> > > > > > Rachel: Of course it can work well in limited domain, like DC or
> HPC
> > > > > clusters. However, I also look for some solutions that could be
> able
> > > to go
> > > > > through internet
> > > > >
> > > > > CSIG is targeted at specific use cases in limited domains,
> primarily
> > > data
> > > > > centers, for congestion control, traffic management and network
> > > > > debuggability. The requirements for such use cases vary
> significantly
> > > from
> > > > > those of internet deployments, which is not in scope for CSIG.
> > > > > IOAM and hop-by-hop options in general are tuned for a broader set
> of
> > > use
> > > > > cases and do not meet all the requirements for the specific use
> cases
> > > that
> > > > > CSIG addresses, including interop with legacy devices and
> in-network
> > > > > tunneling, due to the placement of the header.  Section 2
> > > > > <
> > >
> https://datatracker.ietf.org/doc/html/draft-ravi-ippm-csig-00#name-design-principles
> > > >
> > > > > speaks to these requirements.
> > > > >
> > > > > > Rachel: For L2 solution, it should be developed together with
> IEEE
> > > 802.1.
> > > > >
> > > > > Acknowledging that IEEE will be involved as well.
> > > > >
> > > > > > Sebastian: What happens if bottlenecks hand out immediate
> > > capacity/rate
> > > > > estimates and all greedy flows start increasing their cwin really
> fast?
> > > > >
> > > > > CSIG supports both min(ABW) and min(ABW/C). Using min(ABW/C), the
> each
> > > > > flow can increase its rate in proportion to the % available
> bandwidth,
> > > so
> > > > > that in aggregate the flows respect the available bottleneck
> bandwidth
> > > with
> > > > > reduced risk of overshoot. See Section 8.1.2
> > > > > <
> > >
> https://datatracker.ietf.org/doc/html/draft-ravi-ippm-csig-00#name-using-maximum-link-utilizat
> > > >
> > > > > .
> > > > >
> > > > > > Ingemar: CSIG sounds to me like something that belongs more in
> ICCRG
> > > > >
> > > > > CSIG is applicable to use cases beyond Congestion control (which
> is an
> > > > > important one), such as traffic management and network debugging.
> > > Section
> > > > > 8
> > > > > <
> > >
> https://datatracker.ietf.org/doc/html/draft-ravi-ippm-csig-00#name-use-cases-defined-by-bottle
> > > >
> > > > > describes the use cases in more detail.
> > > > >
> > > > > > Tom: A related proposal might be FAST draft-herbert-fast. These
> > > might be
> > > > > complementary and options for both may be in the same packet
> > > > > > Hang: We call it Advanced ECN. See draft-shi-ccwg-advanced-ecn
> > > > > > Ingemar: L4S is recently standardised and it is definitely
> gaining
> > > > > traction also in 3GPP
> > > > >
> > > > > Thank you for the pointers. We agree that these proposals are all
> > > > > complementary to CSIG.
> > > > >
> > > > >
> > > > > On Wed, Sep 13, 2023 at 5:20?AM <Ruediger.Geib@telekom.de> wrote:
> > > > >
> > > > >> Hi Ingemar, hi Sebastian,
> > > > >>
> > > > >> Skimming over the draft only, isn't CSIG about Ethernet-domains,
> while
> > > > >> L4S is E2E?
> > > > >>
> > > > >> Regards,
> > > > >>
> > > > >> Ruediger
> > > > >>
> > > > >> -----Urspr?ngliche Nachricht-----
> > > > >> Von: tsvwg <tsvwg-bounces@ietf.org> Im Auftrag von Sebastian
> Moeller
> > > > >> Gesendet: Mittwoch, 13. September 2023 13:42
> > > > >> An: Ingemar Johansson S <ingemar.s.johansson=
> > > > >> 40ericsson.com@dmarc.ietf.org>
> > > > >> Cc: Vidhi Goel <vidhi_goel=40apple.com@dmarc.ietf.org>;
> > > Shihang(Vincent)
> > > > >> <shihang9=40huawei.com@dmarc.ietf.org>; tsvwg <tsvwg@ietf.org>;
> Jai
> > > > >> Kumar <jai.kumar@broadcom.com>; IETF IPPM WG <ippm@ietf.org>; Tom
> > > > >> Herbert <tom=40herbertland.com@dmarc.ietf.org>; iccrg@irtf.org;
> > > Abhiram
> > > > >> Ravi <abhiramr=40google.com@dmarc.ietf.org>; Nandita Dukkipati <
> > > > >> nanditad@google.com>; ccwg@ietf.org; Huangyihong (Rachel)
> > > <rachel.huang=
> > > > >> 40huawei.com@dmarc.ietf.org>; Naoshad Mehta <naoshad@google.com>
> > > > >> Betreff: Re: [tsvwg] [iccrg] New Internet Draft: Congestion
> Signaling
> > > > >> (CSIG)
> > > > >>
> > > > >> Hi Ingemar,
> > > > >>
> > > > >>
> > > > >> > On Sep 13, 2023, at 12:30, Ingemar Johansson S
> <ingemar.s.johansson=
> > > > >> 40ericsson.com@dmarc.ietf.org> wrote:
> > > > >> >
> > > > >> > Hi
> > > > >> >
> > > > >> > I agree with Vihdi
> > > > >> >
> > > > >> > L4S is recently standardised
> > > > >>
> > > > >>         [SM] In experimental track, the goal is currently to test
> > > whether
> > > > >> it can/should be deployed at scale....
> > > > >>
> > > > >> > and it is definitely gaining traction also in 3GPP. We have an
> echo
> > > > >> system that is looking forward to having L4S widely deployed.
> > > > >> > Still, the congestion control aspects are not fully explored
> yet.
> > > One
> > > > >> interesting topic is if L4S allows to more safely deviate from
> > > additive
> > > > >> increase to make congestion control algorithms more quickly
> converge
> > > to
> > > > >> higher link capacity. There are a number of study topics around
> L4S
> > > > >> congestion control that are listed in e.g the TCP Prague draft.
> > > > >> >
> > > > >> > I cannot dictate what others should do with their time and
> money but
> > > > >> personally I'd prefer that the IETF explores L4S and its
> > > possibilities and
> > > > >> downsides before jumping on the next idea.
> > > > >>
> > > > >>         [SM] L4S can be described as taking the ideas behind
> DCTCP and
> > > > >> making them fit for use over the internet*. Yet the signaling
> > > discussed
> > > > >> here is to be used in e.g. data center contexts where DCTCP is
> > > already used
> > > > >> and found lacking compared to newer methods operating on richer
> > > congestion
> > > > >> information (HPCC, Swift, Poseidon, ...).
> > > > >>         Given that L4S essentially uses a multi-packet signal(**)
> to
> > > > >> report the "queue filling state" that is then stochastically
> > > distributed
> > > > >> over all concurrent flows, it seems obvious to me that
> reconstructing
> > > a
> > > > >> reliable estimate of on-path queueing will take some time and
> > > averaging for
> > > > >> each individual flow, I would guess that in some environments this
> > > delay
> > > > >> simply is too costly.
> > > > >>         So L4S and CSIG seem complementary and in no way mutually
> > > > >> exclusive.
> > > > >>
> > > > >>
> > > > >> Regards
> > > > >>         Sebastian
> > > > >>
> > > > >>
> > > > >>
> > > > >> *) I will not further discuss whether that is achieved or not as
> it
> > > seems
> > > > >> irrelevant here.
> > > > >> **) In essence transmission of congestion state via a 1-bit serial
> > > > >> channel, clocked at the (variable***) packet rate at the
> bottleneck.
> > > > >> ***) as packets are not of uniform size
> > > > >>
> > > > >> >
> > > > >> > CSIG sounds to me like something that belongs more in ICCRG or ?
> > > > >> >
> > > > >> > /Ingemar
> > > > >> >
> > > > >> > From: tsvwg <tsvwg-bounces@ietf.org> On Behalf Of Vidhi Goel
> > > > >> > Sent: Wednesday, 13 September 2023 00:59
> > > > >> > To: Shihang(Vincent) <shihang9=40huawei.com@dmarc.ietf.org>
> > > > >> > Cc: Huangyihong (Rachel) <rachel.huang=
> 40huawei.com@dmarc.ietf.org
> > > >;
> > > > >> Tom Herbert <tom=40herbertland.com@dmarc.ietf.org>; Abhiram Ravi
> > > > >> <abhiramr=40google.com@dmarc.ietf.org>; IETF IPPM WG <
> ippm@ietf.org>;
> > > > >> tsvwg <tsvwg@ietf.org>; ccwg@ietf.org; iccrg@irtf.org; Nandita
> > > Dukkipati
> > > > >> <nanditad@google.com>; Naoshad Mehta <naoshad@google.com>; Jai
> Kumar
> > > <
> > > > >> jai.kumar@broadcom.com>
> > > > >> > Subject: Re: [tsvwg] [iccrg] New Internet Draft: Congestion
> > > Signaling
> > > > >> (CSIG)
> > > > >> >
> > > > >> > Not sure why we are coming up with so many new techniques when
> ECN
> > > just
> > > > >> works fine.
> > > > >> > ECN is a 2 bit field (not 1 bit) and seems to be sufficient to
> > > indicate
> > > > >> extent of congestion by marking it per packet. Adding more
> complexity
> > > to
> > > > >> any layer whether it is L2 or L3 doesn?t work well in deployments.
> > > Our goal
> > > > >> should be to simplify things and only add new headers if
> absolutely
> > > > >> necessary.
> > > > >> >
> > > > >> > Vidhi
> > > > >> >
> > > > >> >
> > > > >> > On Sep 12, 2023, at 3:12 AM, Shihang(Vincent) <shihang9=
> > > > >> 40huawei.com@dmarc.ietf.org> wrote:
> > > > >> >
> > > > >> > Hi,
> > > > >> > I agree L2 may not be the best choice to carry the congestion
> > > signaling
> > > > >> end-to-end and more bits are needed. We have submitted a draft to
> > > carry the
> > > > >> multi-bits congestion signaling in L3. We call it Advanced ECN.
> See
> > > > >> https://datatracker.ietf.org/doc/draft-shi-ccwg-advanced-ecn/.
> > > > >> >
> > > > >> > Thanks,
> > > > >> > Hang
> > > > >> >
> > > > >> > From: CCWG <ccwg-bounces@ietf.org> On Behalf Of Huangyihong
> > > (Rachel)
> > > > >> > Sent: Tuesday, September 12, 2023 5:41 PM
> > > > >> > To: Tom Herbert <tom=40herbertland.com@dmarc.ietf.org>; Abhiram
> > > Ravi
> > > > >> <abhiramr=40google.com@dmarc.ietf.org>
> > > > >> > Cc: IETF IPPM WG <ippm@ietf.org>; tsvwg <tsvwg@ietf.org>;
> > > ccwg@ietf.org;
> > > > >> iccrg@irtf.org; Nandita Dukkipati <nanditad@google.com>; Naoshad
> > > Mehta <
> > > > >> naoshad@google.com>; Jai Kumar <jai.kumar@broadcom.com>
> > > > >> > Subject: Re: [CCWG] [iccrg] [tsvwg] New Internet Draft:
> Congestion
> > > > >> Signaling (CSIG)
> > > > >> >
> > > > >> > Hi,
> > > > >> >
> > > > >> > I also have the same feeling. Implementing in L2 may be
> difficult
> > > to be
> > > > >> used in e2e transport. Of course it can work well in limited
> domain,
> > > like
> > > > >> DC or HPC clusters. However, I also look for some solutions that
> > > could be
> > > > >> able to go through internet. We have submitted a draft to
> describe the
> > > > >> transport challenges. See
> > > > >>
> > >
> https://datatracker.ietf.org/doc/html/draft-huang-tsvwg-transport-challenges
> > > > >> .
> > > > >> >
> > > > >> > I share the same opinion that the congestion signal is useful
> and
> > > > >> current 1-bit ECN solution is not fully sufficient. But I also
> feel
> > > like
> > > > >> the more straight way is to extend L3, or l4, like update IOAM, to
> > > carry
> > > > >> the information. For L2 solution, it should be developed together
> > > with IEEE
> > > > >> 802.1.
> > > > >> >
> > > > >> > BR?
> > > > >> > Rachel
> > > > >> >
> > > > >> > ???: iccrg <iccrg-bounces@irtf.org> ?? Tom Herbert
> > > > >> > ????: 2023?9?10? 0:10
> > > > >> > ???: Abhiram Ravi <abhiramr=40google.com@dmarc.ietf.org>
> > > > >> > ??: IETF IPPM WG <ippm@ietf.org>; tsvwg <tsvwg@ietf.org>;
> > > ccwg@ietf.org;
> > > > >> iccrg@irtf.org; Nandita Dukkipati <nanditad@google.com>; Naoshad
> > > Mehta <
> > > > >> naoshad@google.com>; Jai Kumar <jai.kumar@broadcom.com>
> > > > >> > ??: Re: [iccrg] [tsvwg] New Internet Draft: Congestion Signaling
> > > (CSIG)
> > > > >> >
> > > > >> > Hi, thanks for draft!
> > > > >> >
> > > > >> > The first thing that stands out to me is the carrier of the new
> > > packet
> > > > >> headers. In the forward path it would be in L2 and in reflection
> it
> > > would
> > > > >> be L4. As the draft describes, this would entail having to
> support the
> > > > >> protocol in multiple L2 and multiple L4 protocols-- that's going
> to
> > > be a
> > > > >> pretty big lift! Also, L2 is not really an end-to-end protocol
> (would
> > > > >> legacy switches in the path also forward the header)l?).
> > > > >> >
> > > > >> > The signaling being described in the draft is network layer
> > > > >> information, and hence IMO should be conveyed in network layer
> > > headers.
> > > > >> That's is L3 which conveniently is the average of L2+L4 :-)
> > > > >> >
> > > > >> > IMO, the proper carrier of the signal data is Hop-by-Hop
> Options.
> > > This
> > > > >> is end-to-end and allows modification of data in-flight. The
> typical
> > > > >> concern with Hop-by-Hop Options is high drop rates on the
> Internet,
> > > however
> > > > >> in this case the protocol is explicitly confined to a limited
> domain
> > > so I
> > > > >> don't see that as a blocking issue for this use case.
> > > > >> >
> > > > >> > The information being carried seems very similar to that of IOAM
> > > (IOAM
> > > > >> uses Hop-by-Hop Options and supports reflection). I suppose the
> > > differences
> > > > >> are that this protocol is meant to be consumed by the transport
> Layer
> > > and
> > > > >> the data is a condensed summary of path characteristics. IOAM
> seems
> > > pretty
> > > > >> extensible, so maybe it could be adapted to carry the signals of
> this
> > > draft?
> > > > >> >
> > > > >> > A related proposal might be FAST draft-herbert-fast. Where the
> CSIG
> > > is
> > > > >> network to host signaling, FAST is host to network signaling for
> the
> > > > >> purposes of requesting network services. These might be
> complementary
> > > and
> > > > >> options for both may be in the same packet. FAST also uses
> > > reflection, so
> > > > >> we might be able to leverage some common implementation at a
> > > destination.
> > > > >> >
> > > > >> > Tom
> > > > >> >
> > > > >> > On Fri, Sep 8, 2023, 7:43 PM Abhiram Ravi <abhiramr=
> > > > >> 40google.com@dmarc.ietf.org> wrote:
> > > > >> > Hi IPPM folks,
> > > > >> >
> > > > >> > I am pleased to announce the publication of a new internet
> draft,
> > > > >> Congestion Signaling (CSIG):
> > > > >> https://datatracker.ietf.org/doc/draft-ravi-ippm-csig/
> > > > >> >
> > > > >> > CSIG is a new end-to-end packet header mechanism for in-band
> > > signaling
> > > > >> that is simple, efficient, deployable, and grounded in concrete
> use
> > > cases
> > > > >> of congestion control, traffic management, and network
> debuggability.
> > > We
> > > > >> believe that CSIG is an important new protocol that builds on top
> of
> > > > >> existing in-band network telemetry protocols.
> > > > >> >
> > > > >> > We encourage you to read the CSIG draft and provide your
> feedback
> > > and
> > > > >> comments. We have also cc'd the TSVWG, CCWG, and ICCRG mailing
> lists,
> > > as we
> > > > >> believe that this work may be of interest to their members as
> well.
> > > > >> >
> > > > >> > Thank you for your time and consideration.
> > > > >> >
> > > > >> > Sincerely,
> > > > >> > Abhiram Ravi
> > > > >> > On behalf of the CSIG authors
> > > > >>
> > > > >>
> > > > >
> > > > > --
> > > > > Abhiram Ravi
> > > > > --
> > > > > CCWG mailing list
> > > > > CCWG@ietf.org
> > > > > https://www.ietf.org/mailman/listinfo/ccwg
> > > > >
> > >
> > > --
> > > Rod Grimes
> > > rgrimes@freebsd.org
> > >
>
> --
> Rod Grimes
> rgrimes@freebsd.org
>


-- 
Abhiram Ravi