Re: [AVTCORE] I-D Action: draft-ietf-payload-rtp-jpegxs-04.txt

Antonin Descampe <> Wed, 29 July 2020 11:53 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0F8563A09BD for <>; Wed, 29 Jul 2020 04:53:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 6sLVWY_q9Ba1 for <>; Wed, 29 Jul 2020 04:53:18 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 5E8F93A09B8 for <>; Wed, 29 Jul 2020 04:53:18 -0700 (PDT)
X-Virus-Scanned: Proofpoint Essentials engine
Received: from ( []) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (PPE Hosted ESMTP Server) with ESMTPS id 35FAF280066 for <>; Wed, 29 Jul 2020 11:53:15 +0000 (UTC)
Received: from ([]) by ([]) with mapi id 14.03.0487.000; Wed, 29 Jul 2020 13:53:15 +0200
From: Antonin Descampe <>
To: "" <>
Thread-Topic: [AVTCORE] I-D Action: draft-ietf-payload-rtp-jpegxs-04.txt
Thread-Index: AQHWZZ5WOcjbE0pflk+TnLp2QsK2vqkeUOmA
Date: Wed, 29 Jul 2020 11:53:14 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: fr-FR, fr-BE, en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-ID: <>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MDID: 1596023596-S-Eok-GlZEk9
Archived-At: <>
Subject: Re: [AVTCORE] I-D Action: draft-ietf-payload-rtp-jpegxs-04.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 29 Jul 2020 11:53:21 -0000

Dear all,

As the notification you received indicates, a new version of the RTP payload format for ISO/IEC 21122 (JPEG XS) has been submitted.

Compared to version 3, a number of changes have been brought to the document, which I summarise hereunder:

* Section 3.4:  In case of interlaced frames, video support box and color spec box are now duplicated in front of each field: although the boxes are the same for both fields, it simplifies implementation and the overhead is negligible. For this purpose, we did define a « JPEG XS picture segment » as the concatenation of a VS box, a CS box and a JPEG XS codestream.
* Section 4.1: we added some suggestions about the usage of padding data or empty RTP packets in case the slice packetization mode is used.
* Section 4.3: In the interlace scenario, we renamed « interlace_mode » field in payload header to « interlace_information »  to distinguish it from the interlace_mode of the frat field in the video information box. Note that the frat field indicates whether the first or the second field is the top field, while the interlace information in the payload header simply indicates if the payload data belongs to the first or second field. 
* Sections 4.2 and 4.3: We separated the description of the RTP header (equal to the one described in RFC3550) from the description of the payload header. This does not change the actual syntax, but it is more consistent with other RFC. It also slightly modifies the definition of packetization unit.
* Section 4.4: We added examples for the 2 transmission modes (codestream/slice) and the 2 scanning cases (progressive/interlace) => 4 examples in total
* Section 6.1: We renamed the required parameter « transmission mode » to « transmode » to avoid white space
* Section 6.2.1: note added indicating that in case of discrepancy between parameters found in the payload and in the SDP fields, parameters from the payload shall prevail.
* Section 6.2.2: transmode parameter has been moved to the fmtp parameter line (comment from Jonathan Lennox).
* References have been updated

There is still an ongoing work on Section 6.1 (Media Type Definition) and 6.2 (SDP mapping) as the parameters signalling needs to be made consistent with the signalling found in the boxes included in the payload data (JPEG XS header segment). A note has already been added indicating the precedence of payload parameters over SDP parameters, as mentioned above. In any case, This is currently being solved but we wanted to already provide this new version.

Please provide your comments or questions, if any.

Kind regards,


> Le 29 juil. 2020 à 13:47, a écrit :
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Audio/Video Transport Core Maintenance WG of the IETF.
>        Title           : RTP Payload Format for ISO/IEC 21122 (JPEG XS)
>        Authors         : Sébastien Lugan
>                          Antonin Descampe
>                          Corentin Damman
>                          Thomas Richter
>                          Alexandre Willeme
> 	Filename        : draft-ietf-payload-rtp-jpegxs-04.txt
> 	Pages           : 27
> 	Date            : 2020-07-29
> Abstract:
>   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.
> The IETF datatracker status page for this draft is:
> There are also htmlized versions available at:
> A diff from the previous version is available at:
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at
> Internet-Drafts are also available by anonymous FTP at:
> _______________________________________________
> Audio/Video Transport Core Maintenance