Re: [tsvwg] WGLC for comments for draft-ietf-tsvwg-udp-options and draft-ietf-tsvwg-udp-options-dplpmtud to end 1st May 2024

[Erik Auerswald <[e-mail]>]

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<[e-mail]>).
> 
> Best wishes,
> Gorry and Marten
> (tsvwg co-chairs)
> 
> —
> 
> The IETF WG Last Call process is described in RFC 6174.
>