Re: [tsvwg] A review of draft-ietf-tsvwg-udp-options-12

Paul Vixie <paul@redbarn.org> Sun, 13 June 2021 22:56 UTC

Return-Path: <vixie@redbarn.org>
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 10FF03A1330 for <tsvwg@ietfa.amsl.com>; Sun, 13 Jun 2021 15:56:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 5t-yTqFvuJB9 for <tsvwg@ietfa.amsl.com>; Sun, 13 Jun 2021 15:56:41 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [24.104.150.213]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C5EE73A132F for <tsvwg@ietf.org>; Sun, 13 Jun 2021 15:56:41 -0700 (PDT)
Received: by family.redbarn.org (Postfix, from userid 716) id 5A6A27599B; Sun, 13 Jun 2021 22:56:40 +0000 (UTC)
Date: Sun, 13 Jun 2021 22:56:40 +0000
From: Paul Vixie <paul@redbarn.org>
To: "C. M. Heard" <heard@pobox.com>
Cc: Joseph Touch <touch@strayalpha.com>, Gorry Fairhurst <gorry@erg.abdn.ac.uk>, TSVWG <tsvwg@ietf.org>
Message-ID: <20210613225640.pmnhuqwh3fcsorq6@family.redbarn.org>
References: <CACL_3VGb_9P5SfPGRJtf1ZBvEhgywc2ZEGr-qbgNOMXV20rFeA@mail.gmail.com> <CACL_3VHyoRr5ju8203DiLTUo-658DCj7ud+1dQE2o0hUPVhF0A@mail.gmail.com> <7D766992-AEEB-434F-BB1D-3817EE07DE61@strayalpha.com> <11037_1623411791_60C34C4F_11037_1_3_787AE7BB302AE849A7480A190F8B9330353A9C56@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <7aaa39d3-0431-e4b0-36bd-1db0686b24dc@erg.abdn.ac.uk> <1FF4F896-0CB8-4AC6-93A4-EAA716BB21A6@strayalpha.com> <CACL_3VFSoHzHdrps_9X2er+Z3S+_r5z9BstE6cJ0f7k8hgyfSA@mail.gmail.com> <3BECDCD0-F6CA-4725-86ED-092FE69DF1D9@strayalpha.com> <CACL_3VGF_+Oh_LbmL=LL-Pd_6dMX0WOaYU9z2x-EMnmgpWiPZg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CACL_3VGF_+Oh_LbmL=LL-Pd_6dMX0WOaYU9z2x-EMnmgpWiPZg@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/juj_HDeCNT_NDf5ZNTGVgQPM2Vw>
Subject: Re: [tsvwg] A review of draft-ietf-tsvwg-udp-options-12
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: Sun, 13 Jun 2021 22:56:46 -0000

On Sun, Jun 13, 2021 at 03:00:35PM -0700, C. M. Heard wrote:
> Responding to just this one specific point ...

same.

> On Sun, Jun 13, 2021 at 12:55 PM Joseph Touch wrote:
> 
> > And no, I do not think we should rely on RMSS to indicate that this is
> > available. Note that a receiver would have to indicate RMSS and know the
> > path MTU to know how many fragments it would actually take; we don???t
> > require path MTU discovery for UDP options, so that???s an undue burden.
> > Besides again injecting state into UDP.
> 
> For IPv6 -- where fragmentation has the greatest issues -- we are
> guaranteed a minimum MTU of 1280 bytes. A DNS server operating over IPv6
> would be able to serve up a fragmented response with the right number of
> 1280 byte fragments (or else set the TC bit) if it received the MRSS option
> in the request from the client.

computing UDP payload size by subtraction requires either that one be inside
the network stack (sometimes this means "in the kernel") so as to know the
interface MTU and perhaps the path MTU, as well as the IP6 header and option
sizes. when this information is unavailable, for example when running inside
a DNS responder, pessimistic assumptions have to be made, such as a payload
maximum for DNS data of 1232 or even 1220 octets. this is not just pessimistic
but also pessimal, and ought to be avoided.

i have high hopes for a non-pessimal future to be reached via:

https://www.rfc-editor.org/rfc/rfc8899.html

for which assumptions such as 1280, 1232, or 1220 will be "of last resort".
i think this may mean i disagree with joe's estimation of "undue" above. when
commodity (end user) hardware reaches terabit speed, we are going to wish we
were not shackled to the MTU of 10-megabit ethernet for wide area packets. in
fact i already wish this, but in the future the wish will be universal. it was
not too early to plan and develop for this future starting ~20 years ago, and
it is definitely not too early today.

-- 
Paul Vixie