[rtcweb] API requirements

Martin Thomson <martin.thomson@gmail.com> Mon, 09 July 2012 21:10 UTC

Return-Path: <martin.thomson@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 CC10E11E8212 for <rtcweb@ietfa.amsl.com>; Mon, 9 Jul 2012 14:10:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.723
X-Spam-Status: No, score=-3.723 tagged_above=-999 required=5 tests=[AWL=-0.124, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id LycI7rcUGEJ8 for <rtcweb@ietfa.amsl.com>; Mon, 9 Jul 2012 14:10:02 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com []) by ietfa.amsl.com (Postfix) with ESMTP id 1826E11E81D4 for <rtcweb@ietf.org>; Mon, 9 Jul 2012 14:10:01 -0700 (PDT)
Received: by bkty7 with SMTP id y7so3129585bkt.31 for <rtcweb@ietf.org>; Mon, 09 Jul 2012 14:10:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=km6Wze+o0MZ2cPHwksxBezdNim4evUnpzz5fPi3QW7k=; b=gcM7f5he7J7JubXmmryyLFRPylLpenwBG05pWTcARTtb7D1dLzpMBOrLOJYzTLt3mG K5XiZSVVrBJqwwNkRJ3R2G/uvSrE/YRBsPrTHjduVGTEbk7xARnhp/ZhsEgQLPt1401Y 9HP7S0kk8mD+VNcN4I5McbMZUuG53cj88lECe6vrEfkPTXlyT6uST2y5TPZmXUbgecyn 7ZxWM8UNQMBUmEviaoAjX+nemRe7uAPrv1hksP9ofGHIVVCPFbKimSAVnxUj2FA+PFEt uh5ac4K5D76bpotY2fLwNjQQREHr6D+tXHDTk1p+GTPT/zI/lQcuSplqEJddn7hH11Tm TK/A==
MIME-Version: 1.0
Received: by with SMTP id r5mr9741762bkw.49.1341868227079; Mon, 09 Jul 2012 14:10:27 -0700 (PDT)
Received: by with HTTP; Mon, 9 Jul 2012 14:10:27 -0700 (PDT)
Date: Mon, 09 Jul 2012 14:10:27 -0700
Message-ID: <CABkgnnWfes+v0eGjP=CavKnp5xri0yJu3XO1zr3jLHR-MvUL+A@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: rtcweb@ietf.org
Content-Type: text/plain; charset="UTF-8"
Subject: [rtcweb] API requirements
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, 09 Jul 2012 21:10:06 -0000

We have just submitted a draft for discussion in the rtcweb working group:


This draft describes the information that must pass between browser
and application in order to establish real-time communications.  This
is not user-facing requirements (-rtcweb-use-cases-and-requirements)
or an outright API specification (-jsep).

The goal here is to enable the creation and consumption of streams of
media packets within the security constraints.  The draft describes
the minimum necessary set of information only to achieve this end.

In related news, Microsoft just joined the W3C Web Real-Time
Communications Working Group.  Once a few clerical issues are
addressed, new W3C proposals that address these requirements will