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

[Gunnar Hellström <[e-mail]>]

Hi Christer,

Please see inline,

Den 2019-08-25 kl. 11:23, skrev Christer Holmberg:
> Hi Gunnar,
>
> ....
>
>>> So, what about the following text:
>>>
>>> "If an implementation needs to support multi-party scenarios,
>>> implementations (both clients and servers) need to support multiple
>>> simultaneous T.140 data channels, one for each source. At the time of
>>> writing this document, this is true even in scenarios where each participants
>>> communicate via a centralized conference server. The reason is that, unlike
>>> RTP media, WebRTC data channels and the T.140 protocol do not support the
>>> indication of the source of T.140 data.
>> "participants" s.b. "participant"
> Will fix.
>
>>> NOTE: Future extensions to T.140, or to the T140block, might allow
>>> indicating the source of T.140 data, in which case it might be possible to use
>>> a single T.140 data channel to transport data from multiple sources."
>> Should also "the T140 data channel data format" be among the options for where to place the source information?
> What is the "data format"? Isn't the T140block the data format?

Currently yes, but a more complex format could be defined, e.g. with a 
structure containing a source indicator and the T140blocks with some 
separator or structure. Of coulse it would be best to have that 
structure in place already from the beginning in this draft, so that 
there will be no interworking problems when a source address is 
introduced. Or at least a specified way to extend the format.


Regards

Gunnar

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

-- 
-----------------------------------------
Gunnar Hellström
Omnitor
[e-mail]
[phone]