Re: [MMUSIC] New Liaison Statement, "W3C WEBRTC WG to IETF MMUSIC WG"

Cullen Jennings <fluffy@iii.ca> Fri, 12 May 2017 20:56 UTC

Return-Path: <fluffy@iii.ca>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A0C4127977 for <mmusic@ietfa.amsl.com>; Fri, 12 May 2017 13:56:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.7
X-Spam-Level:
X-Spam-Status: No, score=-4.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a7_fZIkTT7A0 for <mmusic@ietfa.amsl.com>; Fri, 12 May 2017 13:56:09 -0700 (PDT)
Received: from smtp74.iad3a.emailsrvr.com (smtp74.iad3a.emailsrvr.com [173.203.187.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 467D8130F27 for <mmusic@ietf.org>; Fri, 12 May 2017 13:51:31 -0700 (PDT)
Received: from smtp26.relay.iad3a.emailsrvr.com (localhost [127.0.0.1]) by smtp26.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 698F75865; Fri, 12 May 2017 16:51:30 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp26.relay.iad3a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 8F80D57A8; Fri, 12 May 2017 16:51:29 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [10.1.3.67] (S01065475d0f7dcd1.cg.shawcable.net [70.75.17.123]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:587 (trex/5.7.12); Fri, 12 May 2017 16:51:30 -0400
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <7db1eac1-1667-8371-34ae-1462910f561c@cisco.com>
Date: Fri, 12 May 2017 14:51:28 -0600
Cc: Bo Burman <bo.burman@ericsson.com>, Ben Campbell <ben@nostrum.com>, Multiparty Multimedia Session Control Discussion List <mmusic@ietf.org>, Alexey Melnikov <aamelnikov@fastmail.fm>, stefhak@gmail.com, alvestrand@gmail.com
Content-Transfer-Encoding: quoted-printable
Message-Id: <C2CB1FF5-794D-4795-ACB2-3D67716853B5@iii.ca>
References: <149123343669.13157.18402606352918183703.idtracker@ietfa.amsl.com> <7db1eac1-1667-8371-34ae-1462910f561c@cisco.com>
To: Flemming Andreasen <fandreas@cisco.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/gyvp-NC4EcEJdk1XFbHUN_Q1XDI>
Subject: Re: [MMUSIC] New Liaison Statement, "W3C WEBRTC WG to IETF MMUSIC WG"
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 May 2017 20:56:12 -0000

Just read this now  and a few points ... 

1) I don't think this answer the questions asked.

2) the a and b miss the discussion of the context where this happens where things like a 2nd DTLS connection replacing a prior DTLS connection but on the same flow. 

I'm focused on getting JSEP completed right now so don't plan to spend time on this till somewhat later. 


> On Apr 21, 2017, at 6:44 AM, Flemming Andreasen <fandreas@cisco.com> wrote:
> 
> Greetings MMUSIC.
> 
> The issue raised below has been discussed on the MMUSIC mailing (see thread starting at https://www.ietf.org/mail-archive/web/mmusic/current/msg17646.html) and the recent MMUSIC meeting at IETF 98 (Chicago). A summary discussion has been provided at https://github.com/w3c/webrtc-pc/pull/1026#issuecomment-291194679 as well.
> 
> Based on the above, we suggest to answer the liaison statement as follows:
> 
> <quote>
> Thank you for raising the question regarding playout of unverified media to the MMUSIC WG. We have looked further into the issue raised and we 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
> (a) how ICE can complete prior to DTLS fingerprint exchange, or
> (b) how media can be received prior to ICE completing
> 
> It is currently unclear to us how either of these situations can arise in which case we do not believe the issue raised would apply to WebRTC.
> 
> For further background information, please refer to:
> - https://www.ietf.org/mail-archive/web/mmusic/current/msg17646.html
> - https://github.com/w3c/webrtc-pc/pull/1026#issuecomment-291194679
> </quote>
> 
> Please let the chairs know (before April 28) if you have any comments.
> 
> Thanks
> 
> -- Flemming
> 
> 
> 
> On 4/3/17 11:30 AM, Liaison Statement Management Tool wrote:
>> Title: W3C WEBRTC WG to IETF MMUSIC WG
>> Submission Date: 2017-04-03
>> URL of the IETF Web page: https://datatracker.ietf.org/liaison/1511/
>> Please reply by 2017-04-16
>> From: Bernard Aboba <bernard.aboba@gmail.com>
>> To: Flemming Andreasen <fandreas@cisco.com>,Bo Burman <bo.burman@ericsson.com>
>> Cc: Adam Roach <adam@nostrum.com>,Flemming Andreasen <fandreas@cisco.com>,Ben Campbell <ben@nostrum.com>,Bo Burman <bo.burman@ericsson.com>,Alexey Melnikov <aamelnikov@fastmail.fm>,Multiparty Multimedia Session Control Discussion List <mmusic@ietf.org>
>> Response Contacts: bernard.aboba@gmail.com, alvestrand@gmail.com, stefhak@gmail.com
>> Technical Contacts:
>> Purpose: For action
>> 
>> Body: Colleagues:
>> 
>> In the W3C WEBRTC WG, an issue has been submitted relating to playout of unverified media:
>> https://github.com/w3c/webrtc-pc/issues/849
>> 
>> It has been suggested that if the browser is configured to do so, that playout be allowed for a limited period
>> (e.g. 5 seconds) prior to fingerprint verification:
>> https://github.com/w3c/webrtc-pc/pull/1026
>> 
>> Section 6.2 of draft-ietf-mmusic-4572-update-13 contains the following text, carried over from RFC 4572:
>> 
>> Note that when the offer/answer model is being used, it is possible
>> for a media connection to outrace the answer back to the offerer.
>> Thus, if the offerer has offered a 'setup:passive' or 'setup:actpass'
>> role, it MUST (as specified in RFC 4145 [7]) begin listening for an
>> incoming connection as soon as it sends its offer. However, it MUST
>> NOT assume that the data transmitted over the TLS connection is valid
>> until it has received a matching fingerprint in an SDP answer. If
>> the fingerprint, once it arrives, does not match the client's
>> certificate, the server endpoint MUST terminate the media connection
>> with a bad_certificate error, as stated in the previous paragraph.
>> 
>> Given the outstanding issue relating to handling of unverified media, the Chairs of the W3C WEBRTC WG
>> would like to request clarification from the IETF MMUSIC WG as to the meaning of the "MUST NOT" in the
>> above paragraph. In particular, what is it permitted for a WebRTC implementation to do with received data prior
>> to verification? For example:
>> 
>> 1. May data received over the data channel be provided to the web application prior to verification?
>> 2. May received media be played out prior to verification?
>> Attachments:
>> 
>>     webrtc-liason-to-mmusic copy.pdf
>>     https://www.ietf.org/lib/dt/documents/LIAISON/liaison-2017-04-03-w3c-webrtc-mmusic-w3c-webrtc-wg-to-ietf-mmusic-wg-attachment-1.pdf
>> 
>> .
>> 
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic