[tsvwg] Re: WGLC for comments for draft-ietf-tsvwg-udp-options and draft-ietf-tsvwg-udp-options-dplpmtud to end 1st May 2024
Erik Auerswald <auerswal@unix-ag.uni-kl.de> Tue, 07 May 2024 15:23 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 03EAFC14F694 for <tsvwg@ietfa.amsl.com>; Tue, 7 May 2024 08:23:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 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_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 c8JkOV2E4_q5 for <tsvwg@ietfa.amsl.com>; Tue, 7 May 2024 08:23:03 -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 E4B6FC14EB19 for <tsvwg@ietf.org>; Tue, 7 May 2024 08:23:02 -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 447FNHvE130616 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 7 May 2024 17:23:17 +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 447FMvs7030137 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 7 May 2024 17:22:58 +0200
Received: (from auerswal@localhost) by sushi.unix-ag.uni-kl.de (8.14.4/8.14.4/Submit) id 447FMv4J030136; Tue, 7 May 2024 17:22:57 +0200
From: Erik Auerswald <auerswal@unix-ag.uni-kl.de>
To: "C. M. Heard" <heard@pobox.com>
Message-ID: <20240507152257.GA28913@unix-ag.uni-kl.de>
References: <0f72bf81-5fd1-490d-9077-051ce5ebebc0@erg.abdn.ac.uk> <20240503085711.GA9028@unix-ag.uni-kl.de> <CACL_3VEszVBZ-TV3c8E6T9X7O_gRZeG4hvv1E_D1k6_AShwXug@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CACL_3VEszVBZ-TV3c8E6T9X7O_gRZeG4hvv1E_D1k6_AShwXug@mail.gmail.com>
Author: Erik Auerswald <auerswal@unix-ag.uni-kl.de>
Message-ID-Hash: 4CUHTONIEDRPQYAGHVKSMMMITN65RST6
X-Message-ID-Hash: 4CUHTONIEDRPQYAGHVKSMMMITN65RST6
X-MailFrom: auerswal@unix-ag.uni-kl.de
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tsvwg.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: tsvwg@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [tsvwg] Re: WGLC for comments for draft-ietf-tsvwg-udp-options and draft-ietf-tsvwg-udp-options-dplpmtud to end 1st May 2024
List-Id: Transport Area Working Group <tsvwg.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/f5fk4WDCq8PEgAB4JcET3TFVjws>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Owner: <mailto:tsvwg-owner@ietf.org>
List-Post: <mailto:tsvwg@ietf.org>
List-Subscribe: <mailto:tsvwg-join@ietf.org>
List-Unsubscribe: <mailto:tsvwg-leave@ietf.org>
Date: Tue, 21 May 2024 17:26:39 -0000
X-Original-Date: Tue, 7 May 2024 17:22:57 +0200
Hi Mike, the first and third issues are still open (section numbers in the UDP Options draft have increased since the last adjustment of those in draft-ietf-tsvwg-udp-options-dplpmtud -- possibly because of the addition of the two early sections "UDP Option Intended Uses" and "UDP Option Design Principles"). The second issue, paraphrased "s/MSS/MDS/", is addressed in -12. Thanks, Erik On Tue, May 07, 2024 at 08:04:38AM -0700, C. M. Heard wrote: > Erik, > > I opened Issue #30 > <https://github.com/tsvwg/draft-udp-options-dplpmtud/issues/30> to cover > the following comments. If > https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-udp-options-dplpmtud-12 > (just > posted) satisfactorily addresses them, please let us know. > > Mike Heard > > On Fri, May 3, 2024 at 1:57 AM Erik Auerswald <auerswal@unix-ag.uni-kl.de> > wrote: > > > Hi, > > > > a bit late, but here are a few nits regarding > > draft-ietf-tsvwg-udp-options-dplpmtud-11: > > > > * Section 3.2 on page 6 refers to wrong section of > > I-D.ietf-tsvwg-udp-options for EOL: > > > > (Section 9.1 of [I-D.ietf-tsvwg-udp-options]) > > ---> > > (Section 11.1 of [I-D.ietf-tsvwg-udp-options]) > > > > * Section 4.2 on page 8 uses "Maximum Segment Size" / "MSS" instead of > > "Maximum Datagram Size" / "MDS": > > > > ...When the remote endpoint advertises a UDP Maximum > > Segment Size (MSS) option,... > > ---> > > ...When the remote endpoint advertises a UDP Maximum > > Datagram Size (MDS) option,... > > > > * Section 4.4 on page 9 has a wrong section reference for the UDP > > Options API: > > > > ...(Section 13 of > > [I-D.ietf-tsvwg-udp-options]). > > ---> > > ...(Section 15 of > > [I-D.ietf-tsvwg-udp-options]). > > > > Best regards, > > Erik > > > > > > On Wed, Apr 24, 2024 at 08:02:12PM +0100, Gorry Fairhurst wrote: > > > This is a reminder of the on-going 3 weeks WG Last Call to determine if > > the > > > following TSVWG IDs are ready: > > > > > > https://datatracker.ietf.org/doc/draft-ietf-tsvwg-udp-options/ > > > https://datatracker.ietf.org/doc/draft-ietf-tsvwg-udp-options-dplpmtud/ > > > > > > These documents both target PROPOSED STANDARD. > > > > > > The document shepherd for the UDP Options will be: Gorry Fairhurst. > > > The document shepherd for DPLPMTUD with UDP Options will be: Marten > > Seemann. > > > > > > The WGLC will end at midnight UTC on 1st May 2024. > > > > > > Please do read the drafts, and please do send any comments/concerns > > > to the TSVWG mailing list, including notes on whether these are > > > ready to publish (or send an email directly to the > > > chairs<tsvwg-chairs@ietf.org>). > > > > > > Best wishes, > > > Gorry and Marten > > > (tsvwg co-chairs) > > > > > > — > > > > > > The IETF WG Last Call process is described in RFC 6174.
- [tsvwg] WGLC for comments for draft-ietf-tsvwg-ud… Gorry Fairhurst
- Re: [tsvwg] WGLC for comments for draft-ietf-tsvw… Erik Auerswald
- Re: [tsvwg] WGLC for comments for draft-ietf-tsvw… C. M. Heard
- Re: [tsvwg] WGLC for comments for draft-ietf-tsvw… Erik Auerswald
- Re: [tsvwg] WGLC for comments for draft-ietf-tsvw… Erik Auerswald
- [tsvwg] Re: WGLC for comments for draft-ietf-tsvw… C. M. Heard
- [tsvwg] Re: WGLC for comments for draft-ietf-tsvw… Erik Auerswald