Re: [AVT] SVC and multiscreen

Hi,

I have privately communicated my skepticism about this draft before.

The content of this draft may have been appropriate in an SVC requirements
document, published in 2005 or so.  Indeed, most (if not all) of the
information presented here is available in the SVC requirements documents
used in JVT.  

There is nothing in the document that refers to RTP, related signaling, the
transport of SVC over IP, or other aspects the IETF is concerned about.  No
codepoints are defined, no novel technical concepts are described.  No
normative content is presented.  At best, the draft contains an IMO quite
obvious application example for the use of SVC.

As the draft adds or removes nothing of substance, I have no concern that it
would create a problem for the technology defined in the SVC payload draft.
Therefore, I'm not violently objecting its inclusion.  At the same time,
though, I believe that the signal to noise ratio of the SVC draft, after
inclusion, would go down.  Therefore, I'm mildly against including it.

As for the relationship with MVC: there is none, except perhaps for the well
understood feature of MVC that allows stereo/3d content to be also displayed
as flat content on a 2d display.  Which, again, has been documented in JVT.

Stephan

On 12/13/09 8:47 AM, "Tom Taylor" <tom111.taylor@bell.net> wrote:

> Given that SVC hasn't quite been put to bed, I would like to draw the WG's
> attention to draft-nanwang-avt-svc-multiscreen-00.txt.
> 
> The original intention of the author was that this text be added to the SVC
> draft. Could I ask for comment from the WG on whether that is sensible or
> whether it is better to develop a separate document? Further: how does this
> relate to draft-wang-avt-rtp-mvc, which was agreed to be a WG item at the
> Dublin 
> meeting once the SVC work was done?
> 
> Tom Taylor
> 
> _______________________________________________
> Audio/Video Transport Working Group
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt