* Section 9.6: Change "segment" to "datagram"

[Mike-Heard]

Raised by Mike Heard and Erik Auerswald.

[Mike-Heard]

This is the change that was requested:

OLD: largest reassembled UDP segment

NEW: largest reassembled UDP datagram

That will make the terminology consistent with that in the remainder of the draft, including the title of the section.

[gorryfair]

The text in draft-ietf-tsvwg-udp-options-22 reads: Note: per packet options can occur either at the end of the original user data or be placed after the FRAG option of the first segment, with the Reassembled Datagram Option Start (RDOS)

[Mike-Heard]

The text you quote is in Section 9.4, not in section 9.6, so the comment should be about issue #3, not about issue #13.

On Wed, Jul 19, 2023 at 8:08 AM Gorry Fairhurst @.***> wrote:

The text in draft-ietf-tsvwg-udp-options-22 reads: Note: per packet options can occur either at the end of the original user data or be placed after the FRAG option of the first segment, with the Reassembled Datagram Option Start (RDOS)

— Reply to this email directly, view it on GitHub https://github.com/tsvwg/draft-ietf-tsvwg-udp-options/issues/13#issuecomment-1642271111, or unsubscribe https://github.com/notifications/unsubscribe-auth/BBA6FAU4GYSULWGM6J4BCL3XQ7Z75ANCNFSM6AAAAAAZ5DEWFA . You are receiving this because you authored the thread.Message ID: @.***>

[gorryfair]

Ah moving that part to issue from #13 to #3.

[jtouch]

Segment has been changed to datagram everywhere it refers to UDP in -21. Additional text added in the terminology section to explain that the original intent - of 1:1 correspondence with IP datagrams - is changed herein.

[gorryfair]

Discussed at Interim and closed.