[tsvwg] Re: TSVWG Adoption Call for draft-duke-tsvwg-udp-ecn-03 as Informational, ending on 29th November 2024

[Max Franke <[e-mail]>]

I also support adoption of this draft with one minor comment.

„On Apple and FreeBSD hosts, the application only sets the IPPROTO_IPV6-level socket option with name IPV6_RECVTCLASS; setting an IPPROTO_IP-level socket option on an IPv6 socket results in an error. In particular this applies to the IPPROTO_IP-level socket option with the name IP_RECVTOS.“ 

I assume this means that setting IPV6_RECVTCLASS is enough to receive ECN marks on all incoming packets on Apple/FreeBSD. If this is the case this could potentially be stated slightly more clearly as currently it could be understood that you can’t set the v4 option on those socket and thus not receive marks on v4 packets. 

Best,

Max 

Am 13.11.2024 um 15:04 schrieb Marten Seemann <[e-mail]>:



Speaking as an individual, I support adoption of this document.

It would've been very helpful when I implemented ECN support in quic-go.

On Wed, 13 Nov 2024 at 13:47, Neal Cardwell <ncardwell=[e-mail]> wrote:

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 AM Ingemar Johansson S <ingemar.s.johansson=[e-mail]> wrote:

Hi

Having fiddled with these ECN bits and in the process trying to dig up the best ways to do it on the internet....
Yes, I definitely support the adoption of this draft.

 

/Ingemar Johansson

 

From: Gorry Fairhurst <[e-mail]>
Sent: Wednesday, 13 November 2024 08:57
To: [e-mail]
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/" target="_blank" rel="nofollow">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.