IETF Logo Mail Archive

Re: [rtcweb] Use Case draft - legacy interop

Iñaki Baz Castillo <ibc@aliax.net> Fri, 04 May 2012 20:05 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 D41DA21E8012 for <rtcweb@ietfa.amsl.com>; Fri, 4 May 2012 13:05:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.613
X-Spam-Level:
X-Spam-Status: No, score=-2.613 tagged_above=-999 required=5 tests=[AWL=0.064, 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 8F1JkqF8yTcu for <rtcweb@ietfa.amsl.com>; Fri, 4 May 2012 13:05:23 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id C1F9621F855A for <rtcweb@ietf.org>; Fri, 4 May 2012 13:05:22 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so2751117vbb.31 for <rtcweb@ietf.org>; Fri, 04 May 2012 13:05:22 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding:x-gm-message-state; bh=er7gqC6aJOEkVaD6wTZxpoGkJ9yjpbxp06ceffUB/tY=; b=OKezuEmlx/a4zMdUO/Ir/82stedz0IrDHxvidHk0J9dZOVMsmdOKKcp/5yEuf6Lci2 uIVvFLTAo9iAFoG9la/aGsN4GfotNIX32nGR7t77I/ttP0ApwRUhk8THXvZPMGfGR1N/ 3SrpX9oML/jzvoQNPYTbeRaieEznmOEDAqYPvQblbAFHh+QGh3LQ0wGsXxqZz/VhlWnL v+n3txgUGT2lhlfneLHsF/fnnFMQoVQWptnCxrt6c8XH9l8GHwBt5vpiHVVZ0mUhcY+4 8zAVqIC60hCONyK48X2ZYBCO0uajag7O5PmkvALs+SkJZc2JaDHPpHe7WZh4Vrz7uauQ k4Yg==
Received: by 10.52.94.34 with SMTP id cz2mr634280vdb.100.1336148247295; Fri, 04 May 2012 09:17:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.107.199 with HTTP; Fri, 4 May 2012 09:17:07 -0700 (PDT)
In-Reply-To: <4FA37A1E.4080806@alvestrand.no>
References: <CA+9kkMCYArLPRP3c00UdOja64WRT6ghN0PSy7XvM_wbxBBB+vA@mail.gmail.com> <E17CAD772E76C742B645BD4DC602CD810616F066@NAHALD.us.int.genesyslab.com> <BLU169-W7C59E1EDB4CB06B648577932B0@phx.gbl> <387F9047F55E8C42850AD6B3A7A03C6C0E23AFFF@inba-mail01.sonusnet.com> <2E496AC9-63A0-464A-A628-7407ED8DD9C4@phonefromhere.com> <387F9047F55E8C42850AD6B3A7A03C6C0E23B16B@inba-mail01.sonusnet.com> <E2714FBC-D06B-4A12-9E07-C49EBF55084C@phonefromhere.com> <4F9EC0B2.10903@alcatel-lucent.com> <101C6067BEC68246B0C3F6843BCCC1E31299282765@MCHP058A.global-ad.net> <CAJNg7VKENERKAFA-n5KeoeBNmGgHrnzDOU0BzC9+fSdsuGwdEw@mail.gmail.com> <E17CAD772E76C742B645BD4DC602CD810616F24F@NAHALD.us.int.genesyslab.com> <4FA0F43E.4020308@ericsson.com> <E17CAD772E76C742B645BD4DC602CD810616F336@NAHALD.us.int.genesyslab.com> <4FA1575C.4050508@ericsson.com> <E17CAD772E76C742B645BD4DC602CD810616F4BF@NAHALD.us.int.genesyslab.com> <4FA37A1E.4080806@alvestrand.no>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Fri, 04 May 2012 18:17:07 +0200
Message-ID: <CALiegf=H5QH_YY-cJ4z29wChWZ-VoQpHvsZCeaJPjTgVp+km3Q@mail.gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQk/qwWdRbWXgmK9CCYoNjZoxIZC32GCbqiXcwvP4rqMeg7Kkk7CNYhOlMJYxDCaHzqpC+Al
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Use Case draft - legacy interop
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: Fri, 04 May 2012 20:05:24 -0000

2012/5/4 Harald Alvestrand <harald@alvestrand.no>:
> My memory of our last rounds of discussion was that we decided not to have a
> non-gateway legacy interop case

Hi Harald, is that really *decided*? I will ask the same question in a
different way:

If I have a SIP phone implementing ICE and DTLS-SRTP (which is
standarized for SIP regardless it has null impementation), will my SIP
phone be able to *directly* talk in the media plane with a WebRTC
browser? or not?

And also, what does it mean a "non-gateway"? Gateways are not
specified, they are custom boxes implementing some kind of protocol
translation. The only way in which it can be said that "there is not
non-gateway legacy interop" is by making WebRTC *explicitly*
non-compliant with any other existing device (for example by requiring
some annoying a=ensureWebRTC line in the SDP, in this way you can be
sure that WebRTC entities will interop with nobody but with specific
"gateways" that know the trick).


Thanks a lot.


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

v2.23.0 | Report a Bug | By Email