[tsvwg] Re: New Version Notification for draft-duke-tsvwg-udp-ecn-00.txt

Martin Duke <martin.h.duke@gmail.com> Mon, 26 August 2024 20:46 UTC

Return-Path: <martin.h.duke@gmail.com>
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 C533AC1CAE8D; Mon, 26 Aug 2024 13:46:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 2AQU06RwpJ_x; Mon, 26 Aug 2024 13:46:58 -0700 (PDT)
Received: from mail-vk1-xa36.google.com (mail-vk1-xa36.google.com [IPv6:2607:f8b0:4864:20::a36]) (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 19BCCC15108A; Mon, 26 Aug 2024 13:46:58 -0700 (PDT)
Received: by mail-vk1-xa36.google.com with SMTP id 71dfb90a1353d-4fce6fd54ebso1691618e0c.1; Mon, 26 Aug 2024 13:46:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1724705217; x=1725310017; 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=SFTdModl+YqaMZNAkRbh68KuczHMr0B/97yJWBxTo6A=; b=LdL4g4sMGPi2mFOZThyGXhkXVGo3UtSou5pOG6LzrQkh8/pbW0gD7Q6YAAi8ywa/Mj GX6n0QX9EutyswoRWl2pACG0bmvj99i7HcOCkEFopgcobpfPuj6wN+C3+G/57ZEIjxWh bPUgkm+Fmdvax+F176KQdx6pt6Kdj2fM4sfSts1wLTNnra9NvgZfR523kJkl+hNnjTlu NZn2ve2FxqzhP877SKeJIgg1cTR+meRQ+IF8jjRMb7A4KzH2dBg12uZVRLwpB8IqZKNh c5fCiSjd7/1N8kVN9snwkMeD3eKqm/EZwh4ZgrMbzjQKC66HF9LA9og8QIawkiNhpiSv j2uw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724705217; x=1725310017; 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=SFTdModl+YqaMZNAkRbh68KuczHMr0B/97yJWBxTo6A=; b=HXgued/UMhhPRIe5fUzSINxDqbZ+8dvN4WzrVc1ArFx2uBgJSyg6/ZCfDAdZYAwSQS 4aYbWZsK/xlv3Sq+mzsuxYqWBwSQxcf990IKMfZejXkGkd+JctzQq5RPz9VJMHZC6zyM IRwPETPyOpeuagP3lmUiiwtlZAtZZjGQBy+zWLqvTOayWaoEPphKBCfvQUzXOxRPP4wN 2YtqMfwruXuRXVOCk8G5xhBaV/N9witRwRs4cq0inoTOdVJ+IZK//1pL7Rbfx88uspKr wACAHnAXbmqJUezQCxuQaNMxc4N0nZtr+RsxAYsI712PtBhI2kvMq/dU+mMsE5hm8y0X VQtA==
X-Forwarded-Encrypted: i=1; AJvYcCUOyYAxUH2mT998jFe5Sn2ZJW5mN004LOXcDvB4cqZBUo5B3ZB5ASa6aYL45+XnoUqNJiZn@ietf.org
X-Gm-Message-State: AOJu0YzhOX7DR8i5D0bBsJER0oBHQriyizAU2dKKob7Ciy1+C8F7prEG wDAr8Z/JceNxsV1B7iisDCnSPNOgZETxPZmVmHATIxuUI/QlmCPEV2spZ/bakmpn65X7L7vQk59 yH0Eg2CIydMqjglBFfGhdasTE4HQYvg==
X-Google-Smtp-Source: AGHT+IGluww4eEdSPxMAZlzE3Sch59/+ZZSE1pzaHeDabIctF1bmGoYyCD8mhiUB9IK9VxYb8HfqhfFvRHIbEoqE4TI=
X-Received: by 2002:a05:6122:2015:b0:4f6:b240:4af8 with SMTP id 71dfb90a1353d-4fd1acc9d4fmr14395277e0c.11.1724705216763; Mon, 26 Aug 2024 13:46:56 -0700 (PDT)
MIME-Version: 1.0
References: <172444161279.128198.6556076320862990924@dt-datatracker-584cd6c8dd-fvr2f> <CAM4esxRNbWKq3X-0HQmasDhozP5WR1AcJnczdLTgKbrMF4XXAA@mail.gmail.com>
In-Reply-To: <CAM4esxRNbWKq3X-0HQmasDhozP5WR1AcJnczdLTgKbrMF4XXAA@mail.gmail.com>
From: Martin Duke <martin.h.duke@gmail.com>
Date: Mon, 26 Aug 2024 13:46:42 -0700
Message-ID: <CAM4esxQMba8gZ7pMkPKb7TjpamO20oA+m0Kbu=hzKv+Ex+WjFw@mail.gmail.com>
To: tsvwg <tsvwg@ietf.org>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c99cfd06209c39ae"
Message-ID-Hash: 3SM3AJYFGGSCTPYEELZDKO5TEWQMUEHN
X-Message-ID-Hash: 3SM3AJYFGGSCTPYEELZDKO5TEWQMUEHN
X-MailFrom: martin.h.duke@gmail.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
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [tsvwg] Re: New Version Notification for draft-duke-tsvwg-udp-ecn-00.txt
List-Id: Transport Area Working Group <tsvwg.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/rrKQNCsJKLCB-yxzNNXwBbeVblo>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Owner: <mailto:tsvwg-owner@ietf.org>
List-Post: <mailto:tsvwg@ietf.org>
List-Subscribe: <mailto:tsvwg-join@ietf.org>
List-Unsubscribe: <mailto:tsvwg-leave@ietf.org>

Thanks to everyone who's provided feedback! I hope to publish draft-01 soon.

 I have a strange question: does it ever make any sense to bind or connect
to an IPv4-mapped IPv6 address (i.e. ::ffff:<Ipv4_address>)? I've been
experimenting with this, and the results are sometimes goofy for each
platform. Is this even worth addressing in the draft, or is it too silly of
a use case?

On Fri, Aug 23, 2024 at 12:39 PM Martin Duke <martin.h.duke@gmail.com>
wrote:

> Hi TSVWG and QUIC,
>
> I've made it some of the way through implementing receive ECN for
> Chromium, which involved quite a bit of trial and error in figuring out the
> quirks of the Apple and Windows UDP socket APIs.
>
> This is an informational draft that tries to capture some of that
> learning, since hopefully more QUIC implementations will add ECN support
> across multiple platforms.
>
> Obviously, this is a work in progress. People that have worked with other
> OSes, or that can see into the kernel code and update/correct/refute some
> of my statements here, are welcome to contribute.
>
> My guess is that it fits into TSVWG, although it is mostly of relevance to
> QUIC folks. If people are really interested in it, we could adopt it TSVWG.
> If not, at least there's a record somewhere so that others don't have to
> suffer as I did.
>
> Martin
>
> ---------- Forwarded message ---------
> From: <internet-drafts@ietf.org>
> Date: Fri, Aug 23, 2024 at 12:33 PM
> Subject: New Version Notification for draft-duke-tsvwg-udp-ecn-00.txt
> To: Martin Duke <martin.h.duke@gmail.com>
>
>
> A new version of Internet-Draft draft-duke-tsvwg-udp-ecn-00.txt has been
> successfully submitted by Martin Duke and posted to the
> IETF repository.
>
> Name:     draft-duke-tsvwg-udp-ecn
> Revision: 00
> Title:    Configuring UDP Sockets for ECN for Common Platforms
> Date:     2024-08-23
> Group:    Individual Submission
> Pages:    9
> URL:      https://www.ietf.org/archive/id/draft-duke-tsvwg-udp-ecn-00.txt
> Status:   https://datatracker.ietf.org/doc/draft-duke-tsvwg-udp-ecn/
> HTMLized: https://datatracker.ietf.org/doc/html/draft-duke-tsvwg-udp-ecn
>
>
> Abstract:
>
>    Explicit Congestion Notification (ECN) applies to all transport
>    protocols in principle.  However, it had limited applications for UDP
>    until QUIC became widely deployed.  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.
>
>
>
> The IETF Secretariat
>
>
>