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

Justin Uberti <juberti@google.com> Thu, 24 October 2013 18:05 UTC

Return-Path: <juberti@google.com>
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 1C4DA11E81AB for <rtcweb@ietfa.amsl.com>; Thu, 24 Oct 2013 11:05:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 l3hblPoLY2un for <rtcweb@ietfa.amsl.com>; Thu, 24 Oct 2013 11:05:24 -0700 (PDT)
Received: from mail-ve0-x232.google.com (mail-ve0-x232.google.com [IPv6:2607:f8b0:400c:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id 17BDA11E81C5 for <rtcweb@ietf.org>; Thu, 24 Oct 2013 11:05:22 -0700 (PDT)
Received: by mail-ve0-f178.google.com with SMTP id jy13so1850794veb.37 for <rtcweb@ietf.org>; Thu, 24 Oct 2013 11:05:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=WWaR8R0Vj1Bh3XpQwF73T8aUzCru13Kts8LyRhzIqbg=; b=MBQOYGjH2i1gP9G756RhU+yv4RHoqxsXfLIh3qSqevn3D4rc1WYnGmCey8y5p+85Yp 9Ja48dWnmwfXzJKPZYg12wibJRob00AvPGOUk6wbhh2or/j7LT6Eoaot+3MxdXn5lOdC /ChZ9dRanY4R6XqbcopSEqAuMKclk1ffCGSyB5PfFvm/p69YE4jjAm6BnSPIc1kuBXvm DL4VU0x2wMoyDnNvqFJBV4Q1c7QEzr0hN6FTAbIiXN8pbrOvrbahNQZZEP6E4jMtVx4/ +IYwWfJeiHGx5/G1aVc31o4CwiO1LXo3zEwSBVI8E9JhO4aLWzvGpsrSnR4Dxuub6eGT IAkw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=WWaR8R0Vj1Bh3XpQwF73T8aUzCru13Kts8LyRhzIqbg=; b=VbZsdmxun0pLdOEwBMxRW+z19mnm9jzDwyL1JIj06vgE6eGSfRXcTjdZCcJh9NeGXM ENtebcFdedQLaco1SRdUthMwe0inHDy280YfDqDPQgEHlpR3kRVYImgksEnyoEOE6luF Ml5ldhutPNsT4aGG1nw7AWyvn+94prsKVDLnkuj2wGcHQ6nWv/KRQGpVqVlwmvMxQuex +AGhw4C+T2zbKm4LKdycpmcF21uArioTtajZdALBJDswPOFodIlKoyBlEZY8fyxxyjDw mNIGEIFSVxazjFy38BmSyjRY3R7KPBIH0FUGw2IWcJf7Nl2O5Y9hAyH7p/8KLY43SBtb CIgA==
X-Gm-Message-State: ALoCoQkNy7FE3g4a8u1Mu3kwdyIyJ5BnUNDm0EvUmNFvmbAaBnBcqfiBhd6j32WWq7yJqGag84LQMeX2KjbSeHSk3g3/++nduDrXHg8TzW2ZFCKJeR416JLR7krH88wXaO2nfGmYNEoqeNF1D5sO28Zov1qpmYZYZkH6IgAwXnUE5KZOvdTlK6F7VD3G4NLjkcOu6X/tU3o+
X-Received: by 10.220.173.134 with SMTP id p6mr1648352vcz.36.1382637922471; Thu, 24 Oct 2013 11:05:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.110.101 with HTTP; Thu, 24 Oct 2013 11:05:02 -0700 (PDT)
In-Reply-To: <A87B4291-FA11-43BB-B8F0-55C59CF63421@lurchi.franken.de>
References: <20131021191343.32574.60876.idtracker@ietfa.amsl.com> <03FBA798AC24E3498B74F47FD082A92F3D86C821@US70UWXCHMBA04.zam.alcatel-lucent.com> <A87B4291-FA11-43BB-B8F0-55C59CF63421@lurchi.franken.de>
From: Justin Uberti <juberti@google.com>
Date: Thu, 24 Oct 2013 11:05:02 -0700
Message-ID: <CAOJ7v-20YkvazNLqmbjQcOkhaedd+MKm8d6x2oeL46imvuLrzA@mail.gmail.com>
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Content-Type: multipart/alternative; boundary="089e0158b15438ecc604e9807ab4"
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: Thu, 24 Oct 2013 18:05:31 -0000

In Chrome, the stream identifier isn't chosen until the DTLS roles are
known; as Michael says, this is fine because the DTLS roles are known
before the SCTP association starts up.

Note that the DTLS roles can change during the lifetime of the call, so the
initial role ends up being the one that is used.


On Thu, Oct 24, 2013 at 10:06 AM, Michael Tuexen <
Michael.Tuexen@lurchi.franken.de> wrote:

> On Oct 24, 2013, at 6:59 PM, "Ejzak, Richard P (Richard)" <
> richard.ejzak@alcatel-lucent.com> wrote:
>
> > I have a question about draft-ietf-rtcweb-data-protocol-01.  The browser
> uses DTLS role to determine which side uses even or odd stream identifiers.
>  What does the application on the side sending the initial SDP offer that
> establishes the peer connection do if it wants to create data channels
> before the DTLS role can be determined?  How does the browser know if the
> application tries to select a disallowed stream id?  If the application
> asks the browser to select the stream identifier before DTLS role can be
> determined, what does the browser do?
> Hmm. You can't setup a data channel before you have setup the SCTP
> association which you
> can't setup before the DTLS handshake is complete. So how do you want to
> setup a data channel
> before knowing the DTLS role?
>
> Best regards
> Michael
> >
> > Thanks,
> > Richard
> >
> > _______________________________________________
> > rtcweb mailing list
> > rtcweb@ietf.org
> > https://www.ietf.org/mailman/listinfo/rtcweb
> >
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>