Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Case 1: Clarify RTCP, remove custom NACK/RTX #28

Merged
merged 1 commit into from
May 20, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
17 changes: 1 addition & 16 deletions explainer-use-case-1.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,8 +15,7 @@ In this use case, packetization of encoded video or audio frames is handled by t

Custom packetization/depacketization enables applications to do things such as:
- Encode with a custom (WASM) codec, packetize and send
- Observe incoming NACKs and resend with custom RTX behavior
- Observe incoming packets and customize when NACKs are sent
- Observe incoming packets
- Receive packets using a custom jitter buffer implementation
- Use WebCodecs for encode or decode, implement packetization/depacketization, a custom jitter buffer, and custom FEC
- Obtain a bandwidth estimate from RtpTransport, do bitrate allocation, and set bitrates of RtpSenders
Expand Down Expand Up @@ -88,20 +87,6 @@ dictionary RtpHeaderExtensionInit {
required ArrayBuffer value;
}

interface RtcpPacket {
constructor(required RtcpPacketInit);
readonly attribute octet type;
readonly attribute octet subType;
readonly attribute ArrayBuffer value;
}

dictionary RtcpPacketInit {
// TODO: Should we force the type APP?
required octet type;
required octet subType; // AKA FMT
required ArrayBuffer value;
}

```
### RTCPeerConnection, RTCRtpSender, RTCRtpReceiver Extensions

Expand Down