Re: [ippm] Review of: draft-ietf-ippm-reordering-12.txt

Mark Allman <mallman@icir.org> Fri, 21 April 2006 20:22 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FX28v-0007yh-9F; Fri, 21 Apr 2006 16:22:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FX28t-0007rr-BI for ippm@ietf.org; Fri, 21 Apr 2006 16:22:15 -0400
Received: from wyvern.icir.org ([192.150.187.14]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FX28r-0004Py-V4 for ippm@ietf.org; Fri, 21 Apr 2006 16:22:15 -0400
Received: from guns.icir.org (adsl-69-222-35-58.dsl.bcvloh.ameritech.net [69.222.35.58]) by wyvern.icir.org (8.12.11/8.12.11) with ESMTP id k3LKM39n003989; Fri, 21 Apr 2006 13:22:07 -0700 (PDT) (envelope-from mallman@icir.org)
Received: from lawyers.icir.org (guns.icir.org [69.222.35.58]) by guns.icir.org (Postfix) with ESMTP id 773A277AB77; Fri, 21 Apr 2006 16:22:01 -0400 (EDT)
Received: from lawyers.icir.org (localhost [127.0.0.1]) by lawyers.icir.org (Postfix) with ESMTP id A41DD3F92A5; Fri, 21 Apr 2006 16:21:09 -0400 (EDT)
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
From: Mark Allman <mallman@icir.org>
Subject: Re: [ippm] Review of: draft-ietf-ippm-reordering-12.txt
In-Reply-To: <7D5D48D2CAA3D84C813F5B154F43B15509D5BEB8@nl0006exch001u.nl.lucent.com>
Organization: ICSI Center for Internet Research (ICIR)
Song-of-the-Day: The Rising
MIME-Version: 1.0
Date: Fri, 21 Apr 2006 16:21:09 -0400
Message-Id: <20060421202109.A41DD3F92A5@lawyers.icir.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: "Dan Romascanu (E-mail)" <dromasca@avaya.com>, "Mreview (E-mail)" <mreview@ops.ietf.org>, ippm@ietf.org
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: mallman@icir.org
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org >
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org ?subject=unsubscribe>
List-Post: <mailto:ippm@ietf.org >
List-Help: <mailto:ippm-request@ietf.org ?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org ?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0625029018=="
Errors-To: ippm-bounces@ietf.org

> Dan Romascanu (new OPS AD) asked on MIB Doctors list for review
> of this document, since it is on IESG agenda for April 27th.
> 
> So I reviewed the document.
> 
> Looks pretty good.
> 
> I have one question that maybe the authors or other WG members can answer
> for me and that is:
> 
>   In section 4.5, it seems to allow for using msg sequence numbers OR 
>   units of time (without even having defined what the unit is).
> 
> So I wonder how this definitions specifies an exact metric. The metric would
> not be comparable from one to the other measurement if one of them uses
> msg sequence numbers, while the other uses "units of time". Even if two of
> them use "units of time" but different units (e.g. micro seconds vs milliseconds)
> even then they would not be comparable.
> 
> Was it not the goal of IPPM to define EXACT metrics, so that results of
> two different tests/measurments could be compared?

I thought we agree to get rid of the "units of time" notion in that it
makes it either damn hard or impossible for the receiver to know what is
expected (as opposed to a sequence number, which makes it trivial).

allman



_______________________________________________
ippm mailing list
ippm@ietf.org 
https://www1.ietf.org/mailman/listinfo/ippm