RE: ORTC CG Meeting #6 - Agenda Bashing

That’s why you may want to schedule meetings in the very early hours, let’s say 8:00 am PST,  that will cover most Europe as well as all US and LatAm and MEA….

My 1 cent.



From: Mary Barnes [mailto:mary.ietf.barnes@gmail.com]
Sent: Wednesday, October 1, 2014 09:47
To: Alexandre GOUAILLARD
Cc: Erik Lagerway; public-ortc@w3.org
Subject: Re: ORTC CG Meeting #6 - Agenda Bashing



Yeah, that time is pretty much only convenient for people in North (and I guess South) American timezones.  Certainly, it's hard to find something that works for everyone, but afternoon Pacific time is bad for many.





On Wed, Oct 1, 2014 at 7:24 AM, Alexandre GOUAILLARD <agouaillard@gmail.com<mailto:agouaillard@gmail.com>> wrote:

   hum,



   4am singapore time saturday 18th ......



   On Tue, Sep 30, 2014 at 1:36 AM, Erik Lagerway <erik@hookflash.com<mailto:erik@hookflash.com>> wrote:

      My bad,



      Pacific - Daylight Savings. (PDT)



      UTC/GMT -7 hour



      In case anyone was wondering, DST ends on Sunday 02 November 2014, 02:00 local daylight time = this will not affect the meeting time.




      Erik Lagerway<http://ca.linkedin.com/in/lagerway> | Hookflash<http://hookflash.com/> | 1 (855) Hookflash ext. 2 | Twitter<http://twitter.com/elagerway> | WebRTC.is Blog<http://webrtc.is/>



      On Mon, Sep 29, 2014 at 10:25 AM, Mary Barnes <mary.ietf.barnes@gmail.com<mailto:mary.ietf.barnes@gmail.com>> wrote:

         What's the timezone?



         On Mon, Sep 29, 2014 at 11:24 AM, Erik Lagerway <erik@hookflash.com<mailto:erik@hookflash.com>> wrote:

            It's getting near that time again, the proposed date for the next ORTC CG Meeting:



            Friday October 17 at 1pm.



            The draft agenda:



            ---



            Review of spec changes



            Outstanding 1.0 issues

             - Stats

             - IdP

             - Synchronize with 1.0

              - Datachannel ?



            Rename IceListener to IceGatherer



            Latching rules definition & added into spec

             - Undefined RTP listening behavior - issue 48

            Discuss SVC "automatic" configuration scenario vs manual configuration



            Call for implementations. Existing reference implementations:

             - ORTC Library: http://www.slideshare.net/ErikLagerway/ortc-lib-introduction


              - Call for help, there is plenty to do, some examples:

                - Browsers - JS Shim work

                - Servers - Node.js work eg. SIP to ORTC Gateway

             - Google progress; Canary 39 Sender/Receiver - JS bindings, when will we see the rest of the ORTC API ?

             - Microsoft progress; Progress of Modern API? Under Consideration to Under Development ?



            Discuss options to migrate this work into the W3C WebRTC WG



            ---



            Comments? Are we missing anything?



            /Erik








            Erik Lagerway<http://ca.linkedin.com/in/lagerway>  | Hookflash<http://hookflash.com/>  | 1 (855) Hookflash ext. 2 | Twitter<http://twitter.com/elagerway>  | WebRTC.is Blog<http://webrtc.is/>











   --

   Alex. Gouaillard, PhD, PhD, MBA

   ------------------------------------------------------------------------------------

   CTO - Temasys Communications, S'pore / Mountain View

   President - CoSMo Software, Cambridge, MA

   ------------------------------------------------------------------------------------

   sg.linkedin.com/agouaillard<http://sg.linkedin.com/agouaillard>

   •••••••••