Protocol Action: 'RTP Payload Format for Scalable Video Coding' to Proposed Standard (draft-ietf-avt-rtp-svc-27.txt)
The IESG <iesg-secretary@ietf.org> Tue, 15 February 2011 14:49 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix)
with ESMTP id 8456D3A6D2E; Tue, 15 Feb 2011 06:49:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.53
X-Spam-Level:
X-Spam-Status: No, score=-102.53 tagged_above=-999 required=5 tests=[AWL=0.069,
BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com
[127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XIAPVU7qfVJp;
Tue, 15 Feb 2011 06:49:42 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix)
with ESMTP id 3048B3A6D62; Tue, 15 Feb 2011 06:49:42 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Protocol Action: 'RTP Payload Format for Scalable Video Coding' to
Proposed Standard (draft-ietf-avt-rtp-svc-27.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110215144942.32331.1437.idtracker@localhost>
Date: Tue, 15 Feb 2011 06:49:42 -0800
Cc: payload chair <payload-chairs@tools.ietf.org>,
Internet Architecture Board <iab@iab.org>,
payload mailing list <payload@ietf.org>,
RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>,
<mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>,
<mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Feb 2011 14:49:43 -0000
The IESG has approved the following document: - 'RTP Payload Format for Scalable Video Coding' (draft-ietf-avt-rtp-svc-27.txt) as a Proposed Standard This document is the product of the Audio/Video Transport Payloads Working Group. The IESG contact persons are Gonzalo Camarillo and Robert Sparks. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-avt-rtp-svc/ Technical Summary This memo describes an RTP payload format for Scalable Video Coding (SVC) as defined in Annex G of ITU-T Recommendation H.264, which is technically identical to Amendment 3 of ISO/IEC International Standard 14496-10. The RTP payload format allows for packetization of one or more Network Abstraction Layer (NAL) units in each RTP packet payload, as well as fragmentation of a NAL unit in multiple RTP packets. Furthermore, it supports transmission of an SVC stream over a single as well as multiple RTP sessions. The payload format defines a new media subtype name "H264-SVC", but is still backwards compatible to [I-D.ietf-avt-rtp-rfc3984bis] since the base layer, when encapsulated in its own RTP stream, must use the H.264 media subtype name ("H264") and the packetization method specified in [I- D.ietf-avt-rtp-rfc3984bis]. The payload format has wide applicability in videoconferencing, Internet video streaming, and high bit-rate entertainment-quality video, among others. Working Group Summary There was a very heated discussion before the two proposals were merged. Once agreement was achieved the work progress smoothly using a design team. The registration template was posted to ietf-types@iana.org for 2 weeks review: <http://www.ietf.org/mail-archive/web/ietf-types/current/msg00996.html> Document Quality This is a payload specification for H.264 scalable video coding. It is being used in some streaming and video conferencing applications. It is referenced by other standard bodies. Personnel Who is the Document Shepherd for this document? Who is the Responsible Area Director? Roni Even is the document shepherd. The responsible area director is Gonzalo Camarillo.