A new Request for Comments is now available in online RFC libraries.

        RFC 10034

        Title:      RTP Payload Format for Visual Volumetric Video-Based Coding 
(V3C)
        Author:     L. Ilola,
                    L. Kondrad
        Status:     Proposed Standard
        Stream:     IETF
        Date:       August 2026
        Mailbox:    [email protected],
                    [email protected]
        Pages:      43


        I-D Tag:    draft-ietf-avtcore-rtp-v3c-17

        URL:        https://www.rfc-editor.org/info/rfc10034

        DOI:        10.17487/RFC10034

A visual volumetric video-based coding (V3C) ISO/IEC 23090-5 bitstream is 
composed of V3C units that contain V3C atlas sub-bitstreams, V3C video 
sub-bitstreams, and a V3C parameter set. This document describes an RTP payload 
format for V3C atlas sub-bitstreams. The RTP payload format for V3C video 
sub-bitstreams is defined by relevant IETF RFCs for the applicable video codec. 
The V3C RTP payload format allows for the packetization of one or more V3C 
atlas Network Abstraction Layer (NAL) units in an RTP packet payload as well as 
the fragmentation of a V3C atlas NAL unit into multiple RTP packets. The 
document also describes the mechanisms for grouping RTP streams of V3C 
component sub-bitstreams, providing a complete solution for streaming 
V3C-encoded content.

This document is a product of the Audio/Video Transport Core Maintenance 
Working Group of the IETF.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and
suggestions for improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search/
For downloading RFCs, see https://www.rfc-editor.org/series/rfc-download/

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team

_______________________________________________
IETF-Announce mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to