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

Roman Shpount <roman@telurix.com> Thu, 22 March 2012 16:13 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 2443521F85ED for <rtcweb@ietfa.amsl.com>; Thu, 22 Mar 2012 09:13:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.791
X-Spam-Level:
X-Spam-Status: No, score=-2.791 tagged_above=-999 required=5 tests=[AWL=0.185, 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 65Ydn8OeVrA8 for <rtcweb@ietfa.amsl.com>; Thu, 22 Mar 2012 09:13:39 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 79DEF21F856F for <rtcweb@ietf.org>; Thu, 22 Mar 2012 09:13:39 -0700 (PDT)
Received: by iazz13 with SMTP id z13so3880003iaz.31 for <rtcweb@ietf.org>; Thu, 22 Mar 2012 09:13:39 -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=zsx6Grx05ULQ8KXGAn7uwBQD4bWGOXjaWrtwemmxNd0=; b=M3FJEw5jQfRPAmRwxh4T3t1H1mGd0vLnOmx4+WRCf+wm/i9UYNuWy59Lps2bjO+d3u SBNmvoWbLKGhicsljRbnE04NrbrGk/+QB/S5MsnUITneWAORJNqfo4pacaI5Nwp0wv/6 3LBKD8pZeT04836h5GJGAuGvKgiPkJSJAZmS2jIx3yUssGbCnuhJDaeB4VhJoDnJDx5i pPrzJE38KsRf49iPWNfWIopaLaNMzQyhVwUhcjNQrFARyUKF8yKzfJHnBWLh8EncUs0/ DFqrxOQ4ZHHG4/pJPm0cdTkW5lPzVE9TCzI0Fo8BWaUH8e05n/bpxryzu8JxVOCH44Mu dDdw==
Received: by 10.43.52.138 with SMTP id vm10mr5238843icb.31.1332432818507; Thu, 22 Mar 2012 09:13:38 -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 t8sm1668162igw.0.2012.03.22.09.13.34 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 22 Mar 2012 09:13:36 -0700 (PDT)
Received: by pbbrq13 with SMTP id rq13so1837225pbb.31 for <rtcweb@ietf.org>; Thu, 22 Mar 2012 09:13:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.135.40 with SMTP id pp8mr21649510pbb.13.1332432813733; Thu, 22 Mar 2012 09:13:33 -0700 (PDT)
Received: by 10.68.6.67 with HTTP; Thu, 22 Mar 2012 09:13:33 -0700 (PDT)
In-Reply-To: <CABkgnnUZgtgEWZvYiyxDVNsDRDNsdr30Pd38cZeR18UB1Z04mw@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> <CAD5OKxswXun5nVhKcN2oXkTdr-wKuOB7PhbXgdGSE4RexhTd3A@mail.gmail.com> <CABkgnnUZgtgEWZvYiyxDVNsDRDNsdr30Pd38cZeR18UB1Z04mw@mail.gmail.com>
Date: Thu, 22 Mar 2012 12:13:33 -0400
Message-ID: <CAD5OKxuLY2hZVqmna_GmpcBdFbZiP6ybKTJ19DN4f25mabLTrg@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary="047d7b10d17b8cb87504bbd7305c"
X-Gm-Message-State: ALoCoQnHaWuGblfPD+sQKjiULiMsNnnUiCwBAXqRI+pLOmuMJQXCtZBXzDi/sDhpxMcc3QNpH6FG
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 16:13:40 -0000

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

> On 22 March 2012 08:39, Roman Shpount <roman@telurix.com> wrote:
> > 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?
>
> If you can install trust anchors, what more do you need?  A set of
> instructions?
>

Ok, repeating my previous email:

If, as an owner of a computer, you want to enable media monitoring with an
existing standard you need to know exactly how each application is
implemented. This is a solution for hacker but not the normal enterprise.
In order to have monitoring support in the enterprise environment you need
an ability to force the browser to proxy all the media through a monitoring
application without any application modification, via browser settings
alone. For the monitoring proxy to work it would need some sort of network
protocol to communicate with the browser (similar how HTTP proxy needs a
network protocol to work with the browser). I would expect what's needed is
some sort of network based protocol to send the SDP to a proxy, get
modified SDP back and pass it to JavaScript (or take the SDP from
JavaScript, through the proxy and to the media stack).
_____________
Roman Shpount