Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-protocol-01.txt

Paul Kyzivat <pkyzivat@alum.mit.edu> Tue, 29 October 2013 18:30 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 400D311E8251 for <rtcweb@ietfa.amsl.com>; Tue, 29 Oct 2013 11:30:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.063
X-Spam-Level:
X-Spam-Status: No, score=0.063 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, J_CHICKENPOX_13=0.6, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RWbq9BK8st2C for <rtcweb@ietfa.amsl.com>; Tue, 29 Oct 2013 11:30:21 -0700 (PDT)
Received: from qmta15.westchester.pa.mail.comcast.net (qmta15.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:228]) by ietfa.amsl.com (Postfix) with ESMTP id 364B911E8185 for <rtcweb@ietf.org>; Tue, 29 Oct 2013 11:30:21 -0700 (PDT)
Received: from omta07.westchester.pa.mail.comcast.net ([76.96.62.59]) by qmta15.westchester.pa.mail.comcast.net with comcast id j3GW1m0051GhbT85F6WLeB; Tue, 29 Oct 2013 18:30:20 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta07.westchester.pa.mail.comcast.net with comcast id j6WL1m00F3ZTu2S3T6WL75; Tue, 29 Oct 2013 18:30:20 +0000
Message-ID: <526FFEBC.7090302@alum.mit.edu>
Date: Tue, 29 Oct 2013 14:30:20 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Eric Rescorla <ekr@rtfm.com>
References: <20131021191343.32574.60876.idtracker@ietfa.amsl.com> <03FBA798AC24E3498B74F47FD082A92F3D86C821@US70UWXCHMBA04.zam.alcatel-lucent.com> <A87B4291-FA11-43BB-B8F0-55C59CF63421@lurchi.franken.de> <CAOJ7v-20YkvazNLqmbjQcOkhaedd+MKm8d6x2oeL46imvuLrzA@mail.gmail.com> <03FBA798AC24E3498B74F47FD082A92F3D86C8DB@US70UWXCHMBA04.zam.alcatel-lucent.com> <120FE29C-150E-47BF-951C-B8124EB7A262@lurchi.franken.de> <03FBA798AC24E3498B74F47FD082A92F3D86C9A2@US70UWXCHMBA04.zam.alcatel-lucent.com> <5269F3B5.2020308@alvestrand.no> <03FBA798AC24E3498B74F47FD082A92F3D86CD4C@US70UWXCHMBA04.zam.alcatel-lucent.com> <526C4297.2000006@alum.mit.edu> <526CE0BE.90606@jesup.org> <526FD2D8.7000709@alum.mit.edu> <CABcZeBOiKboabmjRqWxzD8-SD9M01FkuQEH9M4+jN8dV=t0Z8Q@mail.gmail.com>
In-Reply-To: <CABcZeBOiKboabmjRqWxzD8-SD9M01FkuQEH9M4+jN8dV=t0Z8Q@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1383071420; bh=yF606yi4Mlk+KLRjMGKwhsHylRUzvf+nyrOIPHw87kk=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=tntReen9mgy00aMdmGdmLw9d+4o6iruu6T6j7XVqieYFVa8qmHcRbaKHSVWGjV6yS t6p0K2YuAIHL4MYspXEZKZakQ31t2ji9GllTHZXjVuJtLJr/gr1MpvcObZaDPBiSgw 3DiGd9MohexlPsuicGMFKJSpMvHmZcTLeqY2EdkoaSYL8VPOshQt3cpI1AOi20fhlD dOXrtJ9D3g8dqtJJp2IWmKH95sLOJ+C6pbLX+5Jq6lWR65Si68/FSutCCmZO51iCs9 1NVf7U/xQ5oHZG03uAbS8gib/Woqc9TU5L/uAQmV33dTK/4gt9AcZAhk+mlodVuDit ppRNIf7fxYBRA==
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-protocol-01.txt
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Oct 2013 18:30:27 -0000

Comment at end.

On 10/29/13 11:28 AM, Eric Rescorla wrote:
>
> On Tue, Oct 29, 2013 at 8:23 AM, Paul Kyzivat <pkyzivat@alum.mit.edu
> <mailto:pkyzivat@alum.mit.edu>> wrote:
>     On 10/27/13 5:45 AM, Randell Jesup wrote:
>         On 10/26/2013 6:30 PM, Paul Kyzivat wrote:
>
>                 My proposal has three elements, which together can
>                 guarantee that
>                 there are no stream id allocation conflicts between peers:
>                      1. The browser and application select stream ids
>                 based on initial
>                 SDP offerer/answerer role rather than DTLS role (e.g.,
>                 initial
>                 offerer uses even ids, initial answerer uses odd ids).
>                 With this
>                 rule, the offering application knows its role
>                 immediately without
>                 waiting for the DTLS or SDP handshake to occur.
>
>             A similar issue has come up in the discussion of partial
>             offers/answers. (Regarding how to assign a=mid values.) And
>             a similar
>             solution was proposed.
>
>             It was then rejected on the basis that sometimes both "ends"
>             think
>             they are offerers or answerers. This comes about as a result of
>             signaling-only B2BUAs that play games with O/A on two legs.
>
>         Exactly why we went with DTLS roles.
>
>     I'm not sure this eliminates the problem.
>
>     Is it not possible for an intermediary on the signaling path to
>     insert itself in the media path, manipulating the SDP such that the
>     two ends both establish the DTLS with the intermediary?
>
> There is a separate role negotiation for DTLS (actpass, etc.) that works
> even if both sides think they are the offerer or answerer.

I know about that. That mechanism is also used for TCP negotiation in 
SDP. And that is one place where an intermediary sometimes sticks its 
nose in explicitly to manipulate the roles, allowing both ends to be active.

In the current case, ICE and possible TURN result in getting the media 
path established without those games. So maybe there is less motivation 
for an intermediary. But still, they still seem to show up because 
administrators think they need them. And once there, couldn't the 
intermediary still end up making both ends think they are active?

	Thanks,
	Paul