15:00:52 <RRSAgent> RRSAgent has joined #webrtc
15:00:52 <RRSAgent> logging to http://www.w3.org/2017/09/13-webrtc-irc
15:01:00 <dom> Meeting: WebRTC Virtual Interim
15:01:05 <dom> Chair: stefanh, aboba
15:01:12 <dom> Agenda: https://www.w3.org/2011/04/webrtc/wiki/September_13_2017
15:02:45 <dom> Present+ Dominique_Hazael-Massieux, Stefan_Hakansson, Bernard_Aboba, Taylor_Brandsetter, Shijun_Sun, Patrick_Rockhill, Jianjun_Zhu, Lennart_Grahl, VIvien_Lacourba
15:02:58 <dom> Present+ Eric_Rescorla
15:03:42 <adambe> adambe has joined #webrtc
15:04:09 <vivien> vivien has changed the topic to: WebRTC Virtual Interim join us on WebEx https://www.w3.org/2011/04/webrtc/wiki/September_13_2017
15:04:20 <dom> Present+ Cullen_Jennings, Randell_Jesup
15:04:24 <jib> jib has joined #webrtc
15:04:32 <fluffy> fluffy has joined #webrtc
15:04:39 <dom> Present+ Adam_Bergkvist
15:04:54 <jesup> jesup has joined #webrtc
15:04:58 <vivien> [recording now in progress]
15:05:16 <dom> Present+ Jan-Ivar_Bruaroey
15:05:23 <dom> ScribeNick: adambe
15:05:58 <vivien> Topic: Issue 1128: Does msid still work?
15:06:35 <dom> -> https://github.com/w3c/webrtc-pc/issues/1128 Issue 1128
15:08:38 <dom> -> https://github.com/w3c/webrtc-pc/pull/1567 PR 1567 Adding `remoteTrackId` attribute to represent SDP-signaled track ID
15:09:17 <adambe> fluffy: Why doesn't the track id change?
15:09:36 <adambe> taylor: Other stuff rely on track id's being constant
15:10:12 <burn> Present+ Dan_Burnett
15:11:17 <adambe> taylor: Before, you got a new track (with a new id)
15:16:43 <adambe> jib: An other option would be to allow changing the track id in mediacap spec
15:17:18 <fluffy> Present+ Cullen_Jennings
15:22:44 <adambe> fluffy: I don't like adding something that you can't use in this case, and this case and this other case
15:28:34 <adambe> jib: There's also no guarantee that remote track ids are unique anyhow
15:29:50 <dom> Present+ Justin_Uberti, SHIM
15:32:50 <adambe> fluffy: Suggests to fix the issue on both sides. This solution only addresses the problem on one side
15:35:30 <adambe> Resolution: We revert the PR (1567)
15:35:58 <stefanh> Also, we close 1128 with a comment.
15:37:39 <adambe> taylor: Should we always generate track id so it doesn't work in some situations, but not in others
15:40:05 <vivien> Topic: Issue 1161/Issue 1181: What happens remotely when a track is “removed”?
15:40:05 <vivien> -> https://github.com/w3c/webrtc-pc/issues/1161 Issue 1161
15:40:05 <vivien> -> https://github.com/w3c/webrtc-pc/issues/1181 Issue 1181
15:40:06 <adambe> Topic: Issue 1161/Issue 1181: What happens remotely when a track is “removed”?
15:41:08 <adambe> jib: I think this is fine
15:42:02 <adambe> Resolution is to accept the current state after PR 1402
15:42:16 <adambe> and we close 1161 and 1181
15:42:18 <vivien> Topic: Issue 1207/PR 1592: Setting a remote description may cause discontinuity
15:42:19 <vivien> -> https://github.com/w3c/webrtc-pc/issues/1207 Issue 1207
15:42:19 <vivien> -> https://github.com/w3c/webrtc-pc/pull/1592 PR 1592
15:50:44 <RRSAgent> I have made the request to generate http://www.w3.org/2017/09/13-webrtc-minutes.html vivien
15:51:21 <adambe> Resolution is to accept the changes proposed by PR 1592
15:51:48 <vivien> Topic: Issue 1178: Need to describe when ICE and DTLS transport objects are created/changed
15:51:48 <vivien> -> https://github.com/w3c/webrtc-pc/issues/1178 Issue 1178
15:52:18 <vivien> present+ Peter_Thatcher
15:54:53 <adambe> Resolution is to go for the "one object" approach proposed by Taylor
15:55:07 <vivien> Topic: Issue 1406: When ICE restart results in connection to a new endpoint
15:55:07 <vivien> -> https://github.com/w3c/webrtc-pc/issues/1406 Issue 1406
15:57:48 <adambe> Resolution is to reuse the same RTCDtlsTransport object when a new DTLS association is started as proposed by Taylor
15:58:07 <vivien> Topic: Issue 1563: Ambiguities with BUNDLE and ICE
15:58:07 <vivien> -> https://github.com/w3c/webrtc-pc/issues/1563 Issue 1563
16:09:13 <adambe> Resolution is that we are waiting for the mmuisc feedback
16:09:35 <stefanh> Issue 1520/1560
16:09:35 <vivien> Topic: Issue 1520/PR 1560: setParameters input validation
16:09:35 <vivien> -> https://github.com/w3c/webrtc-pc/issues/1520 Issue 1520
16:09:35 <vivien> -> https://github.com/w3c/webrtc-pc/pull/1560 PR 1560
16:13:15 <adambe> Resolution is that there are no objections to the model proposed in PR 1520
16:13:31 <dom> s/PR 1520/PR 1560/
16:13:43 <stefanh> my audio has dropped
16:13:47 <vivien> Topic: Issue 1564/PR 1577: Deciding on resolutions with scaleResolutionDownBy (Pehrsons)
16:13:47 <vivien> -> https://github.com/w3c/webrtc-pc/issues/1564 Issue 1564
16:13:47 <vivien> -> https://github.com/w3c/webrtc-pc/pull/1577 PR 1577
16:13:47 <stefanh> will re-dial
16:19:56 <adambe> Resolution is to floor instead ceil and document what happens if the result is zero (PR 1577 is not accepted)
16:21:11 <adambe> Topic: Issue 1564/PR 1577:  Deciding on resolutions with scaleResolutionDownBy
16:26:25 <adambe> Resolution is that we allows aspect ratios to change due to integer width and height rounding
16:27:09 <vivien> s/Topic: Issue 1564/PR 1577:  Deciding on resolutions with scaleResolutionDownBy//
16:27:23 <vivien> Topic: Issue 1259/PR 1553: What keygenAlgorithm values are supported?
16:27:23 <vivien> -> https://github.com/w3c/webrtc-pc/issues/1259 Issue 1259
16:27:23 <vivien> -> https://github.com/w3c/webrtc-pc/pull/1553 PR 1553
16:30:22 <dom> RRSAgent, draft minutes
16:30:22 <RRSAgent> I have made the request to generate http://www.w3.org/2017/09/13-webrtc-minutes.html dom
16:30:59 <adambe> Resolution is that no one objects to the proposed PR but it needs review
16:31:15 <dom> RRSAgent, draft minutes
16:31:15 <RRSAgent> I have made the request to generate http://www.w3.org/2017/09/13-webrtc-minutes.html dom
16:37:25 <vivien> RRSAgent, bye
16:37:25 <RRSAgent> I see no action items