Re: [rtcweb] I-D Action: draft-ietf-rtcweb-security-arch-04.txt
Eric Rescorla <ekr@rtfm.com> Mon, 22 October 2012 16:35 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 F121721F8B46 for <rtcweb@ietfa.amsl.com>; Mon, 22 Oct 2012 09:35:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.811
X-Spam-Level:
X-Spam-Status: No, score=-102.811 tagged_above=-999 required=5 tests=[AWL=0.166, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1-qfcR88+pnh for <rtcweb@ietfa.amsl.com>; Mon, 22 Oct 2012 09:35:20 -0700 (PDT)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 08A1821F8B50 for <rtcweb@ietf.org>; Mon, 22 Oct 2012 09:35:19 -0700 (PDT)
Received: by mail-la0-f44.google.com with SMTP id b11so2025994lam.31 for <rtcweb@ietf.org>; Mon, 22 Oct 2012 09:35:13 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:from:date :message-id:subject:to:content-type:x-gm-message-state; bh=wPAH2Dns99sUokDve80el+t58EiImJgrv3MWj26H0Fw=; b=lZx87hM204SfZpXfgmTyFbuYT3s9SUS/zYhX7re9zsqkHVDlsuuuClGEeXFMpSfhbI L4ZU72RJOmLlcFSdl/LjD6EKvUZNd/RsMibAe+XfNHFyM8nx8iD2wqItrmALuI9gw3ca wQB2almQnL1FAS3+KYCK/zc8LC4VDgCXm9ymMHz3XXQVuvd+2tGj+MyXUJCSz7MCCWaL 5HsKmfCyuN27okGCDS73ODSbd77hGcHtPfsNTuKncTlcdgAGZPpbBZvSgAeHFHjhPjiH 0Ld9EtHpC5uUzIoGgYgixsf+wdhppstsUQWffs4nABLUynE05YGdSjH+mS418tSoHyJG B3ag==
Received: by 10.152.103.243 with SMTP id fz19mr8747865lab.27.1350923713637; Mon, 22 Oct 2012 09:35:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.152.25.39 with HTTP; Mon, 22 Oct 2012 09:34:33 -0700 (PDT)
X-Originating-IP: [74.95.2.173]
In-Reply-To: <20121022162719.7586.16379.idtracker@ietfa.amsl.com>
References: <20121022162719.7586.16379.idtracker@ietfa.amsl.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Mon, 22 Oct 2012 09:34:33 -0700
Message-ID: <CABcZeBMMWnawOOi9WWJxF0-OGNKJmj4COx2kNohu2SMLj5Xc5g@mail.gmail.com>
To: rtcweb@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
X-Gm-Message-State: ALoCoQmL9C6MMDJFfEqeDFUG2BzoeGOo5eITwO90pf1+QsDthcu9jvw/iZl6GiSwCVPgVEUjbyOc
Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-security-arch-04.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: Mon, 22 Oct 2012 16:35:21 -0000
Please ignore this version. I had a version control hiccup. Will post the correct version in a few minutes after I unscrew things. -Ekr On Mon, Oct 22, 2012 at 9:27 AM, <internet-drafts@ietf.org> wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Real-Time Communication in WEB-browsers Working Group of the IETF. > > Title : RTCWEB Security Architecture > Author(s) : Eric Rescorla > Filename : draft-ietf-rtcweb-security-arch-04.txt > Pages : 37 > Date : 2012-10-22 > > Abstract: > The Real-Time Communications on the Web (RTCWEB) working group is > tasked with standardizing protocols for enabling real-time > communications within user-agents using web technologies (e.g > JavaScript). The major use cases for RTCWEB technology are real-time > audio and/or video calls, Web conferencing, and direct data transfer. > Unlike most conventional real-time systems (e.g., SIP-based soft > phones) RTCWEB communications are directly controlled by some Web > server, which poses new security challenges. For instance, a Web > browser might expose a JavaScript API which allows a server to place > a video call. Unrestricted access to such an API would allow any > site which a user visited to "bug" a user's computer, capturing any > activity which passed in front of their camera. [I-D.ietf-rtcweb- > security] defines the RTCWEB threat model. This document defines an > architecture which provides security within that threat model. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-rtcweb-security-arch > > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-rtcweb-security-arch-04 > > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=draft-ietf-rtcweb-security-arch-04 > > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb
- [rtcweb] I-D Action: draft-ietf-rtcweb-security-a… internet-drafts
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-securi… Eric Rescorla