- From: Janina Sajka (janina@rednote.net) <janina@rednote.net>
- Date: Wed, 21 Aug 2019 10:38:35 -0400
- To: Bernard Aboba <Bernard.Aboba@microsoft.com>
- Cc: Harald Alvestrand <hta@google.com>, Jan-Ivar Bruaroey <jib@mozilla.com>, Dominique Hazael-Massieux <dom@w3.org>, "White, Jason J" <jjwhite@ets.org>, Judy Brewer <jbrewer@w3.org>, W3C WAI Accessible Platform Architectures <public-apa@w3.org>, "public-rqtf@w3.org" <public-rqtf@w3.org>, Joshue O Connor <joconnor@w3.org>, Michael Cooper <cooper@w3.org>
Thank you, Bernard. We look forward to meeting with you in Fukuoka. Best, Janina Bernard Aboba writes: > I have set aside time on the WEBRTC WG schedule from 1 PM - 2 PM on Friday for a joint meeting. > > ________________________________ > From: Janina Sajka (janina@rednote.net) <janina@rednote.net> > Sent: Wednesday, August 21, 2019 5:20 AM > To: Bernard Aboba <Bernard.Aboba@microsoft.com> > Cc: Harald Alvestrand <hta@google.com>; Jan-Ivar Bruaroey <jib@mozilla.com>; Dominique Hazael-Massieux <dom@w3.org>; White, Jason J <jjwhite@ets.org>; Judy Brewer <jbrewer@w3.org>; W3C WAI Accessible Platform Architectures <public-apa@w3.org>; public-rqtf@w3.org <public-rqtf@w3.org>; Joshue O Connor <joconnor@w3.org>; Michael Cooper <cooper@w3.org> > Subject: Re: Request for joint meeting at TPAC > > Hello Bernard, All: > > I have learned one of our key participants has an early evening flight > Friday. > > So, we would prefer to make our joint meeting an early afternoon meeting > on TPAC Friday. APA is planning lunch from Noon-1:00 PM. So, would 1:00 > PM work as our joint time? > > Best, > > Janina > > Bernard Aboba writes: > > Good to hear from you, Janina. > > > > We are still in the early stages of working through the WEBRTC WG schedule for TPAC 2019, but currently it would appear that the best time for a joint meeting would be on Friday afternoon. During that portion of the agenda we will be considering WebRTC-NV Use Cases<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%2Fwebrtc-nv-use-cases%2F&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C8c642011771e4801849508d726320afd%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637019868694597951&sdata=DJQmzJEQRK87cc30zp6%2FTFr9v8UE7MaTgO7B2P%2FAT1E%3D&reserved=0>. Note that within these "Next Version" use cases we have included requirements for access to raw media, which can be leveraged to enable accessibility functionality such as speech transcription, language translation and captioning. > > > > A bit of background on the division of labor between the W3C and IETF with respect to WebRTC. > > > > The W3C WEBRTC WG focuses on the development of APIs, while the IETF ART Area (including the RTCWEB, MMUSIC, RUM and SLIM WGs) has focused on protocol development. In practice, this means that the IETF owns protocol development work relating to accessibility, such as the following: > > > > OPUS WG<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fwg%2Fcodec%2Fdocuments%2F&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C8c642011771e4801849508d726320afd%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637019868694597951&sdata=ZbKQJ11%2FRu%2BPWjUKF93Xy5RxRVwpD5iWOcbBJslcPHU%3D&reserved=0>: This concluded WG developed the Opus Codec<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc6716&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C8c642011771e4801849508d726320afd%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637019868694597951&sdata=X82HU3D1GyfnFe6OOeUhyQEr%2Fo939fq46eACrY4ABP8%3D&reserved=0> which is widely implemented in browsers, supports high quality stereo audio and is IBR approved for Appendix C, Section 412.4 "Digital Encoding of Speech". > > > > RUM WG<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fwg%2Frum%2Fcharters&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C8c642011771e4801849508d726320afd%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637019868694597951&sdata=rV6Uxu%2FsK2WczH6PGVTdYWCeJIVoHXrl9s3QEvJWUS4%3D&reserved=0>: The recently chartered IETF RUM WG is developing a profile of SIP and media features for use with video relay services, based on the protocols defined in the IETF RTCWEB WG. An individual submission under consideration for adoption in IETF RUM WG is available here: https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-rosen-rue&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C8c642011771e4801849508d726320afd%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637019868694607948&sdata=yK9Tr%2FwtRDIDXjGGt7YE%2B7WsbNuM8KGypMwXSrMS6gA%3D&reserved=0 > > > > MMUSIC WG<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fwg%2Fmmusic%2Fcharters&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C8c642011771e4801849508d726320afd%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637019868694607948&sdata=eOle0WFN0tmTcdhJlgRbVTsqlRbzaJjMJQg1AK4dV0I%3D&reserved=0>: Christer Holmberg has recently revived work on RTT over the WebRTC Data Channel, which is a 3GPP dependency ( https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-holmberg-mmusic-t140-usage-data-channel&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C8c642011771e4801849508d726320afd%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637019868694607948&sdata=D3fw1LBM1L7q%2FLLRVnId53kRl%2F%2F2GqJ%2BYkgWLtcXl2Y%3D&reserved=0 ). The approach described in this draft is also mentioned in draft-rosen-rue Section 7.2 (WebRTC data channel to RTT gateway). > > > > SLIM WG<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fwg%2Fslim%2Fcharters&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C8c642011771e4801849508d726320afd%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637019868694607948&sdata=8JsTwUVYnIeEqItAR%2B38jpRDPb6IUoQA%2BO3kU6FQZ%2Fg%3D&reserved=0>: This (now concluded) WG developed RFC 8373<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc8373&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C8c642011771e4801849508d726320afd%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637019868694607948&sdata=lNfKYVS%2FwARmyiQxoTLKC6knfV3K%2FQ%2B9AxaO%2F79zpTo%3D&reserved=0> "Negotiating Human Language in Real-Time Communication", which defines language negotiation (including negotiation of sign language support) in SDP. Note that SLIM WG did not get into the SIP aspects of language preference, such as mechanisms for call routing in VRS or NG emergency services. > > > > > > > > > > > > > > > > > > > > > > ________________________________ > > From: Janina Sajka (janina@rednote.net) <janina@rednote.net> > > Sent: Wednesday, August 14, 2019 12:36 PM > > To: Bernard Aboba <Bernard.Aboba@microsoft.com>; Harald Alvestrand <hta@google.com>; Jan-Ivar Bruaroey <jib@mozilla.com> > > Cc: Dominique Hazael-Massieux <dom@w3.org>; White, Jason J <jjwhite@ets.org>; Judy Brewer <jbrewer@w3.org>; W3C WAI Accessible Platform Architectures <public-apa@w3.org>; public-rqtf@w3.org <public-rqtf@w3.org>; Joshue O Connor <joconnor@w3.org>; Michael Cooper <cooper@w3.org> > > Subject: Request for joint meeting at TPAC > > > > Dear W3C Colleagues: > > > > This is a request for a joint meeting from the Accessible Platform > > Architectures (APA) Working Group. We note that both our WGs are meeting > > Thursday and Friday at TPAC, and we would appreciate an hour of your > > time on several accessibility topics of joint interest. > > > > Most critically we in APA are concerned that implementations of WebRTC > > support cann support the Real Time Text (RTT) protocol being required of > > telecommunications providers in the U.S. by the Federal Communications > > Commission (FCC). There are several wrinkles to this requirement, > > several of which are addressed in the forwarded message below. We want > > you to be fully aware of the requirements as they currently exist, and > > their impact on persons who are deaf or hearing impaired (primarily). > > > > Beyond this most immediate concern we have been developing several > > accessibility related use cases we would hope you can address in future > > revisions of WebRTC, if not already supported. An early draft of our > > document is available here: > > > > https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FWAI%2FAPA%2Fwiki%2FAccessible_RTC_Use_Cases&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C8c642011771e4801849508d726320afd%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637019868694607948&sdata=e2V3r6QFNF74zwtoaJ7bpKsYuIaznV4FQJ3M%2FxaiLAI%3D&reserved=0 > > > > Please advise if and when we might meet during Thursday or Friday of > > TPAC. > > > > Thanking you in advance for your consideration, > > > > Janina Sajka, Chair > > Accessible Platform Architectures (APA) WG > > https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org%2FWAI%2FAPA%2F&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C8c642011771e4801849508d726320afd%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637019868694607948&sdata=k3WXd0p68WqIf1QzwqjZDZqZXPIJqbpSQFnX8kOFlNs%3D&reserved=0 > > > > > > Joshue O Connor writes: > > > Hi Dom, > > > > > > [with Janina and Jason - leads on APA/RQTF respectively, and Judy] > > > > > > It was good to talk earlier and hope here to unpick the question about RTT > > > interoperability and how WebRTC will need to support that. [1] > > > > > > I'm outlining the 'case' here and looking forward to input from Janina, > > > Jason and Judy on this, especially in light of FCC requirements. [2] > > > > > > Looking back at this, and now trying to put together a 'case' - My own > > > reading of the FCC requirements is that it is referencing RTT IETF and that > > > it is implicit (if not explicit ) that there will be interoperability > > > requirements. For example, in the transition from TTY to RTT is that this > > > the case where IETF RFC 4103 is referenced directly in the 'transitioning > > > to' doc. [3] > > > > > > There were some interesting insights from Jason on a private mail - where he > > > mentions for example that if running a relay service, that would need some > > > level of interoperability, so that the RTT wouldn’t be handled differently > > > depending on which WebRTC-based application was bringing the user into the > > > conversation. There is also interoperability with SIP and other existing > > > protocols to consider. > > > > > > Jason also makes the point that it may not be sufficient for each WebRTC > > > application to create its own means of real-time text handling. Should the > > > question is, should this be defined and handled in WebRTC user cases for > > > example? > > > > > > OK, this mail was to get the ball rolling and start to make the case for RTT > > > interoperability support in WebRTC. > > > > > > Thanks and I hope this is helpful Dom - looking forward to your input > > > > > > Josh > > > > > > [1] https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Frealtimetext.org%2Frtt_in_detail%2Fstandards%2Fietf&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C8c642011771e4801849508d726320afd%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637019868694607948&sdata=lnUkPH6kC4CDrAeiNhK%2BoXFcEfqA0b%2Btt83XwMVmWUY%3D&reserved=0 > > > > > > [2] https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.fcc.gov%2Fdocument%2Ftransition-tty-real-time-text-technology&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C8c642011771e4801849508d726320afd%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637019868694607948&sdata=s20JnvwgedmFWLmunKtqItHzNBODrgKE3%2FSrM0Fdyg8%3D&reserved=0 > > > > > > [3] https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Frfc%2Frfc4103.txt&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C8c642011771e4801849508d726320afd%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637019868694607948&sdata=Tcs1kaAwr2EqcHPYadw7ZeC%2BQvteCAt1yib7teaNJgY%3D&reserved=0 > > > > > > > > > -- > > > Emerging Web Technology Specialist/A11y (WAI/W3C) > > > > -- > > > > Janina Sajka > > > > Linux Foundation Fellow > > Executive Chair, Accessibility Workgroup: https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fa11y.org&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C8c642011771e4801849508d726320afd%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637019868695047696&sdata=R5ncrUeBctQ1YfMe69N5%2BWNtK4MqX9igSYBou7yKZ%2Bs%3D&reserved=0 > > > > The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) > > Chair, Accessible Platform Architectures https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org%2Fwai%2Fapa&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C8c642011771e4801849508d726320afd%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637019868695047696&sdata=P53cf5TXEY%2BNQ5%2FbDmfjdxuLfOTYwR%2FJL06E%2BJ71FTE%3D&reserved=0 > > > > -- > > Janina Sajka > > Linux Foundation Fellow > Executive Chair, Accessibility Workgroup: https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fa11y.org&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C8c642011771e4801849508d726320afd%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637019868695047696&sdata=R5ncrUeBctQ1YfMe69N5%2BWNtK4MqX9igSYBou7yKZ%2Bs%3D&reserved=0 > > The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) > Chair, Accessible Platform Architectures https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org%2Fwai%2Fapa&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C8c642011771e4801849508d726320afd%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637019868695047696&sdata=P53cf5TXEY%2BNQ5%2FbDmfjdxuLfOTYwR%2FJL06E%2BJ71FTE%3D&reserved=0 > -- Janina Sajka Linux Foundation Fellow Executive Chair, Accessibility Workgroup: http://a11y.org The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) Chair, Accessible Platform Architectures http://www.w3.org/wai/apa
Received on Wednesday, 21 August 2019 14:39:10 UTC