You are here: Home > Participate > Join a Discussion > Mailman Archives
<<< Chronological >>> Author Index    Subject Index <<< Threads >>>

More RIPE47 followup

  • From: "Henk Uijterwaal (RIPE NCC)" < >
  • Date: Mon, 16 Feb 2004 12:41:08 +0100 (CET)

Dear All,

This is a follow-up on a question raised during the AOB session of the TTM
meeting @ RIPE47.  Two potentially interesting developments were discussed
there:

1. OWAMP.

   As you probably know, TTM implements RFC's 2679 and 2680 for its one
   way loss and delay measurements.  These RFC's specify HOW to measure
   these quantities, but leave details like packet format and set-up
   of measurement sessions open.   As a result, TTM is incompatible with
   other products implementing the same metrics.

   OWAMP (One Way Active Measurement Protocol) is an attempt to solve this
   by specifying packet formats and setup sequences.  For a full
   description, see:

       http://www.ietf.org/internet-drafts/draft-ietf-ippm-owdp-07.txt

   The question I have is whether this protocol should be added to
   the TTM service.

   For measurements between TTM TB's, there won't be a difference.
   However, it would allow TB's to measure between them and boxes from
   other vendors and, as a first guess, immediately add 50-100 measurement
   targets between TB's and boxes from other services (mainly Surveyor
   boxes in North America).

   Adding this is a non-trivial amount of work, so before putting this
   on any NCC workplan, I'd like to have some feedback if there is
   interest in adding this feature.

2. Delay Tomography, SCoLE

   At the last RIPE meeting, 2 authors presented tools that take the
   delays between test-boxes and use that information to estimate delays
   between other hosts on the Internet.  I'm interested to hear if anybody
   has any thought on the role that the RIPE NCC should play here:

   Some possibilities are:

   a) No.
   b) We put pointers to the tools on our website (and/or we make the
      source code easily available).
   c) (b) plus We install the tools ourselves, make sure that they work
               and provide some description how to install them yourself.
   d) (c) plus We actively maintain the software and include
               testing/fixing as part of upgrade paths.
   e) (d) plus We add a webinterface or similar, allowing you to use
               the tool with little/no local installation.

   There are probably more possibilities. However, they all have in common
   (except for doing nothing, of course) that they consume resources, so
   before spending cycles on this, I like to know your opinions on this.
   If such tools were made available, would you use them?

Any comments, either to the list or to me privately, are appreciated,

Henk

------------------------------------------------------------------------------
Henk Uijterwaal                             Email: henk.uijterwaal@localhost
RIPE Network Coordination Centre            WWW: http://www.ripe.net/home/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).




  • Post To The List:
<<< Chronological >>> Author    Subject <<< Threads >>>