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

Iñaki Baz Castillo <ibc@aliax.net> Wed, 21 September 2011 10:26 UTC

Return-Path: <ibc@aliax.net>
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 CEDCF21F8C68 for <rtcweb@ietfa.amsl.com>; Wed, 21 Sep 2011 03:26:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.649
X-Spam-Level:
X-Spam-Status: No, score=-2.649 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
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 FVByYMmV+NLn for <rtcweb@ietfa.amsl.com>; Wed, 21 Sep 2011 03:26:26 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 36F6021F8C4A for <rtcweb@ietf.org>; Wed, 21 Sep 2011 03:26:26 -0700 (PDT)
Received: by vws5 with SMTP id 5so2178774vws.31 for <rtcweb@ietf.org>; Wed, 21 Sep 2011 03:28:54 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.9.129 with SMTP id l1mr114220vcl.87.1316600934147; Wed, 21 Sep 2011 03:28:54 -0700 (PDT)
Received: by 10.220.94.200 with HTTP; Wed, 21 Sep 2011 03:28:54 -0700 (PDT)
In-Reply-To: <CALiegfn8c3Eatc6CkfR=aJYAWkn764rbNo+fzbYrn1rEgKUe7Q@mail.gmail.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> <BACEBE38-1B93-4697-B548-9490339F7288@edvina.net> <4E777414.1040801@mozilla.com> <CALiegfn8c3Eatc6CkfR=aJYAWkn764rbNo+fzbYrn1rEgKUe7Q@mail.gmail.com>
Date: Wed, 21 Sep 2011 12:28:54 +0200
Message-ID: <CALiegfksY5XGxtOFZgHzZ4Fuxt7xLDQFBbzeL6S6s4Osjtgo8Q@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: "Timothy B. Terriberry" <tterriberry@mozilla.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: "rtcweb@ietf.org" <rtcweb@ietf.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 10:26:26 -0000

2011/9/21 Iñaki Baz Castillo <ibc@aliax.net>;:
> 2011/9/19 Timothy B. Terriberry <tterriberry@mozilla.com>;:
>> Perhaps I'm confused, but doesn't MSRP rely on reliable, in-order delivery?
>
> Right, MSRP is supossed to work over TCP or TLS. In fact, TLS usage is
> a "SHOULD" and TCP is just supposed to be used for debugging purposes.

Using a reliable transport means that, in case both peers are behind
NAT, a MSRP Relay server (RFC 4976) is required. So as in the case of
a "RTCweb default signaling protocol" I wonder: would we expect a
'mod_msrp' module for Apache? :) (I don't).

Regards.

-- 
Iñaki Baz Castillo
<ibc@aliax.net>;