IETF Logo Mail Archive

Re: [rtcweb] Use Case draft - legacy interop

"Dan Wing" <dwing@cisco.com> Sat, 05 May 2012 16:24 UTC

Return-Path: <dwing@cisco.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 7173521F8499 for <rtcweb@ietfa.amsl.com>; Sat, 5 May 2012 09:24:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.449
X-Spam-Level:
X-Spam-Status: No, score=-110.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 34sQda545sch for <rtcweb@ietfa.amsl.com>; Sat, 5 May 2012 09:24:45 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 693C821F8497 for <rtcweb@ietf.org>; Sat, 5 May 2012 09:24:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1589; q=dns/txt; s=iport; t=1336235085; x=1337444685; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=T6BgUoU1+3AwVa8CQlv4HTLK1gXVO5thHpWe4v4y8lg=; b=Hk56KxZz/XqoqQRkM0yHAF3mI5pqpjMG7J6dxDRFEYFmvMkit0L9rnhv DBlwqfVnuJIB142nAf4pEh1pKWc7Tqq8JmJJNrCmU2EA34I2BvBl7kYcD Ci1uQ7fjDGeNL7bI9RVUaHQp/ut9amWQaA02OpjRQ+e4J0Xgzg9wRo+2f k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFAFdTpU+Q/khN/2dsb2JhbABFhXKcapAYgQeCDAEBAQMBAQEBBQoBEAdECwUHAQMCCQ8CBAEBAwIjAwICGQ4VCgkIAQEEARILF4dnBQuaN40WkiEEgS+JUIUIgRgEiGSFFpZdgWmDCQ
X-IronPort-AV: E=Sophos;i="4.75,536,1330905600"; d="scan'208";a="72517946"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-2.cisco.com with ESMTP; 05 May 2012 16:24:44 +0000
Received: from dwingWS ([10.32.240.195]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id q45GOglA026263; Sat, 5 May 2012 16:24:43 GMT
From: Dan Wing <dwing@cisco.com>
To: 'Iñaki Baz Castillo' <ibc@aliax.net>, 'Harald Alvestrand' <harald@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> <CALiegf=H5QH_YY-cJ4z29wChWZ-VoQpHvsZCeaJPjTgVp+km3Q@mai l.gmail.com>
In-Reply-To: <CALiegf=H5QH_YY-cJ4z29wChWZ-VoQpHvsZCeaJPjTgVp+km3Q@mail.gmail.com>
Date: Sat, 05 May 2012 09:24:48 -0700
Message-ID: <0db701cd2adb$98082f10$c8188d30$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac0qMUCmLKAjZgQsThOB5NSkyoTFawAqjgnA
Content-Language: en-us
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: Sat, 05 May 2012 16:24:46 -0000

> -----Original Message-----
> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On
> Behalf Of Iñaki Baz Castillo
> Sent: Friday, May 04, 2012 9:17 AM
> To: Harald Alvestrand
> Cc: rtcweb@ietf.org
> Subject: Re: [rtcweb] Use Case draft - legacy interop
> 
> 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?

That would work.

-d


> 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>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email