Re: [tsvwg] I-D Action: draft-ietf-tsvwg-udp-options-13.txt

Joseph Touch <touch@strayalpha.com> Sun, 20 June 2021 19:36 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 8B4FC3A0D60 for <tsvwg@ietfa.amsl.com>; Sun, 20 Jun 2021 12:36:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.455
X-Spam-Level:
X-Spam-Status: No, score=0.455 tagged_above=-999 required=5 tests=[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.652, 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 sAVuFBLl4eQR for <tsvwg@ietfa.amsl.com>; Sun, 20 Jun 2021 12:36:52 -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 F3DC13A0D5E for <tsvwg@ietf.org>; Sun, 20 Jun 2021 12:36:51 -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=0aG9p73lmf9gfZ1Uu8pWFZiyKkwnynA7q/gC/XtXYPg=; b=JDOb4klbxUR2oLmXpmNoXwPZuJ 3Aa+2JTia03tYTN2kLIbEAGFOBpjZVSif+nZmRLdyDHRq1A5nFdl1SwoS+il/q20yT6VOTrGW1mJt XHnFItmMhTMM9QgbMGhLwQY+MKm+KCQ5+wP5H2jRXMHD0vLpV/V5FCaGLTmo9v/9+DMW5sPfeoSlC dbk3Hd+rOO9MC7WQPHsG6CUpWf7/ulLOmxcYmDZNXre1yvaZq4A+twnsL7jhS7xCyUq8AUEHL5H7J hcoba4hedFm7a0CzGsX9erVKwKLbCrVQq43iNettN8UJ4GdNQIACd3EFlHgCA1s9Lt5hbPqxsLGdM zD/1Zwmw==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:49832 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 1lv3FO-001me1-Mb; Sun, 20 Jun 2021 15:36:51 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_8F221EF2-875C-48C9-9B44-B4AA3F41DDF6"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.100.0.2.22\))
From: Joseph Touch <touch@strayalpha.com>
In-Reply-To: <CACL_3VFUpae=ABZu=WuAUmJozOZcr5z4qW3orZGkzVi-niEa4g@mail.gmail.com>
Date: Sun, 20 Jun 2021 12:36:45 -0700
Cc: Jonathan Morton <chromatix99@gmail.com>, TSVWG <tsvwg@ietf.org>
Message-Id: <54092700-A760-4B54-81E7-DDAC518FA27E@strayalpha.com>
References: <162408795080.21706.5548660195641640175@ietfa.amsl.com> <C2C396E7-B728-496E-841B-D9F64004D3E3@strayalpha.com> <20210620043304.c6xerpura7lyw6yo@family.redbarn.org> <95274A1D-3C51-4D40-A5AB-7E8A4AEFDD1B@strayalpha.com> <20210620171249.le6tjyi7h66jggq2@family.redbarn.org> <E716B4A5-44F5-41A1-98C0-A7A25FAFF779@gmail.com> <CACL_3VFUpae=ABZu=WuAUmJozOZcr5z4qW3orZGkzVi-niEa4g@mail.gmail.com>
To: "C. M. Heard" <heard@pobox.com>
X-Mailer: Apple Mail (2.3654.100.0.2.22)
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/_6TwL2UjuORIjWT0YTvHB4PCw5I>
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-udp-options-13.txt
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, 20 Jun 2021 19:36:57 -0000

FWIW, on this point:

> On Jun 20, 2021, at 11:28 AM, C. M. Heard <heard@pobox.com> wrote:
> 
> An option-aware client can and should include the UDP MRSS (Maximum Reassembled Segment Size) option in its request to indicate to the remote server the largest fragmented UDP datagram that it can reassemble.

Agreed, but that doesn’t help the client send a bigger request, which should also be possible, up to the minimums we specify.

I’m wondering if we can say:

- MUST support reassembly of at least (somewhere between 3 and 10), 
	unless considered a constrained instance, which MUST support at least 2

This allows for minimal IoT-style instances but doesn’t open the door too widely.

Joe