From owner-psamp@ops.ietf.org Wed Mar 9 16:34:08 2005 Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22849 for ; Wed, 9 Mar 2005 16:34:07 -0500 (EST) Received: from majordom by psg.com with local (Exim 4.44 (FreeBSD)) id 1D98jR-0001L1-GT for psamp-data@psg.com; Wed, 09 Mar 2005 21:28:41 +0000 Received: from [195.101.245.16] (helo=p-mail2.rd.francetelecom.com) by psg.com with esmtp (Exim 4.44 (FreeBSD)) id 1D98jM-0001Kc-Kv for psamp@ops.ietf.org; Wed, 09 Mar 2005 21:28:37 +0000 Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); Wed, 9 Mar 2005 22:22:54 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [ipfix] new version of IPFIX per packet information Date: Wed, 9 Mar 2005 22:22:44 +0100 Message-ID: Thread-Topic: [ipfix] new version of IPFIX per packet information Thread-Index: AcUemo9JgfJXx9YbTFirIcwvOzUIWQGSo9HA From: "STEPHAN Emile RD-CORE-LAN" To: , Cc: X-OriginalArrivalTime: 09 Mar 2005 21:22:54.0075 (UTC) FILETIME=[27EF7CB0:01C524EE] X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on psg.com X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham version=3.0.1 Sender: owner-psamp@ops.ietf.org Precedence: bulk Content-Transfer-Encoding: quoted-printable Dear all, This memo proposes an excellent approach to use the IPFIX protocol to = export performance measurement data. It is clearly in the scope of PSAMP = WG and of IPFIX WG. The draft should propose stable template definitions to export packet = information from a meter to a collector, but not only. I t should define = a common template to export measure results from the collector to an = application. Following I propose a common template 'header' for these 2 = aspects: -- packet information template: Meter to collector ------- flowID=20 sampleID (packetID) =20 packetTimestamp =20 packetLength =20 --- result template: collector to application ---------- flowID=20 sampleID metricID: see IPPM REGISTRY in the RFC Queues =20 Result =20 Such measurement technique is clearly respectful of the IPPM framework. = The document should have at least an IPPM section to present the metrics = measured and discuss each metric.=20 Regards Emile -----Message d'origine----- De=A0: majordomo listserver [mailto:majordomo@mil.doit.wisc.edu] De la = part de Elisa Boschi Envoy=E9=A0: mardi 1 mars 2005 21:08 =C0=A0: ipfix@net.doit.wisc.edu Objet=A0: [ipfix] new version of IPFIX per packet information Dear all, we have submitted a new version of our draft: "export of per-packet=20 information using IPFIX". The latest version can be found here: http://www.ietf.org/internet-drafts/draft-pohl-perpktinfo-02.txt It has been improved taking into consideration the comments we have=20 received so far and includes a section addressing the management of the=20 "FlowIDs" we have introduced. Since it describes an extension to the protocol aimed at providing a=20 more efficient way to export packet information (without requiring any=20 modification to IPFIX), we propose to merge our draft with the IPFIX=20 protocol draft. (find our suggestion at the end of this email) We would like to hear the opinion of the group about this. Since the=20 export of per-packet information is a relevant issue for PSAMP, and all=20 IPFIX doocuments are currently in last call, merging the current=20 proposal with a PSAMP protocol draft is, to our opinion, a valide=20 alternative. In both cases the FlowID field should be added in the IPFIX information=20 model (as a numeric identifier for the flow) The IPFIX prootocol draft could be modified as follow: > Table of Contents > =20 > 1. Points of Discussion.........................................4 > 2. Introduction.................................................5 > 3. Terminology..................................................6 > 4. Criteria for Flow Expiration and Export.....................12 > 5. Message Format..............................................13 > 6. IPFIX Message Format........................................15 > 7. Specific Reporting Requirements.............................26 One section could be added here describing the special case of export of = packet information (the section could eventually be between 6 and 7 too. > 8. "Export Time" Computation and Flow Record Time..............29 > 9. Linkage with the Information Model..........................31 > 10. Variable Length Information Element........................32 > 11. Template Management........................................33 > 12. The Collecting Process's Side..............................36 > 13. Transport Protocol.........................................38 > 14. Security Considerations....................................47 > 15. IANA Considerations........................................51 > 16. Examples...................................................52 Add here the example in the last section of our draft. > 17. References.................................................58 > 18. Acknowledgments............................................6 Regards, Elisa -- Help mailto:majordomo@net.doit.wisc.edu and say "help" in message = body Unsubscribe mailto:majordomo@net.doit.wisc.edu and say "unsubscribe ipfix" in message body Archive http://ipfix.doit.wisc.edu/archive/ -- to unsubscribe send a message to psamp-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: