[AVTCORE] RFC 9134 on RTP Payload Format for ISO/IEC 21122 (JPEG XS)
rfc-editor@rfc-editor.org Thu, 28 October 2021 23:35 UTC
Return-Path: <wwwrun@rfc-editor.org>
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 9AD703A13AC; Thu, 28 Oct 2021 16:35:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-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 rIdaTPwdhSaO; Thu, 28 Oct 2021 16:35:44 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98F9F3A13A5; Thu, 28 Oct 2021 16:35:44 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 499) id 8A9E2E535D; Thu, 28 Oct 2021 16:35:44 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, avt@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20211028233544.8A9E2E535D@rfc-editor.org>
Date: Thu, 28 Oct 2021 16:35:44 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/bVmQtlMqK_3Xf_X9J8CRysXGu5E>
Subject: [AVTCORE] RFC 9134 on RTP Payload Format for ISO/IEC 21122 (JPEG XS)
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: Thu, 28 Oct 2021 23:35:50 -0000
A new Request for Comments is now available in online RFC libraries. RFC 9134 Title: RTP Payload Format for ISO/IEC 21122 (JPEG XS) Author: T. Bruylants, A. Descampe, C. Damman, T. Richter Status: Standards Track Stream: IETF Date: October 2021 Mailbox: t.bruylants@intopix.com, antonin.descampe@uclouvain.be, c.damman@intopix.com, thomas.richter@iis.fraunhofer.de Pages: 27 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-payload-rtp-jpegxs-18.txt URL: https://www.rfc-editor.org/info/rfc9134 DOI: 10.17487/RFC9134 This document specifies a Real-Time Transport Protocol (RTP) payload format to be used for transporting video encoded with JPEG XS (ISO/IEC 21122). JPEG XS is a low-latency, lightweight image coding system. Compared to an uncompressed video use case, it allows higher resolutions and video frame rates while offering visually lossless quality, reduced power consumption, and encoding-decoding latency confined to a fraction of a video frame. This document is a product of the Audio/Video Transport Core Maintenance Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC