Re: [tcpm] Please review 793bis!

[Wesley Eddy <[e-mail]>]

Many thanks for your comments; my thoughts are below:

On 7/29/2019 5:35 AM, [e-mail] wrote:
> Hi all,
>
> Please find below some very minor comments to enhance the readability of the document:
>
> * Consider moving Section 2.1 to be listed under Section 3.

Either way is fine with me; does anyone have strong preference? The 
section numbering is closer to the original 793 numbering currently, and 
this would probably bump that, but that is a very trivial concern.


> * Rsrvd - Reserved:  s/Reserved/Unassigned. This is to be aligned with https://tools.ietf.org/html/rfc8126#section-6 (reserved in 8126 has a special meaning: "Reserved:  Not assigned and not available for assignment.")

Thanks; I'll have to look at this in all cases and make sure we "do the 
right thing".  I hadn't really been aware of 8126.


> * Add a pointer to the "TCP Header Flags" registry: https://www.iana.org/assignments/tcp-header-flags/tcp-header-flags.xhtml
>
> * Add an IANA action to update the above registry to include all TCP flags, not only those in 3168. Also, the description text in that page should be reworked, IMHO. Unassigned bits should also be indicated as such in that page.
>
> I would like to have those referenced in that page rather than having documents requiring access to these bits to duplicate the effort: see for example  RFC8519 (look for "reserved" and "flags" in Page 33).

Good point.  3168 created the registry, but then didn't fully populate 
it with the bits that 793 had defined.


> * Position titles right after figure #, e.g.,
>
> OLD:
>
>                                 TCP Header Format
>
>               Note that one tick mark represents one bit position.
>
>                                   Figure 1
>
> NEW:
>
>               Note that one tick mark represents one bit position.
>
>                                   Figure 1: TCP Header Format

Also a good idea ... I will make this change, unless anyone shouts.


> * Introduce some notations used in the document (and a pointer to Appendix B), e.g.,
>
>       The window size MUST be treated as an unsigned number, or else
>       large window sizes will appear like negative windows and TCP will
>       now work (MUST-1) .  It is RECOMMENDED that implementations will
>                ^^^^^^^^
>       reserve 32-bit fields for the send and receive window sizes in the
>       connection record and do all window computations with 32 bits (REC-
>                                                                      ^^^^
>       1 ).
>
> Idem for SHLD-, etc.

Good point.  It seems like explaining this in the introduction will work.


> * Section 3.1
>
> OLD:
>
>       The checksum also covers a pseudo header conceptually prefixed to
>       the TCP header.  The pseudo header is 96 bits for IPv4 and 320 bits
>       for IPv6.  For IPv4, this pseudo header contains the Source
>       Address, the Destination Address, the Protocol, and TCP length.
>
> NEW:
>       The checksum also covers a pseudo header conceptually prefixed to
>       the TCP header.  The pseudo header is 96 bits for IPv4 and 320 bits
>       for IPv6.  For IPv4, this pseudo header contains the Source
>       Address, the Destination Address, the Protocol (PTCL), and TCP length.
>                                                      ^^^^^^
>
> * Section 3.1: Add missing figure legend, e.g.,
>
>                     +--------+--------+--------+--------+
>                     |           Source Address          |
>                     +--------+--------+--------+--------+
>                     |         Destination Address       |
>                     +--------+--------+--------+--------+
>                     |  zero  |  PTCL  |    TCP Length   |
>                     +--------+--------+--------+--------+
>
> * Section 3.3:
>
> OLD:
>   The synchronization requires each side to send it's own initial
>
> NEW:
>   The synchronization requires each side to send its own initial

Many thanks; all of the above suggestions look good to me.