| avtcore | S. Lugan |
| Internet-Draft | A. Descampe |
| Intended status: Standards Track | C. Damman |
| Expires: January 30, 2021 | intoPIX |
| T. Richter | |
| IIS | |
| A. Willeme | |
| UCL/ICTEAM | |
| July 29, 2020 |
RTP Payload Format for ISO/IEC 21122 (JPEG XS)
draft-ietf-payload-rtp-jpegxs-04
This document specifies a Real-Time Transport Protocol (RTP) payload format to be used for transporting JPEG XS (ISO/IEC 21122) encoded video. JPEG XS is a low-latency, lightweight image coding system. Compared to an uncompressed video use case, it allows higher resolutions and frame rates, while offering visually lossless quality, reduced power consumption, and end-to-end latency confined to a fraction of a frame.
This Internet-Draft is submitted in full conformance with the 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 and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 30, 2021.
Copyright (c) 2020 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
This document specifies a payload format for packetization of JPEG XS encoded video signals into the Real-time Transport Protocol (RTP).
The JPEG XS coding system offers compression and recompression of image sequences with very moderate computational resources while remaining robust under multiple compression and decompression cycles and mixing of content sources, e.g. embedding of subtitles, overlays or logos. Typical target compression ratios ensuring visually lossless quality are in the range of 2:1 to 10:1, depending on the nature of the source material. The end-to-end latency can be confined to a fraction of a frame, typically between a small number of lines down to below a single line.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
JPEG XS is a low-latency lightweight image coding system for coding continuous-tone grayscale or continuous-tone colour digital images.
This coding system provides an efficient representation of image signals through the mathematical tool of wavelet analysis. The wavelet filter process separates each component into multiple bands, where each band consists of multiple coefficients describing the image signal of a given component within a frequency domain specific to the wavelet filter type, i.e. the particular filter corresponding to the band.
Wavelet coefficients are grouped into precincts, where each precinct includes all coefficients over all bands that contribute to a spatial region of the image.
One or multiple precincts are furthermore combined into slices consisting of an integer number of precincts. Precincts do not cross slice boundaries, and wavelet coefficients in precincts that are part of different slices can be decoded independently from each other. Note, however, that the wavelet transformation runs across slice boundaries. A slice always extends over the full width of the image, but may only cover parts of its height.
A JPEG XS codestream header, followed by several slices, and terminated by an EOC marker form a JPEG XS codestream.
The overall codestream format, including the definition of all markers, is further defined in ISO/IEC 21122-1. It represents sample values of a single image, bare any interpretation relative to a colour space.
While the information defined in the codestream is sufficient to reconstruct the sample values of one image, the interpretation of the samples remains undefined by the codestream itself. This interpretation is given by the video support box and the colour specification box which contain significant information to correctly play the JPEG XS stream. The layout and syntax of these boxes, together with their content, are defined in ISO/IEC 21122-3. The video support box provides information on the maximum bitrate, the frame rate, the subsampling image format, the timecode of the current JPEG XS frame, the profile, level and sublevel used (as defined in ISO/IEC 21122-2), and optionally on the buffer model and the mastering display metadata. The colour specification box indicates the colour primaries, transfer characteristics, matrix coefficients and video full range flag needed to specify the colour space of the video stream.
The concatenation of a video support box, a colour specification box and a JPEG XS codestream forms a JPEG XS picture segment. In the case of a video stream made of progressive frames, each frame is made of one single JPEG XS picture segment. In the case of a video stream made of interlaced frames, each frame is made of two concatenated JPEG XS picture segments. The codestream of each segment corresponds to a field of the interlaced frame. The boxes in the first segment SHALL be equal to the boxes in the second segment. Note that the video information box included in each video support box contains a frat field indicating if the frame is progressive or interlaced, and, in case of interlaced frame, if the top field (i.e. the field containing the top line of the frame) is in the first or second segment (see ISO/IEC 21122-3).
This section specifies the payload format for JPEG XS streams over the Real-time Transport Protocol (RTP).
In order to be transported over RTP, each JPEG XS stream is transported in a distinct RTP stream, identified by a distinct SSRC.
A JPEG XS stream is divided into Application Data Units (ADUs), each ADU corresponding to a single JPEG XS frame.
An ADU is made of several packetization units. If a packetization unit is bigger than the maximum size of a RTP packet payload, the unit is split into multiple RTP packet payloads, as illustrated in Figure 1. As seen there, each packet SHALL contain (part of) one and only one packetization unit. A packetization unit may extend over multiple packets. The payload of every packet SHALL have the same size (based e.g. on the Maximum Transfer Unit of the network), except (possibly) the last packet of a packetization unit. The boundaries of a packetization unit SHALL coincide with the boundaries of the payload of a packet (excluding the payload header), i.e. the first (resp. last) byte of the packetization unit SHALL be the first (resp. last) byte of the payload (excluding its header).
RTP +-----+------------------------+
Packet #1 | Hdr | Packetization unit #1 |
+-----+------------------------+
RTP +-----+--------------------------------------+
Packet #2 | Hdr | Packetization unit #2 |
+-----+--------------------------------------+
RTP +-----+--------------------------------------------------+
Packet #3 | Hdr | Packetization unit #3 (part 1/3) |
+-----+--------------------------------------------------+
RTP +-----+--------------------------------------------------+
Packet #4 | Hdr | Packetization unit #3 (part 2/3) |
+-----+--------------------------------------------------+
RTP +-----+----------------------------------------------+
Packet #5 | Hdr | Packetization unit #3 (part 3/3) |
+-----+----------------------------------------------+
...
RTP +-----+-----------------------------------------+
Packet #P | Hdr | Packetization unit #N (part q/q) |
+-----+-----------------------------------------+
Figure 1: Example of ADU packetization
There are two different packetization modes defined for this RTP payload format.
RTP +-----+--------------------------------------------------+
Packet #1 | Hdr | VS box + CS box + JPEG XS codestream (part 1/q) |
+-----+--------------------------------------------------+
RTP +-----+--------------------------------------------------+
Packet #2 | Hdr | JPEG XS codestream (part 2/q) |
+-----+--------------------------------------------------+
...
RTP +-----+--------------------------------------+
Packet #P | Hdr | JPEG XS codestream (part q/q) |
+-----+--------------------------------------+
Figure 2: Example of codestream packetization mode
RTP +-----+----------------------------+
Packet #1 | Hdr | JPEG XS header segment |
+-----+----------------------------+
RTP +-----+--------------------------------------------------+
Packet #2 | Hdr | Slice #1 (part 1/2) |
+-----+--------------------------------------------------+
RTP +-----+-------------------------------------------+
Packet #3 | Hdr | Slice #1 (part 2/2) |
+-----+-------------------------------------------+
RTP +-----+--------------------------------------------------+
Packet #4 | Hdr | Slice #2 (part 1/3) |
+-----+--------------------------------------------------+
...
RTP +-----+---------------------------------------+
Packet #P | Hdr | Slice #N (part q/q) + EOC marker |
+-----+---------------------------------------+
Figure 3: Example of slice packetization mode
Thanks to the constant bit-rate of JPEG XS, the codestream packetization mode guarantees that a JPEG XS RTP stream will produce a constant number of bytes per frame, and a constant number of RTP packets per frame. To reach the same guarantee with the slice packetization mode, an additional mechanism needs to be put in place. This can involve a constraint at the rate allocation stage in the JPEG XS encoder to impose a constant bit-rate at the slice level, the usage of padding data, or the insertion of empty RTP packets (i.e. a RTP packet whose payload data is empty).
The format of the RTP header is specified in RFC 3550 and reprinted in Figure 4 for convenience. This RTP payload format uses the fields of the header in a manner consistent with that specification.
The RTP payload (and the settings for some RTP header bits) for packetization units are specified in Section 4.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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| V |P|X| CC |M| PT | sequence number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| timestamp |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| synchronization source (SSRC) identifier |
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
| contributing source (CSRC) identifiers |
| .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: RTP header according to RFC 3550
The version (V), padding (P), extension (X), CSRC count (CC), sequence number, synchronization source (SSRC) and contributing source (CSRC) fields follow their respective definitions in RFC 3550.
The remaining RTP header information to be set according to this RTP payload format is set as follows:
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 illustrates the structure of this payload header.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|T|K|L| I |F counter| SEP counter | P counter |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 5: Payload header
The payload header consists of the following fields:
The payload data of a JPEG XS RTP stream consists of a concatenation of multiple JPEG XS frames.
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 for a progressive frame in the codestream packetization mode, Figure 7 depicts this layout for an interlaced frame in the codestream packetization mode, Figure 8 depicts this layout for a progressive frame in the slice packetization mode and Figure 9 depicts this layout for an interlaced frame in the slice packetization mode. The Frame counter value is not indicated because the value is constant for all packetization units of a given frame.
+=====[ Packetization unit (PU) #1 ]====+
| Video support box | SEP counter = 0
| +---------------------------------+ | P counter = 0
| : Sub boxes of the VS box : |
| +---------------------------------+ |
+- - - - - - - - - - - - - - - - - - - -+
| Colour specification box |
| +---------------------------------+ |
| : Fields of the CS box : |
| +---------------------------------+ |
+- - - - - - - - - - - - - - - - - - - -+
| JPEG XS codestream |
: (part 1/q) : M=0, K=0, L=0, I=00
+---------------------------------------+
| JPEG XS codestream | SEP counter = 0
| (part 2/q) | P counter = 1
: : M=0, K=0, L=0, I=00
+---------------------------------------+
| JPEG XS codestream | SEP counter = 0
| (part 3/q) | P counter = 2
: : M=0, K=0, L=0, I=00
+---------------------------------------+
: :
+---------------------------------------+
| JPEG XS codestream | SEP counter = 1
| (part 2049/q) | P counter = 0
: : M=0, K=0, L=0, I=00
+---------------------------------------+
: :
+---------------------------------------+
| JPEG XS codestream | SEP counter = (q-1) div 2048
| (part q/q) | P counter = (q-1) mod 2048
: : M=1, K=0, L=1, I=00
+=======================================+
Figure 6: Example of JPEG XS Payload Data (codestream packetization mode, progressive frame)
+=====[ Packetization unit (PU) #1 ]====+
| Video support box | SEP counter = 0
+- - - - - - - - - - - - - - - - - - - -+ P counter = 0
| Colour specification box |
+- - - - - - - - - - - - - - - - - - - -+
| JPEG XS codestream (1st field) |
: (part 1/q) : M=0, K=0, L=0, I=10
+---------------------------------------+
| JPEG XS codestream (1st field) | SEP counter = 0
| (part 2/q) | P counter = 1
: : M=0, K=0, L=0, I=10
+---------------------------------------+
: :
+---------------------------------------+
| JPEG XS codestream (1st field) | SEP counter = 1
| (part 2049/q) | P counter = 0
: : M=0, K=0, L=0, I=10
+---------------------------------------+
: :
+---------------------------------------+
| JPEG XS codestream (1st field) | SEP counter = (q-1) div 2048
| (part q/q) | P counter = (q-1) mod 2048
: : M=0, K=0, L=1, I=10
+===============[ PU #2 ]===============+
| Video support box | SEP counter = 0
+- - - - - - - - - - - - - - - - - - - -+ P counter = 0
| Colour specification box |
+- - - - - - - - - - - - - - - - - - - -+
| JPEG XS codestream (2nd field) |
| (part 1/q) |
: : M=0, K=0, L=0, I=11
+---------------------------------------+
| JPEG XS codestream (2nd field) | SEP counter = 0
| (part 2/q) | P counter = 1
: : M=0, K=0, L=0, I=11
+---------------------------------------+
: :
+---------------------------------------+
| JPEG XS codestream (2nd field) | SEP counter = (q-1) div 2048
| (part q/q) | P counter = (q-1) mod 2048
: : M=1, K=0, L=1, I=11
+=======================================+
Figure 7: Example of JPEG XS Payload Data (codestream packetization mode, interlaced frame)
+===[ PU #1: JPEG XS Header segment ]===+
| Video support box | SEP counter = 0x07FF
+- - - - - - - - - - - - - - - - - - - -+ P counter = 0
| Colour specification box |
+- - - - - - - - - - - - - - - - - - - -+
| JPEG XS codestream header |
| +---------------------------------+ |
| : Markers and marker segments : |
| +---------------------------------+ | M=0, T=0, K=1, L=1, I=00
+==========[ PU #2: Slice #1 ]==========+
| +---------------------------------+ | SEP counter = 0
| | SLH Marker | | P counter = 0
| +---------------------------------+ |
| : Entropy Coded Data : |
| +---------------------------------+ | M=0, T=0, K=1, L=1, I=00
+==========[ PU #3: Slice #2 ]==========+
| Slice #2 | SEP counter = 1
| (part 1/q) | P counter = 0
: : M=0, T=0, K=1, L=0, I=00
+---------------------------------------+
| Slice #2 | SEP counter = 1
| (part 2/q) | P counter = 1
: : M=0, T=0, K=1, L=0, I=00
+---------------------------------------+
: :
+---------------------------------------+
| Slice #2 | SEP counter = 1
| (part q/q) | P counter = q-1
: : M=0, T=0, K=1, L=1, I=00
+=======================================+
: :
+========[ PU #N: Slice #(N-1) ]========+
| Slice #(N-1) | SEP counter = N-2
| (part 1/r) | P counter = 0
: : M=0, T=0, K=1, L=0, I=00
+---------------------------------------+
: :
+---------------------------------------+
| Slice #(N-1) | SEP counter = N-2
| (part r/r) | P counter = r-1
: + EOC marker : M=1, T=0, K=1, L=1, I=00
+=======================================+
Figure 8: Example of JPEG XS Payload Data (slice packetization mode, progressive frame)
+====[ PU #1: JPEG XS Hdr segment 1 ]===+
| Video support box | SEP counter = 0x07FF
+- - - - - - - - - - - - - - - - - - - -+ P counter = 0
| Colour specification box |
+- - - - - - - - - - - - - - - - - - - -+
| JPEG XS codestream header 1 |
| +---------------------------------+ |
| : Markers and marker segments : |
| +---------------------------------+ | M=0, T=0, K=1, L=1, I=10
+====[ PU #2: Slice #1 (1st field) ]====+
| +---------------------------------+ | SEP counter = 0
| | SLH Marker | | P counter = 0
| +---------------------------------+ |
| : Entropy Coded Data : |
| +---------------------------------+ | M=0, T=0, K=1, L=1, I=10
+====[ PU #3: Slice #2 (1st field) ]====+
| Slice #2 | SEP counter = 1
| (part 1/q) | P counter = 0
: : M=0, T=0, K=1, L=0, I=10
+---------------------------------------+
| Slice #2 | SEP counter = 1
| (part 2/q) | P counter = 1
: : M=0, T=0, K=1, L=0, I=10
+---------------------------------------+
: :
+---------------------------------------+
| Slice #2 | SEP counter = 1
| (part q/q) | P counter = q-1
: : M=0, T=0, K=1, L=1, I=10
+=======================================+
: :
+==[ PU #N: Slice #(N-1) (1st field) ]==+
| Slice #(N-1) | SEP counter = N-2
| (part 1/r) | P counter = 0
: : M=0, T=0, K=1, L=0, I=10
+---------------------------------------+
: :
+---------------------------------------+
| Slice #(N-1) | SEP counter = N-2
| (part r/r) | P counter = r-1
: + EOC marker : M=0, T=0, K=1, L=1, I=10
+=======================================+
+===[ PU #N+1: JPEG XS Hdr segment 2 ]==+
| Video support box | SEP counter = 0x07FF
+- - - - - - - - - - - - - - - - - - - -+ P counter = 0
| Colour specification box |
+- - - - - - - - - - - - - - - - - - - -+
| JPEG XS codestream header 2 |
| +---------------------------------+ |
| : Markers and marker segments : |
| +---------------------------------+ | M=0, T=0, K=1, L=1, I=11
+===[ PU #N+2: Slice #1 (2nd field) ]===+
| +---------------------------------+ | SEP counter = 0
| | SLH Marker | | P counter = 0
| +---------------------------------+ |
| : Entropy Coded Data : |
| +---------------------------------+ | M=0, T=0, K=1, L=1, I=11
+===[ PU #N+3: Slice #2 (2nd field) ]===+
| Slice #2 | SEP counter = 1
| (part 1/s) | P counter = 0
: : M=0, T=0, K=1, L=0, I=11
+---------------------------------------+
| Slice #2 | SEP counter = 1
| (part 2/s) | P counter = 1
: : M=0, T=0, K=1, L=0, I=11
+---------------------------------------+
: :
+---------------------------------------+
| Slice #2 | SEP counter = 1
| (part s/s) | P counter = s-1
: : M=0, T=0, K=1, L=1, I=11
+=======================================+
: :
+==[ PU #2N: Slice #(N-1) (2nd field) ]=+
| Slice #(N-1) | SEP counter = N-2
| (part 1/t) | P counter = 0
: : M=0, T=0, K=1, L=0, I=11
+---------------------------------------+
: :
+---------------------------------------+
| Slice #(N-1) | SEP counter = N-2
| (part t/t) | P counter = t-1
: + EOC marker : M=1, T=0, K=1, L=1, I=11
+=======================================+
Figure 9: Example of JPEG XS Payload Data (slice packetization mode, interlaced frame)
The traffic shaping and delivery timing SHALL be in accordance with the Network Compatibility Model compliance definitions specified in SMPTE ST 2110-21 for either Narrow Linear Senders (Type NL) or Wide Senders (Type W). The session description SHALL include a format-specific parameter of either TP=2110TPNL or TP=2110TPW to indicate compliance with Type NL or Type W respectively.
NOTE: The Virtual Receiver Buffer Model compliance definitions of ST 2110-21 do not apply.
Congestion control for RTP SHALL be used in accordance with RFC 3550, and with any applicable RTP profile: e.g., RFC 3551. An additional requirement if best-effort service is being used is users of this payload format MUST monitor packet loss to ensure that the packet loss rate is within acceptable parameters. Circuit Breakers is an update to RTP that defines criteria for when one is required to stop sending RTP Packet Streams and applications implementing this standard MUST comply with it. RFC 8085 provides additional information on the best practices for applying congestion control to UDP streams.
YCbCr-4:4:4 (4:4:4 sampling)
YCbCr-4:2:2 (4:2:2 sampling)
YCbCr-4:2:0 (4:2:0 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)
ICtCp-4:4:4 (4:4:4 sampling)
ICtCp-4:2:2 (4:2:2 sampling)
ICtCp-4:2:0 (4:2:0 sampling)
RGB RGB or R' G' B' samples
XYZ X' Y' Z' samples
KEY samples of the key signal
BT601-5 ITU Recommendation BT.601-5
BT709-2 ITU Recommendation BT.709-2
SMPTE240M SMPTE standard 240M
BT601 as specified in Recommendation ITU-R BT.601-7
BT709 as specified in Recommendation ITU-R BT.709-6
BT2020 as specified in Recommendation ITU-R BT.2020-2
BT2100 as specified in Recommendation ITU-R BT.2100
Table 2 titled "System colorimetry"
ST2065-1 as specified in SMPTE ST 2065-1 Academy Color
Encoding Specification (ACES)
ST2065-3 as specified for Academy Density Exchange
Encoding (ADX) in SMPTE ST 2065-3
XYZ as specified in ISO 11664-1 section titled
"1931 Observer"
SDR (Standard Dynamic Range) Video streams of standard
dynamic range, that utilize the OETF of Recommendation
ITU-R BT.709 or Recommendation ITU-R BT.2020. Such
streams SHALL be assumed to target the EOTF specified
in ITU-R BT.1886.
PQ Video streams of high dynamic range video that utilize
the Perceptual Quantization system of Recommendation
ITU-R BT.2100
HLG Video streams of high dynamic range video that utilize
the Hybrid Log-Gamma system of Recommendation ITU-R
BT.2100
A Session Description Protocol (SDP) object SHALL be created for each RTP stream and it SHALL be in accordance with the provisions of SMPTE ST 2110-10.
The information carried in the media type specification has a specific mapping to fields in the Session Description Protocol (SDP), which is commonly used to describe RTP sessions. This information is redundant with the information found in the payload data (namely, in the JPEG XS header segment) and SHALL be consistent with it. In case of discrepancy between parameters values found in the payload data and in the SDP fields, the values from the payload data SHALL prevail.
The media type ("video") goes in SDP "m=" as the media name.
The media subtype ("jxsv") goes in SDP "a=rtpmap" as the encoding name, followed by a slash ("/") and the required parameter "rate" corresponding to the RTP timestamp clock rate (which for the payload format defined in this document SHOULD be 90000). The required parameter "transmode" and the additional optional parameters go in the SDP "a=fmtp" attribute by copying them directly from the MIME media type string as a semicolon-separated list of parameter=value pairs.
m=video 30000 RTP/AVP 112
a=rtpmap:112 jxsv/90000
a=fmtp:112 transmode=1;sampling=YCbCr-4:2:2;width=1920;height=1080;
depth=10;colorimetry=BT709;TCS=SDR;
RANGE=FULL;TP=2110TPNL
A sample SDP mapping for JPEG XS video is as follows:
In this example, a JPEG XS RTP stream is being sent to UDP 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 wrapped to fit this page, and will be a single long line in the SDP file.
The SDP object SHALL include the TP parameter (either 2110TPNL or 2110TPW as specified in Section 4.5) and may include the CMAX parameter as specified in SMPTE ST 2110-21.
The following considerations apply when using SDP offer/answer procedures to negotiate the use of the JPEG XS payload in RTP:
This memo requests that IANA registers video/jxsv as specified in Section 6.1. The media type is also requested to be added to the IANA registry for "RTP Payload Format MIME types".
RTP packets using the payload format defined in this specification are subject to the security considerations discussed in the RTP specification and in any applicable RTP profile such as RTP/AVP, RTP/AVPF, RTP/SAVP, or RTP/SAVPF. This implies that confidentiality of the media streams is achieved by encryption.
However, as "Securing the RTP Framework: Why RTP Does Not Mandate a Single Media Security Solution" discusses, it is not an RTP payload format's responsibility to discuss or mandate what solutions are used to meet the basic security goals like confidentiality, integrity, and source authenticity for RTP in general. This responsibility lies on anyone using RTP in an application. They can find guidance on available security mechanisms and important considerations in "Options for Securing RTP Sessions". Applications SHOULD use one or more appropriate strong security mechanisms.
This payload format and the JPEG XS encoding do not exhibit any substantial non-uniformity, either in output or in complexity to perform the decoding operation and thus are unlikely to pose a denial-of-service threat due to the receipt of pathological datagrams.
It is important to note that HD or UHDTV JPEG XS-encoded video can have significant bandwidth requirements (typically more than 1 Gbps for ultra high-definition video, especially if using high framerate). This is sufficient 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 payload format MUST monitor packet loss to ensure that the packet loss rate is within acceptable parameters. Packet loss is considered acceptable if a TCP flow across the same network path, and experiencing the same network conditions, would achieve an average throughput, measured on a reasonable timescale, that is not less than the RTP flow is achieving. This condition can be satisfied by implementing congestion control mechanisms to adapt the transmission rate (or the number of layers subscribed for a layered multicast session), or by arranging for a receiver to leave the session if the loss rate is unacceptably high.
This payload format may also be used in networks that provide quality-of-service guarantees. If enhanced service is being used, receivers SHOULD monitor packet loss to ensure that the service that was requested is actually being delivered. If it is not, then they SHOULD assume that they are receiving best-effort service and behave accordingly.
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.
| [RFC4175] | Gharai, L. and C. Perkins, "RTP Payload Format for Uncompressed Video", RFC 4175, DOI 10.17487/RFC4175, September 2005. |
| [RFC4585] | Ott, J., Wenger, S., Sato, N., Burmeister, C. and J. Rey, "Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF)", RFC 4585, DOI 10.17487/RFC4585, July 2006. |
| [RFC5124] | Ott, J. and E. Carrara, "Extended Secure RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/SAVPF)", RFC 5124, DOI 10.17487/RFC5124, February 2008. |
| [RFC7201] | Westerlund, M. and C. Perkins, "Options for Securing RTP Sessions", RFC 7201, DOI 10.17487/RFC7201, April 2014. |
| [RFC7202] | Perkins, C. and M. Westerlund, "Securing the RTP Framework: Why RTP Does Not Mandate a Single Media Security Solution", RFC 7202, DOI 10.17487/RFC7202, April 2014. |