Skip to main content

Last Call Review of draft-ietf-detnet-bounded-latency-08
review-ietf-detnet-bounded-latency-08-tsvart-lc-nishida-2022-02-06-00

Request Review of draft-ietf-detnet-bounded-latency
Requested revision No specific revision (document currently at 10)
Type Last Call Review
Team Transport Area Review Team (tsvart)
Deadline 2022-02-08
Requested 2022-01-25
Authors Norman Finn , Jean-Yves Le Boudec , Ehsan Mohammadpour , Jiayi Zhang , Balazs Varga
I-D last updated 2022-02-06
Completed reviews Rtgdir Last Call review of -06 by Tony Przygienda (diff)
Genart Last Call review of -08 by Gyan Mishra (diff)
Intdir Last Call review of -08 by Ralf Weber (diff)
Secdir Last Call review of -08 by Watson Ladd (diff)
Artart Last Call review of -08 by Robert Sparks (diff)
Tsvart Last Call review of -08 by Yoshifumi Nishida (diff)
Secdir Telechat review of -10 by Watson Ladd
Assignment Reviewer Yoshifumi Nishida
State Completed
Request Last Call review on draft-ietf-detnet-bounded-latency by Transport Area Review Team Assigned
Posted at https://mailarchive.ietf.org/arch/msg/tsv-art/6_6Z4v80wgJHNq6wg-YIGe4oZHo
Reviewed revision 08 (document currently at 10)
Result Ready w/nits
Completed 2022-02-06
review-ietf-detnet-bounded-latency-08-tsvart-lc-nishida-2022-02-06-00
This document has been reviewed as part of the transport area review team's
ongoing effort to review key IETF documents. These comments were written
primarily for the transport area directors, but are copied to the document's
authors and WG to allow them to address any issues raised and also to the IETF
discussion list for information.

When done at the time of IETF Last Call, the authors should consider this
review as part of the last-call comments they receive. Please always CC
tsv-art@ietf.org if you reply to or forward this review.

I think the draft is well written and informative. I haven't found any
transport related issues in the document. I think the draft is ready for
publication. One minor comment I have in the draft is if we can safely assume
there is no packet reorder in this architecture. I think it would be better to
mention it in the document.

Thanks,
--
Yoshi