Issue 598704  is about removing MediaStreamTrack#remote, which goes together with getLocalStreams and getRemoteStreams. I think those three should be considered together.

Would it be trivial to continue supporting RTCPeerConnection#getLocalStreams/getRemoteStreams and MediaStreamTrack#remote? If so, I would first try to revive them in the spec.

Oh, wait, MediaStreamTrack#remote is in the process of being removed. I'll comment on the intent:
https://groups.google.com/a/chromium.org/d/msg/blink-dev/d20ECb2sWzI/C8DhXa1aAwAJ

Use counters:
https://www.chromestatus.com/metrics/feature/timeline/popularity/1643
https://www.chromestatus.com/metrics/feature/timeline/popularity/1644
https://www.chromestatus.com/metrics/feature/timeline/popularity/1645

getStreamById seems like it'd be a rather different removal, so I've split it into  issue 698163 .

peary2@, can you comment on the connection to MediaStreamTrack#remote?

Can this be considered independently of issue 697059, or should this group of APIs be standardized/removed together? (getStreamById still separate because it's not as widely implemented.)

I've updated the description of issue 697059 to also test getLocalStreams and getRemoteStreams, please merge into that if these are coupled.

Standardization efforts met resistance at https://github.com/w3c/webrtc-pc/issues/1125. They are not going away any time soon, but should be marked as deprecated when we have Unified Plan ( https://crbug.com/799030 ) and RTCRtpTransceivers ( https://crbug.com/777617 ).

Without UP+transceivers, getLocalStreams() and getRemoteStreams() are still necessary to have. While they were successfully implemented on top of track-based APIs ( https://crbug.com/803021 ), this required some magic that JavaScript does not have access to without UP+transceivers, so we can't expect the applications to stop relying on them.

When the referenced bugs are fixed we can deprecate this.

The decision is to deprecate and remove them, but they're too heavily used. This bug is non-actionable for the foreseeable future.