Type name: application

Subtype name: v3c

Required parameters: sprop-v3c-parameter-set

Optional parameters: sprop-v3c-unit-header, sprop-v3c-unit-type, sprop-v3c-vps-id, sprop-v3c-atlas-id, sprop-v3c-attr-idx, sprop-v3c-attr-part-idx, sprop-v3c-map-idx, sprop-v3c-aux-video-flag, sprop-v3c-tile-id, sprop-v3c-tile-id-pres, sprop-v3c-atlas-data, sprop-v3c-common-atlas-data, sprop-v3c-sei, v3c-ptl-level-idc, v3c-ptl-tier-flag, v3c-ptl-codec-idc, v3c-ptl-toolset-idc, v3c-ptl-rec-idc and sprop-max-don-diff.

Encoding considerations: framed

Security considerations: Please see Section 11 of RFC-ietf-avtcore-rtp-v3c-17.

Interoperability considerations: N/A

Published specification: RFC-ietf-avtcore-rtp-v3c-17

Applications that use this media type: Any application that relies on V3C-based media services over RTP

Additional information: N/A

Person & email address to contact for further information: Lauri Ilola (lauri.ilola&nokia.com) or Lukasz Kondrad (lukasz.kondrad&nokia.com)

Intended usage: COMMON

Restrictions on usage: This media type depends on RTP framing and, hence, is only defined for transfer via RTP [RFC3550]. Transport within other framing protocols is not defined at this time.

Author: See Authors' Addresses section of this memo

Change controller: IETF avtcore&ietf.org