IETF Logo Mail Archive

Re: [rtcweb] SDP Security Descriptions (RFC 4568) and RTCWeb

Matthew Kaufman <matthew@matthew.at> Fri, 26 April 2013 04:32 UTC

Return-Path: <matthew@matthew.at>
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 C3DAF21E803D for <rtcweb@ietfa.amsl.com>; Thu, 25 Apr 2013 21:32:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.43
X-Spam-Level:
X-Spam-Status: No, score=-1.43 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745]
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 LpjnClErMBlN for <rtcweb@ietfa.amsl.com>; Thu, 25 Apr 2013 21:32:54 -0700 (PDT)
Received: from where.matthew.at (where.matthew.at [198.202.199.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A67621F9761 for <rtcweb@ietf.org>; Thu, 25 Apr 2013 21:32:54 -0700 (PDT)
Received: from [10.10.155.2] (unknown [10.10.155.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by where.matthew.at (Postfix) with ESMTP id ED1A0148028 for <rtcweb@ietf.org>; Thu, 25 Apr 2013 21:32:51 -0700 (PDT)
Message-ID: <517A0376.3050904@matthew.at>
Date: Thu, 25 Apr 2013 21:32:54 -0700
From: Matthew Kaufman <matthew@matthew.at>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <3FA2E46D-C98E-4FC0-9F1D-AD595A861CE1@iii.ca> <CABkgnnVky++ZF1uaM8p4xtzvDQH7HMCaL8N2ZV3dZDYnv-NvzQ@mail.gmail.com> <CABcZeBOkCC9wn7H7a4U0SYNAfYtNB2w6SvwZi4aL5f9wcwLp+g@mail.gmail.com> <CABkgnnUO657zEBz2V9zyYpFM+GCXr59j-a-PZa8Wj92Yipv21A@mail.gmail.com> <0C0C05DA-C283-40CF-A7CA-BF5F27A21720@cisco.com>
In-Reply-To: <0C0C05DA-C283-40CF-A7CA-BF5F27A21720@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [rtcweb] SDP Security Descriptions (RFC 4568) and RTCWeb
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: Fri, 26 Apr 2013 04:32:55 -0000

On 4/25/2013 5:36 PM, Dan Wing wrote:
>
> Or storing fingerprints into an addressbook (similar to HTTPS key pinning), cooperatively comparing fingerprints (similar to http://perspectives-project.org), and the rest of the state of the art and emerging state of the art for certificate validation.

Yes. And so it'll learn that everyone calls everyone else via Google's 
server. How does that help with people's media staying secure from 
interception exactly?

Matthew Kaufman

v2.23.0 | Report a Bug | By Email