Re: [rtcweb] Let's define the purpose of WebRTC

Eric Rescorla <ekr@rtfm.com> Sat, 05 November 2011 15:38 UTC

Return-Path: <ekr@rtfm.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 CC4A621F8770 for <rtcweb@ietfa.amsl.com>; Sat, 5 Nov 2011 08:38:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level:
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 PViDIyxrOFY2 for <rtcweb@ietfa.amsl.com>; Sat, 5 Nov 2011 08:38:09 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1FD6821F861E for <rtcweb@ietf.org>; Sat, 5 Nov 2011 08:38:09 -0700 (PDT)
Received: by vcbfl11 with SMTP id fl11so3381089vcb.31 for <rtcweb@ietf.org>; Sat, 05 Nov 2011 08:38:08 -0700 (PDT)
Received: by 10.220.2.19 with SMTP id 19mr1481652vch.161.1320507486097; Sat, 05 Nov 2011 08:38:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.118.132 with HTTP; Sat, 5 Nov 2011 08:37:25 -0700 (PDT)
X-Originating-IP: [74.95.2.173]
In-Reply-To: <CAD6AjGRBmrAqB3CEWxtaXnryPA5App13S2jJPAt+7HwWZsQFzA@mail.gmail.com>
References: <CALiegfkVNVAs_MyU_-4koA4zRwSn1-FwLjY9g_oZVkhi9rSK5Q@mail.gmail.com> <CAD5OKxt=k_Mon_GMs1w-bGMgpk12h6ZQ=FkoRVsTp4271iMSLA@mail.gmail.com> <CABcZeBNMTgwH-R_jd-AiEJ8tELTeFMNm-bAJohRg2RxD5e+kZQ@mail.gmail.com> <CAD6AjGRBmrAqB3CEWxtaXnryPA5App13S2jJPAt+7HwWZsQFzA@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sat, 5 Nov 2011 08:37:25 -0700
Message-ID: <CABcZeBNtoizuRymVMxF4CdiLu1Nju63C0xkWJHjoarpxeLXjyA@mail.gmail.com>
To: Cameron Byrne <cb.list6@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Let's define the purpose of WebRTC
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: Sat, 05 Nov 2011 15:38:09 -0000

Good point. Also, of course (unless you use the SRTP header encryption
extension) the SRTP header is in the clear, so you mostly just don't get
the media itself.

-Ekr


On Sat, Nov 5, 2011 at 8:28 AM, Cameron Byrne <cb.list6@gmail.com> wrote:
>
> On Nov 5, 2011 7:35 AM, "Eric Rescorla" <ekr@rtfm.com> wrote:
>>
>> On Sat, Nov 5, 2011 at 6:54 AM, Roman Shpount <roman@telurix.com> wrote:
>> >
>> > On Sat, Nov 5, 2011 at 9:35 AM, Iñaki Baz Castillo <ibc@aliax.net>
>> > wrote:
>> > If you get a quality problem, it would be next to impossible to
>> > figure out what's causing it with everything encrypted
>>
>> It's actually not that bad. There are network analysis tools that can
>> process
>> encrypted traffic if they are provided with the keys. They're a pretty
>> standard
>> tool for debugging HTTPS. I believe wireshark can do this and I know
>> ssldump
>> can.
>>
>
> I think you can set crypto in srtp to null as well for troubleshooting
>
> Cb
>
>> -Ekr
>
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
>