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

Paul Vixie <paul@redbarn.org> Sun, 20 June 2021 17:12 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 25A7C3A1D64; Sun, 20 Jun 2021 10:12:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_NONE=-0.0001, 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 dx8iC_oZI5yP; Sun, 20 Jun 2021 10:12:51 -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 6F84C3A1D62; Sun, 20 Jun 2021 10:12:51 -0700 (PDT)
Received: by family.redbarn.org (Postfix, from userid 716) id C80077599B; Sun, 20 Jun 2021 17:12:49 +0000 (UTC)
Date: Sun, 20 Jun 2021 17:12:49 +0000
From: Paul Vixie <paul@redbarn.org>
To: Joseph Touch <touch@strayalpha.com>
Cc: TSVWG <tsvwg@ietf.org>, i-d-announce@ietf.org
Message-ID: <20210620171249.le6tjyi7h66jggq2@family.redbarn.org>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <95274A1D-3C51-4D40-A5AB-7E8A4AEFDD1B@strayalpha.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/i3E70cTfRJWcNOXrl54k-puOMVU>
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 17:12:56 -0000

On Sun, Jun 20, 2021 at 09:54:54AM -0700, Joseph Touch wrote:
> ...
> 
> Note that TCP bursts up to 10 packets right now anyway,
> so I don???t see why UDP fragments couldn???t do the same.

if tcp sends more than three before it has any estimate of the congestion
window, then i withdraw my suggestion of "3". however, i ask that some
guidance be offered about not transmitting fragments back to back, if the
number is larger than "2". and i do hope the number will be larger than "2",
due to page/MTU sizes.

vixie

re:

> > On Jun 19, 2021, at 9:33 PM, Paul Vixie <paul@redbarn.org> wrote:
> > 
> > On Sat, Jun 19, 2021 at 12:38:51AM -0700, Joseph Touch wrote:
> >> ...
> >> How many frags MUST be supported 2? 4?
> > 
> > if they'll be transmitted back to back, microburst style, like IP fragments are,
> > then 2. if there's implementation guidance to send the frags isochronously on
> > a schedule of some kind, to give other transmissions an opportunity to enter,
> > then 3. on today-typical MTU 1500 networks, "3" allows a today-typical 4K page
> > to be sent as a fragmented UDP datagram. in future networks we should expect
> > this ratio from then-typical MTU to then-typical page size to be more or less
> > similar.
> > 
> > -- 
> > Paul Vixie
> 

-- 
Paul Vixie