Re: [ppsp] Question about SVC/AVC support

Rui Cruz <rui.cruz@ieee.org> Thu, 10 November 2011 12:20 UTC

Return-Path: <rui.cruz@ieee-pt.org>
X-Original-To: ppsp@ietfa.amsl.com
Delivered-To: ppsp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4B7421F8B3B for <ppsp@ietfa.amsl.com>; Thu, 10 Nov 2011 04:20:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.075
X-Spam-Level:
X-Spam-Status: No, score=-103.075 tagged_above=-999 required=5 tests=[AWL=0.523, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 YgRqGKTl2ngv for <ppsp@ietfa.amsl.com>; Thu, 10 Nov 2011 04:20:33 -0800 (PST)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 51E1321F8B46 for <ppsp@ietf.org>; Thu, 10 Nov 2011 04:20:33 -0800 (PST)
Received: by wyf28 with SMTP id 28so843019wyf.31 for <ppsp@ietf.org>; Thu, 10 Nov 2011 04:20:32 -0800 (PST)
Received: by 10.216.131.42 with SMTP id l42mr6428559wei.16.1320927632411; Thu, 10 Nov 2011 04:20:32 -0800 (PST)
Received: from airia.casa (89-180-45-156.net.novis.pt. [89.180.45.156]) by mx.google.com with ESMTPS id gd6sm9384168wbb.1.2011.11.10.04.20.30 (version=SSLv3 cipher=OTHER); Thu, 10 Nov 2011 04:20:31 -0800 (PST)
Sender: Rui Cruz <rui.cruz@ieee-pt.org>
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: multipart/alternative; boundary="Apple-Mail=_00F746F4-EFBF-4C84-85A9-62364A94F4A3"
From: Rui Cruz <rui.cruz@ieee.org>
In-Reply-To: <E84E7B8FF3F2314DA16E48EC89AB49F024E7759F@Polydeuces.office.hd>
Date: Thu, 10 Nov 2011 12:20:29 +0000
Message-Id: <E4310BB1-6E42-4F11-AF83-7F290DF510E3@ieee.org>
References: <E84E7B8FF3F2314DA16E48EC89AB49F024E7759F@Polydeuces.office.hd>
To: Martin Stiemerling <Martin.Stiemerling@neclab.eu>
X-Mailer: Apple Mail (2.1251.1)
Cc: Rui Cruz <rui.cruz@ieee.org>, "ppsp@ietf.org" <ppsp@ietf.org>
Subject: Re: [ppsp] Question about SVC/AVC support
X-BeenThere: ppsp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: discussing to draw up peer to peer streaming protocol <ppsp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppsp>, <mailto:ppsp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ppsp>
List-Post: <mailto:ppsp@ietf.org>
List-Help: <mailto:ppsp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppsp>, <mailto:ppsp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Nov 2011 12:20:34 -0000

Hi Martin,

Perhaps, I my apologies for repeating here what I answered in a previous message, that PPSP should support both "Structured Media"  (SVC/MDC/MVC/multi-bitrate) and unstructured media (AVC) or other formats, although the trend in the Internet has been for H.264 MPEG-4/AVC and its extensions SVC, MVC. In what respects MDC, it can be seen as an option, combined or not with SVC, but can perfectly be supported if the PPSP protocols are "codec agnostic" (not involved in the decoding process) but just "aware", as, in my opinion, they should be.  

A very important principle should be observed, in my opinion, related to the role the PPSP protocols play in the streaming process, as they should be open to support both "Structured Media"  (SVC/MDC/MVC/multi-bitrate) and unstructured media (AVC or other), but not being involved in the decoding/encoding processes of the "Structured Media". 
It is the Media Player application, not the protocols associated with the transport of the Media, the entity that should "know" (via a requester/re-assembler module) how and what to request (to a "peer") and decode the received "Structured Media" (from the "peer") in order to "present" it to the User. 

Both latest draft-gu-ppsp-tracker-protocol and draft-gu-ppsp-peer-protocol were designed with this principle in mind, and able to support (but not involved in the decoding) video streams transmitted at a suitable spacio-temporal resolution, adequate for the user's display device and networking conditions.
 
---------------------------
Best Regards,

Prof. Rui Santos Cruz
Chairman
IEEE Portugal Section
Av. Prof. Dr. Aníbal Cavaco Silva, IST-TagusPark, Office 1-5, 2744-016 Porto Salvo, Portugal
+351 214 233 200 (ext 5044), +351.939 060 939 (mobile)
rui.cruz@ieee.org 
rui.s.cruz@ist.utl.pt
sec.portugal@ieee.org
www.ieee-pt.org
Advancing technology for humanity.

On 10/11/2011, at 08:56, Martin Stiemerling wrote:

> Hi,
> 
> I ran into SVC/AVC in the tracker draft and in draft-gu-ppsp-peer-protocol-03.txt. 
> 
> For the tracker, I'm not sure what the implications are, whereas for the peer protocol I can see implications. 
> 
> However, there has been no large scale discussion if the PPSP peer protocol should actually support SVC/AVC and if it should support it, what the implications are. 
> 
> When writing about this, is there also the need to support MDC?
> 
> Can somebody outline what the implications are if we support SVC/AVC codecs in the peer protocol?
> 
> Thank you,
> 
>  Martin
> 
> martin.stiemerling@neclab.eu
> 
> NEC Laboratories Europe - Network Research Division NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road, London W3 6BL | Registered in England 2832014 
> 
> 
> _______________________________________________
> ppsp mailing list
> ppsp@ietf.org
> https://www.ietf.org/mailman/listinfo/ppsp