[payload] RFC 8450 on RTP Payload Format for VC-2 High Quality (HQ) Profile
rfc-editor@rfc-editor.org Fri, 05 October 2018 23:49 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: payload@ietfa.amsl.com
Delivered-To: payload@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99CCD12D7EA; Fri, 5 Oct 2018 16:49:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 NxWtSCzrVllP; Fri, 5 Oct 2018 16:49:54 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1879129C6B; Fri, 5 Oct 2018 16:49:54 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id DA2CCB80050; Fri, 5 Oct 2018 16:49:42 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, payload@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20181005234942.DA2CCB80050@rfc-editor.org>
Date: Fri, 05 Oct 2018 16:49:42 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/payload/U3JS007nX07k85VZ3dQzuMxCtWE>
Subject: [payload] RFC 8450 on RTP Payload Format for VC-2 High Quality (HQ) Profile
X-BeenThere: payload@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Audio/Video Transport Payloads working group discussion list <payload.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/payload>, <mailto:payload-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/payload/>
List-Post: <mailto:payload@ietf.org>
List-Help: <mailto:payload-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/payload>, <mailto:payload-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Oct 2018 23:49:57 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8450
Title: RTP Payload Format for VC-2
High Quality (HQ) Profile
Author: J. Weaver
Status: Standards Track
Stream: IETF
Date: October 2018
Mailbox: james.barrett@bbc.co.uk
Pages: 24
Characters: 51777
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-payload-rtp-vc2hq-08.txt
URL: https://www.rfc-editor.org/info/rfc8450
DOI: 10.17487/RFC8450
This memo describes an RTP payload format for the High Quality (HQ)
profile of Society of Motion Picture and Television Engineers
Standard ST 2042-1, known as VC-2. This document describes the
transport of HQ Profile VC-2 in RTP packets and has applications for
low-complexity, high-bandwidth streaming of both lossless and lossy
compressed video.
The HQ profile of VC-2 is intended for low-latency video compression
(with latency potentially on the order of lines of video) at high
data rates (with compression ratios on the order of 2:1 or 4:1).
This document is a product of the Audio/Video Transport Payloads 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