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

Saúl Ibarra Corretgé <saul@ag-projects.com> Mon, 19 September 2011 15:04 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 B17D321F8C2F for <rtcweb@ietfa.amsl.com>; Mon, 19 Sep 2011 08:04:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.648
X-Spam-Level:
X-Spam-Status: No, score=-1.648 tagged_above=-999 required=5 tests=[AWL=0.040, 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 nJsZaj3GuhYw for <rtcweb@ietfa.amsl.com>; Mon, 19 Sep 2011 08:04:03 -0700 (PDT)
Received: from mail.sipthor.net (node06.dns-hosting.info [85.17.186.6]) by ietfa.amsl.com (Postfix) with ESMTP id 2AB4121F8C2B for <rtcweb@ietf.org>; Mon, 19 Sep 2011 08:04:03 -0700 (PDT)
Received: by mail.sipthor.net (Postfix, from userid 5001) id 8BCA9B01B5; Mon, 19 Sep 2011 17:06:25 +0200 (CEST)
Received: from [192.168.99.36] (ip3e830637.speed.planet.nl [62.131.6.55]) by mail.sipthor.net (Postfix) with ESMTPSA id E6821B019A; Mon, 19 Sep 2011 17:06:24 +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: <4E774F92.4040405@jesup.org>
Date: Mon, 19 Sep 2011 17:06:24 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <8ECCEE59-E855-4EA9-92B9-543D1585B1F0@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> <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>
To: Randell Jesup <randell-ietf@jesup.org>
X-Mailer: Apple Mail (2.1084)
Cc: rtcweb@ietf.org
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 15:04:03 -0000

Hi,

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


Regards,

--
Saúl Ibarra Corretgé
AG Projects