From MAILER-DAEMON Mon May 01 13:13:33 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fabxl-0008Ga-IO for psamp-archive@lists.ietf.org; Mon, 01 May 2006 13:13:33 -0400 Received: from cumin.apnic.net ([202.12.29.59] helo=apnic.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fabxi-0003Y9-RK for psamp-archive@lists.ietf.org; Mon, 01 May 2006 13:13:33 -0400 Received: from localhost (localhost) by apnic.net (8.12.8/8.12.8) id k41HDTq6003095; Tue, 2 May 2006 03:13:29 +1000 Date: Tue, 2 May 2006 03:13:29 +1000 From: Mail Delivery Subsystem Message-Id: <200605011713.k41HDTq6003095@apnic.net> To: MIME-Version: 1.0 Content-Type: multipart/report; report-type=delivery-status; boundary="k41HDTq6003095.1146503609/apnic.net" Content-Transfer-Encoding: 8bit Subject: Returned mail: see transcript for details Auto-Submitted: auto-generated (failure) X-Spam-Score: 0.0 (/) X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87 This is a MIME-encapsulated message --k41HDTq6003095.1146503609/apnic.net The original message was received at Tue, 2 May 2006 03:13:24 +1000 from kombu.apnic.net [202.12.29.57] ----- The following addresses had permanent fatal errors ----- (reason: 550 Host unknown) ----- Transcript of session follows ----- 550 5.1.2 ... Host unknown (Name server: irr.apnic.net: host not found) --k41HDTq6003095.1146503609/apnic.net Content-Type: message/delivery-status Reporting-MTA: dns; apnic.net Received-From-MTA: DNS; kombu.apnic.net Arrival-Date: Tue, 2 May 2006 03:13:24 +1000 Final-Recipient: RFC822; auto-irr@irr.apnic.net Action: failed Status: 5.1.2 Remote-MTA: DNS; irr.apnic.net Diagnostic-Code: SMTP; 550 Host unknown Last-Attempt-Date: Tue, 2 May 2006 03:13:29 +1000 --k41HDTq6003095.1146503609/apnic.net Content-Type: message/rfc822 Content-Transfer-Encoding: 8bit Return-Path: Received: from kombu.apnic.net (kombu.apnic.net [202.12.29.57]) by apnic.net (8.12.8/8.12.8) with ESMTP id k41HDOq6003081 for ; Tue, 2 May 2006 03:13:24 +1000 Received: from karashi.apnic.net (sec3.apnic.net [202.12.28.140]) by kombu.apnic.net (Postfix) with ESMTP id 62441B0007 for ; Tue, 2 May 2006 03:13:23 +1000 (EST) Received: from lists.ietf.org (ip65-45-63-114.z63-45-65.customer.algx.net [65.45.63.114]) by karashi.apnic.net (Postfix) with ESMTP id EFC826C2B4 for ; Tue, 2 May 2006 03:13:19 +1000 (EST) From: psamp-archive@lists.ietf.org To: auto-irr@apnic.net Subject: delivery failed Date: Mon, 1 May 2006 12:13:17 -0500 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0014_96DD67E0.ACD1E7F3" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Message-Id: <20060501171319.EFC826C2B4@karashi.apnic.net> X-AP-Virus: EMAIL MODIFIED X-AP-Virus: EMAIL MODIFIED X-AP-Spam-Warning: Possible SPAM X-AP-Spam-Status: Yes, hits=8.838 required=6 X-AP-Spam-Score: 8.838 (********) BAYES_99,FORGED_MUA_OUTLOOK,NO_REAL_NAME X-Scanned-By: MIMEDefang 2.15 (www dot roaringpenguin dot com slash mimedefang) This is a multi-part message in MIME format... ------=_NextPart_000_0014_96DD67E0.ACD1E7F3 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline jRA6m`2M}nCIڼQ#>k~pϛe[b%X o&uhen^rF}!-B$H1bU&7rmM y Qƚ\Vi&u6Xεqec S&JQ*O)XC4U9!(0ۘYsAqх˜óX4f~g55֨(e ߹!-pw52to =========================================================================== ====================================================================== WARNING: This e-mail was altered by the APNIC mail system, for security reasons. The specific changes made are described below. For more information about the APNIC Virus and attachments policy, see http://www.apnic.net/info/contact/virus.html ====================================================================== A known virus was discovered and deleted. Virus-scanner messages follow: /var/spool/MIMEDefang/mdefang-445641B4-0/Work/msg-26561-64.zip Found the W32/Mydoom.o@MM!zip virus !!! ------=_NextPart_000_0014_96DD67E0.ACD1E7F3-- --k41HDTq6003095.1146503609/apnic.net-- From psamp-bounces@ietf.org Fri May 05 10:48:40 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fc1bh-0004C9-HE; Fri, 05 May 2006 10:48:37 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fc1bg-0004C4-Sc for psamp@ietf.org; Fri, 05 May 2006 10:48:36 -0400 Received: from mailhub.fokus.fraunhofer.de ([193.174.154.14]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fc1bd-0007CC-CP for psamp@ietf.org; Fri, 05 May 2006 10:48:36 -0400 Received: from EXCHSRV.fokus.fraunhofer.de (bohr [10.147.9.231]) by mailhub.fokus.fraunhofer.de (8.11.6p2/8.11.6) with SMTP id k45EmDn27384; Fri, 5 May 2006 16:48:13 +0200 (MEST) 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="US-ASCII" Content-Transfer-Encoding: quoted-printable Date: Fri, 5 May 2006 16:48:17 +0200 Message-ID: <804B13F8F3D94A4AB18B9B01ACB68FA113792F@EXCHSRV.fokus.fraunhofer.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ipfix] spelling/editorial change to time data types Thread-Index: AcYtZTlV9m5UPK2cTsOcvODB8NSKXhC6vjLg From: "Tanja Zseby" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4 Cc: psamp Subject: [PSAMP] FW: [ipfix] spelling/editorial change to time data types X-BeenThere: psamp@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This mailing list is used for discussion within the IETF packet sampling \(PSAMP\) WG" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: psamp-bounces@ietf.org Hi Thomas, just a small issue: since it was decided for IPFIX to write MilliSeconds etc. with small s instead of capital S, this should also be changed in the next version of PSAMP-INFO. Regards, Tanja=20 -----Original Message----- From: majordomo listserver [mailto:majordomo@mil.doit.wisc.edu] On Behalf Of Benoit Claise Sent: Thursday, February 09, 2006 11:38 AM To: Brian Trammell Cc: ipfix@net.doit.wisc.edu Subject: Re: [ipfix] spelling/editorial change to time data types Brian,=20 All,=20 =09 May be a bit late for this, and may also be a bit pedantic, but I'd like to advocate correcting the spelling of the data type names:=20 =09 3.1.11. dateTimeMilliSeconds . . . . . . . . . . . . . . . . 12=20 3.1.12. dateTimeMicroSeconds . . . . . . . . . . . . . . . . 12=20 3.1.13. dateTimeNanoSeconds . . . . . . . . . . . . . . . . . 12=20 =09 and their associated information elements:=20 =09 5.8.3. flowStartMilliSeconds . . . . . . . . . . . . . . . . 58=20 5.8.4. flowEndMilliSeconds . . . . . . . . . . . . . . . . . 58=20 5.8.5. flowStartMicroSeconds . . . . . . . . . . . . . . . . 58=20 5.8.6. flowEndMicroSeconds . . . . . . . . . . . . . . . . . 58=20 5.8.7. flowStartNanoSeconds . . . . . . . . . . . . . . . . 58=20 5.8.8. flowEndNanoSeconds . . . . . . . . . . . . . . . . . 59=20 5.8.9. flowStartDeltaMicroSeconds . . . . . . . . . . . . . 59=20 5.8.10. flowEndDeltaMicroSeconds . . . . . . . . . . . . . . 59=20 5.8.11. systemInitTimeMilliSeconds . . . . . . . . . . . . . 59=20 5.10.4. flowDurationMilliSeconds . . . . . . . . . . . . . . 67=20 5.10.5. flowDurationMicroSeconds . . . . . . . . . . . . . . 68=20 =09 in IPFIX-INFO 11 and normative references thereto in IPFIX-PROTO 17:=20 =09 6.1.7 dateTimeMilliSeconds.....................................30=20 6.1.8 dateTimeNanoSeconds......................................30=20 6.1.9 dateTimeMicroSeconds.....................................30=20 =09 Addition of an SI prefix does not cause a word break, as implied by the interCap spelling of these identifiers. Suggested correction is to make the "s" in seconds lower-case. This change would of course not apply to dateTimeSeconds, as there _is_ a word break before "Seconds" in that case.=20 =09 (Incidentially, I discovered this problem while testing our implementation, attempting to find the flowStartMilliseconds (properly spelled) IE in our IE registry, which caused a runtime error. Other implementors and users of IPFIX may also run into the same problem in the future, hence this suggestion.)=20 =09 Also, there are references to flowStartDeltaUseconds and flowEndDeltaUseconds in PROTO 19; these should be changed to "DeltaMicroseconds".=20 =09 Good catch! As there were no positive reaction from this community to change the "S" of seconds to lower case, I changed [IPFIX-PROTO] to flowStartDeltaMicroSeconds and flowEndDeltaMicroSeconds... to be consistent with [IPFIX-INFO]. Regards, Benoit. Regards,=20 =09 Brian=20 =09 _______________________________________________ PSAMP mailing list PSAMP@ietf.org https://www1.ietf.org/mailman/listinfo/psamp From psamp-bounces@ietf.org Fri May 05 10:56:59 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fc1jm-0000YY-EH; Fri, 05 May 2006 10:56:58 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fc1jl-0000YT-0b for psamp@ietf.org; Fri, 05 May 2006 10:56:57 -0400 Received: from franclinus.red.cert.org ([192.88.209.16]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fc1jk-0007XF-Nr for psamp@ietf.org; Fri, 05 May 2006 10:56:56 -0400 Received: from franclinus.red.cert.org (localhost [127.0.0.1]) by franclinus.red.cert.org (8.13.1/8.13.1/2.19) with ESMTP id k45Eutd1025842 for ; Fri, 5 May 2006 10:56:55 -0400 Received: (from defang@localhost) by franclinus.red.cert.org (8.13.1/8.13.1/Submit/1.1) id k45Eu881025823 for ; Fri, 5 May 2006 10:56:08 -0400 Received: from villemus.indigo.cert.org (villemus.indigo.cert.org [10.60.10.5]) by franclinus.red.cert.org (envelope-sender ) (MIMEDefang) with ESMTP id k45Eu8d0025821; Fri, 05 May 2006 10:56:08 -0400 (EDT) Received: from [128.237.234.184] (vpn-10-25-4-5.remote.cert.org [10.25.4.5]) by villemus.indigo.cert.org (8.12.11.20060308/8.12.11/2.58) with ESMTP id k45Eu8up031863; Fri, 5 May 2006 10:56:08 -0400 In-Reply-To: <804B13F8F3D94A4AB18B9B01ACB68FA113792F@EXCHSRV.fokus.fraunhofer.de> References: <804B13F8F3D94A4AB18B9B01ACB68FA113792F@EXCHSRV.fokus.fraunhofer.de> Mime-Version: 1.0 (Apple Message framework v749.3) Message-Id: From: Brian Trammell Subject: Re: [PSAMP] FW: [ipfix] spelling/editorial change to time data types Date: Fri, 5 May 2006 10:56:03 -0400 To: Tanja Zseby X-Pgp-Agent: GPGMail 1.1.1 (Tiger) X-Mailer: Apple Mail (2.749.3) X-Spam-Status: No, hits=0 required=5 checker=SpamAssassin version=3.000005 X-Spam-Score: 0.0 (/) X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8 Cc: psamp X-BeenThere: psamp@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This mailing list is used for discussion within the IETF packet sampling \(PSAMP\) WG" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1724745275==" Errors-To: psamp-bounces@ietf.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============1724745275== Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-3-1030039494" Content-Transfer-Encoding: 7bit This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --Apple-Mail-3-1030039494 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed There are also references to the time data types and information element names in PSAMP-PROTO; these should be changed as well. Regards, Brian On May 5, 2006, at 10:48 AM, Tanja Zseby wrote: > Hi Thomas, > > just a small issue: > since it was decided for IPFIX to write MilliSeconds etc. with small s > instead of capital S, this should also be changed in the next > version of > PSAMP-INFO. > > Regards, > Tanja > > -----Original Message----- > From: majordomo listserver [mailto:majordomo@mil.doit.wisc.edu] On > Behalf Of Benoit Claise > Sent: Thursday, February 09, 2006 11:38 AM > To: Brian Trammell > Cc: ipfix@net.doit.wisc.edu > Subject: Re: [ipfix] spelling/editorial change to time data types > > Brian, > > All, > > May be a bit late for this, and may also be a bit pedantic, but > I'd like to advocate correcting the spelling of the data type names: > > 3.1.11. dateTimeMilliSeconds . . . . . . . . . . . . . . > . . 12 > 3.1.12. dateTimeMicroSeconds . . . . . . . . . . . . . . > . . 12 > 3.1.13. dateTimeNanoSeconds . . . . . . . . . . . . . . . > . . 12 > > and their associated information elements: > > 5.8.3. flowStartMilliSeconds . . . . . . . . . . . . . . > . . 58 > 5.8.4. flowEndMilliSeconds . . . . . . . . . . . . . . . > . . 58 > 5.8.5. flowStartMicroSeconds . . . . . . . . . . . . . . > . . 58 > 5.8.6. flowEndMicroSeconds . . . . . . . . . . . . . . . > . . 58 > 5.8.7. flowStartNanoSeconds . . . . . . . . . . . . . . > . . 58 > 5.8.8. flowEndNanoSeconds . . . . . . . . . . . . . . . > . . 59 > 5.8.9. flowStartDeltaMicroSeconds . . . . . . . . . . . > . . 59 > 5.8.10. flowEndDeltaMicroSeconds . . . . . . . . . . . . > . . 59 > 5.8.11. systemInitTimeMilliSeconds . . . . . . . . . . . > . . 59 > 5.10.4. flowDurationMilliSeconds . . . . . . . . . . . . > . . 67 > 5.10.5. flowDurationMicroSeconds . . . . . . . . . . . . > . . 68 > > in IPFIX-INFO 11 and normative references thereto in IPFIX-PROTO > 17: > > 6.1.7 > dateTimeMilliSeconds.....................................30 > 6.1.8 > dateTimeNanoSeconds......................................30 > 6.1.9 > dateTimeMicroSeconds.....................................30 > > Addition of an SI prefix does not cause a word break, as implied > by the interCap spelling of these identifiers. Suggested correction is > to make the "s" in seconds lower-case. This change would of course not > apply to dateTimeSeconds, as there _is_ a word break before > "Seconds" in > that case. > > (Incidentially, I discovered this problem while testing our > implementation, attempting to find the flowStartMilliseconds (properly > spelled) IE in our IE registry, which caused a runtime error. Other > implementors and users of IPFIX may also run into the same problem in > the future, hence this suggestion.) > > Also, there are references to flowStartDeltaUseconds and > flowEndDeltaUseconds in PROTO 19; these should be changed to > "DeltaMicroseconds". > > > > Good catch! > As there were no positive reaction from this community to change > the "S" > of seconds to lower case, I changed [IPFIX-PROTO] to > flowStartDeltaMicroSeconds and flowEndDeltaMicroSeconds... to be > consistent with [IPFIX-INFO]. > > Regards, Benoit. > > > > Regards, > > Brian > > > > > _______________________________________________ > PSAMP mailing list > PSAMP@ietf.org > https://www1.ietf.org/mailman/listinfo/psamp --Apple-Mail-3-1030039494 content-type: application/pgp-signature; x-mac-type=70674453; name=PGP.sig content-description: This is a digitally signed message part content-disposition: inline; filename=PGP.sig content-transfer-encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (Darwin) iD8DBQFEW2eH4/8LCZ4pwvYRAiNyAJ9NNThDciJpsgYe2Cva6S71EC83eQCghuGJ 4gYd9+FBhoMmcH0G41seZrk= =sMlb -----END PGP SIGNATURE----- --Apple-Mail-3-1030039494-- --===============1724745275== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ PSAMP mailing list PSAMP@ietf.org https://www1.ietf.org/mailman/listinfo/psamp --===============1724745275==-- From psamp-bounces@ietf.org Fri May 05 11:02:48 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fc1pP-0002pX-ES; Fri, 05 May 2006 11:02:47 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fc1pN-0002pS-MA for psamp@ietf.org; Fri, 05 May 2006 11:02:45 -0400 Received: from ams-iport-1.cisco.com ([144.254.224.140]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fc1pM-0007lX-Cz for psamp@ietf.org; Fri, 05 May 2006 11:02:45 -0400 Received: from ams-core-1.cisco.com ([144.254.224.150]) by ams-iport-1.cisco.com with ESMTP; 05 May 2006 17:02:45 +0200 Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k45F2hUE007234; Fri, 5 May 2006 17:02:43 +0200 (MEST) Received: from [10.61.64.108] (ams3-vpn-dhcp108.cisco.com [10.61.64.108]) by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id QAA04330; Fri, 5 May 2006 16:02:42 +0100 (BST) Message-ID: <445B6911.8090309@cisco.com> Date: Fri, 05 May 2006 16:02:41 +0100 From: Paul Aitken User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.7.10) Gecko/20050811 Fedora/1.7.10-1.2.1.legacy X-Accept-Language: en-gb, en-us MIME-Version: 1.0 To: Tanja Zseby Subject: Re: [PSAMP] FW: [ipfix] spelling/editorial change to time data types References: <804B13F8F3D94A4AB18B9B01ACB68FA113792F@EXCHSRV.fokus.fraunhofer.de> In-Reply-To: <804B13F8F3D94A4AB18B9B01ACB68FA113792F@EXCHSRV.fokus.fraunhofer.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Cc: psamp X-BeenThere: psamp@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This mailing list is used for discussion within the IETF packet sampling \(PSAMP\) WG" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: psamp-bounces@ietf.org Tanja, > just a small issue: > since it was decided for IPFIX to write MilliSeconds etc. with small s > instead of capital S, this should also be changed in the next version of > PSAMP-INFO. I believe I still have the PSAMP-INFO edit token, so I made this change. I also changed references to the datatype "dateTimeMicroSeconds" into "dateTimeMicroseconds". However, I left "dateTimeSeconds" unchanged. Cheers. -- Paul Aitken Cisco Systems Ltd, Edinburgh, Scotland. _______________________________________________ PSAMP mailing list PSAMP@ietf.org https://www1.ietf.org/mailman/listinfo/psamp From psamp-bounces@ietf.org Fri May 05 11:08:42 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fc1v8-00037m-0E; Fri, 05 May 2006 11:08:42 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fc1v7-00037h-JA for psamp@ietf.org; Fri, 05 May 2006 11:08:41 -0400 Received: from odd-brew.cisco.com ([144.254.15.119] helo=av-tac-bru.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fc1v5-000816-ON for psamp@ietf.org; Fri, 05 May 2006 11:08:41 -0400 X-TACSUNS: Virus Scanned Received: from strange-brew.cisco.com (localhost [127.0.0.1]) by av-tac-bru.cisco.com (8.11.7p1+Sun/8.11.7) with ESMTP id k45F8cl29401; Fri, 5 May 2006 17:08:38 +0200 (CEST) Received: from [10.61.80.95] (ams3-vpn-dhcp4192.cisco.com [10.61.80.95]) by strange-brew.cisco.com (8.11.7p1+Sun/8.11.7) with ESMTP id k45F8aC17058; Fri, 5 May 2006 17:08:37 +0200 (CEST) Message-ID: <445B6A74.30406@cisco.com> Date: Fri, 05 May 2006 17:08:36 +0200 From: Benoit Claise User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Brian Trammell Subject: Re: [PSAMP] FW: [ipfix] spelling/editorial change to time data types References: <804B13F8F3D94A4AB18B9B01ACB68FA113792F@EXCHSRV.fokus.fraunhofer.de> In-Reply-To: X-Spam-Score: 0.1 (/) X-Scan-Signature: df1883a27a831c1ea5e8cfe5eb3ad38e Cc: psamp , Tanja Zseby X-BeenThere: psamp@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This mailing list is used for discussion within the IETF packet sampling \(PSAMP\) WG" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1334448663==" Errors-To: psamp-bounces@ietf.org This is a multi-part message in MIME format. --===============1334448663== Content-Type: multipart/alternative; boundary="------------070804040306030206000307" This is a multi-part message in MIME format. --------------070804040306030206000307 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Brian, > There are also references to the time data types and information > element names in PSAMP-PROTO; these should be changed as well. Good point. In order to avoid any mistake, I will wait for the next version of [IPFIX-INFO] to be out before applying any change. Regards, Benoit. > > Regards, > > Brian > > On May 5, 2006, at 10:48 AM, Tanja Zseby wrote: > >> Hi Thomas, >> >> just a small issue: >> since it was decided for IPFIX to write MilliSeconds etc. with small s >> instead of capital S, this should also be changed in the next version of >> PSAMP-INFO. >> >> Regards, >> Tanja >> >> -----Original Message----- >> From: majordomo listserver [mailto:majordomo@mil.doit.wisc.edu] On >> Behalf Of Benoit Claise >> Sent: Thursday, February 09, 2006 11:38 AM >> To: Brian Trammell >> Cc: ipfix@net.doit.wisc.edu >> Subject: Re: [ipfix] spelling/editorial change to time data types >> >> Brian, >> >> All, >> >> May be a bit late for this, and may also be a bit pedantic, but >> I'd like to advocate correcting the spelling of the data type names: >> >> 3.1.11. dateTimeMilliSeconds . . . . . . . . . . . . . . >> . . 12 >> 3.1.12. dateTimeMicroSeconds . . . . . . . . . . . . . . >> . . 12 >> 3.1.13. dateTimeNanoSeconds . . . . . . . . . . . . . . . >> . . 12 >> >> and their associated information elements: >> >> 5.8.3. flowStartMilliSeconds . . . . . . . . . . . . . . >> . . 58 >> 5.8.4. flowEndMilliSeconds . . . . . . . . . . . . . . . >> . . 58 >> 5.8.5. flowStartMicroSeconds . . . . . . . . . . . . . . >> . . 58 >> 5.8.6. flowEndMicroSeconds . . . . . . . . . . . . . . . >> . . 58 >> 5.8.7. flowStartNanoSeconds . . . . . . . . . . . . . . >> . . 58 >> 5.8.8. flowEndNanoSeconds . . . . . . . . . . . . . . . >> . . 59 >> 5.8.9. flowStartDeltaMicroSeconds . . . . . . . . . . . >> . . 59 >> 5.8.10. flowEndDeltaMicroSeconds . . . . . . . . . . . . >> . . 59 >> 5.8.11. systemInitTimeMilliSeconds . . . . . . . . . . . >> . . 59 >> 5.10.4. flowDurationMilliSeconds . . . . . . . . . . . . >> . . 67 >> 5.10.5. flowDurationMicroSeconds . . . . . . . . . . . . >> . . 68 >> >> in IPFIX-INFO 11 and normative references thereto in IPFIX-PROTO >> 17: >> >> 6.1.7 >> dateTimeMilliSeconds.....................................30 >> 6.1.8 >> dateTimeNanoSeconds......................................30 >> 6.1.9 >> dateTimeMicroSeconds.....................................30 >> >> Addition of an SI prefix does not cause a word break, as implied >> by the interCap spelling of these identifiers. Suggested correction is >> to make the "s" in seconds lower-case. This change would of course not >> apply to dateTimeSeconds, as there _is_ a word break before "Seconds" in >> that case. >> >> (Incidentially, I discovered this problem while testing our >> implementation, attempting to find the flowStartMilliseconds (properly >> spelled) IE in our IE registry, which caused a runtime error. Other >> implementors and users of IPFIX may also run into the same problem in >> the future, hence this suggestion.) >> >> Also, there are references to flowStartDeltaUseconds and >> flowEndDeltaUseconds in PROTO 19; these should be changed to >> "DeltaMicroseconds". >> >> >> >> Good catch! >> As there were no positive reaction from this community to change the "S" >> of seconds to lower case, I changed [IPFIX-PROTO] to >> flowStartDeltaMicroSeconds and flowEndDeltaMicroSeconds... to be >> consistent with [IPFIX-INFO]. >> >> Regards, Benoit. >> >> >> >> Regards, >> >> Brian >> >> >> >> >> _______________________________________________ >> PSAMP mailing list >> PSAMP@ietf.org >> https://www1.ietf.org/mailman/listinfo/psamp > > ------------------------------------------------------------------------ > > _______________________________________________ > PSAMP mailing list > PSAMP@ietf.org > https://www1.ietf.org/mailman/listinfo/psamp > --------------070804040306030206000307 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Brian,
There are also references to the time data types and information element names in PSAMP-PROTO; these should be changed as well.
Good point.
In order to avoid any mistake, I will wait for the next version of [IPFIX-INFO] to be out before applying any change.

Regards, Benoit.

Regards,

Brian

On May 5, 2006, at 10:48 AM, Tanja Zseby wrote:

Hi Thomas,

just a small issue:
since it was decided for IPFIX to write MilliSeconds etc. with small s
instead of capital S, this should also be changed in the next version of
PSAMP-INFO.

Regards,
Tanja

-----Original Message-----
From: majordomo listserver [mailto:majordomo@mil.doit.wisc.edu] On
Behalf Of Benoit Claise
Sent: Thursday, February 09, 2006 11:38 AM
To: Brian Trammell
Cc: ipfix@net.doit.wisc.edu
Subject: Re: [ipfix] spelling/editorial change to time data types

Brian,

    All,
    
    May be a bit late for this, and may also be a bit pedantic, but
I'd like to advocate correcting the spelling of the data type names:
    
           3.1.11. dateTimeMilliSeconds  . . . . . . . . . . . . . .
. .  12
           3.1.12. dateTimeMicroSeconds  . . . . . . . . . . . . . .
. .  12
           3.1.13. dateTimeNanoSeconds . . . . . . . . . . . . . . .
. .  12
    
    and their associated information elements:
    
           5.8.3.  flowStartMilliSeconds . . . . . . . . . . . . . .
. .  58
           5.8.4.  flowEndMilliSeconds . . . . . . . . . . . . . . .
. .  58
           5.8.5.  flowStartMicroSeconds . . . . . . . . . . . . . .
. .  58
           5.8.6.  flowEndMicroSeconds . . . . . . . . . . . . . . .
. .  58
           5.8.7.  flowStartNanoSeconds  . . . . . . . . . . . . . .
. .  58
           5.8.8.  flowEndNanoSeconds  . . . . . . . . . . . . . . .
. .  59
           5.8.9.  flowStartDeltaMicroSeconds  . . . . . . . . . . .
. .  59
           5.8.10. flowEndDeltaMicroSeconds  . . . . . . . . . . . .
. .  59
           5.8.11. systemInitTimeMilliSeconds  . . . . . . . . . . .
. .  59
           5.10.4. flowDurationMilliSeconds  . . . . . . . . . . . .
. .  67
           5.10.5. flowDurationMicroSeconds  . . . . . . . . . . . .
. .  68
    
    in IPFIX-INFO 11 and normative references thereto in IPFIX-PROTO
17:
    
         6.1.7
dateTimeMilliSeconds.....................................30
         6.1.8
dateTimeNanoSeconds......................................30
         6.1.9
dateTimeMicroSeconds.....................................30
    
    Addition of an SI prefix does not cause a word break, as implied
by the interCap spelling of these identifiers. Suggested correction is
to make the "s" in seconds lower-case. This change would of course not
apply to dateTimeSeconds, as there _is_ a word break before "Seconds" in
that case.
    
    (Incidentially, I discovered this problem while testing our
implementation, attempting to find the flowStartMilliseconds (properly
spelled) IE in our IE registry, which caused a runtime error. Other
implementors and users of IPFIX may also run into the same problem in
the future, hence this suggestion.)
    
    Also, there are references to flowStartDeltaUseconds and
flowEndDeltaUseconds in PROTO 19; these should be changed to
"DeltaMicroseconds".
    


Good catch!
As there were no positive reaction from this community to change the "S"
of seconds to lower case, I changed [IPFIX-PROTO] to
flowStartDeltaMicroSeconds and flowEndDeltaMicroSeconds... to be
consistent with [IPFIX-INFO].

Regards, Benoit.



    Regards,
    
    Brian
    



_______________________________________________
PSAMP mailing list
PSAMP@ietf.org
https://www1.ietf.org/mailman/listinfo/psamp 


_______________________________________________
PSAMP mailing list
PSAMP@ietf.org
https://www1.ietf.org/mailman/listinfo/psamp

--------------070804040306030206000307-- --===============1334448663== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ PSAMP mailing list PSAMP@ietf.org https://www1.ietf.org/mailman/listinfo/psamp --===============1334448663==-- From MAILER-DAEMON Tue May 09 09:50:43 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FdSbq-0003iH-WD for psamp-archive@lists.ietf.org; Tue, 09 May 2006 09:50:43 -0400 Received: from omr-m10.mx.aol.com ([64.12.138.22]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FdSbp-0001c4-PS for psamp-archive@lists.ietf.org; Tue, 09 May 2006 09:50:42 -0400 Received: from rly-yh05.mx.aol.com (rly-yh05.mail.aol.com [172.18.180.69]) by omr-m10.mx.aol.com (v107.10) with ESMTP id RELAYIN7-844609e1ee6; Tue, 09 May 2006 09:50:22 -0400 Received: from localhost (localhost) by rly-yh05.mx.aol.com (8.8.8/8.8.8/AOL-5.0.0) with internal id JAC17693; Tue, 9 May 2006 09:50:22 -0400 (EDT) Date: Tue, 9 May 2006 09:50:22 -0400 (EDT) From: Mail Delivery Subsystem Message-Id: <200605091350.JAC17693@rly-yh05.mx.aol.com> To: MIME-Version: 1.0 Content-Type: multipart/report; report-type=delivery-status; boundary="JAC17693.1147182622/rly-yh05.mx.aol.com" Subject: Returned mail: User unknown Auto-Submitted: auto-generated (failure) X-AOL-IP: 172.18.180.69 X-Spam-Score: 0.0 (/) X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88 This is a MIME-encapsulated message --JAC17693.1147182622/rly-yh05.mx.aol.com The original message was received at Tue, 9 May 2006 09:50:06 -0400 (EDT) from host194-158.pool8173.interbusiness.it [81.73.158.194] *** ATTENTION *** Your e-mail is being returned to you because there was a problem with its delivery. The address which was undeliverable is listed in the section labeled: "----- The following addresses had permanent fatal errors -----". The reason your mail is being returned to you is listed in the section labeled: "----- Transcript of Session Follows -----". The line beginning with "<<<" describes the specific reason your e-mail could not be delivered. The next line contains a second error message which is a general translation for other e-mail servers. Please direct further questions regarding this message to your e-mail administrator. --AOL Postmaster ----- The following addresses had permanent fatal errors ----- ----- Transcript of session follows ----- ... while talking to air-yh01.mail.aol.com.: >>> RCPT To: <<< 550 MAILBOX NOT FOUND 550 ... User unknown --JAC17693.1147182622/rly-yh05.mx.aol.com Content-Type: message/delivery-status Reporting-MTA: dns; rly-yh05.mx.aol.com Arrival-Date: Tue, 9 May 2006 09:50:06 -0400 (EDT) Final-Recipient: RFC822; pgoingdown@aol.com Action: failed Status: 5.1.1 Remote-MTA: DNS; air-yh01.mail.aol.com Diagnostic-Code: SMTP; 550 MAILBOX NOT FOUND Last-Attempt-Date: Tue, 9 May 2006 09:50:22 -0400 (EDT) --JAC17693.1147182622/rly-yh05.mx.aol.com Content-Type: text/rfc822-headers Received: from lists.ietf.org (host194-158.pool8173.interbusiness.it [81.73.158.194]) by rly-yh05.mx.aol.com (vx) with ESMTP id MAILRELAYINYH52-2c844609e0a3cf; Tue, 09 May 2006 09:50:03 -0400 From: psamp-archive@lists.ietf.org To: pgoingdown@aol.com Subject: Returned mail: see transcript for details Date: Tue, 9 May 2006 15:49:53 +0200 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0014_9D2890BF.55737E13" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-AOL-IP: 81.73.158.194 X-AOL-SCOLL-SCORE: 0:2:421822723:11542724 X-AOL-SCOLL-URL_COUNT: 0 Message-ID: <200605090950.2c844609e0a3cf@rly-yh05.mx.aol.com> --JAC17693.1147182622/rly-yh05.mx.aol.com-- From MAILER-DAEMON Mon May 15 19:06:17 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ffm8n-0003rn-8g for psamp-archive@lists.ietf.org; Mon, 15 May 2006 19:06:17 -0400 Received: from omr-m06.mx.aol.com ([64.12.138.18]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ffm8k-00023b-1o for psamp-archive@lists.ietf.org; Mon, 15 May 2006 19:06:17 -0400 Received: from air-yd04.mail.aol.com (air-yd04.mail.aol.com [172.18.141.74]) by omr-m06.mx.aol.com (v107.10) with ESMTP id RELAYIN6-7446909561b4; Mon, 15 May 2006 19:05:58 -0400 from: Mail Delivery Subsystem Date: Mon, 15 May 2006 19:01:05 EDT To: Subject: Mail Delivery Problem Mailer: AIRmail [v109.12] X-AOL-IP: 172.18.141.74 Message-ID: <200605151905.7446909561b4@omr-m06.mx.aol.com> X-Spam-Score: 0.0 (/) X-Scan-Signature: 2870a44b67ee17965ce5ad0177e150f4 Sorry psamp-archive@lists.ietf.org. Your mail to the following recipients could not be delivered because they are not accepting mail with attachments or embedded images: emailfaq From psamp-bounces@ietf.org Mon May 29 08:07:40 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FkgWZ-00080F-Hp; Mon, 29 May 2006 08:07:07 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FkgWX-0007zk-Lv for psamp@ietf.org; Mon, 29 May 2006 08:07:05 -0400 Received: from odd-brew.cisco.com ([144.254.15.119] helo=av-tac-bru.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FkgWW-0006EJ-9Z for psamp@ietf.org; Mon, 29 May 2006 08:07:05 -0400 X-TACSUNS: Virus Scanned Received: from strange-brew.cisco.com (localhost [127.0.0.1]) by av-tac-bru.cisco.com (8.11.7p1+Sun/8.11.7) with ESMTP id k4TC73911356; Mon, 29 May 2006 14:07:03 +0200 (CEST) Received: from [10.82.240.95] (rtp-vpn2-95.cisco.com [10.82.240.95]) by strange-brew.cisco.com (8.11.7p1+Sun/8.11.7) with ESMTP id k4TC70C15905; Mon, 29 May 2006 14:07:01 +0200 (CEST) Message-ID: <447AE3E3.8060607@cisco.com> Date: Mon, 29 May 2006 14:06:59 +0200 From: Benoit Claise User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Paul Aitken References: <447AD7D1.2070502@cisco.com> In-Reply-To: <447AD7D1.2070502@cisco.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352 Cc: psamp , ipfix Subject: [PSAMP] Re: [ipfix] multiple Exporting Processes in IPFIX-ARCH X-BeenThere: psamp@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This mailing list is used for discussion within the IETF packet sampling \(PSAMP\) WG" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: psamp-bounces@ietf.org Paul, > Dear all, > > This text in IPFIX-ARCH: > > * IPFIX Device > > An IPFIX Device hosts at least one Observation Point, a Metering > Process and an Exporting Process. > > seems to say that there is one one MP and one EP, which is clearly > wrong. eg, Figure 3 shows one IPFIX device with multiple OPs, multiple > MPs and multiple EPs: > > +------------------------+ > |IPFIX Device(i) | > |[Observation Point(s)] | > |[Metering Process(es)] | > |[Exporting Process(es)] | > +------------------------+ > > The text should say > > An IPFIX Device hosts at least one Observation Point, at least > one Metering Process and at least one Exporting Process. I agree. I modified [IPFIX-PROTO]. Some PSAMP drafts should be modified as well, if I recall correctly Regards, Benoit. > > > Figure 4 doesn't make clear whether there may be multiple exporters > associated with each MP. I believe that should be possible to provide > redundancy, for export over different transports, to convey the MP > output to multiple collectors, or even to impliment different export > protocols. > > Without being spelt out in the text, the way it's drawn does seem to > constrain each MP to just one EP. I don't see any architectural reason > for that. > > Cheers. _______________________________________________ PSAMP mailing list PSAMP@ietf.org https://www1.ietf.org/mailman/listinfo/psamp