- From: Gunnar Hellström <gunnar.hellstrom@omnitor.se>
- Date: Mon, 18 Jun 2018 23:16:47 +0200
- To: public-webrtc@w3.org
I suggest to include real-time text (= text transmitted in the same rate as it is created so that it can be used for real conversational purposes) in the NV work. It is not included in RFC 7478, but included a U-C 5 in section 3.2 of https://tools.ietf.org/html/draft-ietf-rtcweb-data-channel-13 It could possibly be done by continuing the work started in https://datatracker.ietf.org/doc/draft-schwarz-mmusic-t140-usage-data-channel/ Use cases are e.g. 1. conversational two-party sessions with video, audio and real-time text. 2. conversational multi-party sessions with video, audio and real-time text. 3. sessions with automatic speech - to - real-time text conversion in one or both directions. 4. interworking WebRTC with audio, video and real-time text and legacy SIP with audio, video and real-time text. /Gunnar Den 2018-05-09 kl. 21:29, skrev Bernard Aboba: > On June 19-20 the WebRTC WG will be holding a face-to-face meeting in Stockholm, which will focus largely on WebRTC NV. > > Early on in the discussion, we would like to have a discussion of the use cases that WebRTC NV will address. > > Since the IETF has already published RFC 7478, we are largely interested in use cases that are either beyond those articulated in RFC 7478, or use cases in the document that somehow can be done better with WebRTC NV than they could with WebRTC 1.0. > > As with any successful effort, we are looking for volunteers to develop a presentation for the F2F, and perhaps even a document. >
Received on Monday, 18 June 2018 21:17:22 UTC