Re: [ippm] WGLC for draft-ietf-ippm-delay-var-as.

Al Morton <acmorton@att.com> Thu, 09 October 2008 20:02 UTC

Return-Path: <ippm-bounces@ietf.org>
X-Original-To: ippm-archive@megatron.ietf.org
Delivered-To: ietfarch-ippm-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7E42928C0D7; Thu, 9 Oct 2008 13:02:54 -0700 (PDT)
X-Original-To: ippm@core3.amsl.com
Delivered-To: ippm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 26D2A3A6912 for <ippm@core3.amsl.com>; Thu, 9 Oct 2008 13:02:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.509
X-Spam-Level:
X-Spam-Status: No, score=-105.509 tagged_above=-999 required=5 tests=[AWL=0.288, BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pEM-SgivOeEc for <ippm@core3.amsl.com>; Thu, 9 Oct 2008 13:02:52 -0700 (PDT)
Received: from mail120.messagelabs.com (mail120.messagelabs.com [216.82.250.83]) by core3.amsl.com (Postfix) with SMTP id 31EBF28C107 for <ippm@ietf.org>; Thu, 9 Oct 2008 13:02:51 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: acmorton@att.com
X-Msg-Ref: server-11.tower-120.messagelabs.com!1223582462!34813052!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.160.128.141]
Received: (qmail 800 invoked from network); 9 Oct 2008 20:01:02 -0000
Received: from sbcsmtp9.sbc.com (HELO flph161.enaf.ffdc.sbc.com) (144.160.128.141) by server-11.tower-120.messagelabs.com with AES256-SHA encrypted SMTP; 9 Oct 2008 20:01:02 -0000
Received: from enaf.ffdc.sbc.com (localhost.localdomain [127.0.0.1]) by flph161.enaf.ffdc.sbc.com (8.14.2/8.14.2) with ESMTP id m99K11jl010869 for <ippm@ietf.org>; Thu, 9 Oct 2008 13:01:01 -0700
Received: from klph001.kcdc.att.com (klph001.kcdc.att.com [135.188.3.11]) by flph161.enaf.ffdc.sbc.com (8.14.2/8.14.2) with ESMTP id m99K0sPd010270 for <ippm@ietf.org>; Thu, 9 Oct 2008 13:00:54 -0700
Received: from kcdc.att.com (localhost.localdomain [127.0.0.1]) by klph001.kcdc.att.com (8.14.0/8.14.0) with ESMTP id m99K0r9A018952 for <ippm@ietf.org>; Thu, 9 Oct 2008 15:00:53 -0500
Received: from maillennium.att.com (mailgw1.maillennium.att.com [135.25.114.99]) by klph001.kcdc.att.com (8.14.0/8.14.0) with ESMTP id m99K0mAD018744 for <ippm@ietf.org>; Thu, 9 Oct 2008 15:00:48 -0500
Message-Id: <200810092000.m99K0mAD018744@klph001.kcdc.att.com>
Received: from acmt.att.com (unknown[135.210.112.173](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20081009200047gw1003sn4de>; Thu, 9 Oct 2008 20:00:47 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 09 Oct 2008 16:00:46 -0400
To: Benoit Claise <bclaise@cisco.com>, "Geib, Ruediger" <Ruediger.Geib@t-systems.com>
From: Al Morton <acmorton@att.com>
In-Reply-To: <48EDC969.5050706@cisco.com>
References: <48D793F6.70702@ripe.net> <48EB2039.9090105@ripe.net> <1B6169C658325341A3B8066E23919E1C01D6DD81@S4DE8PSAANK.mitte.t-com.de> <48EDC969.5050706@cisco.com>
Mime-Version: 1.0
Cc: henk@ripe.net, ippm@ietf.org
Subject: Re: [ippm] WGLC for draft-ietf-ippm-delay-var-as.
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ippm>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ippm-bounces@ietf.org
Errors-To: ippm-bounces@ietf.org

At 05:05 AM 10/9/2008, Benoit Claise wrote:
>>Rudiger wrote:
>>I'd be interested in learning whether Henk's and Matt's implementations
>>apply this definition or another one. The question goes to all other
>>implementiors too. The more natural selection function seems to be to
>>evaluate pairs of consecutively received packets ignoring their
>>sequence numbers. Draft-ietf-ippm-delay-var-as however works with an
>>IPDV definition assuming awareness of sequence numbers. I'd like to
>>learn whether there are any implementations following the IPDV
>>definition of draft-ietf-ippm-delay-var-as (see section 6.1).
>>
>The Cisco IP SLA feature follows the IPDV definition
>
>Regards, Benoit.

Hi Ruediger,

First, thanks for finding a few typos!

The specific case of packet loss in section 6.1 is also
mentioned in section 4.1 of RFC 3393:
http://tools.ietf.org/html/rfc3393#section-4.1
(don't confuse the selection function with the
conditioned statistics described here, they are
different processes).

In my experience, selection functions are primarily applied
at the Source, and the RFC 3393 definitions refer to index numbers
(or source sequence numbers).  A selection function like you describe
("pairs of consecutively received packets ignoring their
sequence numbers") is certainly possible, and it's important
to understand how different things can be when comparing
results from two different selection functions.
For example, some of your observations on re-routes may not hold for
the IPDV defined in the memo - lost packets and undefined pairs
are a key factor when trying to detect path changes with
"consecutive source packet" IPDV, as we explained.

The WIPM measurement system described in
http://tools.ietf.org/html/draft-ietf-ippm-implement-02
(expired I-D, but I'd still like to see this published as an
Informational RFC, even if it's not a formal part of the
standards track progress of the original RFCs)
implemented both IPDV and PDV as described in the memo.

thanks again, and regards,
Al

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