Re: [AVTCORE] I-D Action: draft-ietf-avtcore-idms-11.txt

"Brandenburg, R. (Ray) van" <> Fri, 14 June 2013 15:04 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7343821F84B2 for <>; Fri, 14 Jun 2013 08:04:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 3.484
X-Spam-Level: ***
X-Spam-Status: No, score=3.484 tagged_above=-999 required=5 tests=[AWL=-3.988, BAYES_00=-2.599, FRT_STOCK1=3.988, FRT_STOCK2=3.988, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id JbaPZlAjm7ne for <>; Fri, 14 Jun 2013 08:04:32 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 604F121F9CFC for <>; Fri, 14 Jun 2013 08:04:28 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,867,1363129200"; d="scan'208";a="1650494"
Received: from unknown (HELO ([]) by with ESMTP; 14 Jun 2013 17:04:26 +0200
Received: from ([]) by ([]) with mapi id 14.02.0318.004; Fri, 14 Jun 2013 17:04:26 +0200
From: "Brandenburg, R. (Ray) van" <>
To: "" <>
Thread-Topic: [AVTCORE] I-D Action: draft-ietf-avtcore-idms-11.txt
Thread-Index: Ac5pEHVQCQtlfKnkRX6TxzlF9erRGw==
Date: Fri, 14 Jun 2013 15:04:25 +0000
Message-ID: <>
Accept-Language: en-US, nl-NL
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Cc: "Romascanu, Dan (Dan) (" <>
Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-idms-11.txt
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 14 Jun 2013 15:04:37 -0000

Hi all,

I've just uploaded a (or actually two, due to human error...) new version(s) of the IDMS draft. This includes all comments received during IETF LC. 

The most important changes are the fact that there is now an IANA Registry for the SPST values and a small informative section detailing the relationship with the ETSI document. 

For those looking for a diff with the IETF LC-version:

Best regards,


-----Original Message-----
From: [] On Behalf Of
Sent: vrijdag 14 juni 2013 16:56
Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-idms-11.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Audio/Video Transport Core Maintenance Working Group of the IETF.

	Title           : Inter-destination Media Synchronization using the RTP Control Protocol (RTCP)
	Author(s)       : Ray van Brandenburg
                          Hans Stokking
                          Oskar van Deventer
                          Fernando Boronat
                          Mario Montagud
                          Kevin Gross
	Filename        : draft-ietf-avtcore-idms-11.txt
	Pages           : 22
	Date            : 2013-06-14

   This document defines a new RTP Control Protocol (RTCP) Packet Type
   and an RTCP Extended Report (XR) Block Type to be used for achieving
   Inter-Destination Media Synchronization (IDMS).  IDMS is the process
   of synchronizing playout across multiple geographically distributed
   media receivers.  Using the RTCP XR IDMS Report Block defined in this
   document, media playout information from participants in a
   synchronization group can be collected.  Based on the collected
   information, an RTCP IDMS Settings Packet can then be sent to
   distribute a common target playout point to which all the distributed
   receivers, sharing a media experience, can synchronize.

   Typical use cases in which IDMS is useful are social TV, shared
   service control (i.e. applications where two or more geographically
   separated users are watching a media stream together), distance
   learning, networked video walls, networked loudspeakers, etc.

The IETF datatracker status page for this draft is:

There's also a htmlized version available at:

A diff from the previous version is available at:

Internet-Drafts are also available by anonymous FTP at:

Audio/Video Transport Core Maintenance
This e-mail and its contents are subject to the DISCLAIMER at