WebRTC Security Architecture
draft-ietf-rtcweb-security-arch-13

Document Type Active Internet-Draft (rtcweb WG)
Last updated 2017-11-21 (latest revision 2017-10-30)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Reviews
Stream WG state Waiting for WG Chair Go-Ahead (wg milestone: Jun 2014 - Send Security Soluti... )
Revised I-D Needed - Issue raised by WGLC, Doc Shepherd Follow-up Underway
Document shepherd Sean Turner
Shepherd write-up Show (last changed 2015-03-19)
IESG IESG state AD is watching
Consensus Boilerplate Unknown
Telechat date
Responsible AD Alissa Cooper
Send notices to Sean Turner <sean@sn3rd.com>
RTCWEB                                                       E. Rescorla
Internet-Draft                                                RTFM, Inc.
Intended status: Standards Track                        October 30, 2017
Expires: May 3, 2018

                      WebRTC Security Architecture
                   draft-ietf-rtcweb-security-arch-13

Abstract

   This document defines the security architecture for WebRTC, a
   protocol suite intended for use with real-time applications that can
   be deployed in browsers - "real time communication on the Web".

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on May 3, 2018.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Rescorla                   Expires May 3, 2018                  [Page 1]
Internet-Draft              WebRTC Sec. Arch.               October 2017

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Trust Model . . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Authenticated Entities  . . . . . . . . . . . . . . . . .   5
     3.2.  Unauthenticated Entities  . . . . . . . . . . . . . . . .   6
   4.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  Initial Signaling . . . . . . . . . . . . . . . . . . . .   8
     4.2.  Media Consent Verification  . . . . . . . . . . . . . . .  10
     4.3.  DTLS Handshake  . . . . . . . . . . . . . . . . . . . . .  11
     4.4.  Communications and Consent Freshness  . . . . . . . . . .  11
   5.  Detailed Technical Description  . . . . . . . . . . . . . . .  12
     5.1.  Origin and Web Security Issues  . . . . . . . . . . . . .  12
     5.2.  Device Permissions Model  . . . . . . . . . . . . . . . .  12
     5.3.  Communications Consent  . . . . . . . . . . . . . . . . .  14
     5.4.  IP Location Privacy . . . . . . . . . . . . . . . . . . .  14
     5.5.  Communications Security . . . . . . . . . . . . . . . . .  15
     5.6.  Web-Based Peer Authentication . . . . . . . . . . . . . .  17
       5.6.1.  Trust Relationships: IdPs, APs, and RPs . . . . . . .  18
       5.6.2.  Overview of Operation . . . . . . . . . . . . . . . .  20
       5.6.3.  Items for Standardization . . . . . . . . . . . . . .  21
       5.6.4.  Binding Identity Assertions to JSEP Offer/Answer
               Transactions  . . . . . . . . . . . . . . . . . . . .  21
         5.6.4.1.  Carrying Identity Assertions  . . . . . . . . . .  22
         5.6.4.2.  a=identity Attribute  . . . . . . . . . . . . . .  23
       5.6.5.  Determining the IdP URI . . . . . . . . . . . . . . .  23
         5.6.5.1.  Authenticating Party  . . . . . . . . . . . . . .  24
         5.6.5.2.  Relying Party . . . . . . . . . . . . . . . . . .  25
       5.6.6.  Requesting Assertions . . . . . . . . . . . . . . . .  25
Show full document text