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

Guidance on RPSI implementation #17

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Guidance on RPSI implementation #17

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
42f19c1
Guidance on RPSI implementation
aboba Sep 28, 2023
4620962
Update hevc-webrtc-04.nr
aboba Oct 2, 2023
f65e05c
Forbid use of RPSI as positive acknowledgement
aboba Oct 9, 2023
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
16 changes: 16 additions & 0 deletions hevc-webrtc-04.nr
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -149,6 +149,18 @@ not signaled as part of the SDP, H.265 implementations MAY send and
SHOULD support proper interpretation of Display Orientation SEI
messages.

[RFC7798] Section 8.3 specifies the use of the Reference Picture Selection
Indication (RPSI) in H.265. As noted in "Media Transport and Use of RTP in WebRTC"
[RFC8834] Section 5.1.4:

.in +0.3i
Receivers that detect that encoder-decoder synchronization has been lost SHOULD
generate an RPSI feedback message if the codec being used supports reference-picture
selection. An RTP packet-stream sender that receives such an RPSI message SHOULD
act on that messages to change the reference picture, if it is possible to do
so within the available bandwidth constraints and with the codec being used.
.in -0.3i

Unless otherwise signaled, WebRTC implementations that support H.265 MUST encode
and decode pixels with an implied 1:1 (square) aspect ratio.
.in -0.3i
Expand Down Expand Up @@ -202,6 +214,10 @@ RFC 7798, DOI 10.17487/RFC7798, March 2016,
Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words",
RFC 8174, DOI 10.17487/RFC8174, May 2017,
<https://www.rfc-editor.org/info/rfc8174>.
.IP [RFC8834]
Perkins, C., Westerlund, M. and J. Ott., "Media Transport and Use of
RTP in WebRTC", RFC 8834, DOI 10.17487/RFC8834, January 2021,
<https://www.rfc-editor.org/info/rfc8834>.
.NH 2
.R
Informative References
Expand Down