W3C home > Mailing lists > Public > public-webrtc@w3.org > October 2012

RE: TPAC f2f: start building agenda

From: Jim Barnett <Jim.Barnett@genesyslab.com>
Date: Fri, 12 Oct 2012 05:29:36 -0700
Message-ID: <E17CAD772E76C742B645BD4DC602CD8106CE0479@NAHALD.us.int.genesyslab.com>
To: "Stefan Hakansson LK" <stefan.lk.hakansson@ericsson.com>, <public-webrtc@w3.org>
Stefan,
  Could we add the topic of reliable media transport for PeerConnection?
I hope the discussion would be brief.

- Jim

-----Original Message-----
From: Stefan Hakansson LK [mailto:stefan.lk.hakansson@ericsson.com] 
Sent: Friday, October 12, 2012 5:57 AM
To: public-webrtc@w3.org
Subject: TPAC f2f: start building agenda

Hi all,

the chairs have assembled a list of possible topics for the f2f at TPAC.

It is divided into a "reporting" part and a "discussion" part.

We have 1.5 days (0.5 day reserved for Media Cap TF), so it is obvious
we can't do all of the below. So we would like feedback from all of you
on:

* What topics have we missed?

* What topics (and include the ones we missed in your consideration) do
you think we should spend f2f time on?


Stefan for the chairs


Possible reports:
=================
* Status implementations and testing
** Report from implementers (including feedback)
** Status on testing
* Reporting from Test The Web Forward, Paris?
* Idea: Feedback from reviewers (we could hand out tasks to review 
sections of the draft to people and have them present at the meeting)?


Possible topics for discussion/decision:
========================================
* States and Call Flows
** PeerConnection states, ICE agent states
*** what is exposed to the app?
*** what transitions are legal
** what events fire, when?
** What is the signaling seq (SDP exchange)
** Rollback (related to error handling)

* Error handling principles

* Stats
** Object-Attribute model of stats (confirm)
** Naming of objects
** Objects referring to each other: how?

* Application of constraints/settings to MediaStream(Tracks) sent over 
PerrConnection
** both at the sending end and at the receiving end
** Signalling recv->sender may be SDP carried - or not
** Examples include AGC (or not), priority, pause/resume, BW setting, 
congestion feedback,
** Should handle added tracks as well
** Can settings/Constraints be changed; or is it one-time (at
addStream)?

* Review of IdP part

* Review of data channel part

* Details that need settling
** Handling of removeTrack/removeStream
*** Are they kept as empty indices in the track-list/stream-list or not?
** DTMF
*** Just pick something
Received on Friday, 12 October 2012 12:30:58 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:30 UTC