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

Improve BYE to CONNECTION_CLOSE mapping considerations #132

Merged
merged 1 commit into from
Oct 16, 2023
Merged

Improve BYE to CONNECTION_CLOSE mapping considerations #132

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
12 changes: 9 additions & 3 deletions draft-ietf-avtcore-rtp-over-quic.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1044,9 +1044,15 @@ frames as described in {{!I-D.draft-smith-quic-receive-ts}} or

### Mapping QUIC Connection Close to RTCP Goodbye Packets ("BYE") {#BYE-mapping}

*Goodbye* (`PT=203`, `Name=BYE`, {{!RFC3550}}) can be replaced by closing the
QUIC connection. However, while QUIC allows application layer error codes, they
do not carry string values.
RTP session participants can use *Goodbye* RTCP packets (`PT=203`, `Name=BYE`,
{{!RFC3550}}), to indicate that a source is no longer active. If the participant
is also going to close the QUIC connection, the *BYE* packet can be replaced by
a QUIC CONNECTION_CLOSE frame. In this case, the reason for leaving can be
transmitted in QUIC's CONNECTION_CLOSE *Reason Phrase*. However, if the
participant wishes to use this QUIC connection for any other multiplexed
traffic, the participant has to use the BYE packet because the QUIC
CONNECTION_CLOSE would close the entire QUIC connection for all other QUIC
streams and datagrams.

## Application Layer Repair and other Control Messages {#al-repair}

Expand Down