Re: [ippm] Call for implementation reports of RFC2678-2681
"Henk Uijterwaal (RIPE NCC)" <henk@ripe.net> Tue, 27 July 2004 11:08 UTC
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA05075 for <ippm-archive@lists.ietf.org>; Tue, 27 Jul 2004 07:08:00 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BpPlw-0004RZ-8j; Tue, 27 Jul 2004 07:05:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BpPlK-0004LA-HJ for ippm@megatron.ietf.org; Tue, 27 Jul 2004 07:04:50 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04957 for <ippm@ietf.org>; Tue, 27 Jul 2004 07:04:47 -0400 (EDT)
Received: from postman.ripe.net ([193.0.0.199]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BpPmu-0005KO-6H for ippm@ietf.org; Tue, 27 Jul 2004 07:06:29 -0400
Received: by postman.ripe.net (Postfix, from userid 8) id A368355E6B; Tue, 27 Jul 2004 13:02:28 +0200 (CEST)
Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by postman.ripe.net (Postfix) with ESMTP id 4B2E855DED for <ippm@ietf.org>; Tue, 27 Jul 2004 13:02:28 +0200 (CEST)
Received: from cow.ripe.net (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.10/8.11.6) with ESMTP id i6RB2S1o005126 for <ippm@ietf.org>; Tue, 27 Jul 2004 13:02:28 +0200
Received: from localhost (henk@localhost) by cow.ripe.net (8.12.10/8.12.6) with ESMTP id i6RB2SUc002367 for <ippm@ietf.org>; Tue, 27 Jul 2004 13:02:28 +0200
X-Authentication-Warning: cow.ripe.net: henk owned process doing -bs
Date: Tue, 27 Jul 2004 13:02:28 +0200
From: "Henk Uijterwaal (RIPE NCC)" <henk@ripe.net>
To: ippm@ietf.org
Subject: Re: [ippm] Call for implementation reports of RFC2678-2681
In-Reply-To: <Pine.LNX.4.58.0403040312060.8271@cow.ripe.net>
Message-ID: <Pine.LNX.4.58.0407271300340.8171@cow.ripe.net>
References: <Pine.LNX.4.58.0403040312060.8271@cow.ripe.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-RIPE-Spam-Status: N 0.000000 / 0.0 / 0.0 / disabled
X-RIPE-Signature: 2436dbd1f73b4c95bb00c499828860f3
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
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>
Sender: ippm-bounces@ietf.org
Errors-To: ippm-bounces@ietf.org
IPPM group, On Thu, 4 Mar 2004, Henk Uijterwaal (RIPE NCC) wrote: > Even though the process to move RFC2678 through 2781 from proposed > standard to standard is likely to be changed in the coming year, the > chairs would like to start collecting implementation reports for these > RFCs. > > If you have implemented any of > > RFC2678 Connectivity > RFC2679 One way delay > RFC2680 Packet Loss > RFC2681 Round trip Delay > > Please provide us with an implementation report. This report should > contain (at least): > > * Name of implementation > * Organization that did the implementation > * Contact details > * Origin of the code > * Platform (what it is running on) > * Metrics implemented > > And optionally: > > * Features implemented > * Metrics and features not implemented, and why you did not implement > them. > * Tests done on the implementation such as: > - Comparison of metrics with 2+ implementations > - Verification of results with passive methods > - Error estimation, clock source > > Please send reports to the chairs privately, > > Matt & Henk So-far, I have received 1 report, with a promise for a second one. If you did implement any of these metrics, please let me know. If you want to discuss your report in San Diego next week, we do have time on the agenda. Henk ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net RIPE Network Coordination Centre http://www.amsterdamned.org/~henk P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------ Process and Procedure are the last hiding place of people without the wit and wisdom to do their job properly. (David Brent). _______________________________________________ ippm mailing list ippm@ietf.org https://www1.ietf.org/mailman/listinfo/ippm
- [ippm] Call for implementation reports of RFC2678… Henk Uijterwaal (RIPE NCC)
- Re: [ippm] Call for implementation reports of RFC… Henk Uijterwaal (RIPE NCC)
- Re: [ippm] RIPE NCC's implementation report for R… Henk Uijterwaal (RIPE NCC)