Re: [rmcat] I-D Action: draft-dt-rmcat-feedback-message-04.txt

Colin Perkins <csp@csperkins.org> Mon, 13 November 2017 04:33 UTC

Return-Path: <csp@csperkins.org>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B15C1293EC for <rmcat@ietfa.amsl.com>; Sun, 12 Nov 2017 20:33:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 iJa71c7WOtM5 for <rmcat@ietfa.amsl.com>; Sun, 12 Nov 2017 20:33:45 -0800 (PST)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4AD91128DE5 for <rmcat@ietf.org>; Sun, 12 Nov 2017 20:33:45 -0800 (PST)
Received: from [66.96.212.196] (port=51215 helo=[10.0.0.254]) by haggis.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from <csp@csperkins.org>) id 1eE6RL-0003lA-AJ; Mon, 13 Nov 2017 04:33:43 +0000
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <DB4PR07MB3482E692582ACB45A21A3BDC2590@DB4PR07MB348.eurprd07.prod.outlook.com>
Date: Mon, 13 Nov 2017 12:33:33 +0800
Cc: "rmcat@ietf.org" <rmcat@ietf.org>, Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>, "varun.singh@iki.fi" <varun.singh@iki.fi>, "mramalho@cisco.com" <mramalho@cisco.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <AFAA1D34-0584-44B8-BF94-43BC38E5F835@csperkins.org>
References: <150913051158.22299.4504001911028448869@ietfa.amsl.com> <DB4PR07MB3482E692582ACB45A21A3BDC2590@DB4PR07MB348.eurprd07.prod.outlook.com>
To: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
X-Mailer: Apple Mail (2.3273)
X-BlackCat-Spam-Score: 4
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/9OR4ByXvd8OfE6wDszjz4ko6O04>
Subject: Re: [rmcat] I-D Action: draft-dt-rmcat-feedback-message-04.txt
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "RTP Media Congestion Avoidance Techniques \(RMCAT\) Working Group discussion list." <rmcat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rmcat>, <mailto:rmcat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rmcat/>
List-Post: <mailto:rmcat@ietf.org>
List-Help: <mailto:rmcat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmcat>, <mailto:rmcat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Nov 2017 04:33:47 -0000

> On 30 Oct 2017, at 15:35, Ingemar Johansson S <ingemar.s.johansson@ericsson.com> wrote:
> 
> Hi
> 
> Read through the draft and I believe that I understand how it should be implemented and when time permits I will replace the home-brewn RTCP feedback that is currently used with SCReAM with the version that is specified in the dt draft.
> 
> There are a few questions though.
> 1)  Arrival time offset (ATO) and Report timestamp (RTS): The time granularity of the ATO is 1ms while the time granularity of the RTS seems to be 0.1ms or can even be configurable?. Is there any reason to have a differing time granularity for ATO and RTS?

We need to define these more carefully, but I agree that ideally they have the same units. The obvious unit for Report Timestamp would be the middle 32 bits out of 64 in the NTP timestamp, as used in the LSR field of SR packets. That doesn’t map so nicely to the 13 bit ATO field though, unless we make it count 1/1024 of a second ticks rather than 1/1000.

> 2) Byte order for ATO and RTS is not specified. I guess it should be network byte order for both RTS and ATO, right ?. 

Right.

Colin



-- 
Colin Perkins
https://csperkins.org/