laurilo / draft-ilola-avtcore-rtp-v3c

Other
0 stars 2 forks source link

5.5.2. Single NAL unit packet - figure #13

Closed lkondrad closed 11 months ago

lkondrad commented 1 year ago

Is there possibility to have padding ? The size of NAL unit data is determined based on the RTP packet itself so I would assume that there is no option for padding

  0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |      RTP payload header       |      DONL (conditional)       |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
    |      v3c-tile-id (cond)       |                               |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+                               |
    |                                                               |
    |                        NAL unit data                          |
    |                                                               |
    |                               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                               :...OPTIONAL RTP padding        |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
laurilo commented 11 months ago

Should be possible to have padding the single nal unit packet too. When padding is present, the nal unit can be parsed from the payload based on the RTP payload header, which contains the NAL unit type. The data left after the NAL unit has been parsed is the padding.