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

Antonin Descampe <a.descampe@intopix.com> Wed, 08 April 2020 21:28 UTC

Return-Path: <a.descampe@intopix.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 698EF3A17BE for <avt@ietfa.amsl.com>; Wed, 8 Apr 2020 14:28:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yJC-wXUc946A for <avt@ietfa.amsl.com>; Wed, 8 Apr 2020 14:27:59 -0700 (PDT)
Received: from mailwdc.intopix.com (mailwdc.intopix.com [212.166.5.108]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD0563A17BB for <avt@ietf.org>; Wed, 8 Apr 2020 14:27:58 -0700 (PDT)
Received: from IPX-MAIL.Intopix.com ([172.30.30.1]) by IPX-MAIL.Intopix.com ([172.30.30.1]) with mapi id 14.03.0487.000; Wed, 8 Apr 2020 23:27:56 +0200
From: Antonin Descampe <a.descampe@intopix.com>
To: "avt@ietf.org" <avt@ietf.org>
Thread-Topic: [AVTCORE] I-D Action: draft-ietf-payload-rtp-jpegxs-03.txt
Thread-Index: AQHWDewr83W1g/uU1UyNLmvCW0f6Tqhvm8EA
Date: Wed, 8 Apr 2020 21:27:55 +0000
Message-ID: <B9AA27D5-FF46-4C4D-804F-9685A01CC95D@intopix.com>
References: <158638108441.24392.9320385311889759632@ietfa.amsl.com>
In-Reply-To: <158638108441.24392.9320385311889759632@ietfa.amsl.com>
Accept-Language: fr-FR, fr-BE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [81.240.62.237]
x-tm-as-product-ver: SMEX-11.7.0.1024-8.500.1020-25342.004
x-tm-as-result: No--15.426700-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: multipart/alternative; boundary="_000_B9AA27D5FF464C4D804F9685A01CC95Dintopixcom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/WG47fiSLR8RvYphlBBGllCTkOOc>
Subject: Re: [AVTCORE] I-D Action: draft-ietf-payload-rtp-jpegxs-03.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Apr 2020 21:28:02 -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 2, a number of changes have been brought to the document, which I summarise hereunder:

- 2 different possible packetization modes: one based on JPEG XS slices and one based on JPEG XS codestream. The later has been introduced because we needed a packetization mode implying very little processing in a « trans-capsulation » use case.  For instance, when switching from MPEG-2 TS to ST2110-22, we needed a way to packetise that would *not* involve any parsing of the codestream, so as to minimise the processing required by such system translating from one encapsulation to the other. This codestream-based packetization also automatically ensure to fulfil the ST2110-22 requirements of having the same amount of bytes and the same amount of RTP packets per frame. We did leave the slice-based packetization as well as it can be useful in certain use cases and if RTP packets are sent out-of-order by the transmitter (which can be relevant for some implementations of a full SW workflow). Note however that in the slice-based packetization, additional constraint need to be set at rate allocation stage to fulfil ST2110-22 requirements mentioned above.
- A bit indicating if the transmitter has sent the packets in sequential order. If packets have been sent out-of-order, the slice-based packetization is required to be used.
- Explicit support for interlace video
- Re-inclusion of EOC marker to keep the JPEG XS codestream consistent and self-contained.

Thanks to these changes, the transport of JPEG XS over RTP inherently gives the following guarantees:
1. Constant number of bytes and number of packets per frame (ST2110-22).
2. No transcoding or deep codestream inspection when changing the encapsulation (see codestream-packetization explanation above).
3. Low-latency behaviour.
4. No quality loss induced by the transport
5. Low complex HW and fast SW decoding.

Please provide your comments or questions, if any.

Kind regards,

Antonin

Le 8 avr. 2020 à 23:24, internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> 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-03.txt
Pages           : 23
Date            : 2020-04-08

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:
https://datatracker.ietf.org/doc/draft-ietf-payload-rtp-jpegxs/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-payload-rtp-jpegxs-03
https://datatracker.ietf.org/doc/html/draft-ietf-payload-rtp-jpegxs-03

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-payload-rtp-jpegxs-03


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


_______________________________________________
Audio/Video Transport Core Maintenance
avt@ietf.org
https://www.ietf.org/mailman/listinfo/avt

--
Antonin Descampe - Ph.D.
Compression technologist

IntoPIX s.a.
+32 10 23 84 70 (Office)
a.descampe@intopix.com<mailto:a.descampe@intopix.com>

CONFIDENTIALITY NOTICE: Unless otherwise explicitly or implictly stated, this email message and any of its attachments are the property of intoPIX SA and are strictly confidential.
If you are an unintended recipient, please notify the sender immediately.