Skip to main content

Last Call Review of draft-ietf-tcpm-tcp-rfc4614bis-05
review-ietf-tcpm-tcp-rfc4614bis-05-secdir-lc-lepinski-2014-06-26-00

Request Review of draft-ietf-tcpm-tcp-rfc4614bis
Requested revision No specific revision (document currently at 08)
Type Last Call Review
Team Security Area Directorate (secdir)
Deadline 2014-06-30
Requested 2014-06-19
Authors Martin Duke , Robert T. Braden , Wesley Eddy , Ethan Blanton , Alexander Zimmermann
I-D last updated 2014-06-26
Completed reviews Genart Last Call review of -05 by Scott W. Brim (diff)
Genart Telechat review of -07 by Scott W. Brim (diff)
Secdir Last Call review of -05 by Matt Lepinski (diff)
Opsdir Last Call review of -05 by Dan Romascanu (diff)
Assignment Reviewer Matt Lepinski
State Completed
Request Last Call review on draft-ietf-tcpm-tcp-rfc4614bis by Security Area Directorate Assigned
Reviewed revision 05 (document currently at 08)
Result Ready
Completed 2014-06-26
review-ietf-tcpm-tcp-rfc4614bis-05-secdir-lc-lepinski-2014-06-26-00
I have reviewed this document as part of the security directorate's ongoing
effort to review all IETF documents being processed by the IESG. These comments
were written primarily for the benefit of the security area directors. Document
editors and WG chairs should treat these comments just like any other last call
comments.

This draft is an update to the Roadmap for TCP specifications (RFC 4614). The
roadmap provides a pointer (along with a brief abstract) to key TCP
specifications. The update to the roadmap makes small changes to the
organization of the roadmap and (more importantly) adds pointers to a number of
more recent TCP-related specifications.

This document appears to be ready for publication. I found no problems with
this document.

As a collection of pointers to other specifications, this document does not
introduce any new security concerns. Security issues related to TCP are
addressed in individual specifications referenced in this roadmap. (Indeed, one
of the changes made in this update to the roadmap is to include more pointers
to documents related to TCP security, such as the specification for TCP-AO.)