IETF Logo Mail Archive

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

Roman Shpount <roman@telurix.com> Thu, 22 March 2012 15:40 UTC

Return-Path: <roman@telurix.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 032F721F85A1 for <rtcweb@ietfa.amsl.com>; Thu, 22 Mar 2012 08:40:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.788
X-Spam-Level:
X-Spam-Status: No, score=-2.788 tagged_above=-999 required=5 tests=[AWL=0.188, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 uriK3an3omW4 for <rtcweb@ietfa.amsl.com>; Thu, 22 Mar 2012 08:39:57 -0700 (PDT)
Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170]) by ietfa.amsl.com (Postfix) with ESMTP id CE3FA21F85AF for <rtcweb@ietf.org>; Thu, 22 Mar 2012 08:39:56 -0700 (PDT)
Received: by wibhr17 with SMTP id hr17so836186wib.1 for <rtcweb@ietf.org>; Thu, 22 Mar 2012 08:39:46 -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:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=ShpxqHzdz/FfOs9O0pfDrmMl84EF8Gute8wRtSNTPVQ=; b=I9XQUco3QnAAWiui09+CPQLVdQ/5P4q5RRqlE0mTFC6Co1GvTng4cKQvZJGD6+r9gx 4gqTJQscihFrgFEsm4DR2M3Ouf5ZYPzDKmQsZcRSylD/2Z5F/BA3/uX+lEj4utzeXKKk oUEM4Vxh6aFSsv2Fhx2bwYqE8/Cd3Idqcdpf5uErB2B9YGSxTdKcJMjIla2Ad1/iBiwa nW/70UgozU/WWScGBV0kO5IILI63omllJlbsQKn0PbxjdHdNyFrFvCU3N7Yt8Uq9gwK6 D0dsSR6/qfyN7FNuVhL29Vpzdl7oZhnhY+JVe5h3/cSM9qYpJ+1TbhD+H7+fdBs5yfHb ZEXw==
Received: by 10.50.153.193 with SMTP id vi1mr2231895igb.2.1332430785435; Thu, 22 Mar 2012 08:39:45 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by mx.google.com with ESMTPS id ut8sm2265939igc.11.2012.03.22.08.39.43 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 22 Mar 2012 08:39:44 -0700 (PDT)
Received: by pbbrq13 with SMTP id rq13so1815892pbb.31 for <rtcweb@ietf.org>; Thu, 22 Mar 2012 08:39:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.135.40 with SMTP id pp8mr21441941pbb.13.1332430782474; Thu, 22 Mar 2012 08:39:42 -0700 (PDT)
Received: by 10.68.6.67 with HTTP; Thu, 22 Mar 2012 08:39:42 -0700 (PDT)
In-Reply-To: <CABkgnnW3AyREj9T2zDzJf64Bhjdfc1K8-ebZe-V0a-tbiTYEpw@mail.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> <CABkgnnW3AyREj9T2zDzJf64Bhjdfc1K8-ebZe-V0a-tbiTYEpw@mail.gmail.com>
Date: Thu, 22 Mar 2012 11:39:42 -0400
Message-ID: <CAD5OKxswXun5nVhKcN2oXkTdr-wKuOB7PhbXgdGSE4RexhTd3A@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary="047d7b10d17b7a286804bbd6b7c1"
X-Gm-Message-State: ALoCoQkNPJfIwd3oCQBL4O/cdrtrc3zFgjnE/4KC/++8SazizqyUoPomerXbV1ZeVDwi2M2EwMZy
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 15:40:02 -0000

On Thu, Mar 22, 2012 at 11:33 AM, Martin Thomson
<martin.thomson@gmail.com>wrote:

> On 22 March 2012 07:18, Roman Shpount <roman@telurix.com> wrote:
> > Yes, I was worried about supporting the interceptor.
>
> Please see: http://tools.ietf.org/html/rfc2804
>

And I did see it. I suggest you do the same. I am not talking about
providing a back door into the system to allow wiretapping. I am talking
about a user voluntarily enabling network based recording of its own WebRTC
traffic. So, if I am an enterprise, and I own the computer, I should be
able to enforce a recording and communications policy on it. Enterprise can
do it now with HTTP/HTTPS, why not WebRTC?
_____________
Roman Shpount

v2.23.0 | Report a Bug | By Email