IETF Logo Mail Archive

Re: [tsvwg] UDP options and header-data split (zero copy)

Joseph Touch <touch@strayalpha.com> Sat, 31 July 2021 18:34 UTC

Return-Path: <touch@strayalpha.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 113623A140A for <tsvwg@ietfa.amsl.com>; Sat, 31 Jul 2021 11:34:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.318
X-Spam-Level:
X-Spam-Status: No, score=-1.318 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QcXdBOIBD-_3 for <tsvwg@ietfa.amsl.com>; Sat, 31 Jul 2021 11:34:06 -0700 (PDT)
Received: from server217-4.web-hosting.com (server217-4.web-hosting.com [198.54.116.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 690353A1409 for <tsvwg@ietf.org>; Sat, 31 Jul 2021 11:34:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Subject:Mime-Version:Content-Type:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=VhPLs7TT4BZYTGuB4UWPaXSI/jkV7qlshhgSpepDHi0=; b=0Nwt1davQz1kTefFvkZgJjbKis 2UHhrvlh1WEjrgDMqOeWTXIJSGYG+McAJUatHdgnlSBQeODEd2m1hn4Q8xETX36KsKFmFA2lvekdJ IUSvyOVkCzN+48IwH9TioKcl/nBfSNFOoSrgoH5aVl9rVP+EeAjjxHAs4/ytWKuYY/1MGSHxlYGWd /7SjCqYBibi7doeFT2RBxlLuDdu+BCl7JHAfMH7shUuvWrqKWaKzmtcg2HhgJ22hOyK8acGpP/SFW LjlFX4f3Ctt9f97ZJFcQgKcemYTtSZjppu4D0w3j4d+rwHqTWDM+RkdpquB3SdXgYDxx/V/IquSlg ccsgW67g==;
Received: from cpe-172-114-237-88.socal.res.rr.com ([172.114.237.88]:62099 helo=smtpclient.apple) by server217.web-hosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <touch@strayalpha.com>) id 1m9to8-001oYT-Fa; Sat, 31 Jul 2021 14:34:05 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_90DFB7D0-F01D-4229-8094-D4664B640789"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Joseph Touch <touch@strayalpha.com>
In-Reply-To: <CALx6S35VyMOdxKLxXzLhPJu6qDK8o8-+SgeV=u89bM3j9BeTSQ@mail.gmail.com>
Date: Sat, 31 Jul 2021 11:33:59 -0700
Cc: tsvwg <tsvwg@ietf.org>
Message-Id: <0BB5684B-C164-4CA4-9208-185FEEECB4D6@strayalpha.com>
References: <CALx6S37zzaZaWNygGt=YaZSAo1e5fTgqmi0ftK4q+puCfbXWGg@mail.gmail.com> <6073AC0D-C32A-4033-BC92-F828BA50BDF7@strayalpha.com> <CALx6S37Nf4U=6aGf7ov_7+UULzuD-DPP+gJzLyJ0vKxRELtLCQ@mail.gmail.com> <3CCB787D-CD9F-4380-9544-F5FEAFAF3E27@strayalpha.com> <CALx6S36pRhJFHnhh58tUabeoc8ScajfUYV1HOg=tPJvic8bJ9Q@mail.gmail.com> <CF65CA93-768D-4070-818F-8DA2D08F5BC3@strayalpha.com> <CALx6S36o8RR3v29A4fEp94O6qwpwU6PUAAAEgVMZidbQS3RvLw@mail.gmail.com> <7AAB2648-3789-44B6-A07F-DA9031AAC9A2@strayalpha.com> <CALx6S35VyMOdxKLxXzLhPJu6qDK8o8-+SgeV=u89bM3j9BeTSQ@mail.gmail.com>
To: Tom Herbert <tom@herbertland.com>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/tzGFC9PWZGdRP0ube6Kyk0fLAPc>
Subject: Re: [tsvwg] UDP options and header-data split (zero copy)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 31 Jul 2021 18:34:11 -0000

Hi, Tom,

> On Jul 31, 2021, at 11:27 AM, Tom Herbert <tom@herbertland.com> wrote:
> 
> Joe,
> 
> You seem to be missing my point. There are implementations that
> terminate UDP and CANNOT process protocol trailers; this is not just
> an inconvenient performance degradation.

If that is the case, then they MUST NOT try to support UDP options. See below.

> Yes, that means that they
> can't use legacy mode, but I don't see the technical argument that UDP
> couldn't be productively supported by these implementations if UDP
> options are all contained in headers.

Again, support for legacy receivers has always been a requirement of a solution.

> I do not believe this is an
> aberration, we know for instance there are HW routers terminating UDP
> tunnels, and it would be a delusion to believe these implementations
> could be fixed to support protocol trailers in a finite time. So if
> protocol trailers are a forced requirement, even in non-legacy mode
> which is what tunnels would use anyway since they're configured, it
> seems like we're excluding use cases such as UDP tunnels where UDP
> options might be compelling. Given this, what is your answer to
> someone who wants to use UDP options with UDP tunnels?


There’s no way that endpoint can ensure it never sees non-fragment UDP options, so it cannot support UDP options.

Joe

v2.35.0 | Report a Bug | By Email | System Status