Re: [MMUSIC] T.140 in Data Channel scenarios

[Bernard Aboba <[e-mail]>]

Thanks for the explanation.  Would there be a way for some of this to make
its way into the document?  I think that would make it easier for the APA
to review.



Christer said:

"T.140 requires the transport mechanism to keep packets in order, and
without duplication. When using RTP, the sequence number is used to detect
out-of-order packets and loss of packets. You don’t have that mechanism in
a data channel, and T.140 itself does not contain a sequence number.



When using RTP, reliability can provided by sending of redundant data,
or by using FEC. FEC is RTP-specific, so you can’t use that on a data
channel.



I don’t think the redundancy mechanism can be used on the data channel
either, because it uses the RTP header timestamp.

 And, you can not re-transmit T.140 text on a data channel (T.140 RTP
packets are not re-transmitted either), because the receiver will not
be able to detect it (again, because T.140 does not contain a sequence
number).



Of course we could have defined an “envelope” for the data channel T.140
text, with sequence numbers. But, the idea was to simply send the T.140
text as the data channel itself provides delivery and reliability."

On Tue, Sep 24, 2019 at 1:12 PM Christer Holmberg <
[e-mail]> wrote:

> Hi Bernard,
>
>
>
> Gunnar will probably be able to give a better answer, but below are some
> comments from me.
>
>
>
> >At the W3C TPAC 2019 meeting last week,
> draft-ietf-mmusic-t140-usage-data-channel came up as part of a discussion
> of Accessible RTC Use Cases:
>
> >https://www.w3.org/WAI/APA/wiki/Accessible_RTC_Use_Cases
>
> >
>
> >Here are a few of the questions that came up.
>
> >
>
> >Section 3
>
> >
>
> >       +--------------------------+-------------------------------+
>
> >       | Subprotocol Identifier   | t140                          |
>
> >       | Transmission reliability | reliable                      |
>
> >       | Transmission order       | in-order                      |
>
> >       | Label                    | See Section 4.1 <https://tools.ietf.org/html/draft-ietf-mmusic-t140-usage-data-channel-05#section-4.1> and Section 6 <https://tools.ietf.org/html/draft-ietf-mmusic-t140-usage-data-channel-05#section-6> |
>
> >       +--------------------------+-------------------------------+
>
> >
>
> > Are there any situations in which unreliable or partially reliable transport might be appropriate?
>
> > For example, some participants envisaged scenarios in which low latency communications might be
>
> >  desirable, such as in emergencies, and questioned whether it might make sense to use the maxPacketLifetime
>
> > or maxRetransmissions parameters.
>
> >
>
> > So there was a question about whether it might ever make sense to support an unreliable data channel (possibly with redundancy).
>
>
>
> T.140 requires the transport mechanism to keep packets in order, and without duplication. When using RTP, the sequence number is used to detect out-of-order packets and loss of packets. You don’t have that mechanism in a data channel, and T.140 itself does not contain a sequence number.
>
>
>
> When using RTP, reliability can provided by sending of redundant data, or by using FEC. FEC is RTP-specific, so you can’t use that on a data channel.
>
>
>
> I don’t think the redundancy mechanism can be used on the data channel either, because it uses the RTP header timestamp.
>
>  And, you can not re-transmit T.140 text on a data channel (T.140 RTP packets are not re-transmitted either), because the receiver will not be able to detect it (again, because T.140 does not contain a sequence number).
>
>
>
> Of course we could have defined an “envelope” for the data channel T.140 text, with sequence numbers. But, the idea was to simply send the T.140 text as the data channel itself provides delivery and reliability.
>
>
>
> ---
>
>
>
> >Lost information (compared with RTP)
>
> >
>
> >We had some questions relating to information "lost in translation" between realtime text
>
> >and data channel.  This includes aspects of the RTP header, including SSRCs, timestamps and sequence numbers.
>
>  Yes, that information is lost.
>
>
>
> There were some discussions about including SSRC somehow, in order to support conferences where a mixer uses a single data channel for text received from multiple remote users, but we decided that it is outside the scope of this draft.
>
>
>
> Regards,
>
>
>
> Christer
>
>
>
>
>