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

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Mon, 03 July 2023 07:28 UTC

Return-Path: <gorry@erg.abdn.ac.uk>
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 E26C8C15107D for <tsvwg@ietfa.amsl.com>; Mon, 3 Jul 2023 00:28:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GH9I-G8u9NV0 for <tsvwg@ietfa.amsl.com>; Mon, 3 Jul 2023 00:28:13 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:42:150::2]) by ietfa.amsl.com (Postfix) with ESMTP id 04ECEC14CF18 for <tsvwg@ietf.org>; Mon, 3 Jul 2023 00:28:11 -0700 (PDT)
Received: from [192.168.1.130] (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id A44E71B0015B for <tsvwg@ietf.org>; Mon, 3 Jul 2023 08:28:09 +0100 (BST)
Message-ID: <a9e415b9-8776-7f0e-2e23-c11e70740467@erg.abdn.ac.uk>
Date: Mon, 03 Jul 2023 08:28:09 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.12.0
To: tsvwg@ietf.org
References: <168805849623.15224.18038199673090941440@ietfa.amsl.com> <CACL_3VGH9BZYyJPc5yFzfsbvnaF__Zi6uw55zfoADOV7NvPF8A@mail.gmail.com>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: UNIVERSITY OF ABERDEEN
In-Reply-To: <CACL_3VGH9BZYyJPc5yFzfsbvnaF__Zi6uw55zfoADOV7NvPF8A@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/yS1JqzC6vUY_vaXieCKhtmsXN88>
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-udp-options-dplpmtud-09.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.39
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, 03 Jul 2023 07:28:17 -0000

On 03/07/2023 01:35, C. M. Heard wrote:
> On Sun, Jul 2, 2023 at 1:50 PM PDT, in the thread entitled "Remaining
> issues for draft-ietf-tsvwg-udp-options-22," Gorry Fairhurst wrote:
>> UDP Options itself doesn't generate the response, it passes the REQ
>> upwards to the protocol that does and that sends the RES option.
> However, Section 3 of  draft-ietf-tsvwg-udp-options-dplpmtud-09 says:
>
>     When DPLPMTUD is within the UDP transport service, the UDP Options
>     processing is responsible for sending probe packets to determine a
>     PLPMTU, as described in this document.
>
> It might be better to say "the DPLPMTUD State Machine" rather than "the
> UDP Options processing" to make it clear that it is the shim above UDP
> Options Transport in the figure that does this, and not UDP Options
> itself. This would help to emphasize the point that UDP Options on its
> own does not generate responses to any option.
Yes, that is better, added.
>
> The document does not describe in detail what happens when an Upper
> Layer Protocol (or application) implements DLPMTUD using UDP options.
> For me. it's easy enough to infer that the DPLPMTUD State Machine has to
> reside within the application, and that the application must initiate
> the actions to generate probe packets and responses. However, a sentence
> making that point explicit would not hurt.

It's the application/library/protocol/ or whatever uses the UDP Options,

I tried to improve that in the Editor's version.

>
> Thanks and regards,
>
> Mike Heard
Gorry
> On Thu, Jun 29, 2023 at 10:08 AM <internet-drafts@ietf.org> wrote:
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories. This Internet-Draft is a work item of the Transport Area Working
>> Group (TSVWG) WG of the IETF.
>>
>>     Title           : Datagram PLPMTUD for UDP Options
>>     Authors         : Godred Fairhurst
>>                       Tom Jones
>>     Filename        : draft-ietf-tsvwg-udp-options-dplpmtud-09.txt
>>     Pages           : 17
>>     Date            : 2023-06-29
>>
>> Abstract:
>>     This document specifies how a UDP Options sender implements Datagram
>>     Packetization Layer Path Maximum Transmission Unit Discovery
>>     (DPLPMTUD) as a robust method for Path Maximum Transmission Unit
>>     discovery.  This method uses the UDP Options packetization layer.  It
>>     allows an application to discover the largest size of datagram that
>>     can be sent across the network path.  It also provides a way to allow
>>     the application to periodically verify the current maximum packet
>>     size supported by a path and to update this when required.
>>
>> The IETF datatracker status page for this Internet-Draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-udp-options-dplpmtud/
>>
>> There is also an htmlized version available at:
>> https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-udp-options-dplpmtud-09
>>
>> A diff from the previous version is available at:
>> https://author-tools.ietf.org/iddiff?url2=draft-ietf-tsvwg-udp-options-dplpmtud-09
>>
>> Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts
>>