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.
w3c/webrtc-quic
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.
| 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 |
Updated: Date & Time: Friday October 17, 8am (PDT)
UPDATED: Location: Virtual Jitsi Meeting https://jitsi.tools.ietf.org/ortc2
Slides:
https://docs.google.com/presentation/d/1hFk9MhiTpwcITsxZ_KWMzmQ3SSmhdiJmLauYtbv8X-A/edit?usp=sharing
Final Agenda:
Review of spec changes
Outstanding 1.0 issues
– Stats
– IdP
– Synchronize with 1.0
– Datachannel ?
Rename IceListener to IceGatherer
Latching rules definition & added into spec
– Undefined RTP listening behavior – issue 48
Discuss SVC “automatic” configuration scenario vs manual configuration
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
Google progress; Canary 39 Sender/Receiver – JS bindings? When will we see the rest of the ORTC API?
Microsoft progress; Progress of Modern API? Under Consideration to Under Development?
Discuss options to migrate this work into the W3C WebRTC WG
On 2014-08-19 the ORTC (Object Real-time Communications) Community Group published the first draft of the following specification:
Participants contribute material to this specification under the W3C Community Contributor License Agreement (CLA).
If you have any questions, please contact the group on their public list: public-ortc@w3.org. Learn more about the ORTC (Object Real-time Communications) Community Group.
Thanks everyone, great meeting, here is the YouTube link for the video..
https://www.youtube.com/watch?v=ITNuuaugtco
—
When: Sunday July 20, 10am
Where: Google Hangouts on Air (Participatory Hangouts link to follow day of meeting) Please contact Bernard Aboba if you wish to co-locate in a physical room at IETF 90 in Toronto.
Agenda
– Review Spec (latest can be found here: http://ortc.org/, top right side)
– Review Issues (https://github.com/openpeer/ortc/issues?state=open)
– Public Draft discussion
If you feel we missed something please let us know.
Since there is quite a bit of overlap between members in the IETF RTCWEB WG and the ORTC CG we thought it would serve us well if we had the next CG meeting on the Sunday July 20, prior to the IETF 90 meeting in Toronto.
Looking at the IETF agenda (https://datatracker.ietf.org/meeting/90/agenda.html) Sunday mid-morning looks to be relatively open. With that in mind I would like to propose we have the next CG meeting on Sunday July 20 at 11:00 am.
We would need some help with room sponsorship at the hotel for the CG meeting room. We will also provide remote attendance as well for those who are not able to make it in person.
I would like to get this nailed down this week so we can announce the meeting as far in advance as possible. If you plan on coming or If you are interested in helping with room sponsorship please let me know via email directly asap: erik@hookflash.com
When: June 24, 2014 @ 10am Pacific
Slides: Can be found Here
Where: Hangouts on Air (https://plus.google.com/u/2/events/cq1mi01d5fdh8vh58t6l5svq22o)
Draft Agenda:
———————-
– Review last Editor’s Draft
http://ortc.org/wp-content/uploads/2014/05/ortc.html
– Review bug list
https://github.com/openpeer/ortc/issues?state=open
– RtpCapabilities
– API Last Call (barring any show stoppers – this will be last call for the API prior to an initial Public Draft)
On 2014-05-14 the ORTC (Object Real-time Communications) Community Group published the first draft of the following specification:
Participants contribute material to this specification under the W3C Community Contributor License Agreement (CLA).
If you have any questions, please contact the group on their public list: public-ortc@w3.org. Learn more about the ORTC (Object Real-time Communications) Community Group.
Slides | IRC Chat Transcript | Video
Agenda: (updated)
– Discussion of changes in the new Editor’s draft
– Summary of open issues (and triage of 1.1/1.2).
– Action items from last time
Proposals
– IPv6 (api or impl) and metering
– RTCP mux and freezing discussion (IceTransports have an optional Session parameter)
Big topics
– Use cases: agree on 3 main use cases beyond base set
Lossy network/SVC/FEC
Multipoint conference/simulcast/layered
Security cameras – non call scenario(s)
– Difficulties in exchanging params
Filter params
JSL vs new APIs
– What is the endgame for this work?
Action items
Links:
Current Editor’s Draft: http://ortc.org/ (Latest drafts are on the right side)
Open Issues: https://github.com/openpeer/ortc/issues?state=open
On 2014-04-29 the ORTC (Object Real-time Communications) Community Group published the first draft of the following specification:
Participants contribute material to this specification under the W3C Community Contributor License Agreement (CLA).
If you have any questions, please contact the group on their public list: public-ortc@w3.org. Learn more about the ORTC (Object Real-time Communications) Community Group.
