Re: [tsvwg] I-D Action: draft-ietf-tsvwg-udp-options-dplpmtud-09.txt
Erik Auerswald <auerswal@unix-ag.uni-kl.de> Sun, 02 July 2023 21:25 UTC
Return-Path: <auerswal@unix-ag.uni-kl.de>
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 EDD7DC14CF1F for <tsvwg@ietfa.amsl.com>; Sun, 2 Jul 2023 14:25:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.893
X-Spam-Level:
X-Spam-Status: No, score=-1.893 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 6jNEUM8NqalX for <tsvwg@ietfa.amsl.com>; Sun, 2 Jul 2023 14:25:24 -0700 (PDT)
Received: from mailgw1.uni-kl.de (mailgw1.uni-kl.de [IPv6:2001:638:208:120::220]) (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 CE184C14F75F for <tsvwg@ietf.org>; Sun, 2 Jul 2023 14:25:23 -0700 (PDT)
Received: from sushi.unix-ag.uni-kl.de (sushi.unix-ag.uni-kl.de [IPv6:2001:638:208:ef34:0:ff:fe00:65]) by mailgw1.uni-kl.de (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id 362LPNal066359 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 2 Jul 2023 23:25:23 +0200
Received: from sushi.unix-ag.uni-kl.de (ip6-localhost [IPv6:::1]) by sushi.unix-ag.uni-kl.de (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id 362LPJ8b000510 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 2 Jul 2023 23:25:19 +0200
Received: (from auerswal@localhost) by sushi.unix-ag.uni-kl.de (8.14.4/8.14.4/Submit) id 362LPJUv000508; Sun, 2 Jul 2023 23:25:19 +0200
Date: Sun, 02 Jul 2023 23:25:19 +0200
From: Erik Auerswald <auerswal@unix-ag.uni-kl.de>
To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Cc: tsvwg@ietf.org
Message-ID: <20230702212519.GB29683@unix-ag.uni-kl.de>
References: <168805849623.15224.18038199673090941440@ietfa.amsl.com> <20230702183214.GA5392@unix-ag.uni-kl.de> <437f3907-d415-f69b-4964-b06a7659bc50@erg.abdn.ac.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <437f3907-d415-f69b-4964-b06a7659bc50@erg.abdn.ac.uk>
Author: Erik Auerswald <auerswal@unix-ag.uni-kl.de>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/ZsPa4fdCVeLaIWqUqlFxHLh4mhI>
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: Sun, 02 Jul 2023 21:25:28 -0000
Hi Gorry, On Sun, Jul 02, 2023 at 07:59:34PM +0100, Gorry Fairhurst wrote: > On 02/07/2023 19:32, Erik Auerswald wrote: > >Hi, > > > >thanks for the additional text in section 4.4! > > > >After re-reading the draft, I have noticed four additional issues resp. > >potential improvements: > > > > > >(1) > > > >In section 4.3 on page 8, section 4.2 of RFC 8899 is given as reference for > >a DPLPMUTD black-hole. This should be section 4.3 of RFC 8899 (Black Hole > >Detection and Reducing the PLPMTU) instead, I'd say. > > > >OLD: > > > > (Section 5.2 of [RFC8899], Section 4.2 of [RFC8899] > > defines a DPLPMTUD black-hole). > > > >NEW: > > > > (Section 5.2 of [RFC8899], Section 4.3 of [RFC8899] > > defines a DPLPMTUD black-hole). > > Thanks, done in this PR for the editor's version. > > See: > > https://github.com/uoaerg/draft-udp-options-dplpmtud/pull/28/files#diff-768474f5b48a4bc0b418862bf044141c340e502c6f99947161841e6137601c85 The PR looks mostly good, but the "black-hole" reference is mixed up. Currently, this draft has two references to "black hole" as described by RFC 8899. One references section 4.2 (wrong), one references section 4.3 (correct). ``` $ grep '4\..\. Black.Hole' rfc8899.txt 4.3. Black Hole Detection and Reducing the PLPMTU 4.3. Black Hole Detection and Reducing the PLPMTU ``` The linked pull request changes the correct reference to be incorrect. > > > >(2) > > > >Then there seems to be an inconsistency in a sentence in section 4.3 on > >page 9. There are three alternatives given for a probe packet, but the > >first ("Probing using padding data") and the third (construct a probe > >packet that does not carry any application data) seem to be the same. I'd > >suggest to just remove the last alternative: > > > >OLD: > > > > A probe packet used to validate the path MAY use either > > "Probing using padding data" or "Probing using application data and > > padding data" (Section 4.1 of [RFC8899]) or can construct a probe > > packet that does not carry any application data, as described in a > > previous section. > > > >NEW: > > > > A probe packet used to validate the path MAY use either > > "Probing using padding data" or "Probing using application data and > > padding data" (Section 4.1 of [RFC8899]). > > > I agree this was unclear, I suggest the revised text in the PR. Looks good. :-) > >(3) > > > >IMHO the text would be easier to understand if all UDP Options used were > >introduced together, i.e., in section 3, e.g., as follows: > > > >OLD: > > > > In this specification, this is realised using a pair > > of UDP Options: the Request (REQ) Option and the Response (RES) > > Option [I-D.ietf-tsvwg-udp-options]. > > > >NEW: > > > > In this specification, this is realised using three > > UDP Options: the End of Options List (EOL) Option, > > the Request (REQ) Option, and the Response (RES) Option > > [I-D.ietf-tsvwg-udp-options]. > > > Kind of, but I think the focus is on REQ/RES. Maybe though to be > complete I could suggest: > > The method also uses the the End of Options List (EOL) Option <xref > target="I-D.ietf-tsvwg-udp-options"></xref>. to > introduce padding to set the size of a probe packet.</t> That looks good, too (but there is a stray period after "</xref>" before "to"). > >(4) > > > >Similarly, section 3.1 could also include all the UDP Options features used > >for DPLPMTUD. This could be accomplished by extending the first sentence > >of section 3.1 and adding another bullet point before the first one: > > > >OLD: > > > > The UDP Options used in this document are described in Section 9.7 of > > [I-D.ietf-tsvwg-udp-options] and are used in the following way: > > > > * The REQ Option is set by a sending PL to solicit a response from a > > remote receiver. A four-byte token identifies each request. > > > >NEW: > > > > The UDP Option features used in this document are described in Section > > 9.1, Section 9.7, and Section 13 of [I-D.ietf-tsvwg-udp-options] and > > are used in the following way: > > I'm inclined to remove the cross reference. References to sections > are rather fragile > > if specs are updated, and the sections can be found from the ToC, so > perhaps it > > might be better without, see PR. That looks good in the PR. > > * A sending PL uses the EOL option together with a minimum datagram > > length to pad probe packets. > > I see, I propose; > > <t>A sending PL can use the EOL option together > with a minimum > datagram length to pad probe packets.</t> That is fine. > > > > * The REQ Option is set by a sending PL to solicit a response from a > > remote receiver. A four-byte token identifies each request. > > > > > >Regards, > >Erik > > > > > >On Thu, Jun 29, 2023 at 10:08:16AM -0700, 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 > >> > >> > Best wishes, > > Gorry Regards, Erik
- [tsvwg] I-D Action: draft-ietf-tsvwg-udp-options-… internet-drafts
- Re: [tsvwg] I-D Action: draft-ietf-tsvwg-udp-opti… Erik Auerswald
- Re: [tsvwg] I-D Action: draft-ietf-tsvwg-udp-opti… Gorry Fairhurst
- Re: [tsvwg] I-D Action: draft-ietf-tsvwg-udp-opti… Erik Auerswald
- Re: [tsvwg] I-D Action: draft-ietf-tsvwg-udp-opti… C. M. Heard
- Re: [tsvwg] I-D Action: draft-ietf-tsvwg-udp-opti… Gorry Fairhurst
- Re: [tsvwg] I-D Action: draft-ietf-tsvwg-udp-opti… Gorry Fairhurst