Clarification when allowing both default and extended length formats for options < 255 bytes

[Mike-Heard]

Section 10 now says:

>> Any UDP option other than EOL and NOP MAY use either the default or extended option formats.

However, all of the subsequent figures show only the default single-byte format.

IMO we should either change this text to require that the length be expressed using the shortest possible encoding or else mention that where subsequent figures show a single-byte Len=n it is also legal to send it as an extended length of n+2.

As editor, I seek input on which way to go. My intention is to take the latter route if no one expresses a preference.

[Mike-Heard]

So far I have received no input, but I did notice this text in Section 10 (after Figure 5)

The Length field is one byte for all lengths below 255 (including the Kind and Length bytes). A Length of 255 indicates use of the UDP option extended format shown in Figure 6.

which implies that the extended format in Figure 6 is not used for lengths of 254 bytes or below. Accordingly, the text in the editor's copy of -33 has been modified as follows:

OLD:

>> Any UDP option other than EOL and NOP MAY use either the default or extended option formats.

NEW:

>> Any UDP option whose length is 254 or less MUST use the UDP option default format shown in Figure 5.

Please speak up if you find this objectionable.

[jtouch]

Suggest that it still is useful to note that NOP and EOL aren't part of this format variation.

"Any option with a length field whose length is 254 or less MUST use the UDP option default format shown in Figure 5. NOP and EOL never use either length format."

[Mike-Heard]

Done:

>> Any UDP option other than NOP or EOL whose length is 254 or less MUST use the UDP option default format shown in Figure 5. NOP and EOL never use either length format