rfc9626v3.txt | rfc9626.txt | |||
---|---|---|---|---|
Internet Engineering Task Force (IETF) M. Zanaty | Internet Engineering Task Force (IETF) M. Zanaty | |||
Request for Comments: 9626 E. Berger | Request for Comments: 9626 E. Berger | |||
Category: Experimental S. Nandakumar | Category: Experimental S. Nandakumar | |||
ISSN: 2070-1721 Cisco Systems | ISSN: 2070-1721 Cisco Systems | |||
February 2025 | March 2025 | |||
Video Frame Marking RTP Header Extension | Video Frame Marking RTP Header Extension | |||
Abstract | Abstract | |||
This document describes a Video Frame Marking RTP header extension | This document describes a Video Frame Marking RTP header extension | |||
used to convey information about video frames that is critical for | used to convey information about video frames that is critical for | |||
error recovery and packet forwarding in RTP middleboxes or network | error recovery and packet forwarding in RTP middleboxes or network | |||
nodes. It is most useful when media is encrypted and essential when | nodes. It is most useful when media is encrypted and essential when | |||
the middlebox or node has no access to the media decryption keys. It | the middlebox or node has no access to the media decryption keys. It | |||
skipping to change at line 643 ¶ | skipping to change at line 643 ¶ | |||
frame size alone can leak this in the absence of any unencrypted | frame size alone can leak this in the absence of any unencrypted | |||
metadata. However, unencrypted metadata provides a reliable signal | metadata. However, unencrypted metadata provides a reliable signal | |||
rather than a statistical probability; so endpoints should take that | rather than a statistical probability; so endpoints should take that | |||
into consideration to balance the privacy leakage risk against the | into consideration to balance the privacy leakage risk against the | |||
potential benefit of optimized media delivery when deciding whether | potential benefit of optimized media delivery when deciding whether | |||
to negotiate and encrypt this header extension. | to negotiate and encrypt this header extension. | |||
5. IANA Considerations | 5. IANA Considerations | |||
This document defines a new extension URI listed in the "RTP Compact | This document defines a new extension URI listed in the "RTP Compact | |||
Header Extensions" subregistry of the "Real-Time Transport Protocol | Header Extensions" registry of the "Real-Time Transport Protocol | |||
(RTP) Parameters" registry, according to the following data: | (RTP) Parameters" registry group, according to the following data: | |||
Extension URI: urn:ietf:params:rtp-hdrext:framemarking | Extension URI: urn:ietf:params:rtp-hdrext:framemarking | |||
Description: Frame marking information for video streams | Description: Frame marking information for video streams | |||
Contact: mzanaty@cisco.com | Contact: mzanaty@cisco.com | |||
Reference: RFC 9626 | Reference: RFC 9626 | |||
6. References | 6. References | |||
skipping to change at line 737 ¶ | skipping to change at line 737 ¶ | |||
Conferencing (PERC)", RFC 8871, DOI 10.17487/RFC8871, | Conferencing (PERC)", RFC 8871, DOI 10.17487/RFC8871, | |||
January 2021, <https://www.rfc-editor.org/info/rfc8871>. | January 2021, <https://www.rfc-editor.org/info/rfc8871>. | |||
[RFC9335] Uberti, J., Jennings, C., and S. Murillo, "Completely | [RFC9335] Uberti, J., Jennings, C., and S. Murillo, "Completely | |||
Encrypting RTP Header Extensions and Contributing | Encrypting RTP Header Extensions and Contributing | |||
Sources", RFC 9335, DOI 10.17487/RFC9335, January 2023, | Sources", RFC 9335, DOI 10.17487/RFC9335, January 2023, | |||
<https://www.rfc-editor.org/info/rfc9335>. | <https://www.rfc-editor.org/info/rfc9335>. | |||
[RFC9627] Lennox, J., Hong, D., Uberti, J., Holmer, S., and M. | [RFC9627] Lennox, J., Hong, D., Uberti, J., Holmer, S., and M. | |||
Flodman, "The Layer Refresh Request (LRR) RTCP Feedback | Flodman, "The Layer Refresh Request (LRR) RTCP Feedback | |||
Message", RFC 9627, DOI 10.17487/RFC9627, February 2025, | Message", RFC 9627, DOI 10.17487/RFC9627, March 2025, | |||
<https://www.rfc-editor.org/info/rfc9627>. | <https://www.rfc-editor.org/info/rfc9627>. | |||
[RFC9628] Uberti, J., Holmer, S., Flodman, M., Hong, D., and J. | [RFC9628] Uberti, J., Holmer, S., Flodman, M., Hong, D., and J. | |||
Lennox, "RTP Payload Format for VP9 Video", RFC 9628, | Lennox, "RTP Payload Format for VP9 Video", RFC 9628, | |||
DOI 10.17487/RFC9628, February 2025, | DOI 10.17487/RFC9628, March 2025, | |||
<https://www.rfc-editor.org/info/rfc9628>. | <https://www.rfc-editor.org/info/rfc9628>. | |||
Acknowledgements | Acknowledgements | |||
Many thanks to Bernard Aboba, Jonathan Lennox, Stephan Wenger, Dale | Many thanks to Bernard Aboba, Jonathan Lennox, Stephan Wenger, Dale | |||
Worley, and Magnus Westerlund for their inputs. | Worley, and Magnus Westerlund for their inputs. | |||
Authors' Addresses | Authors' Addresses | |||
Mo Zanaty | Mo Zanaty | |||
End of changes. 4 change blocks. | ||||
5 lines changed or deleted | 5 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. |