Weekly github digest (WebRTC WG specifications)

Issues
------
* w3c/webrtc-pc (+3/-5/💬9)
  3 issues created:
  - Firing signalingstatechange early and synchronously invites trouble (by jan-ivar)
    https://github.com/w3c/webrtc-pc/issues/1885 
  - Is close() supposed to fire state change events? Connection state change set asynchronously? (by henbos)
    https://github.com/w3c/webrtc-pc/issues/1883 
  - RTCDataChannelInit unknown member handling (by lgrahl)
    https://github.com/w3c/webrtc-pc/issues/1882 

  4 issues received 9 new comments:
  - #1879 Possible to lose data with a reliable, pre-negotiated data channel? (4 by jan-ivar, lgrahl, taylor-b)
    https://github.com/w3c/webrtc-pc/issues/1879 [question] 
  - #1882 RTCDataChannelInit unknown member handling (2 by lgrahl, alvestrand)
    https://github.com/w3c/webrtc-pc/issues/1882 
  - #1883 Is close() supposed to fire state change events? Connection state change set asynchronously? (2 by jan-ivar)
    https://github.com/w3c/webrtc-pc/issues/1883 
  - #1853 Allow to import existing certificate (1 by alvestrand)
    https://github.com/w3c/webrtc-pc/issues/1853 [enhancement] 

  5 issues closed:
  - Allow to import existing certificate https://github.com/w3c/webrtc-pc/issues/1853 [enhancement] 
  - What should receiver.getParameters().encodings[] return? https://github.com/w3c/webrtc-pc/issues/1840 [May 2018 interim] [PR exists] 
  - RTCRtpDecodingParameters https://github.com/w3c/webrtc-pc/issues/1852 [May 2018 interim] [PR exists] 
  - RTCDataChannelInit unknown member handling https://github.com/w3c/webrtc-pc/issues/1882 
  - Initial data channel state is inconsistent https://github.com/w3c/webrtc-pc/issues/1761 [Needs PR] 

* w3c/webrtc-stats (+0/-2/💬6)
  4 issues received 6 new comments:
  - #348 add a graph showing the relationship of stats to the spec (3 by vr000m, jan-ivar, alvestrand)
    https://github.com/w3c/webrtc-stats/issues/348 
  - #275 Add per layer stats for SVC (1 by alvestrand)
    https://github.com/w3c/webrtc-stats/issues/275 [Submitter input needed] 
  - #347 Should WebRTC be [SecureContext] (1 by alvestrand)
    https://github.com/w3c/webrtc-stats/issues/347 [Submitter input needed] 
  - #339 Add stat for RTTs between client and STUN/TURN server (1 by vr000m)
    https://github.com/w3c/webrtc-stats/issues/339 

  2 issues closed:
  - Add per layer stats for SVC https://github.com/w3c/webrtc-stats/issues/275 [Submitter input needed] 
  - Should WebRTC be [SecureContext] https://github.com/w3c/webrtc-stats/issues/347 [Submitter input needed] 



Pull requests
-------------
* w3c/webrtc-pc (+3/-3/💬3)
  3 pull requests submitted:
  - Mark a couple of references as normative (by dontcallmedom)
    https://github.com/w3c/webrtc-pc/pull/1884 
  - Correction for feature at risk (by aboba)
    https://github.com/w3c/webrtc-pc/pull/1881 
  - Specify that "throw" aborts processing (by alvestrand)
    https://github.com/w3c/webrtc-pc/pull/1880 

  3 pull requests received 3 new comments:
  - #1803 Update mandatory to implement stats (1 by aboba)
    https://github.com/w3c/webrtc-pc/pull/1803 
  - #1810 Update structured cloning for recent changes to HTML (1 by stefhak)
    https://github.com/w3c/webrtc-pc/pull/1810 
  - #1822 Data channel closing procedure (1 by alvestrand)
    https://github.com/w3c/webrtc-pc/pull/1822 [Needs submitter action] 

  3 pull requests merged:
  - Specify that "throw" aborts processing
    https://github.com/w3c/webrtc-pc/pull/1880 
  - Mark simulcast reception as a feature at risk
    https://github.com/w3c/webrtc-pc/pull/1876 
  - In-band negotiated channel should be open when dispatching
    https://github.com/w3c/webrtc-pc/pull/1851 


Repositories tracked by this digest:
-----------------------------------
* https://github.com/w3c/webrtc-pc
* https://github.com/w3c/webrtc-stats
* https://github.com/w3c/webrtc-charter