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

Randell Jesup <randell-ietf@jesup.org> Mon, 19 September 2011 18:52 UTC

Return-Path: <randell-ietf@jesup.org>
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 DB5CC21F8CD2 for <rtcweb@ietfa.amsl.com>; Mon, 19 Sep 2011 11:52:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.545
X-Spam-Level:
X-Spam-Status: No, score=-3.545 tagged_above=-999 required=5 tests=[AWL=1.054, BAYES_00=-2.599, GB_I_INVITATION=-2]
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 sBwmUW7+XIrj for <rtcweb@ietfa.amsl.com>; Mon, 19 Sep 2011 11:52:09 -0700 (PDT)
Received: from r2-chicago.webserversystems.com (r2-chicago.webserversystems.com [173.236.101.58]) by ietfa.amsl.com (Postfix) with ESMTP id 6170421F8CDE for <rtcweb@ietf.org>; Mon, 19 Sep 2011 11:52:09 -0700 (PDT)
Received: from pool-173-49-141-165.phlapa.fios.verizon.net ([173.49.141.165] helo=[192.168.1.12]) by r2-chicago.webserversystems.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <randell-ietf@jesup.org>) id 1R5izB-00049D-20 for rtcweb@ietf.org; Mon, 19 Sep 2011 13:54:33 -0500
Message-ID: <4E778F1F.9090105@jesup.org>
Date: Mon, 19 Sep 2011 14:51:11 -0400
From: Randell Jesup <randell-ietf@jesup.org>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0.1) Gecko/20110830 Thunderbird/6.0.1
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <CALiegfnOCxyTo9ffQ272+ncdu5UdgrtDT-dn10BWGTZMEjZoCg@mail.gmail.com> <2E239D6FCD033C4BAF15F386A979BF510F0C0A@sonusinmail02.sonusnet.com> <05CAC192-E462-421F-B1E5-B78DC8F60306@ag-projects.com> <2E239D6FCD033C4BAF15F386A979BF510F0C93@sonusinmail02.sonusnet.com> <16880306-5B3A-4EFD-ADE4-1201138D9182@acmepacket.com> <8584590C8D7DD141AA96D01920FC6C698C896B71@gbplmail03.genband.com> <CA+9kkMAwnnKKO5+q6ey4Z0QNxax1QF21vVtw8FNsHy_rmfenjQ@mail.gmail.com> <4E76E078.5020708@jesup.org> <8548CBBD-4E12-48F3-BC59-341FF45EF22F@acmepacket.com> <4E77495E.4000409@jesup.org> <CALiegfkTdCAeEdZbXP1Y9L6i4Anjrgf1CG6ZNj35WGoHL3p_Ew@mail.gmail.com> <4E774F92.4040405@jesup.org> <8ECCEE59-E855-4EA9-92B9-543D1585B1F0@ag-projects.com>
In-Reply-To: <8ECCEE59-E855-4EA9-92B9-543D1585B1F0@ag-projects.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - r2-chicago.webserversystems.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jesup.org
X-Source:
X-Source-Args:
X-Source-Dir:
Subject: Re: [rtcweb] 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: Mon, 19 Sep 2011 18:52:10 -0000

On 9/19/2011 11:06 AM, Saúl Ibarra Corretgé wrote:
>>> That would require a signaling central point (think about
>>> NAT), does it mean that web sites should provide a like-"SIP proxy"
>>> within their infraestructure? (think about web sites hosted in shared
>>> datacenter by an Apache or other web server not behind the control of
>>> the web developer).
>> It would require a SIP proxy only if the app developer decides to use the SIP
>> module.
>>
> I might be missing something, but how would Alice communicate with Bob if both are behind NAT and there is no server involved? Asking some IP and port out of band? I'm not aware of any Bonjour-style protocol for the Internet, is there something similar which could be leveraged?
>
> I see no clean way for 2 browsers to communicate without a server involved, and since it's not feasible to mandate that every browser manufacturer deploys one, I'd rather not have any simplified or default protocol.
You misunderstood me; I meant "if you use an optional SIP module, you'll
need to have a SIP proxy on your server".  WebRTC in general presumes some sort
of server architecture to solve the discovery/invitation problem.  There *are*
some possible uses of WebRTC that might not use a central server(s).   The simplest
would be the "phone-tag" server, where you and the person you want to talk to
exchange IP addresses and external port numbers over the phone, and type them into
the web app, which then opens a default-configured PeerConnection and re-negotiates
to the actual configuration.


-- 
Randell Jesup
randell-ietf@jesup.org