Closed Mike-Heard closed 2 months ago
I agree, clarification is needed.
MRDS is defined as similar to IP’s EMTU_R, which is a reference to the buffer area for reassembly. For IP, that does include the IP options (which are copied per fragment). For us, it would NOT include the per-fragment UDP options but would include the per-datagram UDP options. I.e., it’s the UDP datagram with options that would have been sent had fragmentation not been needed.
Please confirm whether you think that makes the most sense as being most useful.
MRDS is defined as similar to IP’s EMTU_R, which is a reference to the buffer area for reassembly. For IP, that does include the IP options (which are copied per fragment). For us, it would NOT include the per-fragment UDP options but would include the per-datagram UDP options. I.e., it’s the UDP datagram with options that would have been sent had fragmentation not been needed.
Please confirm whether you think that makes the most sense as being most useful.
This sounds right. Text to that effect will be added to -33.
For us, it would NOT include the per-fragment UDP options but would include the per-datagram UDP options. I.e., it’s the UDP datagram with options that would have been sent had fragmentation not been needed.
Agreed, and the text in the editor's copy of -33 now has the bolded text added:
The Maximum Reassembled Datagram Size (MRDS, Kind=5) option is a 16-bit indicator of the largest reassembled UDP datagram that can be received, including the UDP header and any per-datagram UDP options.
Apologies for not posting this earlier.
In Section 11.6 please replace
with
This is intended to clarify that the MRDS size is intended to be that of the original UDP datagram shown in Figure 12, including all UDP options.