Re: [MMUSIC] Draft new: draft-holmberg-mmusic-t140-usage-data-channel

I also support adoption of this draft.

On Tue, Aug 20, 2019 at 12:46 PM <R.Jesske@telekom.de> wrote:

> Hi
> I support the adoption of the draft.
> Best Regards
> Roland
>
>
>
> sent with Corporate Mobile Service
>
> Am 17.08.2019 08:10 schrieb Christer Holmberg <
> christer.holmberg@ericsson.com>:
>
> Hi Bernard,
>
>
>
> Thank You for the information!
>
>
>
> Does that mean you think we should adopt the draft? :)
>
>
>
> Regards,
>
>
>
> Christer
>
>
>
> *Lähettäjä:* Bernard Aboba <bernard.aboba@gmail.com>
> *Lähetetty:* lauantai 17. elokuuta 2019 2.02
> *Vastaanottaja:* Christer Holmberg <christer.holmberg@ericsson.com>
> *Kopio:* mmusic@ietf.org
> *Aihe:* Re: [MMUSIC] Draft new:
> draft-holmberg-mmusic-t140-usage-data-channel
>
>
>
> You may be interested to know that
> draft-holmberg-mmusic-t140-usage-data-channel appears relevant to "RTC
> Accessibility Use Cases" recently developed by the W3C APA WG:
>
> https://www.w3.org/WAI/APA/wiki/Accessible_RTC_Use_Cases
>
>
>
>
>
>
>
> On Fri, Aug 9, 2019 at 10:42 AM Christer Holmberg <
> christer.holmberg@ericsson.com> wrote:
>
> Hi,
>
> Once upon a time in MMUSIC, there was work on a draft named
> draft-schwarz-mmusic-t140-usage-data-channel.
>
> Then, the authors stopped working on it, and nobody has been willing to
> take over.
>
> The draft is a 3GPP dependency, so there is a need to get it finalized.
>
> Some time ago I decided to take a close look at the draft, so see how much
> work it would take to finalize. One thing led ted to another, and I ended
> up re-writing the draft. Say hello to draft-holmberg-mmusic-t140-usage-data
> channel:
>
>
> https://www.ietf.org/id/draft-holmberg-mmusic-t140-usage-data-channel-00.txt
>
> The holmberg draft is based on the schwarz draft (also mentioned in the
> Acknowledgements), and much of the content is still the same. However, I
> have done editorial changes, and some re-structuring in order to better
> separate between the SDP considerations and the T.140 considerations.
>
> The NEW technical stuff is describing how the T.140 abstract service
> functions map to T.140 data channels established with SDP O/A.
>
> I have removed much of the Gateway text, because that's where most of the
> open issues were. That way, I also got rid of the dependency on
> draft-ietf-rtcweb-gateways, a draft I doubt is ever going to get finalized.
> If needed, gateway functions can be specified elsewhere, and 3GPP has
> already defined the H.248 parts for interworking between T.140 data channel
> and RFC 4103.
>
> There are currently no open issues in the draft.
>
> Regards,
>
> Christer
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>
>