Return-Path: 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 C0F6821F95EF for ; Thu, 18 Jul 2013 08:43:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.032 X-Spam-Level: X-Spam-Status: No, score=-3.032 tagged_above=-999 required=5 tests=[AWL=-0.434, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LabB6ou+Xlnd for ; Thu, 18 Jul 2013 08:43:11 -0700 (PDT) Received: from mail-pd0-f182.google.com (mail-pd0-f182.google.com [209.85.192.182]) by ietfa.amsl.com (Postfix) with ESMTP id 39C8D21F9477 for ; Thu, 18 Jul 2013 08:43:11 -0700 (PDT) Received: by mail-pd0-f182.google.com with SMTP id r10so3211270pdi.13 for ; Thu, 18 Jul 2013 08:43:11 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:x-gm-message-state; bh=hpzGPQhpk8JMByqmNxRrcT/hkDVGpgHxlgsj4Ckl7i4=; b=GKoAI54SKMPtQQ3iJ+C3ym6lluRM3K27NbjVUZ4Jxut27+j1U74y3XOkuhNcqmSumI TiQMpLunbYKbbMsmfo51TgerNPxxACGvED7iO2Ge0W5zV2kIy2G8LnMcUjPz/G4f6gHY tVNeP1hle77V3lvsfBSC2j60KXVuA5A6xSFRMs5YU+dDM8yD+HU29wIGgSUA6x8B/9LM KLOYKLldKhNjSG7dSvmIjDKG0e4mLLlHy35Q9m8gtFSSZobfhN2gviXJbPYF4rIgHrK4 eurQ40SSK8qi4tqC5jayCOw2oyHtwaq/OIhEIGRiP29uQP9BDghEMOct3nRa79Iq/Vl1 j51A== X-Received: by 10.68.223.225 with SMTP id qx1mr12585118pbc.157.1374162190519; Thu, 18 Jul 2013 08:43:10 -0700 (PDT) Received: from Adams-MacBook-Pro.local ([38.102.150.73]) by mx.google.com with ESMTPSA id w8sm11584340pab.12.2013.07.18.08.43.08 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 18 Jul 2013 08:43:09 -0700 (PDT) Message-ID: <51E80D0B.2000209@vline.me> Date: Thu, 18 Jul 2013 08:43:07 -0700 From: Adam Fineberg User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: Harald Alvestrand References: <51E7324A.3090405@vline.me> <51E7A472.3010206@alvestrand.no> In-Reply-To: <51E7A472.3010206@alvestrand.no> Content-Type: multipart/alternative; boundary="------------020204000200030501080602" X-Gm-Message-State: ALoCoQmH1EMNbJGU67mC1pIbGbrW4VAqBSSs+p3Sj6sT583GEsahtWCmW+H2p819dxMdeDY4Hwo7 Cc: rtcweb@ietf.org Subject: Re: [rtcweb] Fwd: New Version Notification for draft-fineberg-avtext-temporal-layer-ext-00.txt X-BeenThere: rtcweb@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Real-Time Communication in WEB-browsers working group list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Jul 2013 15:43:21 -0000 This is a multi-part message in MIME format. --------------020204000200030501080602 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Yes, I apologize for not adding avtext as a cc. Regards, Adam On 7/18/13 1:16 AM, Harald Alvestrand wrote: > On 07/18/2013 02:09 AM, Adam Fineberg wrote: >> Hi, >> >> I'm working on WebRTC services and have found that while developing >> services that forward VP8 video streams if we want to take advantage >> of the VP8 temporal scaling we must get the temporal layer >> information from the RTP header which requires us to decrypt the SRTP >> packets. This is undesirable both because the middle-box needs to >> have access to the keys as well as the because of the added overhead >> of the decrypt/encrypt cycle. This draft proposes an RTP header >> extension that will allow us to use the VP8 temporal layer >> information included in the header extension and therefore do >> forwarding without SRTP decryption. Comments welcome. > > Just checking - you named your draft with the -avtext- convention; > this means that you want comments to go to avtext, yes? > > >> >> Regards, >> Adam Fineberg >> fineberg at vline.com >> >> -------- Original Message -------- >> Subject: New Version Notification for >> draft-fineberg-avtext-temporal-layer-ext-00.txt >> Date: Tue, 09 Jul 2013 10:02:05 -0700 >> From: internet-drafts at ietf.org >> To: Adam Fineberg >> >> >> >> A new version of I-D, draft-fineberg-avtext-temporal-layer-ext-00.txt >> has been successfully submitted by Adam Fineberg and posted to the >> IETF repository. >> >> Filename: draft-fineberg-avtext-temporal-layer-ext >> Revision: 00 >> Title: A Real-Time Transport Protocol (RTP) Header Extension for VP8 Temporal Layer Information >> Creation date: 2013-07-08 >> Group: Individual Submission >> Number of pages: 6 >> URL:http://www.ietf.org/internet-drafts/draft-fineberg-avtext-temporal-layer-ext-00.txt >> Status:http://datatracker.ietf.org/doc/draft-fineberg-avtext-temporal-layer-ext >> Htmlized:http://tools.ietf.org/html/draft-fineberg-avtext-temporal-layer-ext-00 >> >> >> Abstract: >> This document defines a mechanism by which packets of Real-Time >> Tranport Protocol (RTP) video streams encoded with the VP8 codec can >> indicate, in an RTP header extension, the temporal layer information >> about the frame encoded in the RTP packet. This information can be >> used in a middlebox performing bandwidth management of streams >> without requiring it to decrypt the streams. >> >> >> _______________________________________________ >> rtcweb mailing list >> rtcweb@ietf.org >> https://www.ietf.org/mailman/listinfo/rtcweb > -- Regards, Adam --------------020204000200030501080602 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Yes, I apologize for not adding avtext as a cc.

Regards,
Adam

On 7/18/13 1:16 AM, Harald Alvestrand wrote:
On 07/18/2013 02:09 AM, Adam Fineberg wrote:
Hi,

I'm working on WebRTC services and have found that while developing services that forward VP8 video streams if we want to take advantage of the VP8 temporal scaling we must get the temporal layer information from the RTP header which requires us to decrypt the SRTP packets. This is undesirable both because the middle-box needs to have access to the keys as well as the because of the added overhead of the decrypt/encrypt cycle. This draft proposes an RTP header extension that will allow us to use the VP8 temporal layer information included in the header extension and therefore do forwarding without SRTP decryption. Comments welcome.

Just checking - you named your draft with the -avtext- convention; this means that you want comments to go to avtext, yes?



Regards,
Adam Fineberg
fineberg at vline.com

-------- Original Message --------
Subject: New Version Notification for draft-fineberg-avtext-temporal-layer-ext-00.txt
Date: Tue, 09 Jul 2013 10:02:05 -0700
From: internet-drafts at ietf.org
To: Adam Fineberg <fineberg at vline.com> 


A new version of I-D, draft-fineberg-avtext-temporal-layer-ext-00.txt
has been successfully submitted by Adam Fineberg and posted to the
IETF repository.

Filename:	 draft-fineberg-avtext-temporal-layer-ext
Revision:	 00
Title:		 A Real-Time Transport Protocol (RTP) Header Extension for VP8 Temporal Layer Information
Creation date:	 2013-07-08
Group:		 Individual Submission
Number of pages: 6
URL:             http://www.ietf.org/internet-drafts/draft-fineberg-avtext-temporal-layer-ext-00.txt
Status:          http://datatracker.ietf.org/doc/draft-fineberg-avtext-temporal-layer-ext
Htmlized:        http://tools.ietf.org/html/draft-fineberg-avtext-temporal-layer-ext-00


Abstract:
   This document defines a mechanism by which packets of Real-Time
   Tranport Protocol (RTP) video streams encoded with the VP8 codec can
   indicate, in an RTP header extension, the temporal layer information
   about the frame encoded in the RTP packet.  This information can be
   used in a middlebox performing bandwidth management of streams
   without requiring it to decrypt the streams.



_______________________________________________
rtcweb mailing list
rtcweb@ietf.org
https://www.ietf.org/mailman/listinfo/rtcweb



-- 
Regards,
Adam
--------------020204000200030501080602--