[AVTCORE] RFC 6184 on RTP Payload Format for H.264 Video
rfc-editor@rfc-editor.org Wed, 04 May 2011 00:20 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 680BEE0618; Tue, 3 May 2011 17:20:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.935
X-Spam-Level:
X-Spam-Status: No, score=-101.935 tagged_above=-999 required=5 tests=[AWL=0.065, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S45ulCu-54vP; Tue, 3 May 2011 17:20:11 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by ietfa.amsl.com (Postfix) with ESMTP id 5AD90E079C; Tue, 3 May 2011 17:20:10 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5036AE0780; Tue, 3 May 2011 17:20:10 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20110504002010.5036AE0780@rfc-editor.org>
Date: Tue, 03 May 2011 17:20:10 -0700
Cc: avt@ietf.org, rfc-editor@rfc-editor.org
Subject: [AVTCORE] RFC 6184 on RTP Payload Format for H.264 Video
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 04 May 2011 00:20:11 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6184
Title: RTP Payload Format for H.264 Video
Author: Y.-K. Wang, R. Even,
T. Kristensen, R. Jesup
Status: Standards Track
Stream: IETF
Date: May 2011
Mailbox: yekuiwang@huawei.com,
even.roni@huawei.com,
tom.kristensen@tandberg.com,
rjesup@wgate.com
Pages: 101
Characters: 250627
Obsoletes: RFC3984
I-D Tag: draft-ietf-avt-rtp-rfc3984bis-12.txt
URL: http://www.rfc-editor.org/rfc/rfc6184.txt
This memo describes an RTP Payload format for the ITU-T
Recommendation H.264 video codec and the technically identical
ISO/IEC International Standard 14496-10 video codec, excluding the
Scalable Video Coding (SVC) extension and the Multiview Video Coding
extension, for which the RTP payload formats are defined elsewhere.
The RTP payload format allows for packetization of one or more
Network Abstraction Layer Units (NALUs), produced by an H.264 video
encoder, in each RTP payload. The payload format has wide
applicability, as it supports applications from simple low bitrate
conversational usage, to Internet video streaming with interleaved
transmission, to high bitrate video-on-demand.
This memo obsoletes RFC 3984. Changes from RFC 3984 are summarized
in Section 14. Issues on backward compatibility to RFC 3984 are
discussed in Section 15. [STANDARDS-TRACK]
This document is a product of the Audio/Video Transport Working Group of the IETF.
This is now a Proposed Standard Protocol.
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 Internet
Official Protocol Standards (STD 1) 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
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
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