8.3 RTP matching rules and "packet_receiver" (bad word)

[ibc]

Section 8.3 mentions packet_receiver several times but, in fact, it means RTCRtpReceiver and I consider it confusing for the reader. IMHO it should use RTCRtpReceiver or RTP receiver rather than packet_receiver.

[aboba]

packet_receiver denotes an attribute whose value is the RTCRtpReceiver object to which the incoming RTP packet should be delivered. Since the attribute receiver is used earlier in Section 8.3 in a different context (relating to setting up the ssrc_table, muxId_table and pt_table), we didn't want to reuse that attribute name.

Would rtp_receiver work better?

[ibc]

Would "rtp_receiver" work better?

LGTM

Also, not sure now if the spec mentions "attribute" but if so I think that "key" would fit better (an object/map/hash has "key/value" pairs rather than "attribute/value").

[ibc]

Let me a question: this issue is fixed in master, should it remain open?

[aboba]

Once we have a PR in master we mark it as "PR exists". Next step is to close it if there is positive feedback on the PR (or at least no objections for a while).

[ibc]

The PR is merged, that's why I expect this issue to be closed now.