Re: [tsvwg] I-D Action: draft-ietf-tsvwg-udp-options-31.txt
Tom Herbert <tom@herbertland.com> Wed, 06 March 2024 01:57 UTC
Return-Path: <tom@herbertland.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 686CBC14CF0D for <tsvwg@ietfa.amsl.com>; Tue, 5 Mar 2024 17:57:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.106 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, RCVD_IN_DNSWL_HI=-5, 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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=herbertland.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 PD2pFU3zf9np for <tsvwg@ietfa.amsl.com>; Tue, 5 Mar 2024 17:57:47 -0800 (PST)
Received: from mail-ed1-x534.google.com (mail-ed1-x534.google.com [IPv6:2a00:1450:4864:20::534]) (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 53C7EC151075 for <tsvwg@ietf.org>; Tue, 5 Mar 2024 17:57:47 -0800 (PST)
Received: by mail-ed1-x534.google.com with SMTP id 4fb4d7f45d1cf-565d1656c12so655989a12.1 for <tsvwg@ietf.org>; Tue, 05 Mar 2024 17:57:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland.com; s=google; t=1709690265; x=1710295065; darn=ietf.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=oJq9QmUmKzyKAtmvtE9pg7oEyH1FiZh8xWNJdFSBlpg=; b=XPz5+LSgoMDBZlTHqyC9VtEnkvtRXHZfQylZk5UMxExPFjJZHjNN3BS2sQ9CbfBq52 djJAS90XAuhp10gMBbUPpus44/Wca4iSIrMfjiAqOlnUPdlAoqX07lpZTh9BeN81lGTC WxSa7LD6qW8qkJ/k6OPr4TWYfnmA4si5onzfs/H6OFnhrFI3cV/+5FV9HgXpas+OnGQC O+Vkwg8nExzeC/gDtfEsbelQA9Dw9Zw734pvd+eWPOBXJkj09H84HtUZqIoCyt3zi7gs jH1iBPvTmdiM5YvRvpDAXUodDBnQjAkHK9KkkbszwGYZ9L0YicmWvyagtYROeyV6H111 gCJA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709690265; x=1710295065; h=content-transfer-encoding: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=oJq9QmUmKzyKAtmvtE9pg7oEyH1FiZh8xWNJdFSBlpg=; b=aTEkhcZoTPN/tm5D2s6aUUES0zkAjcgCuEEx9pdCe2FATpd3UYmTg/n1b3j3e/KFlB T11/qCxuJFDaIRIKrrDyyxUO8OoaY10w812WSrLSfoz0TwSYFptyDs4gULnJrB6iJ4/U fZZlzUqzEbeV+X5eF742RdFss1WgRf4400HBh8eSwRXC/sRoKc5cPwCEiKIUNBzAVntY nqLfLniizQ/NCXzd9GMkk7jQQrO8sd3OVVI39mVmZGk5M2XGTKVDc9x5xNLq1QlpC65z 379UBP3wgcajPsHI+g3Phtfi2bro0r5erUFLVvRtvpZFYKVxtBejjFrDk4rvpDOEkaxY PSSg==
X-Gm-Message-State: AOJu0YyzOZIvrRtlNMvy7KNpLavBChYD5CYSI1fEjXHfvxraneNL63Rb XTFXn7/sLPd9/LAk6T8K0311g04ONeBVvMLFEAks16O1zwgb5zAGxnycS51E/8k6axDYy1H9wJQ HbcT0Oqngqii/+MFZsw8nuvAxMw1txaXDrZ60x+1wjRHgZYTO4w==
X-Google-Smtp-Source: AGHT+IE+n6gIGpVxGferVKWkHraINTuz3VTzB524JLihbKGor6yeOCm/f2l9GDFHZgwfeqMoNlzWoB5PtHV4f5UL7vs=
X-Received: by 2002:a50:8dcb:0:b0:567:e0e:dda5 with SMTP id s11-20020a508dcb000000b005670e0edda5mr4482050edh.17.1709690265286; Tue, 05 Mar 2024 17:57:45 -0800 (PST)
MIME-Version: 1.0
References: <170959656644.33419.9287184380133878464@ietfa.amsl.com>
In-Reply-To: <170959656644.33419.9287184380133878464@ietfa.amsl.com>
From: Tom Herbert <tom@herbertland.com>
Date: Tue, 05 Mar 2024 17:57:33 -0800
Message-ID: <CALx6S36KofxYq1H1iiUG-rSgEAZ+XSqB4S5A_9jaRbUMUy_wEg@mail.gmail.com>
To: tsvwg@ietf.org
Cc: i-d-announce@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/jZW_s1UdjUjgR41q9_FgfGbLC74>
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 01:57:51 -0000
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 > >
- [tsvwg] I-D Action: draft-ietf-tsvwg-udp-options-… internet-drafts
- Re: [tsvwg] I-D Action: draft-ietf-tsvwg-udp-opti… Tom Herbert
- Re: [tsvwg] I-D Action: draft-ietf-tsvwg-udp-opti… Dan Wing
- Re: [tsvwg] I-D Action: draft-ietf-tsvwg-udp-opti… C. M. Heard
- Re: [tsvwg] I-D Action: draft-ietf-tsvwg-udp-opti… touch@strayalpha.com
- Re: [tsvwg] I-D Action: draft-ietf-tsvwg-udp-opti… Tom Herbert
- Re: [tsvwg] I-D Action: draft-ietf-tsvwg-udp-opti… Gorry (erg)
- Re: [tsvwg] I-D Action: draft-ietf-tsvwg-udp-opti… C. M. Heard
- Re: [tsvwg] I-D Action: draft-ietf-tsvwg-udp-opti… touch@strayalpha.com
- Re: [tsvwg] I-D Action: draft-ietf-tsvwg-udp-opti… Tom Herbert
- Re: [tsvwg] I-D Action: draft-ietf-tsvwg-udp-opti… C. M. Heard
- Re: [tsvwg] I-D Action: draft-ietf-tsvwg-udp-opti… Tom Herbert