Using Privacy Enhanced Real-time Conferencing (PERC) in a WebRTC Context
draft-roach-perc-webrtc-00

Document Type Active Internet-Draft (individual)
Last updated 2017-03-13
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           A. Roach
Internet-Draft                                                   Mozilla
Intended status: Informational                            March 10, 2017
Expires: September 11, 2017

Using Privacy Enhanced Real-time Conferencing (PERC) in a WebRTC Context
                       draft-roach-perc-webrtc-00

Abstract

   The Privacy-Enhanced Realtime Conferencing (PERC) architecture
   defines a system by which multiparty conferences can be handled by a
   conference server that is "semi-trusted": that is, it is trusted to
   correctly handle media packets, but it is not trusted with the actual
   contents of the media streams.  In order to use this architecture
   within WebRTC, we must describe how information is conveyed among
   various network functions.  This document describes the information
   to be conveyed and how it is transferred.

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 September 11, 2017.

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

Roach                  Expires September 11, 2017               [Page 1]
Internet-Draft               PERC in WebRTC                   March 2017

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Goals . . . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Data Flows  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     4.1.  Key Distributor Co-Located with Browser . . . . . . . . .   3
       4.1.1.  Conference Establishment  . . . . . . . . . . . . . .   5
       4.1.2.  Owner Sends Offer to Conference . . . . . . . . . . .   7
       4.1.3.  Conference Processes Owner Offer  . . . . . . . . . .   9
       4.1.4.  Owner Processes Answer  . . . . . . . . . . . . . . .  10
       4.1.5.  Owner sets up media connection  . . . . . . . . . . .  11
       4.1.6.  Participant Joins Conference  . . . . . . . . . . . .  11
       4.1.7.  Conference Processes Participant Offer  . . . . . . .  13
       4.1.8.  Participant Processes Answer  . . . . . . . . . . . .  14
       4.1.9.  Participant sets up media connection  . . . . . . . .  15
     4.2.  Key Distributor Separate From Browser . . . . . . . . . .  16
   5.  New Mechanisms Required . . . . . . . . . . . . . . . . . . .  16
     5.1.  New Key Distributor DOM Object  . . . . . . . . . . . . .  16
     5.2.  New "sign" Tunnel Message . . . . . . . . . . . . . . . .  17
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  17
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  17
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  17
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  17
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  18
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  18

1.  Introduction

   The Privacy-Enhanced Realtime Conferencing (PERC) architecture
   [I-D.ietf-perc-private-media-framework] defines a system by which
   multiparty conferences can be handled by a conference server that is
   "semi-trusted": that is, it is trusted to correctly handle media
   packets, but it is not trusted with the actual contents of the media
   streams.  In order to use this architecture within WebRTC
   [W3C.WD-webrtc-20170313], we must describe how information is
   conveyed among various network functions.  This document describes
Show full document text