W3C home > Mailing lists > Public > public-webrtc@w3.org > May 2017

Re: Suggested resolution of Issue 849: Specify an AllowUnverifiedMedia RTCConfiguration property

From: Cullen Jennings (fluffy) <fluffy@cisco.com>
Date: Tue, 2 May 2017 21:15:05 +0000
To: Roman Shpount <roman@telurix.com>
CC: Bernard Aboba <Bernard.Aboba@microsoft.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <A72ABEE5-1967-4E02-82F4-AA05DABBF161@cisco.com>

> On Apr 26, 2017, at 10:26 AM, Roman Shpount <roman@telurix.com> wrote:
> 
> Cullen,
> 
> Until we see the scenario where unverified media can be received by a full ICE end point which implements consent to send, there is general consensus that unverified media to WebRTC endpoint cannot happen.
> 
> Regards,

The example I gave was fully consistent with everything WebRTC requires including consent. 

> 
> _____________
> Roman Shpount
> 
> On Wed, Apr 26, 2017 at 11:45 AM, Cullen Jennings (fluffy) <fluffy@cisco.com> wrote:
> 
> I did explain the issue where this can happen in the PR. There may not be agreement that the case can not happen but there is also not agreement that it can not. So until someone explains to my why this can not happen, I think it should remain open. I'm not really following the mmusic conversation and have no idea why they are sending a liaison like that.
> 
> 
> > On Apr 25, 2017, at 11:52 AM, Bernard Aboba <Bernard.Aboba@microsoft.com> wrote:
> >
> > At the March 1, 2017 virtual interim, the WEBRTC WG discussed Issue 849 and PR 1026 and Peter and Cullen were given the task of producing “more exact info on the offers and answers”: https://www.w3.org/2017/03/01-webrtc-minutes

> >
> > Since then, we have had considerable discussion on Github relating to PR 1026 , as well as related discussion on the IETF MMUSIC WG mailing list and at the IETF 98 MMUSIC WG meeting.
> >
> > Over time, the focus of the discussion has narrowed to whether it is possible for unverified media to arise within the WebRTC 1.0 API.
> >
> > The MMUSIC WG is now in the process of drafting a response to the W3C WEBRTC WG liaison statement :
> > https://mailarchive.ietf.org/arch/msg/mmusic/TcyynbwyBsmJhE9eLac-gt33wtQ

> >
> > In this draft liaison response, the IETF MMUSIC WG indicates that they “would like to request a clarification of the exact sequence of events that WEBRTC believes can lead to this.  In particular, we ask you to please show either
> >
> >       • How ICE can complete prior to DTLS fingerprint exchange, or
> >       • How media can be received prior to ICE completing”
> >
> > Looking over the discussion of PR 1026 , multiple scenarios are investigated, but in the end, it appears that in each scenario the above conditions cannot be met.
> >
> > Given the extensive discussion that has taken place, and the inability to come up with a sequence of events, I would like to propose that we close Issue 849.
> >
> > Thoughts?
> 
> 

Received on Tuesday, 2 May 2017 21:15:40 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:50 UTC