Skip to main content

Telechat Review of draft-ietf-taps-arch-18

Request Review of draft-ietf-taps-arch
Requested revision No specific revision (document currently at 19)
Type Telechat Review
Team Internet Area Directorate (intdir)
Deadline 2023-09-01
Requested 2023-08-21
Requested by Éric Vyncke
Authors Tommy Pauly , Brian Trammell , Anna Brunstrom , Gorry Fairhurst , Colin Perkins
I-D last updated 2023-08-25
Completed reviews Opsdir Telechat review of -18 by Dhruv Dhody (diff)
Intdir Telechat review of -18 by Bernie Volz (diff)
Secdir Early review of -12 by Watson Ladd (diff)
Artart Early review of -11 by Robert Sparks (diff)
Secdir Last Call review of -17 by Watson Ladd (diff)
Opsdir Last Call review of -17 by Dhruv Dhody (diff)
Assignment Reviewer Bernie Volz
State Completed
Request Telechat review on draft-ietf-taps-arch by Internet Area Directorate Assigned
Posted at
Reviewed revision 18 (document currently at 19)
Result Ready
Completed 2023-08-25
I am an assigned INT directorate reviewer for draft-ietf-taps-arch. These
comments were written primarily for the benefit of the Internet Area Directors.
Document editors and shepherd(s) should treat these comments just like they
would treat comments from any other IETF contributors and resolve them along
with any other Last Call comments that have been received. For more details on
the INT Directorate, see

Based on my review, if I was on the IESG I would ballot this document as NO

The document is well written and seems complete.

I have only a few minor nits:

- In section 4.1.4:

“If successful, the Rendezvous call returns a Connection object to represent
the established peer-to-peer connection.”

Doesn’t sound very asynchronous, especially because of “established” which
implies it could take some time?

- In section 1.4, the last entry (Transport Services System) is missing period
at end on sentence.