We should probably have a look at our depacketizers at some point and
see if we need to make any adjustments.
-------- Оригинално писмо --------
Тема: [AVTCORE] RFC 6184 on RTP Payload Format for H.264 Video
Дата: Tue, 3 May 2011 17:20:10 -0700 (PDT)
До: firstname.lastname@example.org, email@example.com
A new Request for Comments is now available in online RFC libraries.
Title: RTP Payload Format for H.264 Video
Author: Y.-K. Wang, R. Even,
T. Kristensen, R. Jesup
Status: Standards Track
I-D Tag: draft-ietf-avt-rtp-rfc3984bis-12.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
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
Requests for special distribution should be addressed to either the
author of the RFC in question, or to firstname.lastname@example.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
The RFC Editor Team
Association Management Solutions, LLC