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

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Mon, 28 February 2022 12:34 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 3044D3A101A for <tsvwg@ietfa.amsl.com>; Mon, 28 Feb 2022 04:34:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 Sf-B5BphD69J for <tsvwg@ietfa.amsl.com>; Mon, 28 Feb 2022 04:33:56 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [137.50.19.135]) by ietfa.amsl.com (Postfix) with ESMTP id DDAFD3A10D6 for <tsvwg@ietf.org>; Mon, 28 Feb 2022 04:33:54 -0800 (PST)
Received: from [192.168.1.64] (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 665E11B0009C; Mon, 28 Feb 2022 12:33:16 +0000 (GMT)
Message-ID: <904a7b54-1b67-d2e9-4dba-f81a43798978@erg.abdn.ac.uk>
Date: Mon, 28 Feb 2022 12:33:15 +0000
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:91.0) Gecko/20100101 Thunderbird/91.6.1
To: mohamed.boucadair@orange.com, "tsvwg@ietf.org" <tsvwg@ietf.org>
References: <164578863105.24459.298900087249411180@ietfa.amsl.com> <29133_1646045545_621CA969_29133_321_7_787AE7BB302AE849A7480A190F8B93303549BA6C@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
In-Reply-To: <29133_1646045545_621CA969_29133_321_7_787AE7BB302AE849A7480A190F8B93303549BA6C@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/41yUAnWyku7jTcseOCiVtZNVyIQ>
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-udp-options-dplpmtud-03.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: Mon, 28 Feb 2022 12:34:00 -0000

On 28/02/2022 10:52, mohamed.boucadair@orange.com wrote:
> Hi Gorry,
>
> Thank you for taking care of the comments. I like in particular how you recorded the outcome of the nonce discussion in the security section. I consider that all my previous comments are adequately addressed.
>
> One last comment in reference to this part from the udp-options spec (which covers RES/REQ):
>
> ==
>     >> All other options (without a "*") MAY be implemented, and their
>     use SHOULD be determined either out-of-band or negotiated.
> ==
>
> I wonder whether it is useful to be explicit how retransmission is managed by the sender when no response is received from a peer.

Med, I'm not sure what you suggest this time, so this not be the answer 
you are asking ...

While a UDP application could itself retransmit (some) datagrams that it 
somehow determined to be lost, I don't think there is any single 
approach, and so I'd prefer to suggest that the easy approach to 
DPLPMTUD is not to send a probe with any application data, or at least 
not with any data that needs to be reliably sent.

The DPLPMTUD probes themselves are not really retransmitted, rather, if 
a probe times-out or is discovered lost, then a new probe is then 
scheduled. This could have the same size, or the next size chosen.  It 
will have new token.

What text might be helpful to add?

Gorry

> Thanks.
>
> Cheers,
> Med
>
>> -----Message d'origine-----
>> De : I-D-Announce <i-d-announce-bounces@ietf.org> De la part de
>> internet-drafts@ietf.org
>> Envoyé : vendredi 25 février 2022 12:31
>> À : i-d-announce@ietf.org
>> Cc : tsvwg@ietf.org
>> Objet : I-D Action: draft-ietf-tsvwg-udp-options-dplpmtud-03.txt
>>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the Transport Area Working Group WG of the
>> IETF.
>>
>>          Title           : Datagram PLPMTUD for UDP Options
>>          Authors         : Godred Fairhurst
>>                            Tom Jones
>> 	Filename        : draft-ietf-tsvwg-udp-options-dplpmtud-03.txt
>> 	Pages           : 12
>> 	Date            : 2022-02-25
>>
>> 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 a datagram application to discover the largest size of
>>     datagram that can be sent across a specific network path.
>>
>>
>> The IETF datatracker status page for this 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-03
>>
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-udp-options-dplpmtud-
>> 03
>>
>>
>> Internet-Drafts are also available by rsync at rsync.ietf.org::internet-
>> drafts
>>
>>
>> _______________________________________________
>> I-D-Announce mailing list
>> I-D-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/i-d-announce
>> Internet-Draft directories: http://www.ietf.org/shadow.html or
>> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> _________________________________________________________________________________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.