Re: [rtcweb] On video codec for rtcweb
Martin Thomson <martin.thomson@gmail.com> Fri, 23 March 2012 15:22 UTC
Return-Path: <martin.thomson@gmail.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 04CBF21F84EA for <rtcweb@ietfa.amsl.com>; Fri, 23 Mar 2012 08:22:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.596
X-Spam-Level:
X-Spam-Status: No, score=-4.596 tagged_above=-999 required=5 tests=[AWL=-0.997, BAYES_00=-2.599, 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 mSkOx02Y5aPt for <rtcweb@ietfa.amsl.com>; Fri, 23 Mar 2012 08:21:59 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 49AF621F84D1 for <rtcweb@ietf.org>; Fri, 23 Mar 2012 08:21:59 -0700 (PDT)
Received: by bkuw5 with SMTP id w5so3038030bku.31 for <rtcweb@ietf.org>; Fri, 23 Mar 2012 08:21:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=fR7qWGWMiyvh2FfQlucdJ0+rqLIqitNeVhZWhSptAB8=; b=w4fZ+K8nRB5w//MiS6o+Jn7BnFe7nlyTZ2rAY+MyovFLtVaP5/6gYQijCYtor7YF8N tNUKKhISxj8W1gwSqiLvVAMi1xsPGrTqLF1fD4fSBVAYEBiKNBllqM5ovO1yumLXg+gU EZSKho2382JEDumQMik7kWcwOItZ31R6TJp6KGxkT+3NNi6y6JbAoip+uZbcIZLTSrsF pU11iS0SmvMJOoJY7I5UrNY2OrS4D0I41h3bQX5FKVNtN0H2XwP9boLgch5CCUFdoh56 /4embsV/VvJWqmtX00ZjL3B7wlIWQQ+K2LRyhXovmAPvAUvB5lk3L8INCmRWlrtvaqyw iclQ==
MIME-Version: 1.0
Received: by 10.204.154.210 with SMTP id p18mr1592684bkw.122.1332516118414; Fri, 23 Mar 2012 08:21:58 -0700 (PDT)
Received: by 10.204.121.208 with HTTP; Fri, 23 Mar 2012 08:21:58 -0700 (PDT)
In-Reply-To: <4F6C6DC1.7020606@mozilla.com>
References: <4F6C5A5E.6050100@ericsson.com> <4F6C6138.6010908@mozilla.com> <E44893DD4E290745BB608EB23FDDB76219E813@008-AM1MPN1-041.mgdnok.nokia.com> <4F6C6DC1.7020606@mozilla.com>
Date: Fri, 23 Mar 2012 08:21:58 -0700
Message-ID: <CABkgnnUVXRZWNSO_oHbHBx24KeJdZLieNq44FaDf6wZtUD55kg@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: "Timothy B. Terriberry" <tterriberry@mozilla.com>
Content-Type: text/plain; charset="UTF-8"
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] On video codec for 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, 23 Mar 2012 15:22:00 -0000
On 23 March 2012 05:34, Timothy B. Terriberry <tterriberry@mozilla.com> wrote: > With a direct browser-to-browser connection, there is nothing sitting > between them to do the transcoding. In the DTLS-SRTP case with identity > verification, which I think a number of people here view as highly > important, you are in fact _guaranteeing_ that nothing but the browser can > encode or decode the video. This is incorrect. The browser can implement the DTLS handshake and crypto renegotiation, plus the SRTP shim. It is possible for the browser to perform the crypto without performing encode or decode if the source is capable of providing RTP. From RFC 3711: [...] Conceptually, we consider SRTP to be a "bump in the stack" implementation which resides between the RTP application and the transport layer. SRTP intercepts RTP packets and then forwards an equivalent SRTP packet on the sending side, and intercepts SRTP packets and passes an equivalent RTP packet up the stack on the receiving side.
- Re: [rtcweb] On video codec for rtcweb Bernard Aboba
- Re: [rtcweb] On video codec for rtcweb Matthew Kaufman
- [rtcweb] On video codec for rtcweb Stefan Hakansson LK
- Re: [rtcweb] On video codec for rtcweb Timothy B. Terriberry
- Re: [rtcweb] On video codec for rtcweb Lorenzo Miniero
- Re: [rtcweb] On video codec for rtcweb Markus.Isomaki
- Re: [rtcweb] On video codec for rtcweb Timothy B. Terriberry
- Re: [rtcweb] On video codec for rtcweb Cavigioli, Chris
- Re: [rtcweb] On video codec for rtcweb Markus.Isomaki
- Re: [rtcweb] On video codec for rtcweb Basil Mohamed Gohar
- Re: [rtcweb] On video codec for rtcweb Timothy B. Terriberry
- Re: [rtcweb] On video codec for rtcweb Timothy B. Terriberry
- Re: [rtcweb] On video codec for rtcweb Timothy B. Terriberry
- Re: [rtcweb] On video codec for rtcweb Timothy B. Terriberry
- Re: [rtcweb] On video codec for rtcweb Martin Thomson
- Re: [rtcweb] On video codec for rtcweb Matthew Kaufman
- Re: [rtcweb] On video codec for rtcweb Basil Mohamed Gohar
- Re: [rtcweb] On video codec for rtcweb Roman Shpount
- Re: [rtcweb] On video codec for rtcweb Tim Panton
- Re: [rtcweb] On video codec for rtcweb Serge Lachapelle
- Re: [rtcweb] On video codec for rtcweb Basil Mohamed Gohar
- Re: [rtcweb] On video codec for rtcweb Schleef, David
- Re: [rtcweb] On video codec for rtcweb Roman Shpount
- Re: [rtcweb] On video codec for rtcweb Gregory Maxwell
- Re: [rtcweb] On video codec for rtcweb Cameron Byrne
- Re: [rtcweb] On video codec for rtcweb Roman Shpount
- Re: [rtcweb] On video codec for rtcweb Jean-Marc Valin