%% You should probably cite draft-ietf-avtcore-rtp-v3c instead of this I-D.
@techreport{ilola-avtcore-rtp-v3c-02,
    number =    {draft-ilola-avtcore-rtp-v3c-02},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ilola-avtcore-rtp-v3c/02/},
    author =    {Lauri Ilola and Lukasz Kondrad},
    title =     {{RTP Payload Format for Visual Volumetric Video-based Coding (V3C)}},
    pagetotal = 41,
    year =      2022,
    month =     jun,
    day =       27,
    abstract =  {This memo describes an RTP payload format for visual volumetric video-based coding (V3C) {[}ISO.IEC.23090-5{]}. A V3C bitstream is composed of V3C units that contain V3C video sub-bitstreams, V3C atlas sub-bitstreams, or a V3C parameter set. The RTP payload format for V3C video sub-bitstreams is defined by appropriate Internet Standards for the applicable video codec. The RTP payload format for V3C atlas sub-bitstreams is described by this memo. The RTP payload format allows for packetization of one or more V3C Network Abstraction Layer (NAL) units in a RTP packet payload as well as fragmentation of a V3C NAL unit into multiple RTP packets. The memo also describes the mechanisms for grouping RTP streams of V3C component sub-bitstreams, providing a complete solution for streaming V3C bitstream.},
}