Re: [tsvwg] UDP options and header-data split (zero copy)
Joseph Touch <touch@strayalpha.com> Mon, 02 August 2021 01:58 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 CEAE43A0A93 for <tsvwg@ietfa.amsl.com>; Sun, 1 Aug 2021 18:58:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.317
X-Spam-Level:
X-Spam-Status: No, score=-1.317 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, RCVD_IN_DNSWL_BLOCKED=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 gOw5F7PPThYA for <tsvwg@ietfa.amsl.com>; Sun, 1 Aug 2021 18:58:04 -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 4EF8D3A0A92 for <tsvwg@ietf.org>; Sun, 1 Aug 2021 18:58:04 -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=7v3MmVE4U/LN5Av7KPeShHtcs4K/L1wBEwEl0LXdEVk=; b=PdRbtOqSrDY2Wd/jZsje468kao 8MDZcFIcdljYzZKg7SHkB86WklbDApK8Q5fJgvQWnFeX+INmdFLgjoXV2uZw0GzOqK+uBivk9Gzx9 EQLWZJ2HeYo2sP0JwGAp/eJDjdkg2m1GKQJo44SH7yrTkU9jZv0ZHBqAbk1UpY6w/xLcy8yNMFn9f A9QD6Z4hattUwCCicgEGdnpmQ9t+bJ3Kmvh5xzXFVoYmk0ra2Tuc8Sv4zMqC3mRrJzJx+e+YYZhag 9+UG24o2ZUZQUIvDk/bYpoebc3eGLwHUEadfw55WhFCdeiw2YRDZTfIpXYwQrt0Szwea57mDqJgId 2NvDTY0Q==;
Received: from cpe-172-114-237-88.socal.res.rr.com ([172.114.237.88]:51302 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 1mANDK-001e81-VR; Sun, 01 Aug 2021 21:58:03 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_978EE439-63C7-40B4-9B3B-0F6C99D63498"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Joseph Touch <touch@strayalpha.com>
In-Reply-To: <CACL_3VFRfSNsac=a_Jdd6KnoAxDUPNdRKJ5x0FOCUroA3e398A@mail.gmail.com>
Date: Sun, 01 Aug 2021 18:57:57 -0700
Cc: tsvwg <tsvwg@ietf.org>, Michael Tuexen <michael.tuexen@lurchi.franken.de>
Message-Id: <C48D347F-EFE3-4F30-BB71-C6B45996B2C3@strayalpha.com>
References: <058C1360-D1BF-4C15-A0E3-D1C98DC8C45F@lurchi.franken.de> <04C250F8-7C10-4300-862B-7FFD739CA8B3@strayalpha.com> <C65F0BB6-BA2D-49F3-A473-32EEDF6C9467@lurchi.franken.de> <CALx6S36a66Ty6EUa9nRdvSQjaxepA7g1Np5T16iXuoTC3ZCd+g@mail.gmail.com> <48A4AB1F-A5E2-447E-8C20-AEC532269BFD@strayalpha.com> <CALx6S37wXiXhb9arG3BOw8RZUmGSX=a0KKKgS8MhyuKv52T+5Q@mail.gmail.com> <8EF9AB38-202D-4207-BCEA-24D65D208F09@strayalpha.com> <CACL_3VFRfSNsac=a_Jdd6KnoAxDUPNdRKJ5x0FOCUroA3e398A@mail.gmail.com>
To: "C. M. Heard" <heard@pobox.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/QF8UW4dlNDs5dRMIg2XWG-OBh_I>
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: Mon, 02 Aug 2021 01:58:09 -0000
> On Aug 1, 2021, at 6:16 PM, C. M. Heard <heard@pobox.com> wrote: > > On Sun, Aug 1, 2021 at 6:13 PM Joseph Touch wrote: > However, that does not prevent use of UDP fragmentation - which would both be opaque to avoiding IP fragmentation and QUIC, as well as would traverse NATs because of the replicated UDP header in UDP fragments. > > True, but QUIC has its own solutions to that problem. From recollection, the comments I've seen from QUIC proponents is that there is no interest in that quarter in UDP options. Perhaps, but they have no solution to protecting the transport layer header - if that’s something users want. Nor do they have a solution to using more IP option space. Those can’t be solved inside QUIC. Joe
- [tsvwg] UDP options and header-data split (zero c… Tom Herbert
- Re: [tsvwg] UDP options and header-data split (ze… Joseph Touch
- Re: [tsvwg] UDP options and header-data split (ze… Tom Herbert
- Re: [tsvwg] UDP options and header-data split (ze… Paul
- Re: [tsvwg] UDP options and header-data split (ze… Joseph Touch
- Re: [tsvwg] UDP options and header-data split (ze… Tom Herbert
- Re: [tsvwg] UDP options and header-data split (ze… Joe Touch
- Re: [tsvwg] UDP options and header-data split (ze… Sebastian Moeller
- Re: [tsvwg] UDP options and header-data split (ze… Tom Herbert
- Re: [tsvwg] UDP options and header-data split (ze… Joseph Touch
- Re: [tsvwg] UDP options and header-data split (ze… Tom Herbert
- Re: [tsvwg] UDP options and header-data split (ze… Joseph Touch
- Re: [tsvwg] UDP options and header-data split (ze… Tom Herbert
- Re: [tsvwg] UDP options and header-data split (ze… Joseph Touch
- Re: [tsvwg] UDP options and header-data split (ze… Tom Herbert
- Re: [tsvwg] UDP options and header-data split (ze… Tom Herbert
- Re: [tsvwg] UDP options and header-data split (ze… Joe Touch
- Re: [tsvwg] UDP options and header-data split (ze… Tom Herbert
- Re: [tsvwg] UDP options and header-data split (ze… Joseph Touch
- Re: [tsvwg] UDP options and header-data split (ze… C. M. Heard
- Re: [tsvwg] UDP options and header-data split (ze… Joseph Touch
- Re: [tsvwg] UDP options and header-data split (ze… Tom Herbert
- Re: [tsvwg] UDP options and header-data split (ze… Joseph Touch
- Re: [tsvwg] UDP options and header-data split (ze… Tom Herbert
- Re: [tsvwg] UDP options and header-data split (ze… Joseph Touch
- Re: [tsvwg] UDP options and header-data split (ze… Tom Herbert
- Re: [tsvwg] UDP options and header-data split (ze… Joseph Touch
- Re: [tsvwg] UDP options and header-data split (ze… Tom Herbert
- Re: [tsvwg] UDP options and header-data split (ze… Joe Touch
- Re: [tsvwg] UDP options and header-data split (ze… Tom Herbert
- Re: [tsvwg] UDP options and header-data split (ze… Joseph Touch
- Re: [tsvwg] UDP options and header-data split (ze… Joseph Touch
- Re: [tsvwg] UDP options and header-data split (ze… Tom Herbert
- Re: [tsvwg] UDP options and header-data split (ze… Joseph Touch
- Re: [tsvwg] UDP options and header-data split (ze… Tom Herbert
- Re: [tsvwg] UDP options and header-data split (ze… Joseph Touch
- Re: [tsvwg] UDP options and header-data split (ze… C. M. Heard
- Re: [tsvwg] UDP options and header-data split (ze… Tom Herbert
- Re: [tsvwg] UDP options and header-data split (ze… Joseph Touch
- Re: [tsvwg] UDP options and header-data split (ze… Joseph Touch
- Re: [tsvwg] UDP options and header-data split (ze… Tom Herbert
- Re: [tsvwg] UDP options and header-data split (ze… Joe Touch
- Re: [tsvwg] UDP options and header-data split (ze… Joe Touch
- Re: [tsvwg] UDP options and header-data split (ze… Michael Tuexen
- Re: [tsvwg] UDP options and header-data split (ze… Joe Touch
- Re: [tsvwg] UDP options and header-data split (ze… Michael Tuexen
- Re: [tsvwg] UDP options and header-data split (ze… Tom Herbert
- Re: [tsvwg] UDP options and header-data split (ze… Joseph Touch
- Re: [tsvwg] UDP options and header-data split (ze… C. M. Heard
- Re: [tsvwg] UDP options and header-data split (ze… Joseph Touch
- Re: [tsvwg] UDP options and header-data split (ze… C. M. Heard
- Re: [tsvwg] UDP options and header-data split (ze… Tom Herbert
- Re: [tsvwg] UDP options and header-data split (ze… Joseph Touch
- Re: [tsvwg] UDP options and header-data split (ze… C. M. Heard
- Re: [tsvwg] UDP options and header-data split (ze… Tom Herbert
- Re: [tsvwg] UDP options and header-data split (ze… Tom Herbert
- Re: [tsvwg] UDP options and header-data split (ze… Joseph Touch
- Re: [tsvwg] UDP options and header-data split (ze… Joseph Touch
- Re: [tsvwg] UDP options and header-data split (ze… Tom Herbert
- Re: [tsvwg] UDP options and header-data split (ze… C. M. Heard
- Re: [tsvwg] UDP options and header-data split (ze… Sebastian Moeller
- Re: [tsvwg] UDP options and header-data split (ze… C. M. Heard
- Re: [tsvwg] UDP options and header-data split (ze… Joe Touch
- Re: [tsvwg] UDP options and header-data split (ze… Joe Touch
- Re: [tsvwg] UDP options and header-data split (ze… C. M. Heard
- Re: [tsvwg] UDP options and header-data split (ze… Joe Touch
- Re: [tsvwg] UDP options and header-data split (ze… C. M. Heard
- Re: [tsvwg] UDP options and header-data split (ze… Joe Touch