[ippm] Implementation report
"Yves Cognet" <yves@qosmetrics.net> Wed, 25 August 2004 13:21 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 JAA13057 for <ippm-archive@lists.ietf.org>; Wed, 25 Aug 2004 09:21:48 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BzxBG-0006T9-Eq; Wed, 25 Aug 2004 08:47:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bzjz9-00036X-Og for ippm@megatron.ietf.org; Tue, 24 Aug 2004 18:41:52 -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 SAA19964 for <ippm@ietf.org>; Tue, 24 Aug 2004 18:41:39 -0400 (EDT)
Received: from [69.84.11.62] (helo=mail.qosmetrics.com) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1Bzjzf-0002eq-9d for ippm@ietf.org; Tue, 24 Aug 2004 18:42:20 -0400
Received: (qmail 3999 invoked from network); 24 Aug 2004 22:41:26 -0000
Received: from unknown (HELO yves) (69.84.11.62) by bugs.internal.qosmetrics.com with SMTP; 24 Aug 2004 22:41:26 -0000
Message-ID: <026401c48a2b$5c7ae040$870110ac@yves>
From: Yves Cognet <yves@qosmetrics.net>
To: ippm@ietf.org
Date: Wed, 25 Aug 2004 00:40:31 +0200
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 559439f19b20fd64c5cd872aef84c6f3
X-Mailman-Approved-At: Wed, 25 Aug 2004 08:47:09 -0400
Cc: STEPHAN Emile FTRD/DAC/LAN <emile.stephan@francetelecom.com>, joeo@qosmetrics.com
Subject: [ippm] Implementation report
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Yves Cognet <yves@qosmetrics.net>
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="===============1902945371=="
Sender: ippm-bounces@ietf.org
Errors-To: ippm-bounces@ietf.org
Hi all I'm not sure this is the right channel, but we do have an iplementation of IPPM and you will find some more detail herafter. We are working closely with FT R&D Emile Stephan on several subjects including the IPPM MIB. Feel free to contact me or us regards Yves Cognet President yves_cognet@qosmetrics.com General ======= Name of Implementation: NetWarrior Organization: QoSmetrics, SA. Contact details: QoSmetrics, Inc. Joe Ovanesian VP Engineering 802 Calle Plano Camarillo, CA 93012 USA joe_ovanesian@qosmetrics.com www.qosmetrics.com Origin of code: Written from scratch. Platform: Last release run on Linux 2.4.22 Hardware time stamping engine TSE (tx and rx) with built-in GPS and TXC0 This platform is running IPv4 and IPv6, PPPoE with both static, dynamic and Nated IP address. The platform has been tested in both ipv4 and ipv6 environment (except PPPoE) Metrics considered ---------------------------- RFC2330 IPPM sync method RFC2678 Connectivity RFC2679 One way delay RFC2680 Packet Loss RFC2681 Round trip Delay RFC2678/Type-P-Instantaneous-Bidirectional-Connectivity ------------------------------------------------------- Parameters: Implemented? + Src, the IP address of a host Yes + Dst, the IP address of a host Yes + T, a time Yes + TTL Yes + payload length Yes + TOS/DSCP Yes + VLAN Yes Units: + dT Yes Methodology: + According to section 3.1 of RFC 2678 + Synchronization via TSE card + Timestamping in hardware via TSE card Comments (Type-P): + TCP packets are being used over ipv4 and ipv6. + TCP checksum is over written when the frame is sent and when the TSE is appending the time stamp + The port numbers for test traffic can be specified + User data length is user defined + access to special IP bits ( TOS/DSCP values ) + If a packet is duplicated, any duplicates are counted (the delay of the first packet to arrives is used). + Corrupted packets are counted as lost; they will fail either a hardware CRC check, or IP or UDP checksum verification. Features included: + path variation (TTL variation) Features not implemented: Reporting the metric: + all results are recorded in an SQL database, good and bad records (lost of synchronization) + all timestamps are reported in UTC + local aggregation can be done + TTL variation are being recorded RFC2679/Type-P-One-way-Delay ---------------------------- Parameters: Implemented? + Src, the IP address of a host Yes + Dst, the IP address of a host Yes + T, a time Yes + Payload yes + VLAN ID Yes Units: + dT Yes Methodology: + According to section 3.6 of RFC 2679 + Synchronization via TSE card + Timestamping in hardware via TSE card Comments (Type-P): + UDP and TCP packets are being used over ipv4 and ipv6. + TCP checksum is over written when the frame is sent and when the TSE is appending the time stamp + The port numbers for test traffic can be specified among sessions, although for any given session port numbers were fixed + User data length was 12 bytes (32 bit sequence number, 64 bit time value) + access to special IP bits ( TOS/DSCP values ) + If a packet is duplicated, any duplicates are counted (the delay of the first packet to arrives is used). + Corrupted packets are counted as lost; they will fail either a hardware CRC check, or IP or UDP checksum verification. Features included: + If either end lost synchronization (as reported by the TSE timing card) the session is kept but results are marked invalid. + path variation (TTL variation) Features not implemented: Reporting the metric: + all results are recorded in an SQL database, good and bad records (lost of synchronization) + The loss threshold is 1 received packets for UPD traffic. + all timestamps are reported in UTC + local aggregation can be done + TTL variation are being recorded Tests performed: + calibration, measured time uncertainty is in the 450 ns range end to end once TSE cards are in sync RFC2679/Type-P-One-way-Delay-Poisson-Stream ------------------------------------------- not implemented RFC2679/Type-P-One-way-Delay-Percentile --------------------------------------- By default, the 50th percentile (median) and 90th percentile are calculated and reported for x minute intervals.(user setup) RFC2679/Type-P-One-way-Delay-Median ----------------------------------- This value can be calculated and reported from the database RFC2679/Type-P-One-way-Delay-Minimum ------------------------------------ This value is reported for x minute intervals (user setup) RFC2679/Type-P-One-way-Delay-Inverse-Percentile ----------------------------------------------- Not implemented. RFC2680/Type-P-One-way-Packet-Loss ---------------------------------- Metric Parameters: Implemented + Src, the IP address of a host Yes + Dst, the IP address of a host Yes + T, a time Yes Metric Units: + Type-P-One-way-Packet-Loss Yes Comments: + The time is the time the packet was sent, (40 nano second ticks). + Packets that arrive at the machine corrupted are dropped (CRC failure or by IP or UDP checksum failure) + If a packet is duplicated, any duplicates are ignored. RFC2680/Type-P-One-way-Packet-Loss-Poisson-Stream ------------------------------------------------- Not implemented RFC2680/Type-P-One-way-Packet-Loss-Average ------------------------------------------ Not implemented RFC2681 Round trip Delay -------------------------- Not implemented , comuted - (we make use of One Way Delay) Other features implemented -------------------------- Our system is implementing the E Model as defined by ITU for accumulated loss and jitter over period of time IPPM MIB (experimental) - the test has been done with FT R&D Lannion and San Francisco: contact name Emile Stephan IPFIX (passive monitoring)
_______________________________________________ ippm mailing list ippm@ietf.org https://www1.ietf.org/mailman/listinfo/ippm
- [ippm] Implementation report Yves Cognet