ORTC (Object Real-time Communications) Community Group
The mission of the Object Real-Time Communications Community Group, is to define Object-centric APIs (client-side at first) to enable Real-Time Communications in Web browsers, Mobile endpoints and Servers.
Note: Community Groups are proposed and run by the community. Although W3C hosts these conversations, the groups do not necessarily represent the views of the W3C Membership or staff.
Drafts / licensing info
| Date | Name |
|---|---|
| Object RTC (ORTC) API for WebRTC [2014/08/19] | |
| Object RTC (ORTC) API for WebRTC [2014/05/14] | |
| Object RTC (ORTC) API for WebRTC |
ORTC Draft Report Update
Updated ORTC CG Draft Report / API:
http://ortc.org/wp-content/uploads/2016/05/ortc.html
B.1 Changes since 01 March 2016
- Added the
gather()method, as noted in: Issue 165 - Removed “public” from
, as noted in: Issue 224RTCIceGatherPolicy - Removed the minQuality attribute, as noted in: Issue 351
- Made
send()andreceive()asynchronous, as noted in: Issue 399, Issue 463, Issue 468 and Issue 469 - Provided additional information on ICE candidate errors, as noted in: Issue 402
- Added state attribute to
, as noted in: Issue 403RTCSctpTransport - Provided an example of RTX/RED/FEC configuration, as noted in: Issue 404
- Clarified
payloadTypeuniqueness, as noted in: Issue 405 - Updated the list of header extensions, as noted in: Issue 409
- Added “goog-remb” to the list of feedback mechanisms, as noted in: Issue 410
- Added kind argument to the
constructor, as noted in: Issue 411RTCRtpReceiver - Clarified
send()restrictions on kind, as noted in: Issue 414 - Added
getAlgorithm()method, as noted in: Issue 427 - Changed
protocol and label to USVString, as noted in: Issue 429RTCDataChannel - Clarified nullable attributes and methods returning empty lists, as noted in: Issue 433
- Clarified support for the “direction” parameter, as noted in: Issue 442
- Clarified the apt capability of the “red” codec, as noted in: Issue 444
- Clarified usage of
attributes, as noted in: Issue 445RTCRtpEncodingParameters - Clarified firing of
onssrcconflictevent, as noted in: Issue 448 - Clarified that CNAME is only set on an
, as noted in: Issue 450RTCRtpSender - Updated references, as noted in: Issue 457
- Described behavior of
send()andreceive()with unset, as noted in: Issue 461RTCRtpEncodingParameters - Corrected dictionary initialization in the examples, noted in: Issue 464 and Issue 465
- Corrected use of enums in the examples, noted in: Issue 466
- Clarified handling of identity constraints, as noted in: Issue 467 and Issue 468
- Clarified use of
RTCRtpEncodingParameters, as noted in: Issue 470 - Changed hostCandidate type, as noted in: Issue 474
- Renamed state change event handlers to onstatechange, as noted in: Issue 475
- Updated description of
closed state, as noted in: Issue 476RTCIceGatherer - Updated description of
object, as noted in: Issue 477RTCIceTransport - Updated description of relatedPort, as noted in: Issue 484
- Updated description of
, as noted in: Issue 485RTCIceParameters - Clarified exceptions in
construction, as noted in: Issue 492RTCDataChannel - Provided a reference to
error.message, as noted in: Issue 495 - Clarified
description, as noted in: Issue 496RTCRtpReceiver - Clarified default for clockRate attribute, as noted in: Issue 500
- Removed use of “null if unset”, as noted in: Issue 503
- Updated
constructor, as noted in: Issue 504RTCSctpTransport - Clarified behavior of
getCapabilities(), as noted in: Issue 509 - Addressed issues with
, as noted in: Issue 519RTCDataChannelParameters
W3C ORTC CG Meeting 10 – November 20 2015
When: November 20, 2015 10am Pacific
Concluded
Video: coming
Slides: https://docs.google.com/presentation/d/11JBlA-9gY4qZzUB6YhhMjeeA7tc9vSJowvs6tgI2f1c/edit#slide=id.p
Minutes: http://ortc.org/wp-content/uploads/2015/11/ortc-cg-meeting10-mins.txt
Agenda
Review action items from last meeting
Review open issues: https://github.com/openpeer/ortc/issues?q=is%3Aopen
Review current draft: http://ortc.org (upper right hand side)
Review implementation progress: ORTC Lib, MS Edge, Google ?
Review ORTC Spec alignment with WebRTC WG 1.0 spec, review WebRTC NV direction.
ORTC CG Editors Draft Update – June 22 2015
Big thanks to everyone (especially Bernard) for putting in the extra work required here for our next CG meeting:
Draft Community Group Report 22 June 2015
B.1 Changes since 7 May 2015
- Addressed Philipp Hancke’s review comments, as noted in: Issue 198
- Added the “failed” state to
, as noted in: Issue 199RTCIceTransportState - Added text relating to handling of incoming media packets prior to remote fingerprint verification, as noted in: Issue 200
- Added a complete attribute to the
dictionary, as noted in: Issue 207RTCIceCandidateComplete - Updated the description of
RTCIceGatherer.close()and the “closed” state, as noted in: Issue 208 - Updated Statistics API error handling to reflect proposed changes to the WebRTC 1.0 API, as noted in: Issue 214
- Updated Section 10 (RTCDtmfSender) to reflect changes in the WebRTC 1.0 API, as noted in: Issue 215
- Clarified state transitions due to consent failure, as noted in: Issue 216
- Added a reference to [FEC], as noted in: Issue 217
ORTC CG Meeting 9 – June 24, 10am PDT
Video recording: https://www.youtube.com/watch?v=7P2M_T0H6r8
Slides: ORTC-CG-2015-06-24
IRC Chat: http://irc.w3.org/ channel: ORTC
Minutes: http://ortc.org/wp-content/uploads/2015/06/ortc-cg-meeting-9-june24-2015.txt
When: June 24, 2015 10am PDT
Agenda
Review action items from last meeting:
– RTCIceCandidateComplete dictionary
https://github.com/openpeer/ortc/issues/207
– RTCIceGatherer.close affect on RTCIceTransport / RTCDtlsTransport
https://github.com/openpeer/ortc/issues/208
– Comments added to #200
Incoming media prior to Remote Fingerprint Verification
https://github.com/openpeer/ortc/issues/200
– Comments added to #170, Peter to send fuller proposal to list
Response to connectivity checks prior to calling iceTransport.start()?
https://github.com/openpeer/ortc/issues/170#issuecomment-105629219
– Original #188 – Priority Calculation, new bug #209
Trying to remove RTCIceTransport.createAssociatedTransport(component)
https://github.com/openpeer/ortc/issues/209
– Philipp Hancke’s Review Comments
https://github.com/openpeer/ortc/issues/198
Review open issues: https://github.com/openpeer/ortc/issues?q=is%3Aopen
Review current draft: http://ortc.org (upper right hand side)
Review implementation progress: ORTC Lib, MS Edge, Google ?
Review ORTC CG alignment with WebRTC WG and 1.0 spec.
Questions, comments?
Plan next meeting.
W3C ORTC CG Meeting #9 – schedule bashing
On the last call we decided to have our next CG meeting around the third week in June. Here is the doodle for that meeting. Please chime in and let us know when you would prefer to have that meeting. All times are in PDT.
Doodle Link: http://doodle.com/w2wtthx3xbuaxexw#table
ORTC CG Meeting 8
ORTC CG Meeting 8 will be held on May 13 at 10am – Pacific Daylight Time.
Agenda:
- Review Bugs:
https://github.com/openpeer/ortc/issues?q=is%3Aopen - Review current draft
http://ortc.org/wp-content/uploads/2015/05/ortc.html - Stefan requested we comment on this…
The WebRTC and Device APIs Working Groups request feedback on the Last
Call Working Draft of Media Capture and Streams, a JavaScript API that
enables access to cameras and microphones from Web browsers as well as
control of the use of the data generated (e.g. rendering what a camera
captures in a html video element):
http://www.w3.org/TR/2015/WD-mediacapture-streams-20150414/ - CG alignment with 1.0
Updated ORTC API 3/25/2015
The ORTC Editors Draft has been updated today:
http://ortc.org/wp-content/uploads/2015/03/ortc.html
B.1 Changes since 22 January 2015
- Updated Section 8.3 on RTP matching rules, as noted in: Issue 48
- Further updates to the Statistics API, reflecting: Issue 85
- Added support for maxptime, as noted in: Issue 160
- Revised the text relating to
RTCDtlsTransport.start(), as noted in: Issue 168 - Clarified handling of incoming connectivity checks by the
, as noted in: Issue 170RTCIceGatherer - Added Section 9.3.2.1, defining DTMF capabilities and settings, as noted in: Issue 177
- Clarified pre-requisites for
insertDTMF(), based on: Issue 178 - Added Section 13.4 and updated Section 9.5.1 to clarify aspects of RTCP sending and receiving, based on: Issue 180
- Fixed miscellaneous typos, as noted in: Issue 183
- Added informative reference to [RFC3264] Section 5.1, as noted in: Issue 184
Now that we have an updated draft we will be calling for the next ORTC Community Group meeting. That post will follow soon.
ORTC W3C CG Meeting 7
Minutes: ORTC CG 7
Slides: ORTC-CG-2015-01-27
22 January 2015 Editor’s draft:
http://ortc.org/wp-content/uploads/2015/01/ortc.html
Changes from the October 14 Editor’s Draft:
WebRTC 1.0 compatibility
- Statistics API Update (Issue 85)
- H.264 parameters update (Issue 158)
- Support for maxptime (Issue 160)
- RTCRtpUnhandledEvent update (Issue 163)
- Support for RTCIceGatherer.state (Issue 164)
Call for Implementations
Existing reference implementations:
– ORTC Library: http://www.slideshare.net/ErikLagerway/ortc-lib-introduction
– Call for help, there is plenty to do, some examples:
> Browsers: JS Shim work
> Servers: Node.js work eg. SIP to ORTC Gateway
—
UPDATE: ORTC CG Meeting 7 will be held on January 27 at 9am – Pacific Standard Time.
UPDATE Video Bridge (Chrome Required) https://plus.google.com/hangouts/_/guhlgxwpkjvqvqq5nd7576zcc4a?hl=en
Slides: https://docs.google.com/presentation/d/14YFaZyXgyrHeKTCnSrDYQQvoSNw1SSfuzy0bAUKnnrc/edit#slide=id.p
—-
As a follow-up to the recent email list posting, here are some proposed dates/times for ORTC CG Meeting 7. Please indicate your preference on dates/times here: http://doodle.com/mzxf4wucswqgc698
Note: I have kept the meeting times in the morning to aid in EU / Overseas member participation.
We would like to use Jitsi for this one again. Emil, would you be ok with that? If so is this the correct link?
Draft Agenda
Review of spec changes
Review of issues:
https://github.com/openpeer/ortc/issues?q=is%3Aopen
Issue 48 (Matching Rules)
Issue 165 (ICE re-gathering)
Issue 167 (DTLS role)
Issue 168 (DTLS interop)
Call for Implementations: Share what you are working on!
Existing reference implementations:
– ORTC Library (incomplete): http://www.slideshare.net/ErikLagerway/ortc-lib-introduction
There is plenty to do! Some examples:
– Browsers: JS shim work
– Servers: Node.js work eg. SIP to ORTC Gateway
See something missing? Please reply to the mail list posting with your comments.
W3C ORTC CG in Top 5
ORTC CG Meeting 6 – Recording
Here is the recording and minutes from the CG meeting on October 14 2014.
Meeting Recording: https://www.youtube.com/watch?v=Ezg82YNLHv8
Minutes: w3c-ortc-cg-6
