Re: [webrtc-rtptransport] RtpSendStreamInit and RtpReceiveStreamInit are not defined in explainer-use-case-1.md (#35) from Tony Herre via GitHub on 2024-06-24 (public-webrtc-logs@w3.org from June 2024)

From: Tony Herre via GitHub <sysbot+gh@w3.org>
Date: Mon, 24 Jun 2024 14:44:35 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-2186753505-1719240273-sysbot+gh@w3.org>

Looks like just an oversight. Peter's rough doc had:
```
dictionary RtpSendStreamInit {
  DOMString mid;  // optional
  DOMString rid;  // optional
  unsigned long ssrc;  // optional; automatically assigned if unset
  unsigned long rtxSsrc;  // optional; automatically assigned if unset

  bool disableRtx = false;
  bool disableSenderReports = false;
}

dictionary RtpReceiveStreamInit {
  // MID and SSRC can't both be unset
  DOMString mid;  // optional
  DOMString rid;  // optional
  unsigned long ssrc;  // optional
  unsigned long rtxSsrc;  // optional

  bool disableNack = false;
  bool disableReceiverReports = false;
}
```

I'm thinking of adding them without the rtx/nack/reports control for now - adding those in with specific feature discussions eg #52 around nack.

-- 
GitHub Notification of comment by tonyherre
Please view or discuss this issue at https://github.com/w3c/webrtc-rtptransport/issues/35#issuecomment-2186753505 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 24 June 2024 14:44:36 UTC