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

Michael Tuexen <Michael.Tuexen@lurchi.franken.de> Thu, 24 October 2013 19:20 UTC

Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 1BA9B11E83A0 for <rtcweb@ietfa.amsl.com>; Thu, 24 Oct 2013 12:20:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.479
X-Spam-Level:
X-Spam-Status: No, score=-2.479 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599]
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 o6ekkNyO8xtz for <rtcweb@ietfa.amsl.com>; Thu, 24 Oct 2013 12:20:38 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by ietfa.amsl.com (Postfix) with ESMTP id 09FAB11E83AA for <rtcweb@ietf.org>; Thu, 24 Oct 2013 12:20:35 -0700 (PDT)
Received: from [192.168.1.101] (p508F0D8F.dip0.t-ipconnect.de [80.143.13.143]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 4E6201C0C069B; Thu, 24 Oct 2013 21:20:33 +0200 (CEST)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <03FBA798AC24E3498B74F47FD082A92F3D86C8DB@US70UWXCHMBA04.zam.alcatel-lucent.com>
Date: Thu, 24 Oct 2013 21:20:31 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <120FE29C-150E-47BF-951C-B8124EB7A262@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> <CAOJ7v-20YkvazNLqmbjQcOkhaedd+MKm8d6x2oeL46imvuLrzA@mail.gmail.com> <03FBA798AC24E3498B74F47FD082A92F3D86C8DB@US70UWXCHMBA04.zam.alcatel-lucent.com>
To: "Ejzak, Richard P (Richard)" <richard.ejzak@alcatel-lucent.com>
X-Mailer: Apple Mail (2.1510)
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 19:20:39 -0000

On Oct 24, 2013, at 8:36 PM, "Ejzak, Richard P (Richard)" <richard.ejzak@alcatel-lucent.com> wrote:

> Justin, Michael,
> Thanks for the clarifications.  One more question.  What happens if the application tries to select a stream id before the DTLS role is known and it ends up selecting an invalid one?
I'm not completely familiar with the JS API, but if you want to select a stream, aren't
you managing the stream completely on your own. I think the DTLS role stuff is only
relevant if the streams are managed by the browser.
>  
> Michael,
> While it’s true that the data channel control protocol cannot open the channel with the peer before the DTLS role is known, the API allows the application to create the data channel before the DTLS role is known, in which case the sending of the Open message must wait until the SCTP association is established.  I want to know what the application is supposed to do it if needs to create data channels with preselected stream ids before the DTLS role is known.  This seems like something that the spec should make clear rather than leaving it to implementation.
Can you assign the stream ID in the API? Could you point me to the text?

Best regards
Michael
>  
> Thanks,
> Richard
>  
> From: Justin Uberti [mailto:juberti@google.com] 
> Sent: Thursday, October 24, 2013 1:05 PM
> To: Michael Tuexen
> Cc: Ejzak, Richard P (Richard); rtcweb@ietf.org
> Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-data-protocol-01.txt
>  
> 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
>