W3C home > Mailing lists > Public > public-webrtc@w3.org > November 2017

Fwd: WebRTC 1.0: Real-time Communication Between Browsers is a W3C Candidate Recommendation (Call for Implementations)

From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
Date: Thu, 2 Nov 2017 11:05:49 +0000
To: "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <HE1PR07MB3418DFFCDAFF51AFC228DE34C95C0@HE1PR07MB3418.eurprd07.prod.outlook.com>
FYI, transition to CR has now happened!

-------- Forwarded Message --------
Subject: WebRTC 1.0: Real-time Communication Between Browsers is a W3C 
Candidate Recommendation (Call for Implementations)
Date: Thu, 2 Nov 2017 11:59:53 +0100
From: Xueyuan <xueyuan@w3.org>
To: w3c-ac-forum@w3.org <w3c-ac-forum@w3.org>
CC: chairs@w3.org <chairs@w3.org>

Dear Advisory Committee Representative,

I am pleased to announce that the WebRTC 1.0: Real-time Communication 
Between Browsers specification is a W3C Candidate Recommendation:

The approval and publication are in response to this transition request:

Please provide feedback by 2018-04-15 raising issues through:

There are no known objections.

Patent disclosures relevant to this specification may be found on the 
Web Real-Time Communications Working Group's patent disclosure list in 
conformance with W3C policy:

This Call for Implementations follows section 6.4 "Candidate 
Recommendation" of the W3C Process Document:

Thank you,

For Tim Berners-Lee, W3C Director,
Philippe Le Hégaret, Project Management Lead, and
Dominique Hazael-Massieux and Vivien Lacourba, WebRTC WG Staff Contacts;
Xueyuan Jia, W3C Marketing & Communicaitons

Quoting from
WebRTC 1.0: Real-time Communication Between Browsers
W3C Candidate Recommendation 02 November 2017

This version:
Latest published version:


This document defines a set of ECMAScript APIs in WebIDL to allow media 
to be sent to and received from another browser or device implementing 
the appropriate set of real-time protocols. This specification is being 
developed in conjunction with a protocol specification developed by the 
IETF RTCWEB group and an API specification to get access to local media 
devices developed by the Media Capture Task Force.

Status of This Document:

This section describes the status of this document at the time of its 
publication. Other documents may supersede this document. A list of 
current W3C publications and the latest revision of this technical 
report can be found in the W3C technical reports index at 

The API is based on preliminary work done in the WHATWG.

While the specification is feature complete and is expected to be 
stable, there are also a number of known substantive issues on the 
specification that will be addressed during the Candidate Recommendation 
period based on implementation experience feedback.

It might also evolve based on feedback gathered as its associated test 
suite evolves. This test suite will be used to build an implementation 
report of the API.

To go into Proposed Recommendation status, the group expects to 
demonstrate implementation of each feature in at least two deployed 
browsers, and at least one implementation of each optional feature. 
Mandatory feature with only one implementation may be marked as optional 
in a revised Candidate Recommendation where applicable.

The following features are marked as risk:
      * The value negotiate of RTCRtcpMuxPolicy

This document was published by the Web Real-Time Communications Working 
Group as a Candidate Recommendation. This document is intended to become 
a W3C Recommendation. Comments regarding this document are welcome. 
Please send them to public-webrtc@w3.org (subscribe, archives). W3C 
publishes a Candidate Recommendation to indicate that the document is 
believed to be stable and to encourage implementation by the developer 
community. This Candidate Recommendation is expected to advance to 
Proposed Recommendation no earlier than 15 April 2018.

Publication as a Candidate Recommendation does not imply endorsement by 
the W3C Membership. This is a draft document and may be updated, 
replaced or obsoleted by other documents at any time. It is 
inappropriate to cite this document as other than work in progress.

This document was produced by a group operating under the W3C Patent 
Policy. W3C maintains a public list of any patent disclosures made in 
connection with the deliverables of the group; that page also includes 
instructions for disclosing a patent. An individual who has actual 
knowledge of a patent which the individual believes contains Essential 
Claim(s) must disclose the information in accordance with section 6 of 
the W3C Patent Policy.

This document is governed by the 1 March 2017 W3C Process Document.
Received on Thursday, 2 November 2017 11:06:17 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 2 November 2017 11:06:18 UTC