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

Clarify usage of "RTP" and "RTCP" in the document #190

Merged
merged 3 commits into from Apr 9, 2024

Conversation

SpencerDawkins
Copy link
Collaborator

closes #188

This specification describes an application usage of QUIC ({{?RFC9308}}).
As a baseline, the specification does not expect more than a standard QUIC implementation
This document describes an application usage of QUIC ({{?RFC9308}}).
As a baseline, the Document does not expect more than a standard QUIC implementation
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
As a baseline, the Document does not expect more than a standard QUIC implementation
As a baseline, the document does not expect more than a standard QUIC implementation

as defined in {{!RFC8999}}, {{!RFC9000}}, {{!RFC9001}}, and {{!RFC9002}},
providing a secure end-to-end transport that is also expected to work well through NATs and firewalls.
Beyond this baseline, real-time applications can benefit from QUIC extensions such as unreliable DATAGRAMs
{{!RFC9221}}, which provides additional desirable properties for
real-time traffic (e.g., no unnecessary retransmissions, avoiding head-of-line
blocking).

## What's in Scope for this Specification {#in-scope}
## What's in Scope for this document {#in-scope}
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
## What's in Scope for this document {#in-scope}
## What's in Scope for this Document {#in-scope}

@@ -1,5 +1,5 @@
---
title: "RTP over QUIC (RoQ)"
title: "RTP and RTCP over QUIC (RoQ)"
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree with the other changes, but I don't think it is necessary to change the title. RTCP is part of RTP in RFC 3550, which only has RTP in its title.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree with the other changes, but I don't think it is necessary to change the title. RTCP is part of RTP in RFC 3550, which only has RTP in its title.

@mengelbart - thank you for pushing back on this change. My intention going into this PR was to make it obvious that what we said about encapsulation applied to both RTP Data Transfer Protocol and RTP Control Protocol, but after I added the Note to the Reader about this, I ought to have reversed the proposed change to the title.

And I am slightly cursing under my breath that "RTCP" caught on, but "RTDTP" never did! 😵‍💫

@SpencerDawkins
Copy link
Collaborator Author

I've applied @mengelbart's review comments, and am merging now.

@SpencerDawkins SpencerDawkins merged commit f5fb597 into main Apr 9, 2024
2 checks passed
@SpencerDawkins SpencerDawkins deleted the clarify-rtp/rtcp branch April 9, 2024 18:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Clarify RTP vs RTCP vs RTP/RTCP handling early in the document
2 participants