[tsvwg] Re: Resolving UDP Options Issue #52

["C. M. Heard" <[e-mail]>]

On Sat, Aug 10, 2024 at 3:06 PM C. M. Heard wrote:

> Greetings,
>
> After discussion between the author, the editor, and the document
> shepherd, the editor's current thinking is to address Issue 52
> <https://github.com/tsvwg/draft-ietf-tsvwg-udp-options/issues/52> with
> the following text:
>
> >> Endpoints supporting UDP options MUST be capable of fragmenting and
> reassembling at least two fragments, *each of a size that will fit within
> the standard Ethernet MTU of 1,500 bytes. This corresponds to a maximum
> pre-fragmentation or post-reassembly UDP packet size (including the UDP
> header and any per-datagram UDP options) of 2,926 bytes for IPv4 and 2,886
> bytes for IPv6. Note that these maximum sizes are not guaranteed to be
> achievable under all circumstances; for further details, please see Section
> 11.6.*
>
>
That has been changed (at the author's request) to

> >> Endpoints supporting UDP options MUST be capable of fragmenting and
> reassembling at least two fragments, *each of a size that will fit within
> the standard Ethernet MTU of 1,500 bytes. For further details, please see
> Section 11.6.*
>
>
The text in 11.6 (see #63
<https://github.com/tsvwg/draft-ietf-tsvwg-udp-options/issues/63>) remains
as previously proposed.

 Expect an updated draft within a few days.

Mike Heard

>