|
Hi Linda,
Thank You for the review!
I think Gunnar has already answered your question. I have nothing to add, but I send this reply to indicate that I have ready your review :)
Regards,
Christer
From: Linda Dunbar via Datatracker <noreply@xxxxxxxx>
Sent: Friday, February 14, 2020 6:50 PM To: gen-art@xxxxxxxx <gen-art@xxxxxxxx> Cc: last-call@xxxxxxxx <last-call@xxxxxxxx>; mmusic@xxxxxxxx <mmusic@xxxxxxxx>; draft-ietf-mmusic-t140-usage-data-channel.all@xxxxxxxx <draft-ietf-mmusic-t140-usage-data-channel.all@xxxxxxxx> Subject: Genart last call review of draft-ietf-mmusic-t140-usage-data-channel-11 Reviewer: Linda Dunbar
Review result: Ready with Nits 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 treat these comments just like any other last call comments. For more information, please see the FAQ at <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>. Document: draft-ietf-mmusic-t140-usage-data-channel-11 Reviewer: Linda Dunbar Review Date: 2020-02-14 IETF LC End Date: 2020-02-06 IESG Telechat date: Not scheduled for a telechat Summary: This document specifies how a WebRTC data channel can be used as a transport mechanism for T.140. The document ties several other documents together, like xxx can be used, yyy must be followed, etc.. So it is not easy to validate the mechanism described by the document unless you are familiar with all the reference documents. But in general, the document is very clear. Just one question: ITU-T T.140 uses RTP as transport, whereas this document describes using WebRTC for transport. WebRTC uses SRTP. Does it mean this document proposes a different transport mechanism as the ITU-T T140? Why? Major issues: None Minor issues: None Nits/editorial comments: Linda Dunbar |
-- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
