July 23 2011: Difference between revisions

From Web Real-Time Communications Working Group Wiki
Shkansso2 (talk | contribs)
Shkansso2 (talk | contribs)
No edit summary
 
(5 intermediate revisions by 3 users not shown)
Line 48: Line 48:


== Presentations ==
== Presentations ==
* Agenda [[file:agenda.pdf]]
* Chrome implementation status: [[file:webrtc-chrome-impl-status.pdf]]
* Chrome implementation status: [[file:webrtc-chrome-impl-status.pdf]]
* Ericsson implementation status: [[file:peerconnection-implementation-experience.pdf]]
* Ericsson implementation status: [[file:peerconnection-implementation-experience.pdf]]
* Cisco implementation status: [[file:RTC-Web-Cisco-Implementations.pdf]]
* Mozilla implementation status: [[file:webrtc-mozilla-impl-status.pdf]]
* Use case presentation: [[file:use cases and reqs_webrtc.pdf]]
* Use case presentation: [[file:use cases and reqs_webrtc.pdf]]
* API (Cullens): [[file:web-rtc-proposal-deltas.pdf]]
* API deltas (Cullen): [[file:web-rtc-proposal-deltas.pdf]]
* API discussion (Cullen): [[file:webrtc-jennings.pdf]]
 
== Minutes ==
[http://www.w3.org/2011/07/23-webrtc-minutes Minutes]
 
== Actions ==
Most actions are captured in the tracker: [http://www.w3.org/2011/04/webrtc/track/ Actions]. However, as some of the actions where on non-WG participants (i.e. IETF rtcweb delegates participating in the meeting) not all could be captured in tracker. So here is the complete list:
* Cullen to send a server-provider TURN use case and user-provider TURN use case
* DanB to send comments reviewing requirements to list
* Harald to query authors on A15 on what context means
* John Elwell to propose use case on recording
* Matthew Kaufman to send some text around SDP
* Roni Even to find some of the use cases in other WG in IETF and send to group

Latest revision as of 05:49, 15 August 2011

Place and Time

  • July 23, 2011 - 1400 to 1800 local time
  • Quebec City Convention Centre - room 2103

Agenda

  • Introduction - 10 min
    • Welcome, presentation, scribe selection
  • Architecture - 20 min
  • Requirements - 20 min
    • Use cases
    • Derived requirements
    • Terminology
  • Implementation experience - 30 min
  • APIs - 1.5 hours
    • MediaStream - 45 min
      • Method of selecting alternatives (music, resolution...)
      • Method of selecting input devices (hints to the browser)
      • Mute / Unmute / Enable / Disable
    • UI requirements for user permission for device usage

Coffee break

  • APIs (continued)
    • PeerConnection - 45 min
      • Listening model
      • Mapping of media streams to RTP sessions
      • Identifying (naming) incoming media streams
      • API for specifying that SRTP is used / key handling
      • TURN server credentials (relation to “origin”????
    • Other?
  • Administrativia - 15 min
    • Working methods
    • Next meetings (phone, f2f)
    • Summary of action items

Documents

Presentations

Minutes

Minutes

Actions

Most actions are captured in the tracker: Actions. However, as some of the actions where on non-WG participants (i.e. IETF rtcweb delegates participating in the meeting) not all could be captured in tracker. So here is the complete list:

  • Cullen to send a server-provider TURN use case and user-provider TURN use case
  • DanB to send comments reviewing requirements to list
  • Harald to query authors on A15 on what context means
  • John Elwell to propose use case on recording
  • Matthew Kaufman to send some text around SDP
  • Roni Even to find some of the use cases in other WG in IETF and send to group