Re: [tsvwg] I-D Action: draft-ietf-tsvwg-udp-options-31.txt

Dan Wing <danwing@gmail.com> Wed, 06 March 2024 04:03 UTC

Return-Path: <danwing@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 CBE4FC14F618 for <tsvwg@ietfa.amsl.com>; Tue, 5 Mar 2024 20:03:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, 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 4vKlQ4OdD3xt for <tsvwg@ietfa.amsl.com>; Tue, 5 Mar 2024 20:03:07 -0800 (PST)
Received: from mail-pf1-x435.google.com (mail-pf1-x435.google.com [IPv6:2607:f8b0:4864:20::435]) (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 E4DD4C14F60F for <tsvwg@ietf.org>; Tue, 5 Mar 2024 20:03:07 -0800 (PST)
Received: by mail-pf1-x435.google.com with SMTP id d2e1a72fcca58-6da9c834646so5866634b3a.3 for <tsvwg@ietf.org>; Tue, 05 Mar 2024 20:03:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1709697787; x=1710302587; darn=ietf.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=n3bvvMg+5fJudINGMqE3U7OzPXvZOcfFQbDEmfHchv0=; b=NtLgAwOomauZCGrxpLPXtNz01l47Y6yO3jRWWvzRZm+xntriJ58rC37eFej7LzOjih Tj+7ok8Eu/5If4GRUwV1QZ/Cb9V8ISqj3Ua4RVTdcRVBBhCWccf57b72Vwn7niRaDC9L xy1BnVGktGcVYTPGSF/Pqexd9raaAR8drwAoRX4jYzj/zaXGjOVfyY6f+9aw/PadVfmD YP9qR9h02NiczsXTxkMbg4fOR8O08KcvVNYle7bExqtjcYAYqXE/rff06+wprCKpMrMR HjnR89/8XrKZGTBdIdzQ97aIv2tK3CBj2wnjY/YmabrV6B2/w+iBBR2U6twK2hnEwTJ/ Ow6A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709697787; x=1710302587; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=n3bvvMg+5fJudINGMqE3U7OzPXvZOcfFQbDEmfHchv0=; b=a8tTOtzkdMRBSW635P3Eckdwx8rGEJmfd3zNQJ3vZ+csSYZ8f/uGQ4rimHX18qC8B9 v+YoxBrp/pNYp5ffiLLIUR8W+fdu+gpAaI5kIw77L+JUhf6BONWd1BeKsn0U/TWFGRx1 oT51JMJuDV5uEq71yVex+fWOi4KUup6wDbd1psIWQwplpSunEkckq0oIZLrz56MgYcZh xZ1gTNpgL0/kW8yHVvtm4a14DDi6BrRC8P4rPhQIAdwzuivDKoPNIFJxlPk4XSS31yVF 4EMdmJ0atV6BYyESr7Yp8B5XuUo92jBhzQLYKJr+9uo28Hj+RckUGf1UTK+mQtx1ffe5 aMfQ==
X-Gm-Message-State: AOJu0Yz3cugsUdg+j1l13bbGpc7yHKhNeSR03QbWzTB2PoISh3QjBlw2 yJEth1jtWEH2HE5bNNLtghiiL5olepl31pYYzUkd6uOgQyjZC5w4EP515PGTVwo=
X-Google-Smtp-Source: AGHT+IHAl2LSpN9WZCA2P1TpsYryhMT4JD4MmYV1iLwXaHDdLFfFyIX9+MPIfojLiqwWmyqXiMEVJw==
X-Received: by 2002:a05:6a00:acb:b0:6e6:1867:89ae with SMTP id c11-20020a056a000acb00b006e6186789aemr10667700pfl.19.1709697786653; Tue, 05 Mar 2024 20:03:06 -0800 (PST)
Received: from smtpclient.apple ([47.208.219.53]) by smtp.gmail.com with ESMTPSA id s62-20020a625e41000000b006e612df4627sm5124917pfb.39.2024.03.05.20.03.05 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 05 Mar 2024 20:03:05 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.400.31\))
From: Dan Wing <danwing@gmail.com>
In-Reply-To: <CALx6S36KofxYq1H1iiUG-rSgEAZ+XSqB4S5A_9jaRbUMUy_wEg@mail.gmail.com>
Date: Tue, 05 Mar 2024 20:03:04 -0800
Cc: tsvwg <tsvwg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <13229860-692D-45BC-A6EE-3268E874555C@gmail.com>
References: <170959656644.33419.9287184380133878464@ietfa.amsl.com> <CALx6S36KofxYq1H1iiUG-rSgEAZ+XSqB4S5A_9jaRbUMUy_wEg@mail.gmail.com>
To: Tom Herbert <tom=40herbertland.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3774.400.31)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/9ItVXj7IvqqtOfNZ8c0YAhii6V4>
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-udp-options-31.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Mar 2024 04:03:09 -0000

In UDP, the only place I have seen this is TFTP, and SIP over UDP (for NATting as part of the ill-advised "ALG" that is widely available)  which is non-standard and BOOTP/DHCP (for DHCP relaying across broadcast domains) which is standard (RFC3046).  Perhaps there are others, but if so I agree it's a tiny, tiny set of IETF standards that allow or encourage modification of UDP payloads.

-d


> On Mar 5, 2024, at 5:57 PM, Tom Herbert <tom=40herbertland.com@dmarc.ietf.org> wrote:
> 
> Hi,
> 
> I don't understand the intent of this new text:
> 
> "Another reason is because APC may fail even where the user data has
> not been corrupted, such as when its contents have been overwritten.
> Such overwrites could be intentional and not widely known; defaulting
> to silent ignore ensures that option-aware endpoints do not change how
> users or applications operate unless explicitly directed to do
> otherwise."
> 
> I am not familiar with any IETF protocol that allows UDP payload to be
> updated in flight. In fact, RFC7605 states that UDP port numbers
> cannot be correctly interpreted in the network, so there is no way to
> implement a robust protocol that changes UDP payload inflight. Because
> of this, an intermediate node that is overwriting the UDP payload *is*
> in fact corrupting the UDP payload. So this new provision is seemingly
> accommodating this non-standard, potentially harmful behavior as the
> default.
> 
> Tom
> 
> On Mon, Mar 4, 2024 at 3:56 PM <internet-drafts@ietf.org> wrote:
>> 
>> Internet-Draft draft-ietf-tsvwg-udp-options-31.txt is now available. It is a
>> work item of the Transport and Services Working Group (TSVWG) WG of the IETF.
>> 
>>   Title:   Transport Options for UDP
>>   Author:  Joe Touch
>>   Name:    draft-ietf-tsvwg-udp-options-31.txt
>>   Pages:   52
>>   Dates:   2024-03-04
>> 
>> Abstract:
>> 
>>   Transport protocols are extended through the use of transport header
>>   options. This document extends UDP by indicating the location,
>>   syntax, and semantics for UDP transport layer options.
>> 
>> The IETF datatracker status page for this Internet-Draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-udp-options/
>> 
>> There is also an HTMLized version available at:
>> https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-udp-options-31
>> 
>> A diff from the previous version is available at:
>> https://author-tools.ietf.org/iddiff?url2=draft-ietf-tsvwg-udp-options-31
>> 
>> Internet-Drafts are also available by rsync at:
>> rsync.ietf.org::internet-drafts
>> 
>> 
>