[payload] RFC 7741 on RTP Payload Format for VP8 Video
rfc-editor@rfc-editor.org Thu, 24 March 2016 20:59 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 9447D12D81F; Thu, 24 Mar 2016 13:59:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.932
X-Spam-Level:
X-Spam-Status: No, score=-106.932 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] 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 uCVULtcBbJhZ; Thu, 24 Mar 2016 13:59:36 -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 56E9912D851; Thu, 24 Mar 2016 13:59:36 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 9F16F180014; Thu, 24 Mar 2016 13:59:22 -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
Message-Id: <20160324205922.9F16F180014@rfc-editor.org>
Date: Thu, 24 Mar 2016 13:59:22 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/payload/guANkkjrbEvmiZ-YOvuI-yD0WkA>
Cc: drafts-update-ref@iana.org, payload@ietf.org, rfc-editor@rfc-editor.org
Subject: [payload] RFC 7741 on RTP Payload Format for VP8 Video
X-BeenThere: payload@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 24 Mar 2016 20:59:38 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7741
Title: RTP Payload Format for VP8 Video
Author: P. Westin, H. Lundin,
M. Glover, J. Uberti,
F. Galligan
Status: Standards Track
Stream: IETF
Date: March 2016
Mailbox: patrik.westin@gmail.com,
hlundin@google.com,
michaelglover262@gmail.com,
justin@uberti.name,
fgalligan@google.com
Pages: 27
Characters: 58399
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-payload-vp8-17.txt
URL: https://www.rfc-editor.org/info/rfc7741
DOI: http://dx.doi.org/10.17487/RFC7741
This memo describes an RTP payload format for the VP8 video codec.
The payload format has wide applicability, as it supports
applications from low-bitrate peer-to-peer usage to high-bitrate
video conferences.
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