Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 538D3C1DA1E0 for ; Wed, 13 Nov 2024 05:45:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.605 X-Spam-Level: X-Spam-Status: No, score=-17.605 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_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, 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 Cwj3XTeu3kq7 for ; Wed, 13 Nov 2024 05:45:22 -0800 (PST) Received: from mail-qt1-x82c.google.com (mail-qt1-x82c.google.com [IPv6:2607:f8b0:4864:20::82c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 79F1CC1D6FD1 for ; Wed, 13 Nov 2024 05:45:22 -0800 (PST) Received: by mail-qt1-x82c.google.com with SMTP id d75a77b69052e-4608dddaa35so275091cf.0 for ; Wed, 13 Nov 2024 05:45:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20230601; t=1731505521; x=1732110321; 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=902C4s5qtuzub+/oSB4/17XNgzrWPK+Tvjy8DTq+3Xw=; b=jj4w1xUBJy6jizIUS+pjupZKDjbXiyibG60MVhyDSRB4Xno6ecqxZXavDgqdbQDRfj isy2mrVKVQnmajkaaj+Otg0X4Aeq0Q/eVrwHjwDsrFHtCjgTpaJav8JPhyT1B9ragDgS BH58gBBM8kLZLSLHOKnRFhvoqrfehJaAT9R+XddLR3V9s8Tcq2r9kcXEXMeFpQD6gNJz Xmq4HYpRp2qvyKSU3LLlNF353J+KJj2otRQQN1hRaQDoUsBVCbtwwn4bem1kzjPEC4Tj JM4NMYfxe43BOzYUr3heOKzEjqY5TKE0fKtJ0Gng0wdx5xszVkgHEv5oydyFbyuPEm29 zLyQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1731505521; x=1732110321; 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=902C4s5qtuzub+/oSB4/17XNgzrWPK+Tvjy8DTq+3Xw=; b=B6nfxeZTFE851wiP/3hG/2UNpmmZWkrnFI6rX1E/g8p0JuMzQNxmIacpDhKNmlqVKm BKbtRtnbtR07kRPs1bKj239ToWDMeKufOAsTOjBxfgXuvs2TCfA6n2Y0Ib4+IlrZpXPF 3jvol2FeR0DRy8ijOBzjQbwqBrv/NsJfr5it7oN8i3sELSrHTukJHhLmzOzKVYWosbtH Iq1Qhru5IagzNjxkMoKq1sCCKw9foHpJQWIOUnAx/SOpny2OTZSXuoPxxyILZT0E26Fo 26PcUYfVhpihZkYGKYAS0r8i5UYjPIVSBmcfABCH2tvolXgP3gu4B7jT2mLAVMs3/8Z3 Ou6A== X-Forwarded-Encrypted: i=1; AJvYcCV/nlnjt+rjybK072gQXHs93mE5EoREVqUJN1Ixb+pyASP2n2cMOJ/T8OXiPQ1Xc7//8Gb+zA==@ietf.org X-Gm-Message-State: AOJu0YyF3JgrFIs5f3G7TekXjOIUwmTbQQT5rmXn6tq9t0Do2qyIP4LP g8kW9qtOiWeMXlKO3LrCPtgTKr4AfeECO6AZYtbEZRanrqacwi0eX9WkhmbrQG6jJYlacPvb+kE lHRbjOubObUbNbIr+QO65zOk9ltNZJ+p/DBNLxEedESni98IDCL0lQKI= X-Gm-Gg: ASbGncvQ6N3sBkoSiBzxaYWbCKciahQuGrRU8dRMDMjxc4KT9EDIaZy7V/+ZpBUUBxm NkJMB3HptkCNBeH7nlw4YoM2/CbE+JZ9LMM313Z11J56REp47l1f/Y3fUBnN+1Fl+ X-Google-Smtp-Source: AGHT+IGIaNAFanYWLEDwgZ/YoVVr9GGciFuHVZ4F5vGd0tOAGI1rmx5OYGGwBAWWCbIxxrcBskRSSDFVEISZHBdGZbA= X-Received: by 2002:ac8:58c8:0:b0:461:66ea:ea70 with SMTP id d75a77b69052e-4634caa8e92mr2541941cf.15.1731505521158; Wed, 13 Nov 2024 05:45:21 -0800 (PST) MIME-Version: 1.0 References: <91c89e4a-834e-4450-bcf8-ecc5fc8b7f03@erg.abdn.ac.uk> In-Reply-To: From: Neal Cardwell Date: Wed, 13 Nov 2024 08:45:04 -0500 Message-ID: To: Ingemar Johansson S Content-Type: multipart/alternative; boundary="0000000000008457c80626cb8b2d" Message-ID-Hash: QDVFSNSUPQQFJLWZL3CJWXSHYL2P7TNU X-Message-ID-Hash: QDVFSNSUPQQFJLWZL3CJWXSHYL2P7TNU X-MailFrom: ncardwell@google.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tsvwg.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: Gorry Fairhurst , "tsvwg@ietf.org" X-Mailman-Version: 3.3.9rc6 Precedence: list Subject: =?utf-8?q?=5Btsvwg=5D_Re=3A_TSVWG_Adoption_Call_for_draft-duke-tsvwg-udp-ecn?= =?utf-8?q?-03_as_Informational=2C_ending_on_29th_November_2024?= List-Id: Transport Area Working Group Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --0000000000008457c80626cb8b2d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi all, I support adopting this draft as a basis for work on documenting ECN support for UDP. I agree this is a very important topic, and a topic where more information would be very useful. best regards, neal On Wed, Nov 13, 2024 at 5:53=E2=80=AFAM Ingemar Johansson S wrote: > Hi > > Having fiddled with these ECN bits and in the process trying to dig up th= e > best ways to do it on the internet.... > Yes, I definitely support the adoption of this draft. > > > > /Ingemar Johansson > > > > *From:* Gorry Fairhurst > *Sent:* Wednesday, 13 November 2024 08:57 > *To:* tsvwg@ietf.org > *Subject:* [tsvwg] TSVWG Adoption Call for draft-duke-tsvwg-udp-ecn-03 as > Informational, ending on 29th November 2024 > > > > Hello TSV WG, > > > This is a formal adoption call that will run 2 weeks, ending on 29th > November 2024. Please respond to this email thread with any comments > indicating support or objection to adopting this draft as a basis for > work on ECN support for UDP. > > During IETF-121, the WG discussed "Configuring UDP Sockets for ECN for > Common Platforms" (draft-duke-tsvwg-udp-ecn) and the sense in the room > indicated some support for adoption, this email provides an opportunity > to contribute comments on this planned work. > > Best wishes, > Gorry and Marten > (tsvwg co-chairs) > > > > See: > > https://datatracker.ietf.org/doc/draft-duke-tsvwg-udp-ecn/ > > > > Abstract > > Explicit Congestion Notification (ECN) applies to all transport > > protocols in principle. However, it had limited deployment for UDP > > until QUIC became widely adopted. As a result, documentation of UDP > > socket APIs for ECN on various platforms is sparse. This document > > records the results of experimenting with these APIs in order to get > > ECN working on UDP for Chromium on Apple, Linux, and Windows > > platforms. > > > > > > > --0000000000008457c80626cb8b2d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi all,

I support adopting this draft a= s a basis for work on=C2=A0 documenting ECN support for UDP.

=
I agree this is a very important topic, and a topic where more i= nformation would be very useful.

best regards,
neal


On Wed, Nov 13, 2024 at 5:53=E2=80=AFAM Ing= emar Johansson S <ingemar.s.johansson=3D40ericsson.com@dmarc.ietf.org> wrote:

Hi

Having fiddled with these ECN b= its and in the process trying to dig up the best ways to do it on the inter= net....
Yes, I definitely support the adoption of this draft.<= /p>

=C2=A0

/Ingemar Johansson

=C2=A0

From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Sent: Wednesday, 13 November 2024 08:57
To: tsvwg@ietf.o= rg
Subject: [tsvwg] TSVWG Adoption Call for draft-duke-tsvwg-udp-ecn-03= as Informational, ending on 29th November 2024

=C2=A0

Hello TSV WG,


This is a formal adoption call that will run 2 weeks, ending on 29th
November 2024. Please respond to this email thread with any comments
indicating support or objection to adopting this draft as a basis for
work on ECN support for UDP.

During IETF-121, the WG discussed "Configuring UDP Sockets for ECN for=
Common Platforms" (draft-duke-tsvwg-udp-ecn)=C2=A0 and the sense in th= e room
indicated some support for adoption, this email provides an opportunity to contribute comments on this planned work.

Best wishes,
Gorry and Marten
(tsvwg co-chairs)

=C2=A0

See:

=C2=A0

Abstract

=C2=A0=C2=A0 Explicit Congestion Notification (ECN) applies to all tra=
nsport
=C2=A0=C2=A0 protocols in principle.=C2=A0 However, it had limited dep=
loyment for UDP
=C2=A0=C2=A0 until QUIC became widely adopted.=C2=A0 As a result, docu=
mentation of UDP
=C2=A0=C2=A0 socket APIs for ECN on various platforms is sparse.=C2=A0=
 This document
=C2=A0=C2=A0 records the results of experimenting with these APIs in o=
rder to get
=C2=A0=C2=A0 ECN working on UDP for Chromium on Apple, Linux, and Wind=
ows
=C2=A0=C2=A0 platforms.

=C2=A0

=C2=A0

=C2=A0

--0000000000008457c80626cb8b2d--