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

"C. M. Heard" <heard@pobox.com> Sun, 13 June 2021 22:00 UTC

Return-Path: <heard@pobox.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 50F7F3A1108 for <tsvwg@ietfa.amsl.com>; Sun, 13 Jun 2021 15:00:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=pobox.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 rvpVpRSl-TjR for <tsvwg@ietfa.amsl.com>; Sun, 13 Jun 2021 15:00:41 -0700 (PDT)
Received: from pb-smtp21.pobox.com (pb-smtp21.pobox.com [173.228.157.53]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C68E93A1107 for <tsvwg@ietf.org>; Sun, 13 Jun 2021 15:00:41 -0700 (PDT)
Received: from pb-smtp21.pobox.com (unknown [127.0.0.1]) by pb-smtp21.pobox.com (Postfix) with ESMTP id 06AB3131968 for <tsvwg@ietf.org>; Sun, 13 Jun 2021 18:00:36 -0400 (EDT) (envelope-from heard@pobox.com)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=pobox.com; h= mime-version:references:in-reply-to:from:date:message-id:subject :to:cc:content-type; s=sasl; bh=AvhLap1H/7cYb3sJTNWZ5oqJOyh0hZoH G7Otg5gpSDY=; b=NtVUtslM0jvQAg6CKPhWjYSr3nGcmILWlO2NNj0GjTUlxLXd xePWk6DYZAPH2UCW+79jnhoAlMqCQt4GhmZaOeWVRnQdKGCGOA82S7Ghcle/LonH eXlj0n4Dgr/kV0QalGg7uvIu1YKgxbFbOtclTwJKP8ROuvhcSFBkW3JJ23g=
Received: from pb-smtp21.sea.icgroup.com (unknown [127.0.0.1]) by pb-smtp21.pobox.com (Postfix) with ESMTP id F3D0B131967 for <tsvwg@ietf.org>; Sun, 13 Jun 2021 18:00:35 -0400 (EDT) (envelope-from heard@pobox.com)
Received: from mail-io1-f50.google.com (unknown [209.85.166.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp21.pobox.com (Postfix) with ESMTPSA id 9F4DD131960 for <tsvwg@ietf.org>; Sun, 13 Jun 2021 18:00:33 -0400 (EDT) (envelope-from heard@pobox.com)
Received: by mail-io1-f50.google.com with SMTP id h5so905501iok.5 for <tsvwg@ietf.org>; Sun, 13 Jun 2021 15:00:33 -0700 (PDT)
X-Gm-Message-State: AOAM530FVQRTfakv50i7anlpt1gv1DfbDdpXnlkrNHoUbSvDtdc+P+/H +J1qOdQyNAZilwQTrI2DtT1x2QgWjB5Yi5NEiyw=
X-Google-Smtp-Source: ABdhPJwyfFe+sWjW3WxIkjOcy4iF6dvcth/yE4Awc5CtfMHMDNSZ9NkHigBoCgeMtWIVrGhF3ivALLYaJuI7couWjao=
X-Received: by 2002:a6b:f717:: with SMTP id k23mr4658630iog.17.1623621632331; Sun, 13 Jun 2021 15:00:32 -0700 (PDT)
MIME-Version: 1.0
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>
In-Reply-To: <3BECDCD0-F6CA-4725-86ED-092FE69DF1D9@strayalpha.com>
From: "C. M. Heard" <heard@pobox.com>
Date: Sun, 13 Jun 2021 15:00:35 -0700
X-Gmail-Original-Message-ID: <CACL_3VGF_+Oh_LbmL=LL-Pd_6dMX0WOaYU9z2x-EMnmgpWiPZg@mail.gmail.com>
Message-ID: <CACL_3VGF_+Oh_LbmL=LL-Pd_6dMX0WOaYU9z2x-EMnmgpWiPZg@mail.gmail.com>
To: Joseph Touch <touch@strayalpha.com>
Cc: "C. M. Heard" <heard@pobox.com>, Gorry Fairhurst <gorry@erg.abdn.ac.uk>, mohamed.boucadair@orange.com, TSVWG <tsvwg@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a5156605c4acde05"
X-Pobox-Relay-ID: C6BF9088-CC92-11EB-B56E-FA9E2DDBB1FC-06080547!pb-smtp21.pobox.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/F4oY_-nKiRTdc-1ipt3_77XUsg0>
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:00:46 -0000

Responding to just this one specific point ...

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.

Mike Heard