Re: [AVTCORE] Gen-ART review of draft-ietf-avtcore-idms-09

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Mon, 10 June 2013 14:40 UTC

Return-Path: <dromasca@avaya.com>
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 F0C3E21F938E; Mon, 10 Jun 2013 07:40:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.348
X-Spam-Level:
X-Spam-Status: No, score=-103.348 tagged_above=-999 required=5 tests=[AWL=0.250, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 N1TuFurvVW-D; Mon, 10 Jun 2013 07:40:27 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 3239421F9399; Mon, 10 Jun 2013 07:40:26 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AioFAJ7ktVGHCzI1/2dsb2JhbABXA4JFIyEwSbV4iEqBBBZ0giMBAQEBAxIbHDAMBAIBCAcGBAMBAQELHQcyFAkIAgQOBQgTB4drAQudR5tMF48HIAENAwYBBgMIgm5hA5hphRmLAIMPgic
X-IronPort-AV: E=Sophos; i="4.87,837,1363147200"; d="scan'208,217"; a="12522144"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 10 Jun 2013 10:40:24 -0400
Received: from unknown (HELO AZ-FFEXHC04.global.avaya.com) ([135.64.58.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 10 Jun 2013 10:35:37 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC04.global.avaya.com ([135.64.58.14]) with mapi id 14.02.0328.009; Mon, 10 Jun 2013 10:40:22 -0400
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Kevin Gross <kevin.gross@avanw.com>, "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
Thread-Topic: [AVTCORE] Gen-ART review of draft-ietf-avtcore-idms-09
Thread-Index: AQHOZeZ7ymQ4hhifMECwBepzBAET3ZkvBFkQ
Date: Mon, 10 Jun 2013 14:40:22 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA199E5B@AZ-FFEXMB04.global.avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA19894C@AZ-FFEXMB04.global.avaya.com> <FCC100FC8D6B034CB88CD8173B2DA1581F34C609@EXC-MBX03.tsn.tno.nl> <CALw1_Q13icqNLGDuvCOMB-O6Q_LtnjXSvZqG_Tyftuf6BjYCEg@mail.gmail.com>
In-Reply-To: <CALw1_Q13icqNLGDuvCOMB-O6Q_LtnjXSvZqG_Tyftuf6BjYCEg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.64.58.46]
Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA199E5BAZFFEXMB04globala_"
MIME-Version: 1.0
Cc: General Area Review Team <gen-art@ietf.org>, "avt@ietf.org" <avt@ietf.org>, "draft-ietf-avtcore-idms.all@tools.ietf.org" <draft-ietf-avtcore-idms.all@tools.ietf.org>
Subject: Re: [AVTCORE] Gen-ART review of draft-ietf-avtcore-idms-09
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: Mon, 10 Jun 2013 14:40:33 -0000

Hi Kevin,

Thank you for looking at my comments and for explaining in detail the editorial decisions that you made. Both explanations make sense, and leaving the current text in place is acceptable.

Regards,

Dan



From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Kevin Gross
Sent: Monday, June 10, 2013 5:26 PM
To: Brandenburg, R. (Ray) van
Cc: Romascanu, Dan (Dan); General Area Review Team; avt@ietf.org; draft-ietf-avtcore-idms.all@tools.ietf.org
Subject: Re: [AVTCORE] Gen-ART review of draft-ietf-avtcore-idms-09

Dan, thanks for looking at this.

As a co-author, I'll weigh in on a couple of things that Ray did not address.

Kevin Gross
+1-303-447-0517
Media Network Consultant
AVA Networks - www.AVAnw.com<http://www.avanw.com/>m/>, www.X192.org<http://www.X192.org>

On Mon, Jun 10, 2013 at 2:33 AM, Brandenburg, R. (Ray) van <ray.vanbrandenburg@tno.nl<mailto:ray.vanbrandenburg@tno.nl>> wrote:

-----Original Message-----
From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com<mailto:dromasca@avaya.com>]
Sent: zondag 9 juni 2013 9:53
To: General Area Review Team
Cc: draft-ietf-avtcore-idms.all@tools.ietf.org<mailto:draft-ietf-avtcore-idms.all@tools.ietf.org>
Subject: Gen-ART review of draft-ietf-avtcore-idms-09

(resending, I mis-spelled .all address at the first try)

I am the assigned Gen-ART reviewer for this draft. For background on Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments you may receive.

Document: draft-ietf-avtcore-idms-09
Reviewer: Dan Romascanu
Review Date: 6/6/13
IETF LC End Date: 6/11/13
IESG Telechat date:

Summary:

Not Ready

Major issues:
5. In Section 8:

   Because RTP
   timestamps do wrap around, the sender of this packet SHOULD use
   recent values, i.e. choose NTP timestamps that reflect current time
   and not too far in the future or in the past.

Why a SHOULD here and not a MUST? If there are any cases of exception they need to be detailed.
[Ray: I will check with my co-authors]

[Kevin] Devices that receive these reports need to deal with rollover conditions both for the RTP timestamp (which can rollover a couple times a day) and the NTP timestamp (which will have its first rollover in 2036). I believe these requirements are already stated in RFC3550 and RFC5905 respectively. The suggestion to use recent timestamps in reporting reduces statistical chance that a receiving device will need to do extra computation required to handle an RTP rollover. There's no way to eliminate this possibility altogether and the requirement is stated in a qualitative way and so could not be enforced as a MUST.

6. In Section 8:

   This SHOULD relate to the first
   arriving RTP packet containing this particular RTP timestamp, in case
   multiple RTP packets contain the same RTP timestamp.

Why a SHOULD here and not a MUST? If there are any cases of exception they need to be detailed.
[Ray: I will check with my co-authors]

[Kevin] This is an issue that the authors discussed at length and for which we do not believe there is an optimal solution and so we were reluctant to require our recommendation. Ideally we want an NTP timestamp indicating when all data required to render the specified RTP timestamp has arrived. For this we'd really like to know when the last packet for an RTP timestamp arrived. In the presence packet loss and reordering, it is not possible to reliably record the last packet. It is possible to record the first packet and so this is our recommendation. The accuracy of arrival times is not so critical in IDMS as arrival time allows a less precise synchronization than presentation times.