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

"Olle E. Johansson" <oej@edvina.net> Wed, 21 September 2011 12:10 UTC

Return-Path: <oej@edvina.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 C5F7F21F8C35 for <rtcweb@ietfa.amsl.com>; Wed, 21 Sep 2011 05:10:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.093
X-Spam-Level:
X-Spam-Status: No, score=-2.093 tagged_above=-999 required=5 tests=[AWL=-0.144, BAYES_00=-2.599, HELO_EQ_SE=0.35, 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 ljClX+epYM+A for <rtcweb@ietfa.amsl.com>; Wed, 21 Sep 2011 05:10:44 -0700 (PDT)
Received: from smtp7.webway.se (smtp7.webway.se [212.3.14.205]) by ietfa.amsl.com (Postfix) with ESMTP id 3349B21F8B73 for <rtcweb@ietf.org>; Wed, 21 Sep 2011 05:10:44 -0700 (PDT)
Received: from [192.168.40.44] (ns.webway.se [87.96.134.125]) by smtp7.webway.se (Postfix) with ESMTPA id 7D0F2754BCE5; Wed, 21 Sep 2011 12:13:10 +0000 (UTC)
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset="iso-8859-1"
From: "Olle E. Johansson" <oej@edvina.net>
In-Reply-To: <CALiegfksY5XGxtOFZgHzZ4Fuxt7xLDQFBbzeL6S6s4Osjtgo8Q@mail.gmail.com>
Date: Wed, 21 Sep 2011 14:13:10 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <86AAA5D9-C19E-406F-A1BE-9CD4C5200FDC@edvina.net>
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> <CALiegfksY5XGxtOFZgHzZ4Fuxt7xLDQFBbzeL6S6s4Osjtgo8Q@mail.gmail.com>
To: Iñaki Baz Castillo <ibc@aliax.net>
X-Mailer: Apple Mail (2.1244.3)
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 12:10:44 -0000

21 sep 2011 kl. 12:28 skrev Iñaki Baz Castillo:

> 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).

Nothing says the relay has to be in the web server. 

As a side note: the first SIP proxy I tested was in fact an Apache module.

/O