[AVTCORE] ***SPAM*** 5.277 (5) FW: New Version Notification for draft-stokking-avtcore-idms-for-iptv-00.txt

["Stokking, H.M. (Hans)" <[e-mail]>]

Hi all,

I'm resending because of e-mail problems, the e-mail below somehow didn't get through. I hope the IETF secretariat has fixed it: if you get this e-mail, it has.

So, see below.

Hans
_____________________________________________
From: Stokking, H.M. (Hans)
Sent: dinsdag 28 oktober 2014 10:05
To: [e-mail]<mailto:[e-mail]> WG
Subject: FW: New Version Notification for draft-stokking-avtcore-idms-for-iptv-00.txt

Hi all,

I've uploaded a new draft yesterday on IDMS in IPTV/SSM environments, for discussion in avtcore.

In IPTV environments, there are some typical situations that are a problem for IDMS. First, in a typical SSM environment we have to deal with a potentially large number of messages, as described in RFC 5760. Also, different groups of viewers may view content together, so one broadcast may have many small groups of receivers to be synchronised. This I-D extends the current RFC 7272 with the ability to use a feedback target for collecting and summarizing IDMS reports, according to the framework from RFC 5760. For this, it defines 2 new sub-report blocks.

Furthermore, in IPTV environments the same content may be distributed in various versions (HD, SD, mobile). RTP timestamps of the various streams will not match, and thus synchronisation is no longer possible. The I-D gives 2 alternative solutions for this problem, for further discussion.

Can you let us know what you think about this draft?

I note that KPN has filed an IPR disclosure on this Internet Draft.

Hans

-----Original Message-----
From: [e-mail]<mailto:[e-mail]> [mailto:[e-mail]]
Sent: maandag 27 oktober 2014 14:24
To: Brandenburg, R. (Ray) van; Fernando Boronat; Mario Montagud; Stokking, H.M. (Hans); Stokking, H.M. (Hans); Deventer, M.O. (Oskar) van; Fernando Boronat; Brandenburg, R. (Ray) van; Deventer, M.O. (Oskar) van; Mario Montagud
Subject: New Version Notification for draft-stokking-avtcore-idms-for-iptv-00.txt


A new version of I-D, draft-stokking-avtcore-idms-for-iptv-00.txt
has been successfully submitted by Hans Stokking and posted to the IETF repository.

Name:           draft-stokking-avtcore-idms-for-iptv
Revision:       00
Title:          Inter-Destination Media Synchronizaton for IPTV Environments Document date:  2014-10-27
Group:          Individual Submission
Pages:          13
URL:            http://www.ietf.org/id/draft-stokking-avtcore-idms-for-iptv-00.txt
Status:         https://datatracker.ietf.org/doc/draft-stokking-avtcore-idms-for-iptv/
Htmlized:       http://tools.ietf.org/html/draft-stokking-avtcore-idms-for-iptv-00


Abstract:
   [RFC7272] describes the use of RTCP for the purpose of Inter-
   Destination Media Synchronization (IDMS) between Synchronization
   Clients (SCs) and an Media Synchronization Application Server (MSAS).
    This document extends that work for application in the area of IPTV.
    First, RTCP can be used according to the single source multicast
   (SSM) principles from [RFC5760] in the IPTV application area.  This
   document specifies the use of a feedback target for collecting and
   possibly summarizing IDMS reports.  For this, the document defines 2
   new sub-report blocks for the use of IDMS according to the SSM
   principles.  Alternatively, the MSAS can be co-located with the
   Feedback Target, for synchronizing small groups of receivers.
   Secondly, in an IPTV environment, different viewers may receive the
   same content, but in non-identical streams.  The IDMS solution
   presented in [RFC7272] will no longer work in such a case.  This
   document provides a solution for this.





Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat



This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. TNO accepts no liability for the content of this e-mail, for the manner in which you use it and for damage of any kind resulting from the risks inherent to the electronic transmission of messages.