RFC 7272 on Inter-Destination Media Synchronization (IDMS) Using the RTP Control Protocol (RTCP)
rfc-editor@rfc-editor.org Tue, 01 July 2014 01:48 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62D9E1A01D5; Mon, 30 Jun 2014 18:48:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.877
X-Spam-Level:
X-Spam-Status: No, score=-96.877 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FRT_STOCK1=3.988, FRT_STOCK2=3.988, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kW0dDxP2Iybt; Mon, 30 Jun 2014 18:48:39 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 617BD1A01D6; Mon, 30 Jun 2014 18:48:33 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 68558180450; Mon, 30 Jun 2014 18:48:29 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7272 on Inter-Destination Media Synchronization (IDMS) Using the RTP Control Protocol (RTCP)
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140701014829.68558180450@rfc-editor.org>
Date: Mon, 30 Jun 2014 18:48:29 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/zbH0Hdse0f3vi4MRn-BenKkYypE
Cc: drafts-update-ref@iana.org, avt@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Jul 2014 01:48:40 -0000
A new Request for Comments is now available in online RFC libraries. RFC 7272 Title: Inter-Destination Media Synchronization (IDMS) Using the RTP Control Protocol (RTCP) Author: R. van Brandenburg, H. Stokking, O. van Deventer, F. Boronat, M. Montagud, K. Gross Status: Standards Track Stream: IETF Date: June 2014 Mailbox: ray.vanbrandenburg@tno.nl, hans.stokking@tno.nl, oskar.vandeventer@tno.nl, fboronat@dcom.upv.es, mamontor@posgrado.upv.es, kevin.gross@avanw.com Pages: 23 Characters: 56261 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-avtcore-idms-13.txt URL: http://www.rfc-editor.org/rfc/rfc7272.txt 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 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. This document is a product of the Audio/Video Transport Core Maintenance Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/search For downloading RFCs, see http://www.rfc-editor.org/rfc.html Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC