IETF Logo Mail Archive

Re: [rtcweb] Use Case draft - legacy interop

"Dan Wing" <dwing@cisco.com> Sat, 05 May 2012 17: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 923D121F85E4 for <rtcweb@ietfa.amsl.com>; Sat, 5 May 2012 10:24:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.399
X-Spam-Level:
X-Spam-Status: No, score=-110.399 tagged_above=-999 required=5 tests=[AWL=-0.100, 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 yw+TBkesYhBH for <rtcweb@ietfa.amsl.com>; Sat, 5 May 2012 10: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 9E56B21F85E3 for <rtcweb@ietf.org>; Sat, 5 May 2012 10:24:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=2122; q=dns/txt; s=iport; t=1336238685; x=1337448285; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=zR3xPsPJ/qLAw1aCTm6DSYxxuENBX9y/is7sjZHe3eY=; b=izW7Huqi8df4fQ3Gnj7B/YhvfvAqJzg8RF8e8nA54+3VIFq2YlpzvJTi IZbAIxBKaNBaxzn6sPVY7Q/HYmfputPssvUhoho6n+ItykEdCybj5SYSf 4aDh+pvX1MI7cxinRfpF8skgztI1A4zBeVz4/0uJhXBXBWG7OHo2cxDZ2 o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFAGdhpU+Q/khM/2dsb2JhbABFhXKcapAYgQeCDAEBAQMBCAoBEAdPBQcBAwIJDwIEAQEDAhESAwICGSMKCQgBAQQTCxeHZwWaPo0WkiOBL4lQgm6CGoEYBIhkhRaWXYFpgwk
X-IronPort-AV: E=Sophos;i="4.75,536,1330905600"; d="scan'208";a="72518940"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 05 May 2012 17:24:44 +0000
Received: from dwingWS ([10.32.240.195]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id q45HOhwn003837; Sat, 5 May 2012 17:24:43 GMT
From: Dan Wing <dwing@cisco.com>
To: 'Iñaki Baz Castillo' <ibc@aliax.net>
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> <0db701cd 2adb$98082f10$c8188d30$@com> <CALiegf=C7a6zeUDHn-Wuku9eFWmADG5N+D8oXSQbwJKSYYjcQg@mail.gmail.com>
In-Reply-To: <CALiegf=C7a6zeUDHn-Wuku9eFWmADG5N+D8oXSQbwJKSYYjcQg@mail.gmail.com>
Date: Sat, 05 May 2012 10:24:48 -0700
Message-ID: <0dc901cd2ae3$f9ffb500$edff1f00$@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: Ac0q3KYDnVHuLjJfSiuEI8vd6hqE0wABsq8g
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 17:24:46 -0000

> -----Original Message-----
> From: Iñaki Baz Castillo [mailto:ibc@aliax.net]
> Sent: Saturday, May 05, 2012 9:32 AM
> To: Dan Wing
> Cc: Harald Alvestrand; rtcweb@ietf.org
> Subject: Re: [rtcweb] Use Case draft - legacy interop
> 
> 2012/5/5 Dan Wing <dwing@cisco.com>:
> >> 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.
> 
> Ok, so then, taking into account that SIP defines the usage of
> DTLS-SRTP in RFC 5763 (regardless no one device implements it), why
> does this WG assumes that "interop with non WebRTC endpoints will be
> made via *gateways*"?

Perhaps a more accurate statement would be:

  directly, if the remote endpoint supports ICE and supports
  DTLS-SRTP; otherwise, via a gateway.

> Let me please repeat my question: if my SIP phone implements RFC 5763,
> can my SIP phone directly interop at media plane with a WebRTC
> browser? (I know you already replied this, but I want to be very very
> sure) :)

Sure seems it should work.  Only nuance that I am aware of at the moment
is WEBRTC seems to want to require Consent Freshness (periodic ICE
connectivity checks) for the duration of the call.  This is okay, and
would work with an existing SIP phone -- so long as the SIP phone
continues to respond to ICE messages.  It should.  But I doubt that
is exercised in SIPIT testing.  The other nuance is that, because
doing the SHA1 for MESSAGE-INTEGRITY isn't needed for consent freshness,
there is desire to allow those periodic ICE connectivity checks to
omit the MESSAGE-INTEGRITY, which is a change to ICE.  See 
draft-muthu-behave-consent-freshness.  Of course, that doesn't require
a gateway, but would require softening the implementation on the
phone.  draft-muthu-behave-consent-freshness might also add a new
SDP attribute, I dunno yet.

-d

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

v2.23.0 | Report a Bug | By Email