Gunnar, Thank you very much for the explanation. Do you mean WebRTC data channel is used as Transport mechanism for real-time text, but Audio and Video of T140 still use RTP or SRTP? Linda -----Original Message----- From: Gunnar Hellström <gunnar.hellstrom@xxxxxxxxxx> Sent: Friday, February 14, 2020 1:03 PM To: Linda Dunbar <linda.dunbar@xxxxxxxxxxxxx>; gen-art@xxxxxxxx Cc: last-call@xxxxxxxx; mmusic@xxxxxxxx; draft-ietf-mmusic-t140-usage-data-channel.all@xxxxxxxx Subject: Re: [MMUSIC] Genart last call review of draft-ietf-mmusic-t140-usage-data-channel-11 Hi Linda, You ask below: "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?" ITU-T T.140 is a generally applicable presentation protocol for real-time text. Transports have been standardized for T.140 in a number of multimedia systems, most of them nowadays obsolete. E.g. ITU-T Q.224 for transport in H.320 ISDN Multimedia system, ITU-T V.18 for transport by low bitrate modems. etc. For use in traditional IP based multimedia systems ITU-T H.323 and IETF SIP, RTP transport is the standardized transport with packetization of T.140 specified in RFC 4103. When WewbRTC was specified it was early said that only audio and video would be transported by RTP. All other, including real-time text would use data channels. This decision was documented in use case U-C-5 in ietf-rtcweb-data-channel. The reviewed draft obeys that decision and specifies how the general T.140 transport is to be applied on a WebRTC data channel. Regards Gunnar Den 2020-02-14 kl. 17:50, skrev Linda Dunbar via Datatracker: > 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://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftrac..ietf.org%2Ftrac%2Fgen%2Fwiki%2FGenArtfaq&data=02%7C01%7Clinda.dunbar%40futurewei.com%7C0c2dca83131747ea654c08d7b18089ee%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637173037946430564&sdata=3V7hrGs6kgkropYOVPNYC87NczEVIYMDzUQO1DsuXZQ%3D&reserved=0>. > > 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 > > _______________________________________________ > mmusic mailing list > mmusic@xxxxxxxx > https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww. > ietf.org%2Fmailman%2Flistinfo%2Fmmusic&data=02%7C01%7Clinda.dunbar > %40futurewei.com%7C0c2dca83131747ea654c08d7b18089ee%7C0fee8ff2a3b24018 > 9c753a1d5591fedc%7C1%7C0%7C637173037946430564&sdata=hrfRcMoBuD%2BH > fqoYmBbjHuYbO829I1eCTpc1tXogeo0%3D&reserved=0 -- + + + + + + + + + + + + + + Gunnar Hellström Omnitor gunnar.hellstrom@xxxxxxxxxx +46 708 204 288 -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
