Skip to main content

Last Call Review of draft-ietf-tcpm-fastopen-09
review-ietf-tcpm-fastopen-09-genart-lc-shirazipour-2014-07-25-00

Request Review of draft-ietf-tcpm-fastopen
Requested revision No specific revision (document currently at 10)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2014-07-23
Requested 2014-07-10
Authors Yuchung Cheng , Jerry Chu , Sivasankar Radhakrishnan , Arvind Jain
I-D last updated 2014-07-25
Completed reviews Genart Last Call review of -09 by Meral Shirazipour (diff)
Genart Telechat review of -09 by Meral Shirazipour (diff)
Secdir Early review of -08 by Shawn M Emery (diff)
Assignment Reviewer Meral Shirazipour
State Completed
Request Last Call review on draft-ietf-tcpm-fastopen by General Area Review Team (Gen-ART) Assigned
Reviewed revision 09 (document currently at 10)
Result Ready w/nits
Completed 2014-07-25
review-ietf-tcpm-fastopen-09-genart-lc-shirazipour-2014-07-25-00

I am the assigned Gen-ART reviewer for this draft. For background on Gen-ART,
please see the FAQ at

http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq

.



Please resolve these comments along with any other Last Call comments you may
receive.



Document: draft-ietf-tcpm-fastopen-09

Reviewer: Meral Shirazipour

Review Date: 2014-07-23

IETF LC End Date:   2014-07-23

IESG Telechat date: NA





Summary:

This draft is ready to be published as Experimental RFC, but I have some
comments.



Nits/editorial comments:

-Abstract says "thus saving up to one full round trip time (RTT)": by just
reading the abstract one would think 1.5 RTT since initial 3WHS is avoided.

Reading the rest of the draft clarifies this though. Suggestion :



"

TFO allows data to be carried in the SYN and SYN-ACK packets

   and consumed by the receiving end during 'an' initial connection

   handshake, 'and' saves up to one full round trip time (RTT) compared

   to the standard TCP, ......

"



-[page 4] "MSL", to spell out at first use "maximum segment lifetime" (or
please consider mentioning reference to key TCP RFCs in Terminology section).



-General: Also few other acronyms used without spelling out at first use,
please consider those as well.



-[Page 7], 'Fast Open Cookie Option', it would be more familiar to IETF
community to call "Kind" field "Type", unless there was a reason for this
differentiation.

-[Page 10] please remove extra space (page break) if not needed.



-[Page 12], typo "connection-sharding"--->"connection-sharing"



-[page 14] "as a application"--->"as an application"



-[Page 17], typo "Neverthless"--->"Nevertheless"



-[Page 18], typo "meet the the"---->"meet the"



-[Page 21], typo "in Section Section 4.1.1"---->"in Section 4.1.1"



-[Page 21] please remove extra space (page break) if not needed.



Best Regards,

Meral





---

Meral Shirazipour

Ericsson

Research

www.ericsson.com