Thank you, Bernie, for your intdir review. As you may have seen, I have referred to it during my own IESG review (I balloted a DISCUSS to have a discussion on the intended status though). Regards -éric On 25/08/2023, 16:35, "Int-dir on behalf of Bernie Volz via Datatracker" <int-dir-bounces@xxxxxxxx <mailto:int-dir-bounces@xxxxxxxx> on behalf of noreply@xxxxxxxx <mailto:noreply@xxxxxxxx>> wrote: Reviewer: Bernie Volz Review result: Ready 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 https://datatracker.ietf.org/group/intdir/about/ <https://datatracker.ietf.org/group/intdir/about/>. Based on my review, if I was on the IESG I would ballot this document as NO OBJECTION. 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. _______________________________________________ Int-dir mailing list Int-dir@xxxxxxxx <mailto:Int-dir@xxxxxxxx> https://www.ietf.org/mailman/listinfo/int-dir <https://www.ietf.org/mailman/listinfo/int-dir> -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
