IETF Logo Mail Archive

Re: [rtcweb] data channel protocol comments and potential agenda topic

"Ejzak, Richard P (Richard)" <richard.ejzak@alcatel-lucent.com> Mon, 23 July 2012 13:16 UTC

Return-Path: <richard.ejzak@alcatel-lucent.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 9B55F21F86C2 for <rtcweb@ietfa.amsl.com>; Mon, 23 Jul 2012 06:16:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.844
X-Spam-Level:
X-Spam-Status: No, score=-9.844 tagged_above=-999 required=5 tests=[AWL=0.405, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
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 LKWH8iAs+Yz1 for <rtcweb@ietfa.amsl.com>; Mon, 23 Jul 2012 06:16:57 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by ietfa.amsl.com (Postfix) with ESMTP id AC66121F8699 for <rtcweb@ietf.org>; Mon, 23 Jul 2012 06:16:55 -0700 (PDT)
Received: from FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (FRMRSSXCHHUB01.dc-m.alcatel-lucent.com [135.120.45.61]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q6NDDPGF006111 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <rtcweb@ietf.org>; Mon, 23 Jul 2012 15:16:53 +0200
Received: from US70UWXCHHUB01.zam.alcatel-lucent.com (135.5.2.48) by FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (135.120.45.61) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 23 Jul 2012 15:16:18 +0200
Received: from US70TWXCHMBA12.zam.alcatel-lucent.com ([169.254.6.16]) by US70UWXCHHUB01.zam.alcatel-lucent.com ([135.5.2.48]) with mapi id 14.02.0247.003; Mon, 23 Jul 2012 09:16:16 -0400
From: "Ejzak, Richard P (Richard)" <richard.ejzak@alcatel-lucent.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] data channel protocol comments and potential agenda topic
Thread-Index: AQHNaJ/kd4zo5CuRTk+Se+350bJd3Jc21oSA
Date: Mon, 23 Jul 2012 13:16:14 +0000
Message-ID: <03FBA798AC24E3498B74F47FD082A92F1771E0E7@US70TWXCHMBA12.zam.alcatel-lucent.com>
References: <03FBA798AC24E3498B74F47FD082A92F1770A313@US70UWXCHMBA04.zam.alcatel-lucent.com> <500A9A7B.8050400@ericsson.com> <03FBA798AC24E3498B74F47FD082A92F1771C06D@US70TWXCHMBA12.zam.alcatel-lucent.com> <500C2708.6040704@ericsson.com> <82DE409C-7669-49B9-AC2C-8834F626C39A@lurchi.franken.de> <500CF488.1070306@jesup.org>
In-Reply-To: <500CF488.1070306@jesup.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.5.27.12]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.80
Subject: Re: [rtcweb] data channel protocol comments and potential agenda topic
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: Mon, 23 Jul 2012 13:16:57 -0000

On July 23, Randell Jesup wrote:
> Correct.  The protocol is *very* simple.  I'll note that my current
> draft indicates signaling for DataChannels that would at least be
> extendable (at the IETF/SDP level) to allowing other/alternate SCTP
> associations on the same DTLS channel, running other protocols, though
> for W3 WebRTC there would be a single one running the DataChannel protocol.

While this may be true from a protocol perspective, it would still require a new API to access other protocols, so they are effectively unavailable to JS.

v2.23.0 | Report a Bug | By Email