Re: [rtcweb] Data Transport, was: Re: RTCWeb default signaling protocol [was RE: About defining a signaling protocol for WebRTC (or not)]

Saúl Ibarra Corretgé <saul@ag-projects.com> Wed, 21 September 2011 13:46 UTC

Return-Path: <saul@ag-projects.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 C748B21F8C99 for <rtcweb@ietfa.amsl.com>; Wed, 21 Sep 2011 06:46:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.708
X-Spam-Level:
X-Spam-Status: No, score=-1.708 tagged_above=-999 required=5 tests=[AWL=-0.020, BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, MIME_8BIT_HEADER=0.3]
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 qbOgdA-RNviJ for <rtcweb@ietfa.amsl.com>; Wed, 21 Sep 2011 06:46:06 -0700 (PDT)
Received: from mail.sipthor.net (node06.dns-hosting.info [85.17.186.6]) by ietfa.amsl.com (Postfix) with ESMTP id 3835521F8C96 for <rtcweb@ietf.org>; Wed, 21 Sep 2011 06:46:06 -0700 (PDT)
Received: by mail.sipthor.net (Postfix, from userid 5001) id 020CAB01B5; Wed, 21 Sep 2011 15:48:33 +0200 (CEST)
Received: from [192.168.99.36] (ip3e830637.speed.planet.nl [62.131.6.55]) by mail.sipthor.net (Postfix) with ESMTPSA id 5CB41B0057; Wed, 21 Sep 2011 15:48:33 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="iso-8859-1"
From: Saúl Ibarra Corretgé <saul@ag-projects.com>
In-Reply-To: <05D1C2F6-96C3-44E3-9FC2-AD2C893C9FC6@acmepacket.com>
Date: Wed, 21 Sep 2011 15:48:32 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <5C49AE82-C0B2-4F6F-A0C7-44DC64D30009@ag-projects.com>
References: <CALiegfnOCxyTo9ffQ272+ncdu5UdgrtDT-dn10BWGTZMEjZoCg@mail.gmail.com> <2E239D6FCD033C4BAF15F386A979BF510F0C0A@sonusinmail02.sonusnet.com> <05CAC192-E462-421F-B1E5-B78DC8F60306@ag-projects.com> <2E239D6FCD033C4BAF15F386A979BF510F0C93@sonusinmail02.sonusnet.com> <4E73C056.2090003@skype.net> <253421CC-AC2C-4896-8F63-68752F15C621@edvina.net> <40AA097E-47BD-44C7-B3E8-F7C056FCD43D@acmepacket.com> <4E776739.4010609@ericsson.com> <4E77949B.4010603@alvestrand.no> <4E78A4FB.1050504@ericsson.com> <4E79AC33.4000900@alvestrand.no> <0075AB47-3DFF-4000-9057-CA0628DF711A@csperkins.org> <05D1C2F6-96C3-44E3-9FC2-AD2C893C9FC6@acmepacket.com>
To: Hadriel Kaplan <HKaplan@acmepacket.com>
X-Mailer: Apple Mail (2.1084)
Cc: "<rtcweb@ietf.org>" <rtcweb@ietf.org>, Colin Perkins <csp@csperkins.org>
Subject: Re: [rtcweb] Data Transport, was: Re: RTCWeb default signaling protocol [was RE: About defining a signaling protocol for WebRTC (or not)]
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: Wed, 21 Sep 2011 13:46:06 -0000

Hi,

On Sep 21, 2011, at 1:45 PM, Hadriel Kaplan wrote:

> 
> Just to make sure I'm on the same wavelength, you're talking about:
> 1) Defining PseudoTCP over UDP (a la libnice and jingle) for stream-oriented reliable data delivery.
> 2) Defining DDCP over UDP for message-oriented unreliable data delivery.
> 3) Requiring the browser to implement and only expose those two options for the "data" stream type and not raw UDP, so that we can enforce congestion control of the data channel. (oh, and the option for it to be PseudoTCP/DTLS/UDP or DCCP/DTLS/UDP)
> 

I'm not familiar with DDCP, but MSRP requires a reliable transport AFAIK, so would DDCP be appropriate for that purpose, for example? I guess that Pseudo TCP would.


Regards,

--
Saúl Ibarra Corretgé
AG Projects