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

Igor Faynberg <igor.faynberg@alcatel-lucent.com> Sun, 18 March 2012 00:38 UTC

Return-Path: <igor.faynberg@alcatel-lucent.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 E56F321F864A for <rtcweb@ietfa.amsl.com>; Sat, 17 Mar 2012 17:38:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.322
X-Spam-Level:
X-Spam-Status: No, score=-9.322 tagged_above=-999 required=5 tests=[AWL=1.277, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 p9JWV+g5su+y for <rtcweb@ietfa.amsl.com>; Sat, 17 Mar 2012 17:38:26 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 5C8AE21F8624 for <rtcweb@ietf.org>; Sat, 17 Mar 2012 17:38:26 -0700 (PDT)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id q2I0cOjR017855 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 17 Mar 2012 19:38:24 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q2I0cO1m008172 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 17 Mar 2012 19:38:24 -0500
Received: from [135.244.32.147] (faynberg.lra.lucent.com [135.244.32.147]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q2I0cN9q016774; Sat, 17 Mar 2012 19:38:23 -0500 (CDT)
Message-ID: <4F652E7E.6040009@alcatel-lucent.com>
Date: Sat, 17 Mar 2012 20:38:22 -0400
From: Igor Faynberg <igor.faynberg@alcatel-lucent.com>
Organization: Alcatel-Lucent
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: Martin Thomson <martin.thomson@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> <CABkgnnWfgbWYzRRBnrZZCLQXL68Hq7d82Xr0NbayTc74nDF1nQ@mail.gmail.com>
In-Reply-To: <CABkgnnWfgbWYzRRBnrZZCLQXL68Hq7d82Xr0NbayTc74nDF1nQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
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
Reply-To: igor.faynberg@alcatel-lucent.com
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: Sun, 18 Mar 2012 00:38:27 -0000

Ah, so this is the enterprise scenario.  I get it. Thanks!

This case though would not worry me much because when you own my 
computer you make me confirm that I understand that I should not expect 
any privacy whatsoever.

Igor

On 3/17/2012 5:31 PM, Martin Thomson wrote:
> On 17 March 2012 14:14, Igor Faynberg<igor.faynberg@alcatel-lucent.com>  wrote:
>> On 3/17/2012 4:45 PM, Martin Thomson wrote:
>>> ... Then I explicitly place a trust anchor for that
>>> certificate in your browser.
>> How?  I thought the browser would never allow that to happen. (I assumed it
>> would come provisioned with anchors,  or would allow anchor provision
>> through some different channel.)
> I own your computer.  Or I make it a condition of you adding your
> computer to my network.