Skip to main content

Telechat Review of draft-ietf-taps-transports-usage-08
review-ietf-taps-transports-usage-08-genart-telechat-even-2017-09-05-00

Request Review of draft-ietf-taps-transports-usage
Requested revision No specific revision (document currently at 09)
Type Telechat Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2017-09-12
Requested 2017-08-31
Authors Michael Welzl , Michael Tüxen , Naeem Khademi
I-D last updated 2017-09-05
Completed reviews Genart Telechat review of -08 by Roni Even (diff)
Secdir Telechat review of -08 by Derrell Piper (diff)
Assignment Reviewer Roni Even
State Completed
Request Telechat review on draft-ietf-taps-transports-usage by General Area Review Team (Gen-ART) Assigned
Reviewed revision 08 (document currently at 09)
Result Ready w/nits
Completed 2017-09-05
review-ietf-taps-transports-usage-08-genart-telechat-even-2017-09-05-00
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-taps-transports-usage-??
Reviewer: Roni Even
Review Date: 2017-09-05
IETF LC End Date: 2017-09-14
IESG Telechat date: 2017-09-14

Summary: The document is ready with nits to be published as informational RFC

Major issues:

Minor issues:

Nits/editorial comments:
1. I think it will be better to have the introduction as section 1 and the
terminology as section 2 2.In section 3.1 in "open" I did not understand the
following sentence "more than TCP's maximum segment size (minus options used in
the SYN)" 3. in section 6 "The views expressed are solely those of the
author(s)" suggest removing the sentence since this document expresses the
views of the WG. 4. A general readability comment when describing primitives in
pass 2 the structure is
               PRIMITIVENAME.PROTOCOL:
                              Pass 1 primitive / event:
                               Parameters:
                                Returns:
                                Comments:
but it will be easier to read if there is for example a line space between the
paragraphs. look for example at CONNECT.TCP: it is difficult to see where
parameters finish and comment starts