Re: [rtcweb] The late, great RTCWEB

Silvia Pfeiffer <> Wed, 14 August 2019 22:18 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6B074120F14 for <>; Wed, 14 Aug 2019 15:18:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.747
X-Spam-Status: No, score=-1.747 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id PrK2SRMZD45F for <>; Wed, 14 Aug 2019 15:18:57 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::72b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 411E41208E3 for <>; Wed, 14 Aug 2019 15:18:57 -0700 (PDT)
Received: by with SMTP id r21so446450qke.2 for <>; Wed, 14 Aug 2019 15:18:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=oe0TUsc35liOTqdZP8WRx3/wnmMvwXk847a8LDDJviU=; b=ArPSAREefRYlktw9Zz7Z/CEjqQZh+VNlYi5O+GseMbrqXHUPXlSj5vXvQcB8O5ylVr AxiweqKdCvq6v5KwH7S+eSyZCaeRERGYFw4iImj1TxiEfxNScUu//0L49otUkJplZ3G1 LQtnlIuOCX+8gbwFuyx1XYwmdAOCzlrNRPu4ZQWFjkh+2+v+1hSCBXRUOcbZL96/Z9rz lca93l630LPMkWHdeV/7tzK4anMVqX9L6vUCwq/kPm76PpqKz8E8sGZNhGvd0jwEvm/l 3zwfRgyQdaNqE9SGcwrdyHmNElWNz7tV4tgyEM3b0sCeKX5ZXqB6SX/XrOdmGgPgjOUX AU7A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=oe0TUsc35liOTqdZP8WRx3/wnmMvwXk847a8LDDJviU=; b=DqisJJSx32yQiriJXKtVHu0Bp89DYfxlUbiHV3tS41cbz5xa90PQiXoqAKGIHUq2kG ECW6p6ioH+uHCLJtVc9wC6MbegwArnaux/x61TUc7a68W640C0O/MEYDKn+CvAcqLVNn lvuggznc284NJjY3wlhzMGNpTdN60Jx0e6Ca4XBmOARt4auz159XsQaJhOdb5SBIpP96 GPeb/j44bVLkmnwf4aWWt2snesKoByKaj332oXGqAcmMdIojLJ2bfIaVnsMwiQN6f29j WgO19x4OToL0bmHC44cXewAVA2oVyguayS3UwJQq22xkM7kgUWCoQwOjGsI7mW394Qw5 6T+Q==
X-Gm-Message-State: APjAAAWwaJas4shIIRm+j3e/J/1rbeOnM6AMPB/6x1JMBcNKHR/H8OGw XJbWRdCMirHxIXoRdn/XFUIlGO5NpVmF3Z6kyWg=
X-Google-Smtp-Source: APXvYqx+jxxDVz9+E+x5s+AxzM1DFEN/u/Si7sMG2Qd/kWjhVi4Kwrj89mvkeqJl5QKNvNMb90Occ0CTZqvIX8Is+Io=
X-Received: by 2002:a37:be41:: with SMTP id o62mr1462160qkf.356.1565821136350; Wed, 14 Aug 2019 15:18:56 -0700 (PDT)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Silvia Pfeiffer <>
Date: Thu, 15 Aug 2019 08:18:45 +1000
Message-ID: <>
To: Ted Hardie <>
Cc:, Harald Alvestrand <>, Gonzalo Camarillo <>, Magnus Westerlund <>, Mary Barnes <>, Sean Turner <>, Cullen Jennings <>, Alissa Cooper <>, Adam Roach <>
Content-Type: multipart/alternative; boundary="0000000000009d347505901b24e5"
Archived-At: <>
X-Mailman-Approved-At: Thu, 15 Aug 2019 11:20:38 -0700
Subject: Re: [rtcweb] The late, great RTCWEB
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 14 Aug 2019 22:19:00 -0000

Mission success!
Congratulations everyone!!

On Thu., 15 Aug. 2019, 5:12 am Ted Hardie, <> wrote:

> For those of you who like to flip to the end of a book:  with the entry of
> the final dependencies of its core work into the RFC Editor queue, the
> working group is closing.  The mailing list will remain open for
> discussion, and any trailing documents will be processed by Adam as AD
> sponsored or headed to DISPATCH.
> For those of you who wish to take a journey, open your books to IETF 80,
> in Prague <>; it's late
> March and Spring is in the air.  A large and plucky band of folks are
> trying to work out if it is possible to have real time communications in a
> browser without any plugins.  The resulting work will require protocol
> changes, new APIs, and a new level of cooperation between the IETF and the
> W3C.  The outlook is optimistic; the IESG agrees to a mailing list on April
> 4, 2011 and to make the effort a working group on May 3rd.
> Our first meeting as a working group was  IETF 81
> <>:  The rooms were large,
> the energy palpable, and the optimism at a quick and decisive effort had
> resulted in a charter with milestones like this:
> Goals and Milestones:
> Aug 2011 Architecture, Security, Privacy and Threat Model sent to W3C
> Aug 2011 Use cases, Scenarios, and Requirements document (I-D) sent to  W3C
> Sep 2011 Architecture and Security, Privacy, and Threat Model document(s)
> to IESG as Informational
> Sep 2011 Use cases, Scenarios, and Requirements for RTCWeb document sent
> to IESG as Informational
> Dec 2011 RTCWeb protocol profiles and Media format specification(s) to
> IESG as PS
> Dec 2011 Information elements and events APIs Input to W3C
> Apr 2012 API to Protocol mapping document submitted to the IESG as
> Informational (if needed)
> Ladies and gentleman, we are a bit late.
> During the time this working group was active, we went through multiple
> ADs: Gonzalo was succeeded by Alissa and then by Adam.  The Area we were
> in, RAI, was merged with APPS to create ART.  Magnus, one of the original
> WG chairs, had a baby and was succeeded by Sean, who then had a baby
> (Actually, make that two babies in both cases).  Cullen was eventually
> poached by his management to serve as CTO of Webex.
> The group was also prolific.  My personal archive for the mailing list
> shows just over 9000 messages, (though this is slightly inflated by my
> putting chair messages in there as well.)   The cluster of documents that
> is the output of the work in RTCWEB and in the working groups on whom we
> had dependencies has become legendary: cluster 238 gave rise to both some
> extraordinary dwell times (the data protocol and channel drafts are at 1679
> days, more than four and half years) and some RFC editor innovations (the
> creation of a cluster mailing list, so that AUTH48 changes are coordinated
> across groups).
> While the working group tussled over interoperability with non-browser
> systems and then on the implications of that decision for codecs, we lost
> some time.  We appear, however,  to have made up for it:  WebRTC is
> available in well over a billion applications or endpoints.  By the simple
> metrics of rough consensus and running code, it is a runaway success.
> On behalf of all the chairs and area directors who were part of the
> journey, for your contributions to that success, whether as document
> author, minute taker, jabber scribe, interim host, comment maker or poser
> of questions,
> many thanks,
> Ted Hardie
> _______________________________________________
> rtcweb mailing list