- From: Ted Guild <ted@w3.org>
- Date: Thu, 04 Oct 2018 10:42:19 -0400
- To: Björkengren, Ulf <ulf.bjorkengren@volvocars.com>, public-automotive <public-automotive@w3.org>
- Message-ID: <4882da99506c0523e6ef1d36b9f495400a680925.camel@w3.org>
Not sure why the link you clicked on truncated, perhaps due to length and mail client wrapping on _, it should be: https://developer.mozilla.org/en-US/docs/Web/API/WebRTC_API/Using_data_channels It came through correctly in the archives. https://lists.w3.org/Archives/Public/public-automotive/2018Oct/0003 Resilience and encryption are two areas to delve into more detail for sure as well as what config to convey from VSS for establishing such a session. On Thu, 2018-10-04 at 08:58 +0000, Björkengren, Ulf wrote: > MO×¾M8-7pu=|MA{tÓDQ83L(#Hi, > > Regarding questions to Dominique, I think we could describe the idea > of using a VSS node to configure a WebRTC session. > If we follow my proposal to have a key named streamConfig, and its > value pair to be a JSON string, in its turn maybe containing > "streamProtocol" = "webRTC" > "streamSpecificConfig" = "xxx" > Then then question could be how should xxx look like to contain the > data necessary to set up a webRTC session (using a key-value pair > syntax)? > > Other questions could be about security in this context. Key > management for encrypted streams, ... > > WebRTC resilience when run over an unreliable transport channel? > > BTW, the link > https://developer.mozilla.org/en-US/docs/Web/API/WebRTC_API/Using_data > seems broken. > > BR > Ulf > > Ulf Björkengren Ph. D. > Connectivity Strategist > > M +4553562142 > ulf.bjorkengren@volvocars.com > > VOLVO CAR CORPORATION > 94014 Lund R&D Tech Center > Frederikskaj 10A > Copenhagen, Denmark > volvocars.com > > > -----Original Message----- > From: Ted Guild [mailto:ted@w3.org] > Sent: den 2 oktober 2018 16:35 > To: Björkengren, Ulf <ulf.bjorkengren@volvocars.com>; public- > automotive <public-automotive@w3.org> > Subject: Re: Streaming sensor support? > > Excerpt of an exchange with a colleague below and pointer to further > reading regarding potential applicability of WebRTC for data > streaming to/from vehicle. Continental, who is presently inactive > within W3C, had previously expressed interest in WebRTC for this > purpose. > > To keep things together here are the minutes for this topic as > prompted by Ulf's email. > > https://www.w3.org/2018/09/11-auto-minutes.html#item04 > > Dominique, who leads WebRTC, could potentially join us at TPAC to > discuss further and would like us to consider explicit questions we > might have of him. > > On Thu, 2018-09-27 at 16:01 +0200, Dominique Hazael-Massieux wrote: > > Le 19/09/2018 à 18:53, Ted Guild a écrit : > > [] > > > Also any primers on data streams in > > > WebRTC or pointers to other potential auto/WebRTC intersections > > > would be appreciated. > > > > https://developer.mozilla.org/en-US/docs/Web/API/WebRTC_API/Using_data > > _channels is a reasonably good technical intro. That being said, > > at > > the very high level, WebRTC data streams are an exact replica of > > Web > > sockets, with the addition of being configurable to be UDP-like > > (where > > web sockets can only be TCP-like, i.e. ordered and reliable). > > > > There are more tentative discussions to design WebRTC data streams > > built on QUIC, but I'm not sure how directly relevant to auto that > > would be. > > > > > > On Tue, 2018-09-11 at 13:38 +0000, Björkengren, Ulf wrote: > > Hi, > > > > I happened to look at https://5g-ppp.eu/5gcar/, and saw that they > > describe use cases where one car transmits a video stream showing > > what > > is in front of it, to cars behind it. Which got me to think about > > supporting streaming sensors in our API. > > > > I do not think we should try to invent any new streaming protocol, > > the > > idea I got was to use our API as the “control channel†for setting > > up > > the video stream (using any established streaming protocol). This > > could be realized by adding a new value to the “function†key that > > I > > have proposed to add to VSS, the value being called e.g. > > “streamsensorâ€, and the add a new key with the name > > “streamconfigâ€, > > having as value a JSON-formatted string containing the data needed > > to > > connect to the streaming server. > > > > I hope to get feedback to this idea at the WG meeting todayJ. > > > > BR > > Ulf > > > > > > Ulf Björkengren Ph. D. > > Connectivity Strategist > > > > M +4553562142 > > ulf.bjorkengren@volvocars.com > > > > VOLVO CAR CORPORATION > > 94014 Lund R&D Tech Center > > Frederikskaj 10A > > Copenhagen, Denmark > > volvocars.com > > > > > > -- > Ted Guild <ted@w3.org> > W3C Automotive Lead > http://www.w3.org > -- Ted Guild <ted@w3.org> W3C Automotive Lead http://www.w3.org
Received on Thursday, 4 October 2018 14:42:23 UTC