There is a some interesting activity regarding Sender / Receivers on both the WebRTC WG and the ORTC CG. Robin Raymond of Hookflash (ORTC CG Editor and Chair), submitted this beauty over an hour ago. To me, this is where we begin to see some real benefits offered by an Object model that is not encumbered by SDP O/A.
Hint: SVC (Scalable Video Coding or Scalable Video Codec) becomes the norm, not the exception.
From Robin’s proposal…
Introduction After attempting to write out some use cases using the existing RTCRtpSender and RTCRtpReceiver objects and parameters for ORTC, some issues were discovered. Specifically, the application developer would need to have a fair amount of knowledge on exactly how to tweak low level parameters for anything beyond very simple use cases. For example, setting up an SVC (Scalable Video Codec) would have required knowing about what codecs support SVC, how the layering is setup for particular codecs, and finally setting up specific geometric (or temporal) attributes and layering relationship details by an application developer.
Robin also includes some great SVC use cases..
Alice wants to use a SVC (Scalable Video Codec) to send to Bob
This is for illustration purposes only. Typical benefits of SVC are
greater in conference scenarios rather than traditional point to point
scenarios. However, this scenario can presume that an intermedia
conferencing bridge would be between Alice and Bob.
Current Parameter Based API
Step 1: (Alice)
var senderCaps = RTCRtpSender.getCapabilities();
Step 2: (Bob)
var senderCaps = mysignal();
var receiverCaps = RTPRtcReceiver.getCapabilities();
Read the rest here…
We have officially changed the name and URLs for the ORTC CG (formally ORCA CG).
The old URLs will be redirected to the new ORTC CG: http://www.w3.org/community/ortc/
If you are an existing member of the ORCA CG please register at the new ORTC CG, or if you wish to become a member please register here.
Here is the notice that went out to existing members…
Hello ORCA Community Group members.
We are changing the CG name from ORCA to ORTC as requested by some of our members and other W3C members for various reasons discussed in that last CG meeting. Minutes can be found here: http://ortc.org/ortc-cg-meetings/
After discussing this with the W3C we had the choice to a.) change the name to ORTC but keep the current ORCA URI or b.) set up an entirely new CG. Since we didn’t want any confusion (ORTC CG name with a ORCA URI) we opted for the second option.
We have been told that a second legal review should not be necessary by your sponsoring organization since the new CG is simply replacing the existing CG.
Here is what that means to you as a member of ORCA:
- You will need to join the new CG: http://www.w3.org/community/ortc/
- You will need to join the public mail list.
- Signups for the ORCA group will soon be suspended
- Emails sent to the ORCA mail lists will not go through, you will need to use the new lists for new postings. Emails sent to the orca lists will return a message pointing to the new lists at ORTC CG.
- ORCA mail lists will live on and will be referenced for historical purposes.
- All Community Groups fall under the guidelines in the W3C Community Contributor License Agreement (CLA), so nothing changes there.
Soon we hope to publish a Public Working Draft of the API so that we can start implementing the API. Some of that work has already begun:https://github.com/openpeer/ortc-lib
If you have any questions about the name change please forward those to email@example.com
Thank you all for you continued support!