Platform/Features/WebRTC: Difference between revisions

Jump to navigation Jump to search
no edit summary
(adding spec)
No edit summary
 
(6 intermediate revisions by 4 users not shown)
Line 11: Line 11:
|Feature feature manager=Maire Reavy
|Feature feature manager=Maire Reavy
|Feature lead engineer=Randell Jesup
|Feature lead engineer=Randell Jesup
|Feature security lead=Curtis Koenig (Maire to verify)
|Feature security lead=Christoph Diehl
|Feature privacy lead=Sid Stamm (Maire to verify)
|Feature privacy lead=Sid Stamm
|Feature accessibility lead=TBD
|Feature accessibility lead=TBD
|Feature qa lead=TBD
|Feature qa lead=Jason Smith
|Feature ux lead=Jennifer Morrow
|Feature ux lead=Jennifer Morrow
|Feature product marketing lead=TBD
|Feature product marketing lead=TBD
|Feature additional members=Cisco Team (Enda Mannion, Suhas Nandakumar, Ethan Hunt), Eric Rescorla, Rob O'Callahan (MediaStreams piece), Ralph Giles, TIm Terriberry, Anant Naranyanan (part time, mostly spec work after IETF 83)
|Feature additional members=Cisco Team (Enda Mannion, Suhas Nandakumar, Ethan Hunt), Eric Rescorla, Rob O'Callahan (MediaStreams piece), Ralph Giles, Tim Terriberry, Adam Roach, Jan-Ivar Bruaroey
}}
}}
{{FeaturePageBody
{{FeaturePageBody
Line 83: Line 83:


* [http://hg.mozilla.org/users/rocallahan_mozilla.com/specs/raw-file/tip/StreamProcessing/StreamProcessing.html Robert's MediaStream Processing API Proposal]
* [http://hg.mozilla.org/users/rocallahan_mozilla.com/specs/raw-file/tip/StreamProcessing/StreamProcessing.html Robert's MediaStream Processing API Proposal]
|Feature ux design=[Latest spec can be viewed here http://people.mozilla.com/~jboriss/specs/webrtc_spec.png]
|Feature ux design=Latest spec can be viewed here: people.mozilla.com/~jboriss/specs/webrtc_spec.png
|Feature implementation plan=We created our first public demo at IETF 83 (Paris).  We were able to demo video/audio calls and working data channels. We need to add signaling (JSEP) support and PeerConnection support.  We’re creating a project planning map of work to be done and we have a WebRTC tracking bug, [https://bugzilla.mozilla.org/show_bug.cgi?id=webrtc bug 665909]
|Feature implementation plan=We created our first public demo at IETF 83 (Paris).  We were able to demo video/audio calls and working data channels. We need to add signaling (JSEP) support and PeerConnection support.  We’re creating a project planning map of work to be done and we have a WebRTC tracking bug, [https://bugzilla.mozilla.org/show_bug.cgi?id=webrtc bug 665909]
|Feature security review=It's important to realize that this is the first step in a plan to bring video to the platform. From both a security and privacy standpoint this means we'll need to be reviewing it with an eye towards an eye towards future use cases as well as what's scoped in this one page.
|Feature security review=It's important to realize that this is the first step in a plan to bring video to the platform. From both a security and privacy standpoint this means we'll need to be reviewing it with an eye towards an eye towards future use cases as well as what's scoped in this one page.
canmove, Confirmed users
637

edits

Navigation menu