W3C home > Mailing lists > Public > public-webrtc-editors@w3.org > September 2017

Re: Thoughts for TPAC regarding your spec?

From: Taylor Brandstetter <deadbeef@google.com>
Date: Mon, 25 Sep 2017 18:34:12 -0700
Message-ID: <CAK35n0bi5yyVcDjztXMwLA+KraYdBGURuyuhs-WJ4+WBhD+--A@mail.gmail.com>
To: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
Cc: "public-webrtc-editors@w3.org" <public-webrtc-editors@w3.org>, Martin Thomson <martin.thomson@gmail.com>, Justin Uberti <juberti@google.com>, "varun@callstats.io" <varun@callstats.io>, Miguel Casas <mcasas@google.com>, "Mandyam, Giridhar" <mandyam@qti.qualcomm.com>, "Mandyam, Giridhar" <mandyam@quicinc.com>, Emircan Uysaler <emircan@google.com>, "Keith Griffin (kegriffi)" <kegriffi@cisco.com>, "guidou@google.com" <guidou@google.com>, "Kostiainen, Anssi" <anssi.kostiainen@intel.com>, "ningxin.hu@intel.com" <ningxin.hu@intel.com>, "aleksandar.stojiljkovic@intel.com" <aleksandar.stojiljkovic@intel.com>, "roBman@awe.media" <roBman@awe.media>, Bernard Aboba <Bernard.Aboba@microsoft.com>, Dominique Hazael-Massieux <dom@w3.org>, Vivien Lacourba <vivien@w3.org>
Topics I can imagine for webrtc-pc:

   - Issues related to call forking, including #1612
   <https://github.com/w3c/webrtc-pc/issues/1612>.
      - 30 minutes, though easily could end up being more.
   - Whether a track can be removed from a subset of its streams
   <https://github.com/w3c/webrtc-pc/issues/1609>, and whether this should
   be supported on the send side.
      - ~30 minutes.
   - Getting into specifics of getParameters/setParameters: errors, the
   effects of setting a description, how scaleDownResolutionBy behaves when
   the implementation is also scaling down due to CPU constraints, etc.
      - ~2-4 hours?
   - Corner cases of BUNDLE that cause ambiguity, which we'll encounter
   when trying to specify RTCIceTransport/RTCDtlsTransport behavior in more
   detail.
      - ~1 hour
   - More differences discovered between the "track model" and "transceiver
   model" which we need to decide what to do with.
      - 1-2 hours? Depends on how much is discovered between now and then.

My estimates could be way off, though. In the last virtual interim, the
topic I thought would be easiest took the most time, and vice versa...

On Mon, Sep 25, 2017 at 12:36 AM, Stefan Håkansson LK <
stefan.lk.hakansson@ericsson.com> wrote:

> Ping! We would very much appreciate some input for TPAC planning!
>
> On 21/09/17 13:38, Stefan Håkansson LK wrote:
> > Hi all Editors!
> >
> > We've started to discuss how we should use the TPAC time, and would like
> > to hear what you think.
> >
> > I hope I got all editors for:
> > - webrtc-pc
> > - webrtc-stats
> > - mediacapture-main
> > - mediacapture-image
> > - mediacapture-depth
> > - mediacapture-record
> > - mediacapture-output
> > - mediacapture-fromelement
> > - mediacapture-screen-share
> > on the sendlist.
> >
> > Any type of input would help us, e.g. are there Issues or other things
> > in the spec(s) you edit that would gain from f2f discussion? How
> > many/how much time would be needed? Are there dependencies to other
> > specs in our stable (or in another group) we should sort out (and make
> > sure we can meet with the right people)? Or do you even think there is
> > no need to spend time at TPAC at all? (If you are not planning to attend
> > at all that is also good info.) Etc.
> >
> > Cheers,
> > Stefan
> >
> >
> >
>
>
>
Received on Tuesday, 26 September 2017 01:34:37 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:19:06 UTC