IETF Logo Mail Archive

Re: [rtcweb] Resolving RTP/SDES question in Paris

"Dan Wing" <dwing@cisco.com> Thu, 22 March 2012 22:44 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 E822221F845B for <rtcweb@ietfa.amsl.com>; Thu, 22 Mar 2012 15:44:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.382
X-Spam-Level:
X-Spam-Status: No, score=-109.382 tagged_above=-999 required=5 tests=[AWL=1.217, BAYES_00=-2.599, 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 kHpM8BdZlNMs for <rtcweb@ietfa.amsl.com>; Thu, 22 Mar 2012 15:44:34 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id D6B9621F845A for <rtcweb@ietf.org>; Thu, 22 Mar 2012 15:44:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1820; q=dns/txt; s=iport; t=1332456270; x=1333665870; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=HCkSZ9AbXS3vqdmsY9PZS5L9rMXqA1K42uFQYIcfRsI=; b=SycHTGPKfOD5U8jeAKW1DX2H9dQw1b+pE4VlG3ZxkE5VxFo20PeNkCri d9LBboSY1JsCo3qXobWcb6yg+kkVBmS2c1bZZcsu0+tQU4l3lHs937av+ ZqwMYxrxfSZNXJCHilR0QBCyOzXbE84W2rcqXs/zoJgq/12kRgYoz8Rgp 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhoFANqqa0+rRDoJ/2dsb2JhbABEp2SPWYEHggkBAQEECAoBFxA/DAEDAgkPAgQBASgHGSMKCQgBAQQBEgsQB4dnmRyNUZE6kGQEiFaFE5Y2gWiDBw
X-IronPort-AV: E=Sophos;i="4.73,633,1325462400"; d="scan'208";a="37304583"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-2.cisco.com with ESMTP; 22 Mar 2012 22:44:29 +0000
Received: from dwingWS ([10.32.240.196]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id q2MMiTBP026833; Thu, 22 Mar 2012 22:44:29 GMT
From: Dan Wing <dwing@cisco.com>
To: 'Roman Shpount' <roman@telurix.com>, 'Harald Alvestrand' <harald@alvestrand.no>, 'Ted Hardie' <ted.ietf@gmail.com>
References: <4F4759DC.7060303@ericsson.com> <387F9047F55E8C42850AD6B3A7A03C6C0E1FEB69@inba-mail01.sonusnet.com> <CALiegfnkYVEpmPV-zSL_4wOY-HiFZN-qJCQCiioaS=5NaqhLZw@mail.gmail.com> <CAD5OKxvtOAxMBx6xDnyfTnEq76oDEm6uj1xL6wGjjrtKUAHy3g@mail.gmail.com> <CABcZeBNZiotPmCfT53uEo+O0xw4xv6tXW1M_G-3A5BHuncsduA@mail.gmail.com> <CAD5OKxvYOY5JZ2mYNGiH1poUBQkyOOycePFijH5H+SxtcdqujQ@mail.gmail.com> <CABkgnnVe-b6Sv=R67bMJk_NQqQwdrRUn6rBm7Gu_CMcfPQwtEg@mail.gmail.com> <4F64FE98.3070605@alcatel-lucent.com> <4F685ED9.2050109@alvestrand.no> <CAD5OKxsVp7px9bHAgxgdqPMxRgppcVUDKt8JHBhyq9qqW3pAMg@mail.gmail.com> <4F68A4CC.9090306@alvestrand.no> <CAD5OKxuiApLKRASc2YuBfkM_8h8wGDPPQ3TdOYGum2yauidA5A@mail.gmail.com> <4F6AECC6.8020004@alvestrand.no> <CAD5OKxsSUeMFYXZMZVqQFWdeEB=30HJuJ=mP9GaYkksBmp1mOA@mail.gmail.com>
In-Reply-To: <CAD5OKxsSUeMFYXZMZVqQFWdeEB=30HJuJ=mP9GaYkksBmp1mOA@mail.gmail.com>
Date: Thu, 22 Mar 2012 15:44:29 -0700
Message-ID: <03fa01cd087d$57899120$069cb360$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac0INr3Z1+RYf6xDTCirryldOl72eAARbPMA
Content-Language: en-us
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Resolving RTP/SDES question in Paris
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: Thu, 22 Mar 2012 22:44:35 -0000

> -----Original Message-----
> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On
> Behalf Of Roman Shpount
> Sent: Thursday, March 22, 2012 7:19 AM
> To: Harald Alvestrand
> Cc: rtcweb@ietf.org
> Subject: Re: [rtcweb] Resolving RTP/SDES question in Paris
...
> Yes, I was worried about supporting the interceptor. This is all
> related to my question of support of WebRTC applications in military,
> prisons, or financial organizations. I think WebRTC would be completely
> disabled in such locations unless web browser can be configured to
> confirm to some sort of communications and monitoring policy. I do not
> think enabling only certain applications is a sustainable solution,
> since application can only be enabled based on its URL, but this in no
> way implies that the actual protocol used for signaling exchange by
> this application will stay the same. In the best case this will result
> in tens of specialized monitoring rules that will need to be
> maintained. In the worst case, WebRTC would be simply disabled. At this
> point the only workable solution that I see is some sort of media proxy
> protocol.

The SIPREC working group, formed in March 2010, has solutions for
this problem.  The problem is not created by RTCWEB.  Disabling 
encryption is not necessary -- nor desirable.  "Jails" get brought up
in this context often, so using that same example, consider a prisoner 
at a jail communicating with their lawyer.  The prisoner needs secure 
communications with their lawyer without the risk of the 
communications being leaked to the press by anyone along the media 
path.  For details see http://tools.ietf.org/wg/siprec/

We will have a brietf presentation on SIPREC during my session
at RTCWEB, explaining how it can work with RTCWEB.

-d

v2.23.0 | Report a Bug | By Email