RTP Payload Format for VP9 Video
draft-ietf-payload-vp9-16

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, avt@ietf.org, avtcore-chairs@ietf.org, bernard.aboba@gmail.com, draft-ietf-payload-vp9@ietf.org, rfc-editor@rfc-editor.org, superuser@gmail.com
Subject: Protocol Action: 'RTP Payload Format for VP9 Video' to Proposed Standard (draft-ietf-payload-vp9-16.txt)

The IESG has approved the following document:
- 'RTP Payload Format for VP9 Video'
  (draft-ietf-payload-vp9-16.txt) as Proposed Standard

This document is the product of the Audio/Video Transport Core Maintenance
Working Group.

The IESG contact persons are Murray Kucherawy and Francesca Palombini.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-payload-vp9/


Technical Summary

   This specification describes an RTP payload format for the VP9 video
   codec.  The payload format has wide applicability, as it supports
   applications from low bit-rate peer-to-peer usage, to high bit-rate
   video conferences.  It includes provisions for temporal and spatial
   scalability.

Working Group Summary



Document Quality

   Recent discussion of the VP9 payload format has centered on support for framemarking as well as some SDP questions.  
   Since framemarking does not support some popular spatial scalability modes (e.g. K-SVC), support for framemarking has
   not caught on, and framemarking support was recently removed from the webrtc.org distribution. As a result, a section
   on framemarking has been removed from the VP9 RTP payload specification.

   The VP9 RTP payload format is widely deployed, as part of the webrtc.org distribution. This includes implementations in browsers as well as mobile, tablet and desktop applications.

Personnel

   Bernard Aboba is the document shepherd.
   Murray Kucherawy is the responsible AD.

IESG Note

  The "PAYLOAD" working group merged with AVTCORE prior to my term as an AD, hence the curious filename for this document.