Last Call Review of draft-ietf-avtcore-rfc7983bis-07
review-ietf-avtcore-rfc7983bis-07-opsdir-lc-romascanu-2023-01-13-00
Request | Review of | draft-ietf-avtcore-rfc7983bis |
---|---|---|
Requested revision | No specific revision (document currently at 09) | |
Type | Last Call Review | |
Team | Ops Directorate (opsdir) | |
Deadline | 2023-01-17 | |
Requested | 2023-01-03 | |
Authors | Dr. Bernard D. Aboba , Gonzalo Salgueiro , Colin Perkins | |
I-D last updated | 2023-01-13 | |
Completed reviews |
Opsdir Last Call review of -07
by Dan Romascanu
(diff)
Genart Last Call review of -07 by Meral Shirazipour (diff) Tsvart Last Call review of -07 by Yoshifumi Nishida (diff) Artart Last Call review of -07 by Marc Blanchet (diff) Secdir Last Call review of -07 by Rich Salz (diff) Intdir Telechat review of -08 by Bernie Volz (diff) |
|
Assignment | Reviewer | Dan Romascanu |
State | Completed | |
Request | Last Call review on draft-ietf-avtcore-rfc7983bis by Ops Directorate Assigned | |
Posted at | https://mailarchive.ietf.org/arch/msg/ops-dir/ai_4HtO6TQNVUIGM3BPxk7yOnGI | |
Reviewed revision | 07 (document currently at 09) | |
Result | Ready | |
Completed | 2023-01-13 |
review-ietf-avtcore-rfc7983bis-07-opsdir-lc-romascanu-2023-01-13-00
This document updates [RFC7983] and [RFC5764] to also allow QUIC [RFC9000] to be multiplexed on the same port, supplementary to DTLS, RTP, RTCP, STUN, TURN and ZRTP. The document is clear and straightforward. Operators should be aware about the scope of the document, but otherwise I see no other operational or manageability issues. As an editorial side note, I found the Abstract a little misleading. At first reading one may understand that the full multiplexing scheme is defined in this RFC, while in reality it needs to be used together with RFC 7983. Maybe the authors should consider shortening the text and making clear that the scope of the RFC is adding QUIC multiplexing. The document is ready from an OPS-DIR point of view.