W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > October 2022

Re: [webrtc-pc] Clarification around msid generation (#2782)

From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
Date: Tue, 25 Oct 2022 22:18:08 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-1291201732-1666736287-sysbot+gh@w3.org>
I agree with the [discussion](https://bugs.chromium.org/p/chromium/issues/detail?id=1342010#c2) in the Chromium tracker that it looks like RFC 8829 wasn't updated when setStreams was added, as further evidenced by paragraphs like this one:
      -  For each MediaStream that was associated with the transceiver
         when it was created via addTrack or addTransceiver, an "a=msid"
         line, as specified in [RFC8830], Section 2, but omitting the
         "appdata" field.
...which doesn't account for: `pc.addTrack(track).setStreams(stream)`.

As [further mentioned](https://bugs.chromium.org/p/chromium/issues/detail?id=1342010#c10) in the Chromium tracker, since the introduction of `mid`, and with `appdata` [now omitted](https://www.ietf.org/rfcdiff?url2=draft-ietf-rtcweb-jsep-25.txt), msid is AFAIK relegated to surfacing stream associations remotely (from changes with `setStreams`), with the stable identifier instead being `mid`.

@docfaraday can we file an errata on the RFC?

GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2782#issuecomment-1291201732 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 25 October 2022 22:18:10 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:59 UTC