IETF Logo Mail Archive

Re: [rtcweb] ICE TCP Candidates and SCTP DataChannels ?

Michael Tuexen <Michael.Tuexen@lurchi.franken.de> Fri, 03 January 2014 17:17 UTC

Return-Path: <Michael.Tuexen@lurchi.franken.de>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E97BD1ADFE0 for <rtcweb@ietfa.amsl.com>; Fri, 3 Jan 2014 09:17:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.789
X-Spam-Level:
X-Spam-Status: No, score=-1.789 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001] autolearn=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 sq0LncDetauw for <rtcweb@ietfa.amsl.com>; Fri, 3 Jan 2014 09:17:16 -0800 (PST)
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 AEF281ADFDC for <rtcweb@ietf.org>; Fri, 3 Jan 2014 09:17:15 -0800 (PST)
Received: from [192.168.1.103] (p508F020F.dip0.t-ipconnect.de [80.143.2.15]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 063B61C0C0692; Fri, 3 Jan 2014 18:17:05 +0100 (CET)
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <1388733929.28294.19.camel@TesterBox>
Date: Fri, 03 Jan 2014 18:17:05 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <46EC7110-272B-4948-87B6-46E54D06D225@lurchi.franken.de>
References: <1388733929.28294.19.camel@TesterBox>
To: Olivier Crête <olivier.crete@collabora.com>
X-Mailer: Apple Mail (2.1510)
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] ICE TCP Candidates and SCTP DataChannels ?
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 03 Jan 2014 17:17:18 -0000

On Jan 3, 2014, at 8:25 AM, Olivier Crête <olivier.crete@collabora.com> wrote:

> Hello,
> 
> draft-ietf-rtcweb-transports-01 mentions ICE TCP Candidates [RFC6062],
> but there is no mention of how they integrated with the SCTP-based data
> channels? ICE-TCP seems to be a good match for ordered reliable
> channels, as I expect these will be the most common. Is there any plans
A single TCP connection for each ordered reliable data channel? How
would you do message framing?
> to support those? Or to do something akin to RFC 4571 framing to put
> SCTP in an ICE-TCP connection? Then that raises the question of DTLS,
> would we want to do SCTP-over-DTLS-over-rfc4571-over-TCP or
> SCTP-over-rfc4571-over-TLS-over-TCP ?
Why do you want to use SCTP-over-rfc4571-over-TLS-over-TCP instead of
SCTP-over-DTLS-over-rfc4571-over-TCP?

Best regards
Michael
> 
> -- 
> Olivier Crête
> olivier.crete@collabora.com
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email