[rtcweb] Fwd: I-D Action: draft-johnston-rtcweb-zrtp-00.txt

Alan Johnston <alan.b.johnston@gmail.com> Fri, 23 August 2013 12:13 UTC

Return-Path: <alan.b.johnston@gmail.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 7DC6611E811D for <rtcweb@ietfa.amsl.com>; Fri, 23 Aug 2013 05:13:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id mIsIppCReV4G for <rtcweb@ietfa.amsl.com>; Fri, 23 Aug 2013 05:13:42 -0700 (PDT)
Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) by ietfa.amsl.com (Postfix) with ESMTP id 4694C11E80FF for <rtcweb@ietf.org>; Fri, 23 Aug 2013 05:13:42 -0700 (PDT)
Received: by mail-wg0-f41.google.com with SMTP id c11so1655078wgh.4 for <rtcweb@ietf.org>; Fri, 23 Aug 2013 05:13:40 -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 :content-type; bh=TZInCw+yV5z+bjSmLRRMjSiHf5PitzT1G67z5Aw5kz4=; b=SH+Uxu7qjB4F2WBz8v1MB4K2glKTRchns7Z3selJKZ0HThFk7zTjybi4CJBOpcWfeL e/A45rosZsBii/ogynHCpEZGRzwysJL+Z7BDkwCLi98ZXM97+5NuWBJsNRa2m6VLn/js YYXRyN4n5GXFiUeGYehvzi6JQfZ5g8awiE330n0TMHWN3PEr3jj8GWXNbLen87yYTBox zWQpPMPfPZ8L/Mx2Myv3LbbXUAXB1qluTTi/BIl4fglBtfaVLL5d4j8zU67iikCV3fBt KEAS7w/90dtbWZ7K02zlky3eYL1mG1yZJUjFQkc4zKw9H7Ap5yKVAkEYjQK1tMV/7PW9 MdkA==
MIME-Version: 1.0
X-Received: by with SMTP id ls1mr1456025wjb.37.1377260020168; Fri, 23 Aug 2013 05:13:40 -0700 (PDT)
Received: by with HTTP; Fri, 23 Aug 2013 05:13:40 -0700 (PDT)
In-Reply-To: <20130823011611.24302.33482.idtracker@ietfa.amsl.com>
References: <20130823011611.24302.33482.idtracker@ietfa.amsl.com>
Date: Fri, 23 Aug 2013 07:13:40 -0500
Message-ID: <CAKhHsXEDnRYoPfNPy882t+q+ENr_6WaU_FdpQG=p5Lg4nQ5gXQ@mail.gmail.com>
From: Alan Johnston <alan.b.johnston@gmail.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="089e012299c843fd1204e49c56bb"
Subject: [rtcweb] Fwd: I-D Action: draft-johnston-rtcweb-zrtp-00.txt
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 Aug 2013 12:13:43 -0000


Here's a new I-D on how ZRTP, implemented in JavaScript and run over the
data channel, can be used to provide MitM protection for WebRTC media
sessions keyed with DTLS-SRTP, without relying on any third party service
or PKI. There is an IPR disclosure submitted as well which will show up as
soon as it has been processed - it is of the usual "free if you're not
suing us" variety.

Comments most welcome.

- Alan -

---------- Forwarded message ----------
From: <internet-drafts@ietf.org>
Date: Thu, Aug 22, 2013 at 8:16 PM
Subject: I-D Action: draft-johnston-rtcweb-zrtp-00.txt
To: i-d-announce@ietf.org

A New Internet-Draft is available from the on-line Internet-Drafts

        Title           : Using ZRTP to Secure WebRTC
        Author(s)       : Alan Johnston
                          Phil Zimmermann
                          Jon Callas
                          Travis Cross
                          John Yoakum
        Filename        : draft-johnston-rtcweb-zrtp-00.txt
        Pages           : 10
        Date            : 2013-08-22

   WebRTC, Web Real-Time Communications, is a set of protocols and APIs
   used to enable web developers to add real-time communications into
   their web pages and applications with a few lines of JavaScript.
   WebRTC media flows are encrypted and authenticated by SRTP, the
   Secure Real-time Transport Protocol while the key agreement is
   provided by DTLS-SRTP, Datagram Transport Layer Security for Secure
   Real-time Transport Protocol.  However, without some third party
   identity service or certificate authority, WebRTC media flows have no
   protection against a man-in-the-middle (MitM) attack.  ZRTP, Media
   Path Key Agreement for Unicast Secure RTP, RFC 6189, does provide
   protection against MitM attackers using key continuity augmented with
   a Short Authentication String (SAS).  This specification describes
   how ZRTP can be used over the WebRTC data channel to provide MitM
   protection for WebRTC media flows keyed using DTLS-SRTP.  This
   provides users protection against MitM attackers without requiring
   browsers to support ZRTP or users to download a plugin or extension
   to implement ZRTP.

The IETF datatracker status page for this draft is:

There's also a htmlized version available at:

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:

I-D-Announce mailing list
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt