Weekly github digest (WebRTC WG specifications)

Issues
------
* w3c/webrtc-pc (+1/-3/💬17)
  1 issues created:
  - Possible to lose data with a reliable, pre-negotiated data channel? (by taylor-b)
    https://github.com/w3c/webrtc-pc/issues/1879 [question] 

  9 issues received 17 new comments:
  - #1858 What happens when an answerer stops a transceiver that others are "bundled" on? (5 by jan-ivar, taylor-b)
    https://github.com/w3c/webrtc-pc/issues/1858 [May 2018 interim] 
  - #1879 Possible to lose data with a reliable, pre-negotiated data channel? (3 by tuexen, lgrahl)
    https://github.com/w3c/webrtc-pc/issues/1879 [question] 
  - #1872 sendEncodings in "create an RTPSender" should reflect platform capabilities (2 by jan-ivar, alvestrand)
    https://github.com/w3c/webrtc-pc/issues/1872 [May 2018 interim] 
  - #230 Add support for WebRTC Data Channel in Workers (2 by feross, alvestrand)
    https://github.com/w3c/webrtc-pc/issues/230 [External feedback] [PR exists] 
  - #1839 What should sender.getParameters().codecs return before negotiation? (1 by alvestrand)
    https://github.com/w3c/webrtc-pc/issues/1839 [May 2018 interim] 
  - #1834 Handling of invalid values in RTCRtpSender.setParameters() (1 by adam-be)
    https://github.com/w3c/webrtc-pc/issues/1834 [May 2018 interim] 
  - #1871 localDescription, remoteDescription et al. need internal slots (1 by aboba)
    https://github.com/w3c/webrtc-pc/issues/1871 [Needs assignee action] 
  - #1840 What should receiver.getParameters() return? (1 by alvestrand)
    https://github.com/w3c/webrtc-pc/issues/1840 [May 2018 interim] 
  - #1852 RTCRtpDecodingParameters (1 by aboba)
    https://github.com/w3c/webrtc-pc/issues/1852 [May 2018 interim] 

  3 issues closed:
  - localDescription, remoteDescription et al. need internal slots https://github.com/w3c/webrtc-pc/issues/1871 [PR exists] 
  - Recycling an m= section may not remove the old transceiver's remote track from its stream https://github.com/w3c/webrtc-pc/issues/1778 [PR exists] 
  - sendEncodings in "create an RTPSender" should reflect platform capabilities https://github.com/w3c/webrtc-pc/issues/1872 [May 2018 interim] 



Pull requests
-------------
* w3c/webrtc-pc (+4/-5/💬4)
  4 pull requests submitted:
  - Fix Respec link error (by jan-ivar)
    https://github.com/w3c/webrtc-pc/pull/1878 
  - Add internal slots for descriptions. (by jan-ivar)
    https://github.com/w3c/webrtc-pc/pull/1877 
  - Mark simulcast reception as a feature at risk (by aboba)
    https://github.com/w3c/webrtc-pc/pull/1876 
  - receiver.getParameters clarification (by aboba)
    https://github.com/w3c/webrtc-pc/pull/1875 

  3 pull requests received 4 new comments:
  - #1851 In-band negotiated channel should be open when dispatching (2 by lgrahl, jan-ivar)
    https://github.com/w3c/webrtc-pc/pull/1851 
  - #1877 Add internal slots for descriptions. (1 by jan-ivar)
    https://github.com/w3c/webrtc-pc/pull/1877 
  - #1822 Data channel closing procedure (1 by lgrahl)
    https://github.com/w3c/webrtc-pc/pull/1822 [Needs submitter action] 

  5 pull requests merged:
  - Fix Respec link error
    https://github.com/w3c/webrtc-pc/pull/1878 
  - Add internal slots for descriptions.
    https://github.com/w3c/webrtc-pc/pull/1877 
  - receiver.getParameters clarification
    https://github.com/w3c/webrtc-pc/pull/1875 
  - Make RTCSctpTransport.maxChannels nullable & line breaks
    https://github.com/w3c/webrtc-pc/pull/1873 
  - Fire events in SLD(answer) in direction rejection edge-case.
    https://github.com/w3c/webrtc-pc/pull/1867 


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