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.

Sign up for GitHub

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

Jump to bottom

Remove UC1's custom seq num & document this in handled by the UA #22

Merged
merged 1 commit into from
Apr 16, 2024
Merged

Remove UC1's custom seq num & document this in handled by the UA #22

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions explainer-use-case-1.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,6 +35,10 @@ Enable applications to do custom packetization/depacketization by enabling them
- Know what bitrate can be sent in addition to what the browser has already allocated to send.
- Cause the browser to allocate less to send, leaving more bitrate available to the application to send.

Complexities of sending and receiving RTP other than these requirements are still handled by the User Agent - in
particular Pacing of sent packets on the wire, inclusion of padding to support bandwidth probing, and RTP Sequence
Numbering taking into account such padding.

## API Outline

### RtpPacket, RtcpPacket
Expand Down Expand Up @@ -72,8 +76,6 @@ interface RtpHeaderExtension {
dictionary RtpPacketInit {
bool marker = false;
required octet payloadType;
// When sending, can be filled in automatically
unsigned short sequenceNumber;
required unsigned long timestamp;
sequence<unsigned long> csrcs = [];
// Cannot be MID, RID, or congestion control sequence number
Expand Down
Loading