Re: [rtcweb] No Interim on SDES at this juncture

Martin Thomson <martin.thomson@gmail.com> Fri, 21 June 2013 18:16 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 0D9A721F9811 for <rtcweb@ietfa.amsl.com>; Fri, 21 Jun 2013 11:16:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, NO_RELAYS=-0.001]
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 uT0ZX7hR9Ka5 for <rtcweb@ietfa.amsl.com>; Fri, 21 Jun 2013 11:16:27 -0700 (PDT)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 4790D21F979E for <rtcweb@ietf.org>; Fri, 21 Jun 2013 11:16:27 -0700 (PDT)
Received: by mail-wi0-f175.google.com with SMTP id m6so902890wiv.8 for <rtcweb@ietf.org>; Fri, 21 Jun 2013 11:16:26 -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:content-transfer-encoding; bh=518OThJwBxEXIAd8klhV/K5M6w7Ak4vJ2PLeuJ+3oL4=; b=pf9ZCs2FE6c5kncvP+cGgjn6ErFJ82tjtp/ELf4Ovr5kFNsW4B84ccWs1kYghff+gX HnG6JXY1FM+284N9QUP0ooAti02dbeY/o5Y5m7R1iyxdRaJs+PgdAjeEI1vqgYAjqQMH OPlQ+P9EVg7DYvC5rbhCiJkYS03g8OV/7mOtl7gbCJGJsjrb9OqS5CoYdnAaBXeQpSdu YnqLJHOeszV9aIWeUJIR0k7t9yH3B18+tfUWp8MWheRNN2n2TSXu0qZQwtFHNKbrZJUK ps+sbz1A6ToCOZUhvbeLaSBu9QlD+YSSSGnSyKPRrn0j5MBovhSkntakxbExMqWmMRNf X64Q==
MIME-Version: 1.0
X-Received: by 10.180.20.46 with SMTP id k14mr3623942wie.14.1371838586447; Fri, 21 Jun 2013 11:16:26 -0700 (PDT)
Received: by 10.194.60.46 with HTTP; Fri, 21 Jun 2013 11:16:26 -0700 (PDT)
In-Reply-To: <12C17BE5-2302-48E9-A745-5B7265E83E8E@cisco.com>
References: <CA+9kkMDnjCNXGV0GU7x6gbbZMf4WiEuVvCRY8_Fix5tmdOB-Kg@mail.gmail.com> <AD220324-EEE7-4800-8512-FD7BADA9EC34@oracle.com> <CA+9kkMDY2Z_5_1uYJ1K_ZmrJB2a1-RE7V3aPqNHQg82DyagjCg@mail.gmail.com> <2975A93F-44DA-4020-B4DE-42E7ED98C08F@oracle.com> <51BAC9BC.6070708@ericsson.com> <94846970-4694-4EC8-AEFA-AEECEE0135AA@oracle.com> <51C02EE8.5070809@ericsson.com> <AE1A6B5FD507DC4FB3C5166F3A05A4841A2C78AD@TK5EX14MBXC273.redmond.corp.microsoft.com> <CAL02cgTFSbYSX7v3q37tsjzaPMshyyBroGWr=qmy-HGm82GJFg@mail.gmail.com> <AE1A6B5FD507DC4FB3C5166F3A05A4841A2C7EF8@TK5EX14MBXC273.redmond.corp.microsoft.com> <CAL02cgQMkHu-NqEeScT2ObfknJ+3OjXi7Y=7rUJtqeu3CbewMQ@mail.gmail.com> <8E9D2A9F-3D8B-4480-A85D-320CF30FEAA6@oracle.com> <CAL02cgT3KEb0VB9kz=QCe7Mt3oj5tZvZouFe5-Uy90Cmm0H0dQ@mail.gmail.com> <30761469-F5CC-4858-8D40-4632A7D5A682@oracle.com> <CAL02cgSS1e5zH2YRh4uTb8qxXF5Ng5y8RxRw-bGP5xmQLkiQ+Q@mail.gmail.com> <529DCF4E-2A8B-475F-8CCE-7E2ABC72EFB1@oracle.com> <CA2956C0-56B7-47E9-9EF4-9D639F8B8AD6@oracle.com> <12C17BE5-2302-48E9-A745-5B7265E83E8E@cisco.com>
Date: Fri, 21 Jun 2013 11:16:26 -0700
Message-ID: <CABkgnnWtrmHU8iOtYN+nTj2GhX4kKLcWeMCjc_K+HDw-72rTbA@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Dan Wing <dwing@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] No Interim on SDES at this juncture
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, 21 Jun 2013 18:16:28 -0000

On 21 June 2013 10:59, Dan Wing <dwing@cisco.com> wrote:
> Will the existence of SDES prevent WebRTC from building this more secure system with strong identity?  That is, when we add cryptographic identity will that be effective to prevent a bid-down attack from DTLS-SRTP to SDES?  I am thinking right now that when we add identity we can prevent that bid-down, so at that time SDES could become a proper second-class citizen.

I have thought about this a little and I can't work out a practical
bid-down.  That is, aside from the human factors/social engineering
problems, which exist in all cases.