Re: [rtcweb] RTP Payload Format for H.264 video

Harald Alvestrand <harald@alvestrand.no> Thu, 10 January 2013 11:57 UTC

Return-Path: <harald@alvestrand.no>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A00FF21F862E for <rtcweb@ietfa.amsl.com>; Thu, 10 Jan 2013 03:57:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.359
X-Spam-Level:
X-Spam-Status: No, score=-110.359 tagged_above=-999 required=5 tests=[AWL=0.240, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 NNledVQZkzw8 for <rtcweb@ietfa.amsl.com>; Thu, 10 Jan 2013 03:57:57 -0800 (PST)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 6F66E21F8634 for <rtcweb@ietf.org>; Thu, 10 Jan 2013 03:57:57 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id AEFCE39E240; Thu, 10 Jan 2013 12:57:49 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KnSZFPA6qsMV; Thu, 10 Jan 2013 12:57:48 +0100 (CET)
Received: from hta-dell.lul.corp.google.com (unknown [IPv6:2620:0:1043:1:be30:5bff:fede:bcdc]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 488DE39E1C9; Thu, 10 Jan 2013 12:57:48 +0100 (CET)
Message-ID: <50EEACBB.2040802@alvestrand.no>
Date: Thu, 10 Jan 2013 12:57:47 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Kaiduan Xie <kaiduanx@gmail.com>
References: <CACKRbQdw=u-M75a=+nfvA1fJwWO03k+Mn9p8fZmbarJ9fGhohA@mail.gmail.com>
In-Reply-To: <CACKRbQdw=u-M75a=+nfvA1fJwWO03k+Mn9p8fZmbarJ9fGhohA@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] RTP Payload Format for H.264 video
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Jan 2013 11:57:59 -0000

On 01/09/2013 10:08 PM, Kaiduan Xie wrote:
> Hi,
>
> This may seems off-topic of webrtc, but I need some advice from
> someone with knowledge on H.264/RTP.
>
> For H.264, do we MUST follow RFC 3984/6184 to encapsulate H.264
> encoded video frame into RTP packet?
Generic codec questions for RTP should probably be addressed to the 
payload@ietf.org list, not here.

(I think the answer is yes, if you want to claim that you're 
implementing H.264 that can interoperate with others, but I haven't 
tried to parse those RFCs.)

>
> Thanks,
>
> /Kaiduan
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb