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

"Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl> Thu, 15 August 2013 09:22 UTC

Return-Path: <ray.vanbrandenburg@tno.nl>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18E5C11E8106 for <avt@ietfa.amsl.com>; Thu, 15 Aug 2013 02:22:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HApQWYYcA8bO for <avt@ietfa.amsl.com>; Thu, 15 Aug 2013 02:22:48 -0700 (PDT)
Received: from fromintoutb.tno.nl (fromintoutb.tno.nl [134.221.1.27]) by ietfa.amsl.com (Postfix) with ESMTP id 48C9D11E8127 for <avt@ietf.org>; Thu, 15 Aug 2013 02:22:40 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.89,884,1367964000"; d="scan'208";a="2081705"
Received: from unknown (HELO mail.tno.nl) ([134.221.225.222]) by mailhost1b.tno.nl with ESMTP; 15 Aug 2013 11:22:38 +0200
Received: from EXC-MBX03.tsn.tno.nl ([169.254.3.163]) by EXC-CASHUB03.tsn.tno.nl ([134.221.225.222]) with mapi id 14.03.0123.003; Thu, 15 Aug 2013 11:22:38 +0200
From: "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, "draft-ietf-avtcore-idms@tools.ietf.org" <draft-ietf-avtcore-idms@tools.ietf.org>
Thread-Topic: [AVTCORE] I-D Action: draft-ietf-avtcore-idms-12.txt
Thread-Index: AQHOjDftiZdFqe4/jEmTIRU5lnJxVJl7WFzbgBqBoACAAD7oEA==
Date: Thu, 15 Aug 2013 09:22:38 +0000
Message-ID: <FCC100FC8D6B034CB88CD8173B2DA1581F4420A0@EXC-MBX03.tsn.tno.nl>
References: <20130729084350.25184.22437.idtracker@ietfa.amsl.com> <B80493A5-F30E-4725-B0C7-8387BB0EF1D6@tno.nl> <520C84B0.4080104@ericsson.com>
In-Reply-To: <520C84B0.4080104@ericsson.com>
Accept-Language: en-US, nl-NL
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [134.221.225.153]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-idms-12.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Aug 2013 09:22:53 -0000

Hi Magnus,

Good point! For some reason, I never really considered that to be an option. I guess you're right and there's no reason not to. 

If I don't see any disagreements from others, I will add it to the next revision. 

Thanks,

Ray

> -----Original Message-----
> From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]
> Sent: donderdag 15 augustus 2013 9:35
> To: Brandenburg, R. (Ray) van; draft-ietf-avtcore-idms@tools.ietf.org
> Cc: avt@ietf.org
> Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-idms-12.txt
> 
> Hi,
> 
> Looking at this latest version I have a comment.
> 
> section 14.4 defines the SPST registry.
> 
> Why isn't is adding the ETSI defined values from the start. If they are known
> and have well known reference I don't see any issues with putting in the
> values into the registry at its creation.
> 
> Value           Name                         Reference
>    -----           ----                         ---------
>    1               Synchronization Client       section 7 of [RFCXXXX]
>    2               <Appropriate Name>           [TS183063]
>    3               <Appropriate Name>           [TS183063]
>    4               <Appropriate Name>           [TS183063]
> 
> 
> Cheers
> 
> Magnus
> 
> 
> On 2013-07-29 10:48, Brandenburg, R. (Ray) van wrote:
> > Hi,
> >
> > This version of the draft includes the final comments received during
> > IETF LC and from Martin Thomson as Appsdir reviewer.
> >
> > Best regards,
> >
> > Ray
> >
> > On 29 jul. 2013, at 10:45, "internet-drafts@ietf.org"
> > <internet-drafts@ietf.org> wrote:
> >
> >>
> >> 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-12.txt Pages
> >> : 22 Date            : 2013-07-29
> >>
> >> Abstract: 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:
> >> https://datatracker.ietf.org/doc/draft-ietf-avtcore-idms
> >>
> >> There's also a htmlized version available at:
> >> http://tools.ietf.org/html/draft-ietf-avtcore-idms-12
> >>
> >> A diff from the previous version is available at:
> >> http://www.ietf.org/rfcdiff?url2=draft-ietf-avtcore-idms-12
> >>
> >>
> >> 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.
> >>
> >> Internet-Drafts are also available by anonymous FTP at:
> >> ftp://ftp.ietf.org/internet-drafts/
> >>
> >> _______________________________________________
> Audio/Video Transport
> >> Core Maintenance avt@ietf.org
> >> https://www.ietf.org/mailman/listinfo/avt
> > This e-mail and its contents are subject to the DISCLAIMER at
> > http://www.tno.nl/emaildisclaimer
> >
> > _______________________________________________ Audio/Video
> Transport
> > Core Maintenance avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt
> >
> 
> 
> --
> 
> Magnus Westerlund
> 
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM
> ----------------------------------------------------------------------
> Ericsson AB                | Phone  +46 10 7148287
> Färögatan 6                | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------