Return-Path: <ibc@aliax.net>
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 AB4D1129518
 for <mmusic@ietfa.amsl.com>; Sat, 11 Mar 2017 07:25:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.698
X-Spam-Level: 
X-Spam-Status: No, score=-0.698 tagged_above=-999 required=5
 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001,
 RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001]
 autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key)
 header.d=aliax-net.20150623.gappssmtp.com
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 MtqosqNGtZJA for <mmusic@ietfa.amsl.com>;
 Sat, 11 Mar 2017 07:25:49 -0800 (PST)
Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com
 [IPv6:2a00:1450:400c:c09::234])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id E785A129524
 for <mmusic@ietf.org>; Sat, 11 Mar 2017 07:25:48 -0800 (PST)
Received: by mail-wm0-x234.google.com with SMTP id t189so13585944wmt.1
 for <mmusic@ietf.org>; Sat, 11 Mar 2017 07:25:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=aliax-net.20150623.gappssmtp.com; s=20150623;
 h=mime-version:in-reply-to:references:from:date:message-id:subject:to
 :cc; bh=vpiY7qPDyu7V6nQ+XzzS2arqa1OPsc6CggCRrCRC+TQ=;
 b=HdE6vCik1MPTMpSFAanznwfwSWsNndCWvSwc2wXGf2BlUUDCo6XZB42eAh/DruiP4A
 XwfE2Ecf3d1ZW4alwOO/uAt+PfYoBeiehkQo+CIOKCr0d26XksswiBTfLLuM6oEJWTqy
 J4V0BHWZ+pbeexmyMQBNLWPF+W0fVR9+EnjWWOSjvFVqzhFR8CSDUKlFa+bwu1lX81Hr
 a460KqMORvr1/wE90+2nVD5/r21l7C3G4gswKgXkYEq5rbM+q6xcXWLwrlxee6IZlkP+
 0vL6oNGcCPwxITbtMMPs3IgOO0Cz7Np92dTebCLDo6eMzlEUvRlLhyREkvUiXsMtO6g8
 qS0Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:in-reply-to:references:from:date
 :message-id:subject:to:cc;
 bh=vpiY7qPDyu7V6nQ+XzzS2arqa1OPsc6CggCRrCRC+TQ=;
 b=gac+TDsSPUoNnpzYwrVMjgvsQ8Zuwwz053ZLvadt9a4fWTZBjukjwSA2FW/Zuenq0Q
 4qajbyKqnpa9dnDMgtHqlcQtaXGPe30OfQrkxfIq2CDnF/vuyhZsrxXJVu9sBpvnxiie
 CANF7SCsjJ/s8SIQjZF1gRGHewI05yElsLxkbg3GhyvFMVrTapHsyJlFgV98wWWJMIB/
 +Qka6iABz+HgbA2/EZa3HAx/8A0ojdqzZX8BNKVJzdwdYuIsju4YgE+rNjtktPkoGEJK
 HkPyntuG5MDLaUPWo3WL6LJEVA5mQfYDi2EA909vs8nWDnSq4XNxIO3vaougracX+FNy
 xRgw==
X-Gm-Message-State: AFeK/H23LEpCJcJiwbU9OAO6G4ZhvFttl/fMTrN/OjRqyfQ+OREBpBm5fl/UODpVKzNI8Kc7Xll7f+ofOJQp+g==
X-Received: by 10.28.19.78 with SMTP id 75mr3813613wmt.108.1489245947392; Sat,
 11 Mar 2017 07:25:47 -0800 (PST)
MIME-Version: 1.0
Received: by 10.80.138.222 with HTTP; Sat, 11 Mar 2017 07:25:46 -0800 (PST)
Received: by 10.80.138.222 with HTTP; Sat, 11 Mar 2017 07:25:46 -0800 (PST)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4CB06EB1@ESESSMB109.ericsson.se>
References: <CAOW+2dseq8AmLKXFGUaiss8ahpkY1ZzYUD_KdirFE1rskfvqjw@mail.gmail.com>
 <CABkgnnUc-XsYivUzSs6W4it_Krykr-reJMDJXqKf5FvGw_NBPg@mail.gmail.com>
 <CAD5OKxvXTsTPaKFNdwS6tPBTAksD=jgiAFGuGMgbepOtBoFT+Q@mail.gmail.com>
 <CALiegfmyKz4JUXBoX7LaRe7U_yE2-_pbBKXHp14zm4DRSYGZgA@mail.gmail.com>
 <7594FB04B1934943A5C02806D1A2204B4CB06EB1@ESESSMB109.ericsson.se>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Date: Sat, 11 Mar 2017 16:25:46 +0100
Message-ID: <CALiegfkfntWj56NEXhr_waogJtsw9oy_P0Jo331ba_WNzBGRSQ@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=001a1146ee9ead90cf054a7617b6
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/vg24CqviTDU-_UJf0j0manepxsA>
Cc: Flemming Andreasen <fandreas@cisco.com>, "hta@google.com" <hta@google.com>,
 mmusic@ietf.org
Subject: Re: [MMUSIC] Handling of unverified data and media
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
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: Sat, 11 Mar 2017 15:25:50 -0000

--001a1146ee9ead90cf054a7617b6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

AFAIK you dont need a SDP aswer for that.

El 11/3/2017 16:24, "Christer Holmberg" <christer.holmberg@ericsson.com>
escribi=C3=B3:

> Hi,
>
> In case of a Data Channel, you also need to establish the SCTP associatio=
n
> before you can send any content.
>
> Regards,
>
> Christer
>
> -----Original Message-----
> From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of I=C3=B1aki Baz
> Castillo
> Sent: 11 March 2017 17:12
> To: Roman Shpount <roman@telurix.com>
> Cc: Flemming Andreasen <fandreas@cisco.com>; hta@google.com; mmusic WG <
> mmusic@ietf.org>
> Subject: Re: [MMUSIC] Handling of unverified data and media
>
> 2017-03-10 23:47 GMT+01:00 Roman Shpount <roman@telurix.com>:
> > My assumption always was that data is received, decoded and discarded
> > until fingerprint is received and verified. This way DTLS handshake
> > completes, key frames are decoded, but user is nor presented with any
> unverified media.
>
> Just imagine an app (running in a computer with public IP) which sends th=
e
> SDP offer to a server, DTLS handshake is done, and the server sends
> DataChannel messages to the browser *before* the browser receives the SDP
> answer.
>
> Do you mean that such a DataChannel messages should be discarded? I
> consider that catastrophic as the server may not know whether the browser
> has yet received the answer or not. Apps should implement some kind of
> 3-way signaling handshake (send offer, receive answer, send
> ACK) before the server sends any DataChannel message.
>
>
> --
> I=C3=B1aki Baz Castillo
> <ibc@aliax.net>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

--001a1146ee9ead90cf054a7617b6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">AFAIK you dont need a SDP aswer for that.</div><div class=
=3D"gmail_extra"><br><div class=3D"gmail_quote">El 11/3/2017 16:24, &quot;C=
hrister Holmberg&quot; &lt;<a href=3D"mailto:christer.holmberg@ericsson.com=
">christer.holmberg@ericsson.com</a>&gt; escribi=C3=B3:<br type=3D"attribut=
ion"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
In case of a Data Channel, you also need to establish the SCTP association =
before you can send any content.<br>
<br>
Regards,<br>
<br>
Christer<br>
<br>
-----Original Message-----<br>
From: mmusic [mailto:<a href=3D"mailto:mmusic-bounces@ietf.org">mmusic-boun=
ces@ietf.<wbr>org</a>] On Behalf Of I=C3=B1aki Baz Castillo<br>
Sent: 11 March 2017 17:12<br>
To: Roman Shpount &lt;<a href=3D"mailto:roman@telurix.com">roman@telurix.co=
m</a>&gt;<br>
Cc: Flemming Andreasen &lt;<a href=3D"mailto:fandreas@cisco.com">fandreas@c=
isco.com</a>&gt;; <a href=3D"mailto:hta@google.com">hta@google.com</a>; mmu=
sic WG &lt;<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a>&gt;<br>
Subject: Re: [MMUSIC] Handling of unverified data and media<br>
<br>
2017-03-10 23:47 GMT+01:00 Roman Shpount &lt;<a href=3D"mailto:roman@teluri=
x.com">roman@telurix.com</a>&gt;:<br>
&gt; My assumption always was that data is received, decoded and discarded<=
br>
&gt; until fingerprint is received and verified. This way DTLS handshake<br=
>
&gt; completes, key frames are decoded, but user is nor presented with any =
unverified media.<br>
<br>
Just imagine an app (running in a computer with public IP) which sends the =
SDP offer to a server, DTLS handshake is done, and the server sends DataCha=
nnel messages to the browser *before* the browser receives the SDP answer.<=
br>
<br>
Do you mean that such a DataChannel messages should be discarded? I conside=
r that catastrophic as the server may not know whether the browser has yet =
received the answer or not. Apps should implement some kind of 3-way signal=
ing handshake (send offer, receive answer, send<br>
ACK) before the server sends any DataChannel message.<br>
<br>
<br>
--<br>
I=C3=B1aki Baz Castillo<br>
&lt;<a href=3D"mailto:ibc@aliax.net">ibc@aliax.net</a>&gt;<br>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/mmusic</a><br=
>
</blockquote></div></div>

--001a1146ee9ead90cf054a7617b6--

