Re: [MMUSIC] draft-holmberg-mmusic-t140-usage-data-channel - multi-party

[Christer Holmberg <[e-mail]>]

Hi,

>>> 4. A multi-party server S, combining a number of sources into one 
>>> call to a participant A, with real-time text from each other 
>>> participant (B,C,...) communicated in just one T140 data channel 
>>> between S and A. There is a need to indicate source for each 
>>> T140block sent to A. We currently have no way specified for that. An 
>>> extension of T.140 could do it.
>>
>> Is there a reason to ever do this?
>>
>> In audio and video the "mixing" actually does something irreversible. 
>> And it takes real work to do it, and doing so reduces the bandwith 
>> considerably over what is required to transmit the individual streams.
>>
>> For RTT none of that is true. There is very little impact in bandwidth 
>> or processing in transmitting them all as separate channels.
>>
>> So why not just say "don't do that"?
>
> Yes, interesting and realistic thought. It would likely be the best choice for many practical cases.
>
> I am not sure however how it will work with a huge conference with hundreds of participants, and some
> of them occasionally asking for the floor and send a bit of RTT text. A server using one data channel per 
> participant would either be required to establish an enormous amount ofT140 data channels being prepared
> to send what has been received, or take the effort to establish a new T140 data channel to all users at the
> moment a user gets the floor, and then possibly close it again.
>
> What do you think about that case?

You earlier told me about the IRC case, where meta data about the transmitted T140 text is included in the actual text, as some kind of a tag/label. You could define some kind of "protocol", so that the receiver doesn't print out those tags/labels as text, but use them for other things. 

That way you don't have to extend T140. But, it would obviously only work for endpoints that support the "protocol". Perhaps even IETF could define such "protocol"?

Regards,

Christer




>
>     Thanks,
>     Paul
>
> _______________________________________________
> mmusic mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/mmusic

_______________________________________________
mmusic mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/mmusic