rfc9134.original   rfc9134.txt 
avtcore S. Lugan Internet Engineering Task Force (IETF) T. Bruylants
Internet-Draft intoPIX Request for Comments: 9134 intoPIX
Intended status: Standards Track A. Descampe Category: Standards Track A. Descampe
Expires: January 29, 2022 UCL ISSN: 2070-1721 UCLouvain
C. Damman C. Damman
intoPIX intoPIX
T. Richter T. Richter
IIS Fraunhofer IIS
T. Bruylants October 2021
intoPIX
July 28, 2021
RTP Payload Format for ISO/IEC 21122 (JPEG XS) RTP Payload Format for ISO/IEC 21122 (JPEG XS)
draft-ietf-payload-rtp-jpegxs-18
Abstract Abstract
This document specifies a Real-Time Transport Protocol (RTP) payload This document specifies a Real-Time Transport Protocol (RTP) payload
format to be used for transporting JPEG XS (ISO/IEC 21122) encoded format to be used for transporting video encoded with JPEG XS (ISO/
video. JPEG XS is a low-latency, lightweight image coding system. IEC 21122). JPEG XS is a low-latency, lightweight image coding
Compared to an uncompressed video use case, it allows higher system. Compared to an uncompressed video use case, it allows higher
resolutions and video frame rates, while offering visually lossless resolutions and video frame rates while offering visually lossless
quality, reduced power consumption, and encoding-decoding latency quality, reduced power consumption, and encoding-decoding latency
confined to a fraction of a video frame. confined to a fraction of a video frame.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This is an Internet Standards Track document.
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
This Internet-Draft will expire on January 29, 2022. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc9134.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2021 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction
2. Conventions, Definitions, and Abbreviations . . . . . . . . . 3 2. Conventions, Definitions, and Abbreviations
3. Media Format Description . . . . . . . . . . . . . . . . . . 5 3. Media Format Description
3.1. Image Data Structures . . . . . . . . . . . . . . . . . . 5 3.1. Image Data Structures
3.2. Codestream . . . . . . . . . . . . . . . . . . . . . . . 5 3.2. Codestream
3.3. Video support box and color specification box . . . . . . 6 3.3. Video Support Box and Color Specification Box
3.4. JPEG XS Frame . . . . . . . . . . . . . . . . . . . . . . 6 3.4. JPEG XS Frame
4. RTP Payload Format . . . . . . . . . . . . . . . . . . . . . 7 4. RTP Payload Format
4.1. RTP packetization . . . . . . . . . . . . . . . . . . . . 7 4.1. RTP Packetization
4.2. RTP Header Usage . . . . . . . . . . . . . . . . . . . . 10 4.2. RTP Header Usage
4.3. Payload Header Usage . . . . . . . . . . . . . . . . . . 11 4.3. Payload Header Usage
4.4. Payload Data . . . . . . . . . . . . . . . . . . . . . . 13 4.4. Payload Data
5. Traffic Shaping and Delivery Timing . . . . . . . . . . . . . 18 5. Traffic Shaping and Delivery Timing
6. Congestion Control Considerations . . . . . . . . . . . . . . 19 6. Congestion Control Considerations
7. Payload Format Parameters . . . . . . . . . . . . . . . . . . 19 7. Payload Format Parameters
7.1. Media Type Registration . . . . . . . . . . . . . . . . . 19 7.1. Media Type Registration
8. SDP Parameters . . . . . . . . . . . . . . . . . . . . . . . 24 8. SDP Parameters
8.1. Mapping of Payload Type Parameters to SDP . . . . . . . . 24 8.1. Mapping of Payload Type Parameters to SDP
8.2. Usage with SDP Offer/Answer Model . . . . . . . . . . . . 25 8.2. Usage with SDP Offer/Answer Model
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26 9. IANA Considerations
10. Security Considerations . . . . . . . . . . . . . . . . . . . 26 10. Security Considerations
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 27 11. References
12. RFC Editor Considerations . . . . . . . . . . . . . . . . . . 27 11.1. Normative References
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 27 11.2. Informative References
13.1. Normative References . . . . . . . . . . . . . . . . . . 27 Acknowledgments
13.2. Informative References . . . . . . . . . . . . . . . . . 29 Authors' Addresses
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 30
1. Introduction 1. Introduction
This document specifies a payload format for packetization of JPEG XS This document specifies a payload format for packetization of video
[ISO21122-1] encoded video signals into the Real-time Transport signals encoded with JPEG XS [ISO21122-1] into the Real-time
Protocol (RTP) [RFC3550]. Transport Protocol (RTP) [RFC3550].
The JPEG XS coding system offers compression and recompression of The JPEG XS coding system offers compression and recompression of
image sequences with very moderate computational resources while image sequences with very moderate computational resources while
remaining robust under multiple compression and decompression cycles remaining robust under multiple compression and decompression cycles
and mixing of content sources, e.g. embedding of subtitles, overlays as well as mixing of content sources, e.g., embedding of subtitles,
or logos. Typical target compression ratios ensuring visually overlays, or logos. Typical target compression ratios ensuring
lossless quality are in the range of 2:1 to 10:1, depending on the visually lossless quality are in the range of 2:1 to 10:1 depending
nature of the source material. The latency that is introduced by the on the nature of the source material. The latency that is introduced
encoding-decoding process can be confined to a fraction of a video by the encoding-decoding process can be confined to a fraction of a
frame, typically between a small number of lines down to below a video frame, typically between a small number of lines down to below
single line. a single line.
2. Conventions, Definitions, and Abbreviations 2. Conventions, Definitions, and Abbreviations
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in
14 [RFC2119] [RFC8174] when, and only when, they appear in all BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
Application Data Unit (ADU) Application Data Unit (ADU):
The unit of source data provided as payload to the transport The unit of source data provided as payload to the transport
layer, and corresponding, in this RTP payload definition, to a layer. In this RTP payload definition, it corresponds to a single
single JPEG XS video frame. JPEG XS video frame.
Color specification box (CS box) Color Specification (CS) box:
An ISO color specification box defined in JPEG XS Part 3 An ISO color specification box defined in [ISO21122-3] (JPEG XS
[ISO21122-3] that includes color related metadata required to Part 3) that includes color-related metadata required to correctly
correctly display JPEG XS video frames, such as color primaries, display JPEG XS video frames, such as color primaries, transfer
transfer characteristics and matrix coefficients. characteristics, and matrix coefficients.
EOC marker End of Codestream (EOC) marker:
A marker that consists of the two bytes 0xff11 indicating the end A marker that consists of the two bytes 0xff11 indicating the end
of a JPEG XS codestream. of a JPEG XS codestream.
JPEG XS codestream JPEG XS codestream:
A sequence of bytes representing a compressed image formatted A sequence of bytes representing a compressed image formatted
according to JPEG XS Part 1 [ISO21122-1]. according to [ISO21122-1] (JPEG XS Part 1).
JPEG XS codestream header JPEG XS codestream header:
A sequence of bytes, starting with a SOC marker, at the beginning A sequence of bytes, starting with an SOC marker, at the beginning
of each JPEG XS codestream encoded in multiple markers and marker of each JPEG XS codestream encoded in multiple markers and marker
segments that does not carry entropy coded data, but metadata such segments that does not carry entropy coded data, but metadata such
as the video frame dimension and component precision. as the video frame dimension and component precision.
JPEG XS frame JPEG XS frame:
In the case of progressive video, a single JPEG XS picture In the case of progressive video, a single JPEG XS picture
segment. In the case of interlaced video, the concatenation of segment. In the case of interlaced video, the concatenation of
two JPEG XS picture segments. two JPEG XS picture segments.
JPEG XS header segment JPEG XS header segment:
The concatenation of a video support box [ISO21122-3], a color The concatenation of a video support box [ISO21122-3], a color
specification box [ISO21122-3], and a JPEG XS codestream header. specification box [ISO21122-3], and a JPEG XS codestream header.
JPEG XS picture segment JPEG XS picture segment:
The concatenation of a video support box [ISO21122-3], a color The concatenation of a video support box [ISO21122-3], a color
specification box [ISO21122-3], and a JPEG XS codestream. specification box [ISO21122-3], and a JPEG XS codestream.
JPEG XS stream JPEG XS stream:
A sequence of JPEG XS frames. A sequence of JPEG XS frames.
Marker Marker:
A two-byte functional sequence that is part of a JPEG XS A two-byte functional sequence that is part of a JPEG XS
codestream starting with a 0xff byte and a subsequent byte codestream starting with a 0xff byte and a subsequent byte
defining its function. defining its function.
Marker segment Marker segment:
A marker along with a 16-bit marker size and payload data A marker along with a 16-bit marker size and payload data
following the size. following the size.
Packetization unit Packetization unit:
A portion of an Application Data Unit whose boundaries coincide A portion of an ADU whose boundaries coincide with boundaries of
with boundaries of RTP packet payloads (excluding payload header), RTP packet payloads (excluding payload header), i.e., the first
i.e. the first (resp. last) byte of a packetization unit is the (or respectively, last) byte of a packetization unit is the first
first (resp. last) byte of an RTP packet payload (excluding its (or respectively, last) byte of an RTP packet payload (excluding
payload header). its payload header).
SLH marker SLH (SLice Header) marker:
A marker that represents a slice header, as defined in A marker that represents a slice header, as defined in
[ISO21122-1]. [ISO21122-1].
Slice Slice:
The smallest independently decodable unit of a JPEG XS codestream, The smallest independently decodable unit of a JPEG XS codestream,
bearing in mind that it decodes to wavelet coefficients which bearing in mind that it decodes to wavelet coefficients, which
still require inverse wavelet filtering to give an image. still require inverse wavelet filtering to give an image.
SOC marker Start of a Codestream (SOC) marker:
A marker that consists of the two bytes 0xff10 indicating the A marker that consists of the two bytes 0xff10 indicating the
start of a JPEG XS codestream. The SOC marker is considered an start of a JPEG XS codestream. The SOC marker is considered an
integral part of the JPEG XS codestream header. integral part of the JPEG XS codestream header.
Video support box (VS box) Video Support (VS) box:
An ISO video support box, as defined in [ISO21122-3], that An ISO video support box, as defined in [ISO21122-3], that
includes metadata required to play back a JPEG XS stream, such as includes metadata required to play back a JPEG XS stream; such
its maximum bitrate, its subsampling structure, its buffer model metadata could include its maximum bit rate, its subsampling
and its frame rate. structure, its buffer model, and its frame rate.
3. Media Format Description 3. Media Format Description
This section explains the terminology and concepts used in this memo This section explains the terminology and concepts used in this memo
that are specific to JPEG XS as specified in [ISO21122-1], specific to JPEG XS as specified in [ISO21122-1], [ISO21122-2], and
[ISO21122-2], and [ISO21122-3]. [ISO21122-3].
3.1. Image Data Structures 3.1. Image Data Structures
JPEG XS is a low-latency lightweight image coding system for coding JPEG XS is a low-latency, lightweight image coding system for coding
continuous-tone grayscale or continuous-tone color digital images. continuous-tone grayscale or continuous-tone color digital images.
This coding system provides an efficient representation of image This coding system provides an efficient representation of image
signals through the mathematical tool of wavelet analysis. The signals through the mathematical tool of wavelet analysis. The
wavelet filter process separates each component into multiple bands, wavelet filter process separates each component into multiple bands,
where each band consists of multiple coefficients describing the where each band consists of multiple coefficients describing the
image signal of a given component within a frequency domain specific image signal of a given component within a frequency domain specific
to the wavelet filter type, i.e. the particular filter corresponding to the wavelet filter type, i.e., the particular filter corresponding
to the band. to the band.
Wavelet coefficients are grouped into precincts, where each precinct Wavelet coefficients are grouped into precincts, where each precinct
includes all coefficients over all bands that contribute to a spatial includes all coefficients over all bands that contribute to a spatial
region of the image. region of the image.
One or multiple precincts are furthermore combined into slices One or multiple precincts are furthermore combined into slices
consisting of an integer number of precincts. Precincts do not cross consisting of an integer number of precincts. Precincts do not cross
slice boundaries, and wavelet coefficients in precincts that are part slice boundaries, and wavelet coefficients in precincts that are part
of different slices can be decoded independently of each other. of different slices can be decoded independently of each other.
Note, however, that the wavelet transformation runs across slice However, note that the wavelet transformation runs across slice
boundaries. A slice always extends over the full width of the image, boundaries. A slice always extends over the full width of the image
but may only cover parts of its height. but may only cover parts of its height.
3.2. Codestream 3.2. Codestream
A JPEG XS codestream is formed by (in the given order): A JPEG XS codestream is formed by (in the given order):
o a JPEG XS codestream header, which starts with an SOC marker, * a JPEG XS codestream header, which starts with a Start of
Codestream (SOC) marker,
o one or more slices, * one or more slices,
o an EOC marker to signal the end of the codestream. * an EOC marker to signal the end of the codestream.
The JPEG XS codestream format, including the definition of all The JPEG XS codestream format, including the definition of all
markers, is further defined in [ISO21122-1]. It represents sample markers, is further defined in [ISO21122-1]. It represents sample
values of a single image, without any interpretation relative to a values of a single image, without any interpretation relative to a
color space. color space.
3.3. Video support box and color specification box 3.3. Video Support Box and Color Specification Box
While the information defined in the codestream is sufficient to While the information defined in the codestream is sufficient to
reconstruct the sample values of one image, the interpretation of the reconstruct the sample values of one image, the interpretation of the
samples remains undefined by the codestream itself. This samples remains undefined by the codestream itself. This
interpretation is given by the video support box and the color interpretation is given by the video support box and the color
specification box which contain significant information to correctly specification box, which contain significant information to correctly
play the JPEG XS stream. The layout and syntax of these boxes, play the JPEG XS stream. The layout and syntax of these boxes,
together with their content, are defined in [ISO21122-3]. together with their content, are defined in [ISO21122-3].
The video support box provides information on the maximum bitrate, The video support box provides information on the maximum bit rate,
the frame rate, the interlaced mode (progressive or interlaced), the the frame rate, the interlaced mode (progressive or interlaced), the
subsampling image format, the informative timecode of the current subsampling image format, the informative timecode of the current
JPEG XS frame, the profile, level/sublevel used, and optionally on JPEG XS frame, the profile, the level/sublevel used, and optionally
the buffer model and the mastering display metadata. the buffer model and the mastering display metadata.
Note that the profile and level/sublevel, specified by respectively Note that the profile and level/sublevel, specified respectively by
the Ppih and Plev fields [ISO21122-2], specify limits on the the Ppih and Plev fields [ISO21122-2], specify limits on the
capabilities needed to decode the codestream and handle the output. capabilities needed to decode the codestream and handle the output.
Profiles represent a limit on the required algorithmic features and Profiles represent a limit on the required algorithmic features and
parameter ranges used in the codestream. The combination of level parameter ranges used in the codestream. The combination of level
and sublevel defines a lower bound on the required throughput for a and sublevel defines a lower bound on the required throughput for a
decoder in respectively the image (or decoded) domain and the decoder in the image (or decoded) domain and the codestream (or
codestream (or coded) domain. The actual defined profiles and coded) domain, respectively. The actual defined profiles and levels/
levels/sublevels, along with the associated values for the Ppih and sublevels, along with the associated values for the Ppih and Plev
Plev fields, are defined in [ISO21122-2]. fields, are defined in [ISO21122-2].
The color specification box indicates the color primaries, transfer The color specification box indicates the color primaries, transfer
characteristics, matrix coefficients and video full range flag needed characteristics, matrix coefficients, and video full range flag
to specify the color space of the video stream. needed to specify the color space of the video stream.
3.4. JPEG XS Frame 3.4. JPEG XS Frame
The concatenation of a video support box, a color specification box, The concatenation of a video support box, a color specification box,
and a JPEG XS codestream forms a JPEG XS picture segment. and a JPEG XS codestream forms a JPEG XS picture segment.
In the case of a progressive video stream, each JPEG XS frame In the case of a progressive video stream, each JPEG XS frame
consists of one single JPEG XS picture segment. consists of one single JPEG XS picture segment.
In the case of an interlaced video stream, each JPEG XS frame is made In the case of an interlaced video stream, each JPEG XS frame is made
of two concatenated JPEG XS picture segments. The codestream of each of two concatenated JPEG XS picture segments. The codestream of each
picture segment corresponds exclusively to one of the two fields of picture segment corresponds exclusively to one of the two fields of
the interlaced frame. Both picture segments SHALL contain identical the interlaced frame. Both picture segments SHALL contain identical
boxes (i.e. concatenation of the video support box and the color boxes (i.e., the byte sequence that contains the concatenation of the
specification box is byte exact the same for both picture segments of video support box and the color specification box is exactly the same
the frame). in both picture segments of the frame).
Note that the interlaced mode, as signaled by the frat field Note that the interlaced mode, as signaled by the frat field
[ISO21122-3] in the video support box, indicates either progressive, [ISO21122-3] in the video support box, indicates either progressive
interlaced top-field first, or interlaced bottom-field first mode. interlaced top-field-first or interlaced bottom-field-first mode.
Thus, in the case of interlaced content, its value SHALL also be Thus, in the case of interlaced content, its value SHALL also be
identical in both picture segments. identical in both picture segments.
4. RTP Payload Format 4. RTP Payload Format
This section specifies the payload format for JPEG XS streams over This section specifies the payload format for JPEG XS streams over
the Real-time Transport Protocol (RTP) [RFC3550]. the Real-time Transport Protocol (RTP) [RFC3550].
In order to be transported over RTP, each JPEG XS stream is In order to be transported over RTP, each JPEG XS stream is
transported in a distinct RTP stream, identified by a distinct transported in a distinct RTP stream, identified by a distinct
Synchronization source (SSRC) [RFC3550]. synchronization source (SSRC) [RFC3550].
A JPEG XS stream is divided into Application Data Units (ADUs), each A JPEG XS stream is divided into Application Data Units (ADUs), each
ADU corresponding to a single JPEG XS frame. ADU corresponding to a single JPEG XS frame.
4.1. RTP packetization 4.1. RTP Packetization
An ADU is made of several packetization units. If a packetization An ADU is made of several packetization units. If a packetization
unit is bigger than the maximum size of an RTP packet payload, the unit is bigger than the maximum size of an RTP packet payload, the
unit is split into multiple RTP packet payloads, as illustrated in unit is split into multiple RTP packet payloads, as illustrated in
Figure 1. As seen there, each packet SHALL contain (part of) one and Figure 1. As seen there, each packet SHALL contain (part of) one,
only one packetization unit. A packetization unit may extend over and only one, packetization unit. A packetization unit may extend
multiple packets. The payload of every packet SHALL have the same over multiple packets. The payload of every packet SHALL have the
size (based e.g. on the Maximum Transfer Unit of the network), except same size (based, e.g., on the Maximum Transfer Unit of the network)
(possibly) the last packet of a packetization unit. The boundaries with the possible exception of the last packet of a packetization
of a packetization unit SHALL coincide with the boundaries of the unit. The boundaries of a packetization unit SHALL coincide with the
payload of a packet (excluding the payload header), i.e. the first boundaries of the payload of a packet (excluding the payload header),
(resp. last) byte of the packetization unit SHALL be the first (resp. i.e., the first (or, respectively, last) byte of the packetization
last) byte of the payload (excluding its header). unit SHALL be the first (or, respectively, last) byte of the payload
(excluding its header).
RTP +-----+------------------------+ RTP +-----+------------------------+
Packet #1 | Hdr | Packetization unit #1 | Packet #1 | Hdr | Packetization unit #1 |
+-----+------------------------+ +-----+------------------------+
RTP +-----+--------------------------------------+ RTP +-----+--------------------------------------+
Packet #2 | Hdr | Packetization unit #2 | Packet #2 | Hdr | Packetization unit #2 |
+-----+--------------------------------------+ +-----+--------------------------------------+
RTP +-----+--------------------------------------------------+ RTP +-----+--------------------------------------------------+
Packet #3 | Hdr | Packetization unit #3 (part 1/3) | Packet #3 | Hdr | Packetization unit #3 (part 1/3) |
+-----+--------------------------------------------------+ +-----+--------------------------------------------------+
skipping to change at page 8, line 25 skipping to change at line 332
Packet #4 | Hdr | Packetization unit #3 (part 2/3) | Packet #4 | Hdr | Packetization unit #3 (part 2/3) |
+-----+--------------------------------------------------+ +-----+--------------------------------------------------+
RTP +-----+----------------------------------------------+ RTP +-----+----------------------------------------------+
Packet #5 | Hdr | Packetization unit #3 (part 3/3) | Packet #5 | Hdr | Packetization unit #3 (part 3/3) |
+-----+----------------------------------------------+ +-----+----------------------------------------------+
... ...
RTP +-----+-----------------------------------------+ RTP +-----+-----------------------------------------+
Packet #P | Hdr | Packetization unit #N (part q/q) | Packet #P | Hdr | Packetization unit #N (part q/q) |
+-----+-----------------------------------------+ +-----+-----------------------------------------+
Figure 1: Example of ADU packetization Figure 1: Example of ADU Packetization
There are two different packetization modes defined for this RTP There are two different packetization modes defined for this RTP
payload format. payload format.
1. Codestream packetization mode: in this mode, the packetization Codestream packetization mode:
unit SHALL be the entire JPEG XS picture segment (i.e. codestream In this mode, the packetization unit SHALL be the entire JPEG XS
preceded by boxes). This means that a progressive frame will picture segment (i.e., codestream preceded by boxes). This means
have a single packetization unit, while an interlaced frame will that a progressive frame will have a single packetization unit,
have two. The progressive case is illustrated in Figure 2. while an interlaced frame will have two. The progressive case is
illustrated in Figure 2.
2. Slice packetization mode: in this mode, the packetization unit Slice packetization mode:
SHALL be the slice, i.e. there SHALL be data from no more than In this mode, the packetization unit SHALL be the slice, i.e.,
one slice per RTP packet. The first packetization unit SHALL be there SHALL be data from no more than one slice per RTP packet.
made of the JPEG XS header segment (i.e. the concatenation of the The first packetization unit SHALL be made of the JPEG XS header
VS box, the CS box and the JPEG XS codestream header). This segment (i.e., the concatenation of the VS box, the CS box, and
first unit is then followed by successive units, each containing the JPEG XS codestream header). This first unit is then followed
one and only one slice. The packetization unit containing the by successive units, each containing one and only one slice. The
last slice of a JPEG XS codestream SHALL also contain the EOC packetization unit containing the last slice of a JPEG XS
marker immediately following this last slice. This is codestream SHALL also contain the EOC marker immediately following
illustrated in Figure 3. In the case of an interlaced frame, the this last slice. This is illustrated in Figure 3. In the case of
JPEG XS header segment of the second field SHALL be in its own an interlaced frame, the JPEG XS header segment of the second
packetization unit. field SHALL be in its own packetization unit.
RTP +-----+--------------------------------------------------+ RTP +-----+--------------------------------------------------+
Packet #1 | Hdr | VS box + CS box + JPEG XS codestream (part 1/q) | Packet #1 | Hdr | VS box + CS box + JPEG XS codestream (part 1/q) |
+-----+--------------------------------------------------+ +-----+--------------------------------------------------+
RTP +-----+--------------------------------------------------+ RTP +-----+--------------------------------------------------+
Packet #2 | Hdr | JPEG XS codestream (part 2/q) | Packet #2 | Hdr | JPEG XS codestream (part 2/q) |
+-----+--------------------------------------------------+ +-----+--------------------------------------------------+
... ...
RTP +-----+--------------------------------------+ RTP +-----+--------------------------------------+
Packet #P | Hdr | JPEG XS codestream (part q/q) | Packet #P | Hdr | JPEG XS codestream (part q/q) |
+-----+--------------------------------------+ +-----+--------------------------------------+
Figure 2: Example of codestream packetization mode Figure 2: Example of Codestream Packetization Mode
RTP +-----+----------------------------+ RTP +-----+----------------------------+
Packet #1 | Hdr | JPEG XS header segment | Packet #1 | Hdr | JPEG XS header segment |
+-----+----------------------------+ +-----+----------------------------+
RTP +-----+--------------------------------------------------+ RTP +-----+--------------------------------------------------+
Packet #2 | Hdr | Slice #1 (part 1/2) | Packet #2 | Hdr | Slice #1 (part 1/2) |
+-----+--------------------------------------------------+ +-----+--------------------------------------------------+
RTP +-----+-------------------------------------------+ RTP +-----+-------------------------------------------+
Packet #3 | Hdr | Slice #1 (part 2/2) | Packet #3 | Hdr | Slice #1 (part 2/2) |
+-----+-------------------------------------------+ +-----+-------------------------------------------+
RTP +-----+--------------------------------------------------+ RTP +-----+--------------------------------------------------+
Packet #4 | Hdr | Slice #2 (part 1/3) | Packet #4 | Hdr | Slice #2 (part 1/3) |
+-----+--------------------------------------------------+ +-----+--------------------------------------------------+
... ...
RTP +-----+---------------------------------------+ RTP +-----+---------------------------------------+
Packet #P | Hdr | Slice #N (part q/q) + EOC marker | Packet #P | Hdr | Slice #N (part q/q) + EOC marker |
+-----+---------------------------------------+ +-----+---------------------------------------+
Figure 3: Example of slice packetization mode Figure 3: Example of Slice Packetization Mode
In a constant bit-rate (CBR) scenario of JPEG XS, the codestream In a constant bitrate (CBR) scenario of JPEG XS, the codestream
packetization mode guarantees that a JPEG XS RTP stream will produce packetization mode guarantees that a JPEG XS RTP stream will produce
a constant number of bytes per video frame, and a constant number of both a constant number of bytes per video frame and a constant number
RTP packets per video frame. However, to provide similar guarantees of RTP packets per video frame. However, to provide similar
with JPEG XS in a variable bit-rate (VBR) mode or when using the guarantees with JPEG XS in a variable bitrate (VBR) mode or when
slice packetization mode (for either CBR or VBR), additional using the slice packetization mode (for either CBR or VBR),
mechanisms are needed. This can involve a constraint at the rate additional mechanisms are needed. This can involve a constraint at
allocation stage in the JPEG XS encoder to impose a constant bit-rate the rate allocation stage in the JPEG XS encoder to impose a CBR at
at the slice level, the usage of padding data, or the insertion of the slice level, the usage of padding data, or the insertion of empty
empty RTP packets (i.e. an RTP packet whose payload data is empty). RTP packets (i.e., an RTP packet whose payload data is empty). But,
But, management of the amount of produced packets per video frame is management of the amount of produced packets per video frame is
application dependent and not a strict requirement of this RTP application dependent and not a strict requirement of this RTP
payload specification. payload specification.
4.2. RTP Header Usage 4.2. RTP Header Usage
The format of the RTP header is specified in [RFC3550] and reprinted The format of the RTP header is specified in [RFC3550] and reprinted
in Figure 4 for convenience. This RTP payload format uses the fields in Figure 4 for convenience. This RTP payload format uses the fields
of the header in a manner consistent with that specification. of the header in a manner consistent with that specification.
The RTP payload (and the settings for some RTP header bits) for The RTP payload (and the settings for some RTP header bits) for
packetization units are specified in Section 4.3. packetization units are specified in Section 4.3.
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| V |P|X| CC |M| PT | sequence number | |V=2|P|X| CC |M| PT | sequence number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| timestamp | | timestamp |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| synchronization source (SSRC) identifier | | synchronization source (SSRC) identifier |
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
| contributing source (CSRC) identifiers | | contributing source (CSRC) identifiers |
| .... | | .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: RTP header according to RFC 3550 Figure 4: RTP Header According to RFC 3550
The version (V), padding (P), extension (X), CSRC count (CC), The version (V), padding (P), extension (X), CSRC count (CC),
sequence number, synchronization source (SSRC) and contributing sequence number, synchronization source (SSRC), and contributing
source (CSRC) fields follow their respective definitions in source (CSRC) fields follow their respective definitions in
[RFC3550]. [RFC3550].
The remaining RTP header information to be set according to this RTP The remaining RTP header information to be set according to this RTP
payload format is set as follows: payload format is set as follows:
Marker (M) [1 bit]: Marker (M) [1 bit]:
If progressive scan video is being transmitted, the marker bit If progressive scan video is being transmitted, the marker bit
denotes the end of a video frame. If interlaced video is being denotes the end of a video frame. If interlaced video is being
transmitted, it denotes the end of the field. The marker bit transmitted, it denotes the end of the field. The marker bit
SHALL be set to 1 for the last packet of the video frame/field. SHALL be set to 1 for the last packet of the video frame/field.
It SHALL be set to 0 for all other packets. It SHALL be set to 0 for all other packets.
Payload Type (PT) [7 bits]: Payload Type (PT) [7 bits]:
The payload type is a dynamically allocated payload type field
A dynamically allocated payload type field that designates the that designates the payload as JPEG XS video.
payload as JPEG XS video.
Timestamp [32 bits]: Timestamp [32 bits]:
The RTP timestamp is set to the sampling timestamp of the content. The RTP timestamp is set to the sampling timestamp of the content.
A 90 kHz clock rate SHALL be used. A 90 kHz clock rate SHALL be used.
As specified in [RFC3550] and [RFC4175], the RTP timestamp As specified in [RFC3550] and [RFC4175], the RTP timestamp
designates the sampling instant of the first octet of the video designates the sampling instant of the first octet of the video
frame to which the RTP packet belongs. Packets SHALL NOT include frame to which the RTP packet belongs. Packets SHALL NOT include
data from multiple video frames, and all packets belonging to the data from multiple video frames, and all packets belonging to the
same video frame SHALL have the same timestamp. Several same video frame SHALL have the same timestamp. Several
successive RTP packets will consequently have equal timestamps if successive RTP packets will consequently have equal timestamps if
they belong to the same video frame (that is until the marker bit they belong to the same video frame (that is until the marker bit
is set to 1, marking the last packet of the video frame), and the is set to 1, marking the last packet of the video frame), and the
timestamp is only increased when a new video frame begins. timestamp is only increased when a new video frame begins.
If the sampling instant does not correspond to an integer value of If the sampling instant does not correspond to an integer value of
the clock, the value SHALL be truncated to the next lowest the clock, the value SHALL be truncated to the next lowest
integer, with no ambiguity. integer, with no ambiguity.
4.3. Payload Header Usage 4.3. Payload Header Usage
The first four bytes of the payload of an RTP packet in this RTP The first four bytes of the payload of an RTP packet in this RTP
payload format are referred to as the payload header. Figure 5 payload format are referred to as the "payload header". Figure 5
illustrates the structure of this payload header. illustrates the structure of this payload header.
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|T|K|L| I |F counter| SEP counter | P counter | |T|K|L| I |F counter| SEP counter | P counter |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 5: Payload header Figure 5: Payload Header
The payload header consists of the following fields: The payload header consists of the following fields:
Transmission mode (T) [1 bit]: Transmission mode (T) [1 bit]:
The T bit is set to indicate that packets are sent sequentially by The T bit is set to indicate that packets are sent sequentially by
the transmitter. This information allows a receiver to dimension the transmitter. This information allows a receiver to dimension
its input buffer(s) accordingly. If T=0, nothing can be assumed its input buffer(s) accordingly. If T=0, nothing can be assumed
about the transmission order and packets may be sent out-of-order about the transmission order and packets may be sent out of order
by the transmitter. If T=1, packets SHALL be sent sequentially by by the transmitter. If T=1, packets SHALL be sent sequentially by
the transmitter. The T bit value SHALL be identical for all the transmitter. The T-bit value SHALL be identical for all
packets of the RTP stream. packets of the RTP stream.
pacKetization mode (K) [1 bit]: pacKetization mode (K) [1 bit]:
The K bit is set to indicate which packetization mode is used. The K bit is set to indicate which packetization mode is used.
K=0 indicates codestream packetization mode, while K=1 indicates K=0 indicates codestream packetization mode, while K=1 indicates
slice packetization mode. In the case that the Transmission mode slice packetization mode. In the case that the Transmission mode
(T) is set to 0 (out-of-order), the slice packetization mode SHALL (T) is set to 0 (out of order), the slice packetization mode SHALL
be used and K SHALL be set to 1. This is required, because only be used and K SHALL be set to 1. This is required because only
the slice packetization mode supports out-of-order packet the slice packetization mode supports out-of-order packet
transmission. The K bit value SHALL be identical for all packets transmission. The K-bit value SHALL be identical for all packets
of the RTP stream. of the RTP stream.
Last (L) [1 bit]: Last (L) [1 bit]:
The L bit is set to indicate the last packet of a packetization The L bit is set to indicate the last packet of a packetization
unit. As the end of the video frame also ends the packet unit. As the end of the video frame also ends the packet
containing the last unit of the video frame, the L bit is set containing the last unit of the video frame, the L bit is set
whenever the M bit is set. In the codestream packetization mode whenever the M bit is set. In the codestream packetization mode,
the L bit and M bit get an equivalent meaning, so they SHALL have the L bit and M bit get an equivalent meaning, so they SHALL have
identical values in each packet. identical values in each packet.
Interlaced information (I) [2 bit]: Interlaced information (I) [2 bits]:
These two I bits are used to indicate how the JPEG XS frame is These two I bits are used to indicate how the JPEG XS frame is
scanned (progressive or interlaced). In case of an interlaced scanned (progressive or interlaced). In case of an interlaced
frame, they also indicate which JPEG XS picture segment the frame, they also indicate which JPEG XS picture segment the
payload is part of (first or second). payload is part of (first or second).
00: The payload is progressively scanned. 00: The payload is progressively scanned.
01: Reserved for future use. 01: This value is reserved for future use.
10: The payload is part of the first JPEG XS picture segment of 10: The payload is part of the first JPEG XS picture segment of
an interlaced video frame. The height specified in the an interlaced video frame. The height specified in the
included JPEG XS codestream header is half of the height of the included JPEG XS codestream header is half of the height of
entire displayed image. the entire displayed image.
11: The payload is part of the second JPEG XS picture segment of 11: The payload is part of the second JPEG XS picture segment of
an interlaced video frame. The height specified in the an interlaced video frame. The height specified in the
included JPEG XS codestream header is half of the height of the included JPEG XS codestream header is half of the height of
entire displayed image. the entire displayed image.
F counter [5 bits]: F counter [5 bits]:
The Frame (F) counter identifies the video frame number modulo 32
The frame (F) counter identifies the video frame number modulo 32
to which a packet belongs. Frame numbers are incremented by 1 for to which a packet belongs. Frame numbers are incremented by 1 for
each video frame transmitted. The frame number, in addition to each video frame transmitted. The frame number, in addition to
the timestamp, may help the decoder manage its input buffer and the timestamp, may help the decoder manage its input buffer and
bring packets back into their natural order. bring packets back into their natural order.
SEP counter [11 bits]: Slice and Extended Packet (SEP) counter [11 bits]:
The SEP counter is used differently depending on the packetization
The Slice and Extended Packet (SEP) counter is used differently mode.
depending on the packetization mode.
* In the case of codestream packetization mode (K=0), this * In the case of codestream packetization mode (K=0), this
counter resets whenever the Packet counter resets (see counter resets whenever the Packet counter resets (see
Section 4.4), and increments by 1 whenever the Packet counter Section 4.4) and increments by 1 whenever the Packet counter
overruns. overruns.
* In the case of slice packetization mode (K=1), this counter * In the case of slice packetization mode (K=1), this counter
identifies the slice modulo 2047 to which the packet identifies the slice modulo 2047 to which the packet
contributes. If the data belongs to the JPEG XS header contributes. If the data belongs to the JPEG XS header
segment, this field SHALL have its maximal value, namely 2047 = segment, this field SHALL have its maximal value, namely 2047 =
0x07ff. Otherwise, it is the slice index modulo 2047. Slice 0x07ff. Otherwise, it is the slice index modulo 2047. Slice
indices are counted from 0 (corresponding to the top of the indices are counted from 0 (corresponding to the top of the
video frame). video frame).
P counter [11 bits]: P counter [11 bits]:
The Packet (P) counter identifies the packet number modulo 2048
The packet (P) counter identifies the packet number modulo 2048
within the current packetization unit. It is set to 0 at the within the current packetization unit. It is set to 0 at the
start of the packetization unit and incremented by 1 for every start of the packetization unit and incremented by 1 for every
subsequent packet (if any) belonging to the same unit. subsequent packet (if any) belonging to the same unit.
Practically, if codestream packetization mode is enabled, this Practically, if codestream packetization mode is enabled, this
field counts the packets within a JPEG XS picture segment and is field counts the packets within a JPEG XS picture segment and is
extended by the SEP counter when it overruns. If slice extended by the SEP counter when it overruns. If slice
packetization mode is enabled, this field counts the packets packetization mode is enabled, this field counts the packets
within a slice or within the JPEG XS header segment. within a slice or within the JPEG XS header segment.
4.4. Payload Data 4.4. Payload Data
skipping to change at page 13, line 45 skipping to change at line 577
their respective layouts for each JPEG XS frame. Thus, each video their respective layouts for each JPEG XS frame. Thus, each video
support box in the RTP stream SHALL define the same sub boxes. The support box in the RTP stream SHALL define the same sub boxes. The
effective values in the boxes are allowed to change under the effective values in the boxes are allowed to change under the
condition that their relative byte offsets SHALL NOT change. condition that their relative byte offsets SHALL NOT change.
Each JPEG XS frame is the concatenation of one or more packetization Each JPEG XS frame is the concatenation of one or more packetization
unit(s), as explained in Section 4.1. Figure 6 depicts this layout unit(s), as explained in Section 4.1. Figure 6 depicts this layout
for a progressive video frame in the codestream packetization mode, for a progressive video frame in the codestream packetization mode,
Figure 7 depicts this layout for an interlaced video frame in the Figure 7 depicts this layout for an interlaced video frame in the
codestream packetization mode, Figure 8 depicts this layout for a codestream packetization mode, Figure 8 depicts this layout for a
progressive video frame in the slice packetization mode and Figure 9 progressive video frame in the slice packetization mode, and Figure 9
depicts this layout for an interlaced video frame in the slice depicts this layout for an interlaced video frame in the slice
packetization mode. The Frame counter value is not indicated because packetization mode. The Frame counter value is not indicated because
the value is constant for all packetization units of a given video the value is constant for all packetization units of a given video
frame. frame.
+=====[ Packetization unit (PU) #1 ]====+ +=====[ Packetization unit (PU) #1 ]====+
| Video support box | SEP counter=0 | Video support box | SEP counter=0
| +---------------------------------+ | P counter=0 | +---------------------------------+ | P counter=0
| : Sub boxes of the VS box : | | : Sub boxes of the VS box : |
| +---------------------------------+ | | +---------------------------------+ |
skipping to change at page 14, line 40 skipping to change at line 618
| (part 2049/q) | P counter=0 | (part 2049/q) | P counter=0
: : M=0, K=0, L=0, I=00 : : M=0, K=0, L=0, I=00
+---------------------------------------+ +---------------------------------------+
: : : :
+---------------------------------------+ +---------------------------------------+
| JPEG XS codestream | SEP counter=(q-1) div 2048 | JPEG XS codestream | SEP counter=(q-1) div 2048
| (part q/q) | P counter=(q-1) mod 2048 | (part q/q) | P counter=(q-1) mod 2048
: : M=1, K=0, L=1, I=00 : : M=1, K=0, L=1, I=00
+=======================================+ +=======================================+
Figure 6: Example of JPEG XS Payload Data (codestream packetization Figure 6: Example of JPEG XS Payload Data (Codestream
mode, progressive video frame) Packetization Mode, Progressive Video Frame)
+=====[ Packetization unit (PU) #1 ]====+ +=====[ Packetization unit (PU) #1 ]====+
| Video support box | SEP counter=0 | Video support box | SEP counter=0
+- - - - - - - - - - - - - - - - - - - -+ P counter=0 +- - - - - - - - - - - - - - - - - - - -+ P counter=0
| Color specification box | | Color specification box |
+- - - - - - - - - - - - - - - - - - - -+ +- - - - - - - - - - - - - - - - - - - -+
| JPEG XS codestream (1st field) | | JPEG XS codestream (1st field) |
: (part 1/q) : M=0, K=0, L=0, I=10 : (part 1/q) : M=0, K=0, L=0, I=10
+---------------------------------------+ +---------------------------------------+
| JPEG XS codestream (1st field) | SEP counter=0 | JPEG XS codestream (1st field) | SEP counter=0
skipping to change at page 15, line 48 skipping to change at line 664
| (part 2/q) | P counter=1 | (part 2/q) | P counter=1
: : M=0, K=0, L=0, I=11 : : M=0, K=0, L=0, I=11
+---------------------------------------+ +---------------------------------------+
: : : :
+---------------------------------------+ +---------------------------------------+
| JPEG XS codestream (2nd field) | SEP counter=(q-1) div 2048 | JPEG XS codestream (2nd field) | SEP counter=(q-1) div 2048
| (part q/q) | P counter=(q-1) mod 2048 | (part q/q) | P counter=(q-1) mod 2048
: : M=1, K=0, L=1, I=11 : : M=1, K=0, L=1, I=11
+=======================================+ +=======================================+
Figure 7: Example of JPEG XS Payload Data (codestream packetization Figure 7: Example of JPEG XS Payload Data (Codestream
mode, interlaced video frame) Packetization Mode, Interlaced Video Frame)
+===[ PU #1: JPEG XS Header segment ]===+ +===[ PU #1: JPEG XS Header segment ]===+
| Video support box | SEP counter=0x07FF | Video support box | SEP counter=0x07FF
+- - - - - - - - - - - - - - - - - - - -+ P counter=0 +- - - - - - - - - - - - - - - - - - - -+ P counter=0
| Color specification box | | Color specification box |
+- - - - - - - - - - - - - - - - - - - -+ +- - - - - - - - - - - - - - - - - - - -+
| JPEG XS codestream header | | JPEG XS codestream header |
| +---------------------------------+ | | +---------------------------------+ |
| : Markers and marker segments : | | : Markers and marker segments : |
| +---------------------------------+ | M=0, T=0, K=1, L=1, I=00 | +---------------------------------+ | M=0, T=0, K=1, L=1, I=00
skipping to change at page 16, line 48 skipping to change at line 710
| (part 1/r) | P counter=0 | (part 1/r) | P counter=0
: : M=0, T=0, K=1, L=0, I=00 : : M=0, T=0, K=1, L=0, I=00
+---------------------------------------+ +---------------------------------------+
: : : :
+---------------------------------------+ +---------------------------------------+
| Slice #(N-1) | SEP counter=N-2 | Slice #(N-1) | SEP counter=N-2
| (part r/r) | P counter=r-1 | (part r/r) | P counter=r-1
: + EOC marker : M=1, T=0, K=1, L=1, I=00 : + EOC marker : M=1, T=0, K=1, L=1, I=00
+=======================================+ +=======================================+
Figure 8: Example of JPEG XS Payload Data (slice packetization mode, Figure 8: Example of JPEG XS Payload Data (Slice Packetization Mode,
progressive video frame) Progressive Video Frame)
+====[ PU #1: JPEG XS Hdr segment 1 ]===+ +====[ PU #1: JPEG XS Hdr segment 1 ]===+
| Video support box | SEP counter=0x07FF | Video support box | SEP counter=0x07FF
+- - - - - - - - - - - - - - - - - - - -+ P counter=0 +- - - - - - - - - - - - - - - - - - - -+ P counter=0
| Color specification box | | Color specification box |
+- - - - - - - - - - - - - - - - - - - -+ +- - - - - - - - - - - - - - - - - - - -+
| JPEG XS codestream header 1 | | JPEG XS codestream header 1 |
| +---------------------------------+ | | +---------------------------------+ |
| : Markers and marker segments : | | : Markers and marker segments : |
| +---------------------------------+ | M=0, T=0, K=1, L=1, I=10 | +---------------------------------+ | M=0, T=0, K=1, L=1, I=10
skipping to change at page 18, line 41 skipping to change at line 798
| (part 1/t) | P counter=0 | (part 1/t) | P counter=0
: : M=0, T=0, K=1, L=0, I=11 : : M=0, T=0, K=1, L=0, I=11
+---------------------------------------+ +---------------------------------------+
: : : :
+---------------------------------------+ +---------------------------------------+
| Slice #(N-1) | SEP counter=N-2 | Slice #(N-1) | SEP counter=N-2
| (part t/t) | P counter=t-1 | (part t/t) | P counter=t-1
: + EOC marker : M=1, T=0, K=1, L=1, I=11 : + EOC marker : M=1, T=0, K=1, L=1, I=11
+=======================================+ +=======================================+
Figure 9: Example of JPEG XS Payload Data (slice packetization mode, Figure 9: Example of JPEG XS Payload Data (Slice Packetization
interlaced video frame) Mode, Interlaced Video Frame)
5. Traffic Shaping and Delivery Timing 5. Traffic Shaping and Delivery Timing
In order to facilitate proper synchronization between senders and In order to facilitate proper synchronization between senders and
receivers it is RECOMMENDED to implement traffic shaping and delivery receivers, it is RECOMMENDED to implement traffic shaping and
timing in accordance with the Network Compatibility Model compliance delivery timing in accordance with the Network Compatibility Model
definitions specified in [SMPTE-ST2110-21]. In such case, the compliance definitions specified in [SMPTE2110-21]. In such a case,
session description SHALL signal the compliance with the media type the session description SHALL signal the compliance with the media
parameter TP. The actual applied traffic shaping and timing delivery type parameter TP. The actual applied traffic shaping and timing
mechanism is outside the scope of this memo and does not influence delivery mechanism is outside the scope of this memo and does not
the payload packetization. influence the payload packetization.
6. Congestion Control Considerations 6. Congestion Control Considerations
Congestion control for RTP SHALL be used in accordance with Congestion control for RTP SHALL be used in accordance with [RFC3550]
[RFC3550], and with any applicable RTP profile: e.g. RTP/AVP and with any applicable RTP profile, e.g., RTP/AVP [RFC3551] or RTP/
[RFC3551] or RTP/AVPF [RFC4585]. AVPF [RFC4585].
While JPEG XS is mainly designed to be used in controlled network While JPEG XS is mainly designed to be used in controlled network
environments, it can also be employed in best-effort network environments, it can also be employed in best-effort network
environments, like the Internet. However, in this case the users of environments, like the Internet. However, in this case, the users of
this payload format SHALL monitor packet loss to ensure that the this payload format SHALL monitor packet loss to ensure that the
packet loss rate is within acceptable parameters. This can be packet loss rate is within acceptable parameters. This can be
achieved for example by means of the RTP Control Protocol (RTCP) achieved, for example, by means of RTP Control Protocol (RTCP)
Feedback for Congestion Control [RFC8888]. Feedback for Congestion Control [RFC8888].
In addition, Circuit Breakers [RFC8083] is an update to RTP [RFC3550] In addition, [RFC8083] is an update to [RFC3550] that defines
that defines criteria for when one is required to stop sending RTP criteria for when one is required to stop sending RTP Packet Streams
Packet Streams and applications implementing this standard SHALL and for when applications implementing this standard SHALL comply
comply with it. with it.
[RFC8085] provides additional information on the best practices for [RFC8085] provides additional information on the best practices for
applying congestion control to UDP streams. applying congestion control to UDP streams.
7. Payload Format Parameters 7. Payload Format Parameters
This section specifies the required and optional parameters of the This section specifies the required and optional parameters of the
payload format and/or the RTP stream. All parameters are payload format and/or the RTP stream. All parameters are
declarative, meaning that the information signaled by the parameters declarative, meaning that the information signaled by the parameters
is also present in the payload data, namely in the payload header is also present in the payload data, namely in the payload header
(see Section 4.3) or in the JPEG XS header segment [ISO21122-1] (see Section 4.3) or in the JPEG XS header segment [ISO21122-1]
[ISO21122-3]. When provided, their respective values SHALL be [ISO21122-3]. When provided, their respective values SHALL be
consistent with the payload. consistent with the payload.
7.1. Media Type Registration 7.1. Media Type Registration
This registration is done using the template defined in [RFC6838] This registration is done using the template defined in [RFC6838] and
and following [RFC4855]. following [RFC4855].
The receiver SHALL ignore any unrecognized parameter. The receiver SHALL ignore any unrecognized parameter.
Type name: video Type name:
video
Subtype name: jxsv Subtype name:
jxsv
Clock rate: 90000
Required parameters: Required parameters:
rate: The RTP timestamp clock rate. Applications using this rate: The RTP timestamp clock rate. Applications using this
payload format SHALL use a value of 90000. payload format SHALL use a value of 90000.
packetmode: This parameter specifies the configured packetization packetmode: This parameter specifies the configured packetization
mode as defined by the pacKetization mode (K) bit in the mode as defined by the pacKetization mode (K) bit in the
payload header of Section 4.3. This value SHALL be equal to payload header of Section 4.3. This value SHALL be equal to
the K bit value configured in the RTP stream (i.e. 0 for the K-bit value configured in the RTP stream (i.e., 0 for
codestream or 1 for slice). codestream or 1 for slice).
Optional parameters: Optional parameters:
transmode: This parameter specifies the configured transmission transmode: This parameter specifies the configured transmission
mode as defined by the Transmission mode (T) bit in the payload mode as defined by the Transmission mode (T) bit in the payload
header of Section 4.3. If specified, this value SHALL be equal header of Section 4.3. If specified, this value SHALL be equal
to the T bit value configured in the RTP stream (i.e. 0 for to the T-bit value configured in the RTP stream (i.e., 0 for
out-of-order-allowed or 1 for sequential-only). If not out-of-order-allowed or 1 for sequential-only). If not
specified, a value 1 (sequential-only) SHALL be assumed and the specified, a value 1 (sequential-only) SHALL be assumed and the
T bit SHALL be set to 1. T bit SHALL be set to 1.
profile: The JPEG XS profile [ISO21122-2] in use. Any white profile: The JPEG XS profile [ISO21122-2] in use. Any white
space in the profile name SHALL be omitted. Examples of valid space Unicode character in the profile name SHALL be omitted.
profile names are 'Main444.12' or 'High444.12'. Examples of valid profile names are 'Main444.12' or
'High444.12'.
level: The JPEG XS level [ISO21122-2] in use. Any white space in level: The JPEG XS level [ISO21122-2] in use. Any white space
the level name SHALL be omitted. Examples of valid levels are Unicode character in the level name SHALL be omitted. Examples
'2k-1' or '4k-2'. of valid levels are '2k-1' or '4k-2'.
sublevel: The JPEG XS sublevel [ISO21122-2] in use. Any white sublevel: The JPEG XS sublevel [ISO21122-2] in use. Any white
space in the sublevel name SHALL be omitted. Examples of valid space Unicode character in the sublevel name SHALL be omitted.
sublevels are 'Sublev3bpp' or 'Sublev6bpp'. Examples of valid sublevels are 'Sublev3bpp' or 'Sublev6bpp'.
depth: Determines the number of bits per sample. This is an depth: Determines the number of bits per sample. This is an
integer with typical values including 8, 10, 12, and 16. integer with typical values including 8, 10, 12, and 16.
width: Determines the number of pixels per line. This is an width: Determines the number of pixels per line. This is an
integer between 1 and 32767 inclusive. integer between 1 and 32767, inclusive.
height: Determines the number of lines per video frame. This is height: Determines the number of lines per video frame. This is
an integer between 1 and 32767 inclusive. an integer between 1 and 32767, inclusive.
exactframerate: Signals the video frame rate in frames per exactframerate: Signals the video frame rate in frames per
second. Integer frame rates SHALL be signaled as a single second. Integer frame rates SHALL be signaled as a single
decimal number (e.g. "25") whilst non-integer frame rates SHALL decimal number (e.g., "25") whilst non-integer frame rates
be signaled as a ratio of two integer decimal numbers separated SHALL be signaled as a ratio of two integer decimal numbers
by a "forward-slash" character (e.g. "30000/1001"), utilizing separated by a "forward-slash" character (e.g., "30000/1001"),
the numerically smallest numerator value possible. utilizing the numerically smallest numerator value possible.
interlace: If this parameter name is present, it indicates that interlace: If this parameter name is present, it indicates that
the video is interlaced, or that the video is Progressive the video is interlaced, or that the video is Progressive
segmented Frame (PsF). If this parameter name is not present, segmented Frame (PsF). If this parameter name is not present,
the progressive video format SHALL be assumed. the progressive video format SHALL be assumed.
segmented: If this parameter name is present, and the interlace segmented: If this parameter name is present, and the interlace
parameter name is also present, then the video is a Progressive parameter name is also present, then the video is a Progressive
segmented Frame (PsF). Signaling of this parameter without the segmented Frame (PsF). Signaling of this parameter without the
interlace parameter is forbidden. interlace parameter is forbidden.
sampling: Signals the color difference signal sub-sampling sampling: Signals the color difference signal sub-sampling
structure. structure.
Signals utilizing the non-constant luminance Y'C'B C'R signal Signals utilizing the non-constant luminance Y'C'B C'R signal
format of Recommendation ITU-R BT.601-7, Recommendation ITU-R format of [BT.601-7], [BT.709-6], [BT.2020-2], or [BT.2100-2]
BT.709-6, Recommendation ITU-R BT.2020-2, or Recommendation SHALL use the appropriate one of the following values for the
ITU-R BT.2100 SHALL use the appropriate one of the following Media Type Parameter "sampling":
values for the Media Type Parameter "sampling":
YCbCr-4:4:4 (4:4:4 sampling) YCbCr-4:4:4 (4:4:4 sampling)
YCbCr-4:2:2 (4:2:2 sampling)
YCbCr-4:2:0 (4:2:0 sampling) YCbCr-4:2:2 (4:2:2 sampling)
YCbCr-4:2:0 (4:2:0 sampling)
Signals utilizing the Constant Luminance Y'C C'BC C'RC signal Signals utilizing the Constant Luminance Y'C C'BC C'RC signal
format of Recommendation ITU-R BT.2020-2 SHALL use the format of [BT.2020-2] SHALL use the appropriate one of the
appropriate one of the following values for the Media Type following values for the Media Type Parameter "sampling":
Parameter "sampling":
CLYCbCr-4:4:4 (4:4:4 sampling) CLYCbCr-4:4:4 (4:4:4 sampling)
CLYCbCr-4:2:2 (4:2:2 sampling)
CLYCbCr-4:2:0 (4:2:0 sampling) CLYCbCr-4:2:2 (4:2:2 sampling)
CLYCbCr-4:2:0 (4:2:0 sampling)
Signals utilizing the constant intensity I CT CP signal format Signals utilizing the constant intensity I CT CP signal format
of Recommendation ITU-R BT.2100 SHALL use the appropriate one of [BT.2100-2] SHALL use the appropriate one of the following
of the following values for the Media Type Parameter values for the Media Type Parameter "sampling":
"sampling":
ICtCp-4:4:4 (4:4:4 sampling) ICtCp-4:4:4 (4:4:4 sampling)
ICtCp-4:2:2 (4:2:2 sampling)
ICtCp-4:2:0 (4:2:0 sampling) ICtCp-4:2:2 (4:2:2 sampling)
ICtCp-4:2:0 (4:2:0 sampling)
Signals utilizing the 4:4:4 R' G' B' or RGB signal format (such Signals utilizing the 4:4:4 R' G' B' or RGB signal format (such
as that of Recommendation ITU-R BT.601, Recommendation ITU-R as that of [BT.601-7], [BT.709-6], [BT.2020-2], [BT.2100-2],
BT.709, Recommendation ITU-R BT.2020, Recommendation ITU-R [SMPTE2065-1], or [SMPTE2065-3]) SHALL use the following value
BT.2100, SMPTE ST 2065-1 or ST 2065-3) SHALL use the following for the Media Type Parameter "sampling":
value for the Media Type Parameter sampling.
RGB (RGB or R' G' B' samples) RGB (RGB or R' G' B' samples)
Signals utilizing the 4:4:4 X' Y' Z' signal format (such as Signals utilizing the 4:4:4 X' Y' Z' signal format (such as
defined in SMPTE ST 428-1) SHALL use the following value for defined in [SMPTE428-1]) SHALL use the following value for the
the Media Type Parameter sampling. Media Type Parameter "sampling":
XYZ (X' Y' Z' samples) XYZ (X' Y' Z' samples)
Key signals as defined in SMPTE RP 157 SHALL use the value key Key signals as defined in [SMPTE157] SHALL use the value key
for the Media Type Parameter sampling. The Key signal is for the Media Type Parameter "sampling". The key signal is
represented as a single component. represented as a single component:
KEY (Samples of the key signal) KEY (Samples of the key signal)
Signals utilizing a color sub-sampling other than what is Signals utilizing a color sub-sampling other than what is
defined here SHALL use the following value for the Media Type defined here SHALL use the following value for the Media Type
Parameter sampling. Parameter "sampling":
UNSPECIFIED (Sampling signaled by the payload.) UNSPECIFIED (Sampling signaled by the payload)
colorimetry: Specifies the system colorimetry used by the image colorimetry: Specifies the system colorimetry used by the image
samples. Valid values and their specification are: samples. Valid values and their specification are the
following:
BT601-5 ITU-R Recommendation BT.601-5. BT601-5: [BT.601-5].
BT709-2 ITU-R Recommendation BT.709-2.
SMPTE240M SMPTE ST 240M.
BT601 ITU-R Recommendation BT.601-7.
BT709 ITU-R Recommendation BT.709-6.
BT2020 ITU-R Recommendation BT.2020-2.
BT2100 ITU-R Recommendation BT.2100
Table 2 titled "System colorimetry".
ST2065-1 SMPTE ST 2065-1 Academy Color Encoding
Specification (ACES).
ST2065-3 SMPTE ST 2065-3 Academy Density Exchange
Encoding (ADX).
XYZ ISO/IEC 11664-1, section titled
"1931 Observer".
UNSPECIFIED Colorimetry is signaled in the payload by
the color specification box of [ISO21122-3],
or it must be manually coordinated between
sender and receiver.
Signals utilizing the Recommendation ITU-R BT.2100 colorimetry BT709-2: [BT.709-2].
SHOULD also signal the representational range using the
optional parameter RANGE defined below. Signals utilizing the SMPTE240M: [SMPTE240M].
UNSPECIFIED colorimetry might require manual coordination
between the sender and the receiver. BT601: [BT.601-7].
BT709: [BT.709-6].
BT2020: [BT.2020-2].
BT2100: [BT.2100-2], Table 2 titled "System
colorimetry".
ST2065-1: Academy Color Encoding Specification (ACES)
[SMPTE2065-1].
ST2065-3: Academy Density Exchange Encoding (ADX)
[SMPTE2065-3].
XYZ: [ISO11664-1], section titled "1931 Observer".
UNSPECIFIED: Colorimetry is signaled in the payload by the
color specification box of [ISO21122-3], or it
must be manually coordinated between sender and
receiver.
Signals utilizing the [BT.2100-2] colorimetry SHOULD also
signal the representational range using the optional parameter
RANGE defined below. Signals utilizing the UNSPECIFIED
colorimetry might require manual coordination between the
sender and the receiver.
TCS: Transfer Characteristic System. This parameter specifies TCS: Transfer Characteristic System. This parameter specifies
the transfer characteristic system of the image samples. Valid the transfer characteristic system of the image samples. Valid
values and their specification are: values and their specification are the following:
SDR Standard Dynamic Range video streams that SDR: Standard Dynamic Range video streams that
utilize the OETF of ITU-R Recommendation utilize the Optical Electrical Transfer Function
BT.709 or ITU-R Recommendation BT.2020. Such (OETF) of [BT.709-6] or [BT.2020-2]. Such
streams SHALL be assumed to target the EOTF streams SHALL be assumed to target the Electro-
specified in ITU-R Recommendation BT.1886. Optical Transfer Function (EOTF) specified in
PQ High dynamic range video streams that utilize [BT.1886-0].
the Perceptual Quantization system of ITU-R
Recommendation BT.2100. PQ: High dynamic range video streams that utilize
HLG High dynamic range video streams that utilize the Perceptual Quantization system of
the Hybrid Log-Gamma system of ITU-R [BT.2100-2].
Recommendation BT.2100.
UNSPECIFIED Video streams whose transfer characteristics HLG: High dynamic range video streams that utilize
are signaled by the payload as specified in the Hybrid Log-Gamma system of [BT.2100-2].
[ISO21122-3], or must be manually
coordinated between sender and receiver. UNSPECIFIED: Video streams whose transfer characteristics are
signaled by the payload as specified in
[ISO21122-3], or that must be manually
coordinated between sender and receiver.
RANGE: This parameter SHOULD be used to signal the encoding range RANGE: This parameter SHOULD be used to signal the encoding range
of the sample values within the stream. When paired with ITU of the sample values within the stream. When paired with
Rec BT.2100 colorimetry, this parameter has two allowed values [BT.2100-2] colorimetry, this parameter has two allowed values,
NARROW and FULL, corresponding to the ranges specified in table NARROW and FULL, corresponding to the ranges specified in TABLE
9 of ITU Rec BT.2100. In any other context, this parameter has 9 of [BT.2100-2]. In any other context, this parameter has
three allowed values: NARROW, FULLPROTECT, and FULL, which three allowed values: NARROW, FULLPROTECT, and FULL, which
correspond to the ranges specified in SMPTE RP 2077. In the correspond to the ranges specified in [SMPTE2077]. In the
absence of this parameter, and for all but the UNSPECIFIED absence of this parameter, and for all but the UNSPECIFIED
colorimetry, NARROW SHALL be the assumed value. When paired colorimetry, NARROW SHALL be the assumed value. When paired
with the UNSPECIFIED colorimetry, FULL SHALL be the default with the UNSPECIFIED colorimetry, FULL SHALL be the default
assumed value. assumed value.
Encoding considerations: Encoding considerations:
This media type is framed in RTP and contains binary data; see This media type is framed in RTP and contains binary data; see
Section 4.8 in [RFC6838]. Section 4.8 of [RFC6838].
Security considerations: Security considerations:
Please see the Security Considerations (Section 10) of RFC XXXX. See the Security Considerations section of RFC 9134.
Interoperability considerations: Interoperability considerations:
None. None
Published specification: Published specification:
See RFC XXXX and its References section. See the References section of RFC 9134.
Applications that use this media type: Applications that use this media type:
Any application that transmits video over RTP (like SMPTE ST Any application that transmits video over RTP (like SMPTE ST
2110). 2110).
Fragment identifier considerations: Fragment identifier considerations:
N/A. N/A
Additional information: Additional information:
None. None
Person & email address to contact for further information: Person & email address to contact for further information:
S. Lugan <rtp@intopix.com> and Th. Richter <jpeg-xs- T. Bruylants <rtp@intopix.com> and T. Richter <jpeg-xs-
techsupport@iis.fraunhofer.de>. techsupport@iis.fraunhofer.de>.
Intended usage: Intended usage:
COMMON COMMON
Restrictions on usage: Restrictions on usage:
This media type depends on RTP framing, and hence is only defined This media type depends on RTP framing; hence, it is only defined
for transfer via RTP [RFC3550]. for transfer via RTP [RFC3550].
Author: Author:
See the Authors' Addresses section of RFC XXXX. See the Authors' Addresses section of RFC 9134.
Change controller: Change controller:
IETF Audio/Video Transport working group delegated from the IESG. IETF Audio/Video Transport Working Group delegated from the IESG.
8. SDP Parameters 8. SDP Parameters
A mapping of the parameters into the Session Description Protocol A mapping of the parameters into the Session Description Protocol
(SDP) [RFC8866] is provided for applications that use SDP. (SDP) [RFC8866] is provided for applications that use SDP.
8.1. Mapping of Payload Type Parameters to SDP 8.1. Mapping of Payload Type Parameters to SDP
The media type video/jxsv string is mapped to fields in the Session The media type video/jxsv string is mapped to fields in the Session
Description Protocol (SDP) [RFC8866] as follows: Description Protocol (SDP) [RFC8866] as follows:
The media type ("video") goes in SDP "m=" as the media name. The media type ("video") goes in SDP "m=" as the media name.
The media subtype ("jxsv") goes in SDP "a=rtpmap" as the encoding The media subtype ("jxsv") goes in SDP "a=rtpmap" as the encoding
name, followed by a slash ("/") and the required parameter "rate" name, followed by a slash ("/") and the required parameter "rate"
corresponding to the RTP timestamp clock rate (which for the corresponding to the RTP timestamp clock rate (which for the
payload format defined in this document SHALL be 90000). payload format defined in this document SHALL be 90000).
The required parameter "packetmode", and any of the additional The required parameter "packetmode" and any of the additional
optional parameters, as described in Section 7.1, go in the SDP optional parameters, as described in Section 7.1, go in the SDP
media format description, being the "a=fmtp" attribute (Format media format description, being the "a=fmtp" attribute (Format
Parameters), by copying them directly from the MIME media type Parameters), by copying them directly from the media type string
string as a semicolon-separated list of parameter=value pairs. as a semicolon-separated list of parameter=value pairs.
All parameters of the media format SHALL correspond to the parameters All parameters of the media format SHALL correspond to the parameters
of the payload. In case of discrepancies between payload parameter of the payload. In case of discrepancies between payload parameter
values and SDP fields, the values from the payload data SHALL values and SDP fields, the values from the payload data SHALL
prevail. prevail.
The receiver SHALL ignore any parameter that is not defined in The receiver SHALL ignore any parameter that is not defined in
Section 7.1. Section 7.1.
An example SDP mapping for JPEG XS video is as follows: An example SDP mapping for JPEG XS video is as follows:
m=video 30000 RTP/AVP 112 m=video 30000 RTP/AVP 112
a=rtpmap:112 jxsv/90000 a=rtpmap:112 jxsv/90000
a=fmtp:112 packetmode=0;sampling=YCbCr-4:2:2; a=fmtp:112 packetmode=0;sampling=YCbCr-4:2:2;
width=1920;height=1080;depth=10; width=1920;height=1080;depth=10;
colorimetry=BT709;TCS=SDR;RANGE=FULL;TP=2110TPNL colorimetry=BT709;TCS=SDR;RANGE=FULL;TP=2110TPNL
In this example, a JPEG XS RTP stream is to be sent to UDP In this example, a JPEG XS RTP stream is to be sent to UDP
destination port 30000, with an RTP dynamic payload type of 112 and a destination port 30000, with an RTP dynamic payload type of 112 and a
media clock rate of 90000 Hz. Note that the "a=fmtp:" line has been media clock rate of 90000 Hz. Note that the "a=fmtp:" line has been
wrapped to fit this page, and will be a single long line in the SDP wrapped to fit this page and will be a single long line in the SDP
file. This example includes the TP parameter (as specified in file. This example includes the TP parameter (as specified in
Section 5). Section 5).
8.2. Usage with SDP Offer/Answer Model 8.2. Usage with SDP Offer/Answer Model
When JPEG XS is offered over RTP using SDP in an offer/answer model When JPEG XS is offered over RTP using SDP in an offer/answer model
[RFC3264] for negotiation for unicast usage, the following [RFC3264] for negotiation for unicast usage, the following
limitations and rules apply: limitations and rules apply:
The "a=fmtp" attribute SHALL be present specifying the required The "a=fmtp" attribute SHALL be present specifying the required
parameter "packetmode", and MAY specify any of the optional parameter "packetmode" and MAY specify any of the optional
parameters, as described in Section 7.1. parameters, as described in Section 7.1.
All parameters in the "a=fmtp" attribute indicate sending All parameters in the "a=fmtp" attribute indicate sending
capabilities (i.e. properties of the payload). capabilities (i.e., properties of the payload).
An answerer of the SDP is required to support all parameters and An answerer of the SDP is required to support all parameters and
values of the parameters provided by the offerer; otherwise, the values of the parameters provided by the offerer; otherwise, the
answerer SHALL reject the session. It falls on the offerer to use answerer SHALL reject the session. It falls on the offerer to use
values that are expected to be supported by the answerer. If the values that are expected to be supported by the answerer. If the
answerer accepts the session, it SHALL reply with the exact same answerer accepts the session, it SHALL reply with the exact same
parameters values in the "a=fmtp" attribute as it was offered. parameter values in the "a=fmtp" attribute as they were initially
offered.
The same RTP payload type number used in the offer SHOULD be used The same RTP payload type number used in the offer SHOULD be used
in the answer, as specified in [RFC3264]. in the answer, as specified in [RFC3264].
9. IANA Considerations 9. IANA Considerations
The IANA is requested to register the media type registration "video/ IANA has registered the media type registration "video/jxsv" as
jxsv" as specified in Section 7.1. The media type is also requested specified in Section 7.1. The media type has also been added to the
to be added to the IANA registry for "RTP Payload Format MIME types" IANA registry for "RTP Payload Format Media Types"
<https://www.iana.org/assignments/rtp-parameters>. <https://www.iana.org/assignments/rtp-parameters>.
10. Security Considerations 10. Security Considerations
RTP packets using the payload format defined in this memo are subject RTP packets using the payload format defined in this memo are subject
to the security considerations discussed in [RFC3550] and in any to the security considerations discussed in [RFC3550] and in any
applicable RTP profile such as RTP/AVP [RFC3551], RTP/AVPF [RFC4585], applicable RTP profile such as RTP/AVP [RFC3551], RTP/AVPF [RFC4585],
RTP/SAVP [RFC3711], or RTP/SAVPF [RFC5124]. This implies that RTP/SAVP [RFC3711], or RTP/SAVPF [RFC5124]. This implies that
confidentiality of the media streams is achieved by encryption. confidentiality of the media streams is achieved by encryption.
skipping to change at page 26, line 41 skipping to change at line 1193
Implementations of this RTP payload format need to take appropriate Implementations of this RTP payload format need to take appropriate
security considerations into account. It is important for the security considerations into account. It is important for the
decoder to be robust against malicious or malformed payloads and decoder to be robust against malicious or malformed payloads and
ensure that they do not cause the decoder to overrun its allocated ensure that they do not cause the decoder to overrun its allocated
memory or otherwise misbehave. An overrun in allocated memory could memory or otherwise misbehave. An overrun in allocated memory could
lead to arbitrary code execution by an attacker. The same applies to lead to arbitrary code execution by an attacker. The same applies to
the encoder, even though problems in encoders are typically rarer. the encoder, even though problems in encoders are typically rarer.
This payload format and the JPEG XS encoding do not exhibit any This payload format and the JPEG XS encoding do not exhibit any
substantial non-uniformity, either in output or in complexity to substantial non-uniformity, either in output or in complexity to
perform the decoding operation and thus are unlikely to pose a perform the decoding operation; thus, they are unlikely to pose a
denial-of-service threat due to the receipt of pathological denial-of-service threat due to the receipt of pathological
datagrams. datagrams.
This payload format and the JPEG XS encoding do not contain code that This payload format and the JPEG XS encoding do not contain code that
is executable. is executable.
It is important to note that HD or UHDTV JPEG XS-encoded video can It is important to note that high-definition (HD) or ultra-high-
have significant bandwidth requirements (typically more than 1 Gbps definition (UHD) video that is encoded with JPEG XS can have
for ultra high-definition video, especially if using high framerate). significant bandwidth requirements (typically more than 1 Gbps for
This is sufficient to cause potential for denial-of-service if UHD video, especially if using high framerate). This is sufficient
transmitted onto most currently available Internet paths. to cause potential for denial of service if transmitted onto most
currently available Internet paths.
Accordingly, if best-effort service is being used, users of this Accordingly, if best-effort service is being used, users of this
payload format SHALL monitor packet loss to ensure that the packet payload format SHALL monitor packet loss to ensure that the packet
loss rate is within acceptable parameters. Packet loss is considered loss rate is within acceptable parameters. Packet loss is considered
acceptable if a TCP flow across the same network path, and acceptable if a TCP flow across the same network path, and
experiencing the same network conditions, would achieve an average experiencing the same network conditions, would achieve an average
throughput, measured on a reasonable timescale, that is not less than throughput, measured on a reasonable timescale, that is not less than
the RTP flow is achieving. This condition can be satisfied by the RTP flow is achieving. This condition can be satisfied by
implementing congestion control mechanisms to adapt the transmission implementing congestion control mechanisms to adapt the transmission
rate (or the number of layers subscribed for a layered multicast rate (or the number of layers subscribed for a layered multicast
session), or by arranging for a receiver to leave the session if the session) or by arranging for a receiver to leave the session if the
loss rate is unacceptably high. loss rate is unacceptably high.
This payload format may also be used in networks that provide This payload format may also be used in networks that provide
quality-of-service guarantees. If enhanced service is being used, quality-of-service guarantees. If enhanced service is being used,
receivers SHOULD monitor packet loss to ensure that the service that receivers SHOULD monitor packet loss to ensure that the service that
was requested is actually being delivered. If it is not, then they was requested is actually being delivered. If it is not, then they
SHOULD assume that they are receiving best-effort service and behave SHOULD assume that they are receiving best-effort service and behave
accordingly. accordingly.
11. Acknowledgments 11. References
The authors would like to thank the following people for their
valuable contributions to this memo: Arnaud Germain, Alexandre
Willeme, Gael Rouvroy, Siegfried Foessel, and Jean-Baptise Lorent.
12. RFC Editor Considerations
Note to RFC Editor: This section may be removed after carrying out
all the instructions of this section.
RFC XXXX is to be replaced by the RFC number this specification
receives when published.
13. References
13.1. Normative References 11.1. Normative References
[ISO21122-1] [ISO21122-1]
International Organization for Standardization (ISO) - ISO/IEC, "Information technology - JPEG XS low-latency
International Electrotechnical Commission (IEC), lightweight image coding system - Part 1: Core coding
"Information technology - JPEG XS low-latency lightweight system", ISO/IEC IS 21122-1.
image coding system - Part 1: Core coding system", ISO/
IEC IS 21122-1.
[ISO21122-2] [ISO21122-2]
International Organization for Standardization (ISO) - ISO/IEC, "Information technology - JPEG XS low-latency
International Electrotechnical Commission (IEC), lightweight image coding system - Part 2: Profiles and
"Information technology - JPEG XS low-latency lightweight buffer models", ISO/IEC IS 21122-2.
image coding system - Part 2: Profiles and buffer models",
ISO/IEC IS 21122-2.
[ISO21122-3] [ISO21122-3]
International Organization for Standardization (ISO) - ISO/IEC, "Information technology - JPEG XS low-latency
International Electrotechnical Commission (IEC), lightweight image coding system - Part 3: Transport and
"Information technology - JPEG XS low-latency lightweight container formats", ISO/IEC IS 21122-3.
image coding system - Part 3: Transport and container
formats", ISO/IEC IS 21122-3.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model [RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model
with Session Description Protocol (SDP)", RFC 3264, with Session Description Protocol (SDP)", RFC 3264,
DOI 10.17487/RFC3264, June 2002, DOI 10.17487/RFC3264, June 2002,
<https://www.rfc-editor.org/info/rfc3264>. <https://www.rfc-editor.org/info/rfc3264>.
skipping to change at page 29, line 18 skipping to change at line 1292
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8866] Begen, A., Kyzivat, P., Perkins, C., and M. Handley, "SDP: [RFC8866] Begen, A., Kyzivat, P., Perkins, C., and M. Handley, "SDP:
Session Description Protocol", RFC 8866, Session Description Protocol", RFC 8866,
DOI 10.17487/RFC8866, January 2021, DOI 10.17487/RFC8866, January 2021,
<https://www.rfc-editor.org/info/rfc8866>. <https://www.rfc-editor.org/info/rfc8866>.
13.2. Informative References 11.2. Informative References
[BT.1886-0]
ITU-R, "Reference electro-optical transfer function for
flat panel displays used in HDTV studio production", ITU-R
Recommendation BT.1886-0, March 2011,
<https://www.itu.int/rec/R-REC-BT.1886-0-201103-I/en>.
[BT.2020-2]
ITU-R, "Parameter values for ultra-high definition
television systems for production and international
programme exchange", ITU-R Recommendation BT.2020-2,
October 2015,
<https://www.itu.int/rec/R-REC-BT.2020-2-201510-I/en>.
[BT.2100-2]
ITU-R, "Image parameter values for high dynamic range
television for use in production and international
programme exchange", ITU-R Recommendation BT.2100-2, July
2018,
<https://www.itu.int/rec/R-REC-BT.2100-2-201807-I/en>.
[BT.601-5] ITU-R, "Studio encoding parameters of digital television
for standard 4:3 and wide screen 16:9 aspect ratios",
ITU-R Recommendation BT.601-5, October 1995,
<https://www.itu.int/rec/R-REC-BT.601-5-199510-S/en>.
[BT.601-7] ITU-R, "Studio encoding parameters of digital television
for standard 4:3 and wide screen 16:9 aspect ratios",
ITU-R Recommendation BT.601-7, March 2011,
<https://www.itu.int/rec/R-REC-BT.601-7-201103-I/en>.
[BT.709-2] ITU-R, "Parameter values for the HDTV standards for
production and international programme exchange", ITU-R
Recommendation BT.709-2, October 1995,
<https://www.itu.int/rec/R-REC-BT.709-2-199510-S/en>.
[BT.709-6] ITU-R, "Parameter values for the HDTV standards for
production and international programme exchange", ITU-R
Recommendation BT.709-6, June 2015,
<https://www.itu.int/rec/R-REC-BT.709-6-201506-I/en>.
[ISO11664-1]
ISO/CIE, "Colorimetry - Part 1: CIE standard colorimetric
observers", ISO/CIE IS 11664-1:2019, June 2019,
<https://www.iso.org/standard/74164.html>.
[RFC3711] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. [RFC3711] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K.
Norrman, "The Secure Real-time Transport Protocol (SRTP)", Norrman, "The Secure Real-time Transport Protocol (SRTP)",
RFC 3711, DOI 10.17487/RFC3711, March 2004, RFC 3711, DOI 10.17487/RFC3711, March 2004,
<https://www.rfc-editor.org/info/rfc3711>. <https://www.rfc-editor.org/info/rfc3711>.
[RFC4175] Gharai, L. and C. Perkins, "RTP Payload Format for [RFC4175] Gharai, L. and C. Perkins, "RTP Payload Format for
Uncompressed Video", RFC 4175, DOI 10.17487/RFC4175, Uncompressed Video", RFC 4175, DOI 10.17487/RFC4175,
September 2005, <https://www.rfc-editor.org/info/rfc4175>. September 2005, <https://www.rfc-editor.org/info/rfc4175>.
skipping to change at page 30, line 5 skipping to change at line 1373
[RFC7202] Perkins, C. and M. Westerlund, "Securing the RTP [RFC7202] Perkins, C. and M. Westerlund, "Securing the RTP
Framework: Why RTP Does Not Mandate a Single Media Framework: Why RTP Does Not Mandate a Single Media
Security Solution", RFC 7202, DOI 10.17487/RFC7202, April Security Solution", RFC 7202, DOI 10.17487/RFC7202, April
2014, <https://www.rfc-editor.org/info/rfc7202>. 2014, <https://www.rfc-editor.org/info/rfc7202>.
[RFC8888] Sarker, Z., Perkins, C., Singh, V., and M. Ramalho, "RTP [RFC8888] Sarker, Z., Perkins, C., Singh, V., and M. Ramalho, "RTP
Control Protocol (RTCP) Feedback for Congestion Control", Control Protocol (RTCP) Feedback for Congestion Control",
RFC 8888, DOI 10.17487/RFC8888, January 2021, RFC 8888, DOI 10.17487/RFC8888, January 2021,
<https://www.rfc-editor.org/info/rfc8888>. <https://www.rfc-editor.org/info/rfc8888>.
[SMPTE-ST2110-21] [SMPTE157] SMPTE, "SMPTE Recommended Practice - Key and Alpha
Society of Motion Picture and Television Engineers, "SMPTE Signals", SMPTE RP 157:2012,
Standard - Professional Media Over Managed IP Networks: DOI 10.1109/ICPST.1998.729044, November 2012,
Traffic Shaping and Delivery Timing for Video", SMPTE ST <https://ieeexplore.ieee.org/document/7290447>.
2110-21:2017, 2017,
<https://doi.org/10.5594/SMPTE.ST2110-21.2017>. [SMPTE2065-1]
SMPTE, "SMPTE Standard - Academy Color Encoding
Specification (ACES)", SMPTE ST 2065-1:2021,
DOI 10.5594/SMPTE.ST2065-1.2021, January 2021,
<https://ieeexplore.ieee.org/document/9343931>.
[SMPTE2065-3]
SMPTE, "SMPTE Standard - Academy Density Exchange Encoding
(ADX) - Encoding Academy Printing Density (APD) Values",
SMPTE ST 2065-3:2020, DOI 10.5594/SMPTE.ST2065-3.2020,
November 2020,
<https://ieeexplore.ieee.org/document/9286953>.
[SMPTE2077]
SMPTE, "SMPTE Recommended Practice - Full-Range Image
Mapping", SMPTE RP 2077:2013,
DOI 10.5594/SMPTE.RP2077.2013, November 2013,
<https://ieeexplore.ieee.org/document/7290588>.
[SMPTE2110-21]
SMPTE, "SMPTE Standard - Professional Media Over Managed
IP Networks: Traffic Shaping and Delivery Timing for
Video", SMPTE ST 2110-21:2017,
DOI 10.5594/SMPTE.ST2110-21.2017, November 2017,
<https://ieeexplore.ieee.org/document/8165971>.
[SMPTE240M]
SMPTE, "SMPTE Standard - For Television - 1125-Line High-
Definition Production Systems - Signal Parameters",
SMPTE ST 240M:1999, DOI 10.5594/SMPTE.ST240.1999, November
1999, <https://ieeexplore.ieee.org/
document/7291461?arnumber=7291461>.
[SMPTE428-1]
SMPTE, "SMPTE Standard - D-Cinema Distribution Master -
Image Characteristics", SMPTE ST 428-1:2019,
DOI 10.5594/SMPTE.ST428-1.2019, March 2019,
<https://ieeexplore.ieee.org/document/8709077>.
Acknowledgments
The authors would like to thank the following people for their
valuable contributions to this memo: Sébastien Lugan, Arnaud Germain,
Alexandre Willème, Gaël Rouvroy, Siegfried Foessel, and Jean-Baptise
Lorent.
Authors' Addresses Authors' Addresses
Sebastien Lugan Tim Bruylants
intoPIX S.A. intoPIX S.A.
Rue Emile Francqui, 9 Rue Emile Francqui, 9
1435 Mont-Saint-Guibert 1435 Mont-Saint-Guibert
Belgium Belgium
Phone: +32 10 23 84 70 Phone: +32 10 23 84 70
Email: rtp@intopix.com Email: t.bruylants@intopix.com
URI: https://www.intopix.com/ URI: https://www.intopix.com/
Antonin Descampe Antonin Descampe
Universite catholique de Louvain Université catholique de Louvain
Place du Levant, 3 - bte L5.03.02 bte L2.03.02
Ruelle de la Lanterne Magique, 14
1348 Louvain-la-Neuve 1348 Louvain-la-Neuve
Belgium Belgium
Phone: +32 10 47 25 97 Phone: +32 10 47 27 87
Email: antonin.descampe@uclouvain.be Email: antonin.descampe@uclouvain.be
URI: https://uclouvain.be/en/research-institutes/icteam URI: https://uclouvain.be/antonin.descampe
Corentin Damman Corentin Damman
intoPIX S.A. intoPIX S.A.
Rue Emile Francqui, 9 Rue Emile Francqui, 9
1435 Mont-Saint-Guibert 1435 Mont-Saint-Guibert
Belgium Belgium
Phone: +32 10 23 84 70 Phone: +32 10 23 84 70
Email: c.damman@intopix.com Email: c.damman@intopix.com
URI: https://www.intopix.com/ URI: https://www.intopix.com/
skipping to change at page 31, line 4 skipping to change at line 1456
Corentin Damman Corentin Damman
intoPIX S.A. intoPIX S.A.
Rue Emile Francqui, 9 Rue Emile Francqui, 9
1435 Mont-Saint-Guibert 1435 Mont-Saint-Guibert
Belgium Belgium
Phone: +32 10 23 84 70 Phone: +32 10 23 84 70
Email: c.damman@intopix.com Email: c.damman@intopix.com
URI: https://www.intopix.com/ URI: https://www.intopix.com/
Thomas Richter Thomas Richter
Fraunhofer IIS Fraunhofer IIS
Am Wolfsmantel 33 Am Wolfsmantel 33
91048 Erlangen 91048 Erlangen
Germany Germany
Phone: +49 9131 776 5126 Phone: +49 9131 776 5126
Email: thomas.richter@iis.fraunhofer.de Email: thomas.richter@iis.fraunhofer.de
URI: https://www.iis.fraunhofer.de/ URI: https://www.iis.fraunhofer.de/
Tim Bruylants
intoPIX S.A.
Rue Emile Francqui, 9
1435 Mont-Saint-Guibert
Belgium
Phone: +32 10 23 84 70
Email: t.bruylants@intopix.com
URI: https://www.intopix.com/
 End of changes. 162 change blocks. 
400 lines changed or deleted 474 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/