From ipfix-bounces@ietf.org Tue May 6 07:15:17 2008 Return-Path: X-Original-To: ipfix-archive@lists.ietf.org Delivered-To: ietfarch-ipfix-archive@core3.amsl.com Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D91D928C3DA; Tue, 6 May 2008 07:15:17 -0700 (PDT) X-Original-To: ipfix@core3.amsl.com Delivered-To: ipfix@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1E24A28C369 for ; Tue, 6 May 2008 07:15:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.352 X-Spam-Level: X-Spam-Status: No, score=0.352 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001] 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 mLbOJz5uk7e9 for ; Tue, 6 May 2008 07:15:14 -0700 (PDT) Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by core3.amsl.com (Postfix) with ESMTP id 4328828C3D6 for ; Tue, 6 May 2008 07:15:13 -0700 (PDT) Received: from FRVELSBHS02.ad2.ad.alcatel.com (frvelsbhs02.ad2.ad.alcatel.com [155.132.6.74]) by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m46EFBuk025294 for ; Tue, 6 May 2008 16:15:11 +0200 Received: from FRVELSMBS13.ad2.ad.alcatel.com ([155.132.6.37]) by FRVELSBHS02.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.2499); Tue, 6 May 2008 16:15:10 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 6 May 2008 16:15:10 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Remote configuration Thread-Index: Acivg5fIL/buQ6vNTU+kHO5r7DA+2w== From: "PECCI PASCAL" To: X-OriginalArrivalTime: 06 May 2008 14:15:10.0934 (UTC) FILETIME=[98366F60:01C8AF83] X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13 Subject: [IPFIX] Remote configuration X-BeenThere: ipfix@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IPFIX WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1144403319==" Sender: ipfix-bounces@ietf.org Errors-To: ipfix-bounces@ietf.org This is a multi-part message in MIME format. --===============1144403319== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C8AF83.98140A1F" This is a multi-part message in MIME format. ------_=_NextPart_001_01C8AF83.98140A1F Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear all, I recently read documents concerning drafts and RFC of IPFIX. It is = underlined that no remote configuration of IPFIX device (end of p4 of = architecture draft for example) will be available with this protocol . = As the definition of the protocol is on-going, do you intend to improve = this protocol and include this characteristic ? Best regards, Pascal PECCI, Ph D Ing=E9nieur de recherche / Research Engineer Alcatel Lucent France Bell Labs Villarceaux (+33) 1 30 77 74 91 Pascal.Pecci@alcatel-lucent.fr ------_=_NextPart_001_01C8AF83.98140A1F Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Remote configFrom ipfix-bounces@ietf.org Tue May 6 07:15:17 2008 Return-Path: <ipfix-bounces@ietf.org> X-Original-To: ipfix-archive@optimus.ietf.org Delivered-To: ietfarch-ipfix-archive@core3.amsl.com Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D91D928C3DA; Tue, 6 May 2008 07:15:17 -0700 (PDT) X-Original-To: ipfix@core3.amsl.com Delivered-To: ipfix@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1E24A28C369 for <ipfix@core3.amsl.com>; Tue, 6 May 2008 07:15:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.352 X-Spam-Level: X-Spam-Status: No, score=0.352 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001] 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 mLbOJz5uk7e9 for <ipfix@core3.amsl.com>; Tue, 6 May 2008 07:15:14 -0700 (PDT) Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by core3.amsl.com (Postfix) with ESMTP id 4328828C3D6 for <ipfix@ietf.org>; Tue, 6 May 2008 07:15:13 -0700 (PDT) Received: from FRVELSBHS02.ad2.ad.alcatel.com (frvelsbhs02.ad2.ad.alcatel.com [155.132.6.74]) by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m46EFBuk025294 for <ipfix@ietf.org>; Tue, 6 May 2008 16:15:11 +0200 Received: from FRVELSMBS13.ad2.ad.alcatel.com ([155.132.6.37]) by FRVELSBHS02.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.2499); Tue, 6 May 2008 16:15:10 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 6 May 2008 16:15:10 +0200 Message-ID: <DDF53707CD16D84DA4BC1DEB5A5DF2390182F0EF@FRVELSMBS13.ad2.ad.alcatel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Remote configuration Thread-Index: Acivg5fIL/buQ6vNTU+kHO5r7DA+2w== From: "PECCI PASCAL" <Pascal.Pecci@alcatel-lucent.fr> To: <ipfix@ietf.org> X-OriginalArrivalTime: 06 May 2008 14:15:10.0934 (UTC) FILETIME=[98366F60:01C8AF83] X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13 Subject: [IPFIX] Remote configuration X-BeenThere: ipfix@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IPFIX WG discussion list <ipfix.ietf.org> List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=unsubscribe> List-Archive: <http://www.ietf.org/pipermail/ipfix> List-Post: <mailto:ipfix@ietf.org> List-Help: <mailto:ipfix-request@ietf.org?subject=help> List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=subscribe> Content-Type: multipart/mixed; boundary="===============1144403319==" Sender: ipfix-bounces@ietf.org Errors-To: ipfix-bounces@ietf.org This is a multi-part message in MIME format. --===============1144403319== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C8AF83.98140A1F" This is a multi-part message in MIME format. ------_=_NextPart_001_01C8AF83.98140A1F Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear all, I recently read documents concerning drafts and RFC of IPFIX. It is = underlined that no remote configuration of IPFIX device (end of p4 of = architecture draft for example) will be available with this protocol . = As the definition of the protocol is on-going, do you intend to improve = this protocol and include this characteristic ? Best regards, Pascal PECCI, Ph D Ing=E9nieur de recherche / Research Engineer Alcatel Lucent France Bell Labs Villarceaux (+33) 1 30 77 74 91 Pascal.Pecci@alcatel-lucent.fr ------_=_NextPart_001_01C8AF83.98140A1F Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Diso-8859-1"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = 6.5.7652.24"> <TITLE>Remote confuration

Dear = all,

I recently read = documents concerning drafts and RFC of IPFIX. It is underlined that no = remote configuration of IPFIX device (end of p4 of architecture draft = for example) will be available with this protocol . As the definition of = the protocol is on-going, do you intend to improve this protocol and = include this characteristic ?

Best = regards,

Pascal PECCI, Ph = D
Ing=E9nieur de = recherche / Research Engineer

Alcatel Lucent = France
Bell Labs = Villarceaux

(+33) 1 30 77 74 = 91
Pascal.Pecci@alcatel-lucent.fr

------_=_NextPart_001_01C8AF83.98140A1F-- --===============1144403319== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ IPFIX mailing list IPFIX@ietf.org https://www.ietf.org/mailman/listinfo/ipfix --===============1144403319==-- iguration

Dear = all,

I recently read = documents concerning drafts and RFC of IPFIX. It is underlined that no = remote configuration of IPFIX device (end of p4 of architecture draft = for example) will be available with this protocol . As the definition of = the protocol is on-going, do you intend to improve this protocol and = include this characteristic ?

Best = regards,

Pascal PECCI, Ph = D
Ing=E9nieur de = recherche / Research Engineer

Alcatel Lucent = France
Bell Labs = Villarceaux

(+33) 1 30 77 74 = 91
Pascal.Pecci@alcatel-lucent.fr

------_=_NextPart_001_01C8AF83.98140A1F-- --===============1144403319== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ IPFIX mailing list IPFIX@ietf.org https://www.ietf.org/mailman/listinfo/ipfix --===============1144403319==-- From ipfix-bounces@ietf.org Tue May 6 07:29:36 2008 Return-Path: X-Original-To: ipfix-archive@optimus.ietf.org Delivered-To: ietfarch-ipfix-archive@core3.amsl.com Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F19563A6954; Tue, 6 May 2008 07:29:35 -0700 (PDT) X-Original-To: ipfix@core3.amsl.com Delivered-To: ipfix@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6C78F3A6AD3 for ; Tue, 6 May 2008 07:29:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.252 X-Spam-Level: X-Spam-Status: No, score=-2.252 tagged_above=-999 required=5 tests=[AWL=0.346, BAYES_00=-2.599, HTML_MESSAGE=0.001] 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 EClQJrEwJ2OX for ; Tue, 6 May 2008 07:29:25 -0700 (PDT) Received: from nj300815-nj-outbound.avaya.com (nj300815-nj-outbound.net.avaya.com [198.152.12.100]) by core3.amsl.com (Postfix) with ESMTP id 9D6773A688E for ; Tue, 6 May 2008 07:29:25 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.27,443,1204520400"; d="scan'208,217";a="117570546" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by nj300815-nj-outbound.avaya.com with ESMTP; 06 May 2008 10:29:22 -0400 X-IronPort-AV: E=Sophos;i="4.27,443,1204520400"; d="scan'208,217";a="198092914" Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by co300216-co-erhwest-out.avaya.com with ESMTP; 06 May 2008 10:29:21 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 6 May 2008 16:29:20 +0200 Message-ID: In-reply-to: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [IPFIX] Remote configuration Thread-Index: Acivg5fIL/buQ6vNTU+kHO5r7DA+2wAAfP4A References: From: "Romascanu, Dan (Dan)" To: "PECCI PASCAL" , Subject: Re: [IPFIX] Remote configuration X-BeenThere: ipfix@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IPFIX WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0821080884==" Sender: ipfix-bounces@ietf.org Errors-To: ipfix-bounces@ietf.org This is a multi-part message in MIME format. --===============0821080884== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C8AF85.92DF06B7" This is a multi-part message in MIME format. ------_=_NextPart_001_01C8AF85.92DF06B7 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable See = http://www.ietf.org/internet-drafts/draft-muenz-ipfix-configuration-04.tx= t.=20 =20 Dan =20 ________________________________ From: ipfix-bounces@ietf.org [mailto:ipfix-bounces@ietf.org] On Behalf = Of PECCI PASCAL Sent: Tuesday, May 06, 2008 5:15 PM To: ipfix@ietf.org Subject: [IPFIX] Remote configuration =09 =09 Dear all,=20 I recently read documents concerning drafts and RFC of IPFIX. It is = underlined that no remote configuration of IPFIX device (end of p4 of = architecture draft for example) will be available with this protocol . = As the definition of the protocol is on-going, do you intend to improve = this protocol and include this characteristic ? Best reFrom ipfix-bounces@ietf.org Tue May 6 07:29:36 2008 Return-Path: X-Original-To: ipfix-archive@lists.ietf.org Delivered-To: ietfarch-ipfix-archive@core3.amsl.com Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F19563A6954; Tue, 6 May 2008 07:29:35 -0700 (PDT) X-Original-To: ipfix@core3.amsl.com Delivered-To: ipfix@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6C78F3A6AD3 for ; Tue, 6 May 2008 07:29:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.252 X-Spam-Level: X-Spam-Status: No, score=-2.252 tagged_above=-999 required=5 tests=[AWL=0.346, BAYES_00=-2.599, HTML_MESSAGE=0.001] 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 EClQJrEwJ2OX for ; Tue, 6 May 2008 07:29:25 -0700 (PDT) Received: from nj300815-nj-outbound.avaya.com (nj300815-nj-outbound.net.avaya.com [198.152.12.100]) by core3.amsl.com (Postfix) with ESMTP id 9D6773A688E for ; Tue, 6 May 2008 07:29:25 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.27,443,1204520400"; d="scan'208,217";a="117570546" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by nj300815-nj-outbound.avaya.com with ESMTP; 06 May 2008 10:29:22 -0400 X-IronPort-AV: E=Sophos;i="4.27,443,1204520400"; d="scan'208,217";a="198092914" Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by co300216-co-erhwest-out.avaya.com with ESMTP; 06 May 2008 10:29:21 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 6 May 2008 16:29:20 +0200 Message-ID: In-reply-to: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [IPFIX] Remote configuration Thread-Index: Acivg5fIL/buQ6vNTU+kHO5r7DA+2wAAfP4A References: From: "Romascanu, Dan (Dan)" To: "PECCI PASCAL" , Subject: Re: [IPFIX] Remote configuration X-BeenThere: ipfix@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IPFIX WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0821080884==" Sender: ipfix-bounces@ietf.org Errors-To: ipfix-bounces@ietf.org This is a multi-part message in MIME format. --===============0821080884== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C8AF85.92DF06B7" This is a multi-part message in MIME format. ------_=_NextPart_001_01C8AF85.92DF06B7 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable See = http://www.ietf.org/internet-drafts/draft-muenz-ipfix-configuration-04.tx= t.=20 =20 Dan =20 ________________________________ From: ipfix-bounces@ietf.org [mailto:ipfix-bounces@ietf.org] On Behalf = Of PECCI PASCAL Sent: Tuesday, May 06, 2008 5:15 PM To: ipfix@ietf.org Subject: [IPFIX] Remote configuration =09 =09 Dear all,=20 I recently read documents concerning drafts and RFC of IPFIX. It is = underlined that no remote configuration of IPFIX device (end of p4 of = architecture draft for example) will be available with this protocol . = As the definition of the protocol is on-going, do you intend to improve = this protocol and include this characteristic ? Best regagards,=20 Pascal PECCI, Ph D=20 Ing=E9nieur de recherche / Research Engineer=20 Alcatel Lucent France=20 Bell Labs Villarceaux=20 (+33) 1 30 77 74 91=20 Pascal.Pecci@alcatel-lucent.fr=20 ------_=_NextPart_001_01C8AF85.92DF06B7 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Remote configuration
See http://www.ietf.org/internet-drafts/draft-muenz-ipfix-configur= ation-04.txt.=20
 
Dan
 

From: ipfix-bounces@ietf.org=20 [mailto:ipfix-bounces@ietf.org] On Behalf Of PECCI=20 PASCAL
Sent: Tuesday, May 06, 2008 5:15 PM
To:=20 ipfix@ietf.org
Subject: [IPFIX] Remote=20 configuration

Dear all, =

I recently read = documents concerning=20 drafts and RFC of IPFIX. It is underlined that no remote configuration = of=20 IPFIX device (end of p4 of architecture draft for example) will be = available=20 with this protocol . As the definition of the protocol is on-going, do = you=20 intend to improve this protocol and include this characteristic=20 ?

Best = regards,

Pascal PECCI, Ph = D=20
Ing=E9nieur de = recherche / Research=20 Engineer

Alcatel Lucent=20 France
Bell Labs=20 Villarceaux

(+33) 1 30 77 74 = 91=20
Pascal.Pecci@alcatel-lucent.fr=20

------_=_NextPart_001_01C8AF85.92DF06B7-- --===============0821080884== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ IPFIX mailing list IPFIX@ietf.org https://www.ietf.org/mailman/listinfo/ipfix --===============0821080884==-- rds,=20 Pascal PECCI, Ph D=20 Ing=E9nieur de recherche / Research Engineer=20 Alcatel Lucent France=20 Bell Labs Villarceaux=20 (+33) 1 30 77 74 91=20 Pascal.Pecci@alcatel-lucent.fr=20 ------_=_NextPart_001_01C8AF85.92DF06B7 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Remote configuration
See http://www.ietf.org/internet-drafts/draft-muenz-ipfix-configur= ation-04.txt.=20
 
Dan
 

From: ipfix-bounces@ietf.org=20 [mailto:ipfix-bounces@ietf.org] On Behalf Of PECCI=20 PASCAL
Sent: Tuesday, May 06, 2008 5:15 PM
To:=20 ipfix@ietf.org
Subject: [IPFIX] Remote=20 configuration

Dear all, =

I recently read = documents concerning=20 drafts and RFC of IPFIX. It is underlined that no remote configuration = of=20 IPFIX device (end of p4 of architecture draft for example) will be = available=20 with this protocol . As the definition of the protocol is on-going, do = you=20 intend to improve this protocol and include this characteristic=20 ?

Best = regards,

Pascal PECCI, Ph = D=20
Ing=E9nieur de = recherche / Research=20 Engineer

Alcatel Lucent=20 France
Bell Labs=20 Villarceaux

(+33) 1 30 77 74 = 91=20
Pascal.Pecci@alcatel-lucent.fr=20

------_=_NextPart_001_01C8AF85.92DF06B7-- --===============0821080884== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ IPFIX mailing list IPFIX@ietf.org https://www.ietf.org/mailman/listinfo/ipfix --===============0821080884==-- From fakename@berkshire.rr.com Tue May 6 15:45:48 2008 Return-Path: X-Original-To: ietfarch-ipfix-archive@core3.amsl.com Delivered-To: ietfarch-ipfix-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3B3CE3A6830 for ; Tue, 6 May 2008 15:45:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -61.793 X-Spam-Level: X-Spam-Status: No, score=-61.793 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_IP_ADDR=1.119, HOST_MISMATCH_COM=0.311, HTML_MESSAGE=0.001, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, URIBL_BLACK=20, URIBL_JP_SURBL=10, 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 zJNee8eiqgyN for ; Tue, 6 May 2008 15:45:47 -0700 (PDT) Received: from [90.199.19.150] (5ac71396.bb.sky.com [90.199.19.150]) by core3.amsl.com (Postfix) with ESMTP id C43163A689A for ; Tue, 6 May 2008 15:45:46 -0700 (PDT) Received: from [90.199.19.150] by cdptpa-smtpin02.mail.rr.com; Tue, 6 May 2008 22:45:43 +0000 Message-ID: <01c8afca$ea58c580$9613c75a@fakename> From: "Google AdWords" To: Subject: You have one or more alerts. Date: Tue, 6 May 2008 22:45:43 +0000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01C8AFCA.EA58C580" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.3790.2663 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2663 This is a multi-part message in MIME format. ------=_NextPart_000_0007_01C8AFCA.EA58C580 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ------------------------------------------------------------------------ This message was sent from a notification-only email address that does not accept incoming email. Please do not reply to this message. --------------------------------------------------------------------- Dear Google AdWords Customer, We were unable to process your payment. Your ads will be suspended soon unless we can process your payment. To prevent your ads from being suspended, please update your payment info= rmation. Please sign in to your account at http://adwords.google.com/select/login, and update your payment information. ------------------------------------------------------------------------- We look forward to providing you with the most effective advertising avai= lable. Thank you for choosing AdWords. ------=_NextPart_000_0007_01C8AFCA.EA58C580 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable -------------------------------------------------------------------------= -
This message was sent from a notification-only email address that does not accept incoming email. Please do not reply to this message.
-------------------------------------------------------------------------= -
Dear Google AdWords Customer,

We were unable to process your payment.
Your ads will be suspended soon unless we can process your payment.
To prevent your ads from being suspended, please update your payment info= rmation.

Please sign in
to your account at http://adwords.google.com/select/login,
and update your payment information.

----------------------------------------------------------------------- We look forward to providing you with the most effective advertising avai= lable.
Thank you for choosing AdWords.
-------------------------------------------------------------------------= ---
------=_NextPart_000_0007_01C8AFCA.EA58C580-- From ipfix-bounces@ietf.org Thu May 8 08:23:00 2008 Return-Path: X-Original-To: ipfix-archive@optimus.ietf.org Delivered-To: ietfarch-ipfix-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C13153A72F6; Thu, 8 May 2008 08:22:13 -0700 (PDT) X-Original-To: ipfix@core3.amsl.com Delivered-To: ipfix@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3B0983A72C7 for ; Thu, 8 May 2008 08:21:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] 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 fMpi4-wn8Zck for ; Thu, 8 May 2008 08:21:26 -0700 (PDT) Received: from gatekeeper.hitachi-eu.com (gatekeeper.hitachi-eu.com [194.36.128.25]) by core3.amsl.com (Postfix) with ESMTP id 335E528C2C9 for ; Thu, 8 May 2008 06:19:34 -0700 (PDT) X-ASG-Debug-ID: 1210249141-5a0201110000-urGyNO X-Barracuda-URL: http://mhd-bar.hitachi-eu.com:8000/cgi-bin/mark.cgi Received: from mhd-mta-int.hitachi-eu.com (localhost [127.0.0.1]) by gatekeeper.hitachi-eu.com (Spam Firewall) with ESMTP id 87A1D2B6C9A for ; Thu, 8 May 2008 13:19:01 +0100 (BST) Received: from mhd-mta-int.hitachi-eu.com ([193.39.225.234]) by gatekeeper.hitachi-eu.com with ESMTP id ugaJIvbz8LRUWaFc for ; Thu, 08 May 2008 13:19:01 +0100 (BST) X-ASG-Whitelist: Client Received: from MHDEXC99.adhel.hitachi-eu.com (Not Verified[193.39.227.52]) by mhd-mta-int.hitachi-eu.com with MailMarshal (v6, 2, 1, 3252) id ; Thu, 08 May 2008 12:19:01 +0000 Received: from mhdexcb.adhel.hitachi-eu.com ([193.39.227.47]) by MHDEXC99.adhel.hitachi-eu.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 8 May 2008 13:19:01 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 X-ASG-Orig-Subj: Comments on "IPFIX Export per SCTP Stream" Date: Thu, 8 May 2008 13:19:01 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Comments on "IPFIX Export per SCTP Stream" Thread-Index: AcixBbKgi2t9qqGCS1SA5QfP+eTbZA== From: "Boschi, Elisa" To: X-OriginalArrivalTime: 08 May 2008 12:19:01.0113 (UTC) FILETIME=[B2B3A690:01C8B105] X-Barracuda-Connect: UNKNOWN[193.39.225.234] X-Barracuda-Start-Time: 1210249141 X-Barracuda-Virus-Scanned: by HEU SPAM Firewall - MHD at hitachi-eu.com Subject: [IPFIX] Comments on "IPFIX Export per SCTP Stream" X-BeenThere: ipfix@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IPFIX WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0904097403==" Sender: ipfix-bounces@ietf.org Errors-To: ipfix-bounces@ietf.org This is a multi-part message in MIME format. --===============0904097403== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C8B105.B2A81F68" This is a multi-part message in MIME format. ------_=_NextPart_001_01C8B105.B2A81F68 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Benoit, all, I've reviewed the per-stream draft. Overall I like the draft and consider= =20it ready for adoption as WG item. Comments below: General Comment: As already said during the IPFIX meeting in Philadelphia, I'd like to see= =20a section on the limitations of this method and a few more words on it= s applicability.=20 While the advantages are clearly listed, it is not clear=20 - to which set of applications this specification is targeted (this might= =20be added in 2.1 Applicability),=20 - which limitations the method has. =20 2. The introduction summarises the IPFIX protocol and then jumps to listi= ng the advantages offered by this draft's specification. It would be nice= =20and would help readability to have another paragraph between the two d= escribing what the method in this draft is about. 3.1.1, 3rd paragraph: Typos "...no way of knowing the which Template ID..." "...now matter..." 3.1.2: from Sequence Number Field --> from the Sequence Number Field 4.1, 4th paragraph: The second sentence "If not sent reliably...", is not very clear. Rewordi= ng might help 4.4, 4th paragraph, last sentence: "If the SCTP stream only contains Data Records from a single Template ID= , the Data Records for that Template ID can be calculated." --> Do you mean "the loss for the Data Records...can be calculated"? 5., 4th paragraph: all IPFIX Message --> all IPFIX Messages 5., 5th paragraph: Figure 3 show --> Figure 3 shows an Template --> a Template Hope it helps. Sorry for the delay in posting these comments, cheers, Elisa *************************************************************************= *************************=20 E-mail Confidentiality Notice and Disclaimer.=20 This e-mail and any files transmitted with it are confidential and are in= tended solely for the use=20 of the individual or entity to which they are addressed. Access to this e= -mail by anyone else is=20 unauthorised. If you are not the intended recipient, any disclosure, copy= ing, distribution or any action taken or omitted to be taken in reliance on it, is prohibited. E-m= ail messages are not=20 necessarily secure. Hitachi does not accept responsibility for any change= s made to this message=20 after it was sent.=20 Hitachi checks outgoing e-mail messages for the presence of computer viru= ses.=20 *************************************************************************= ************************* ------_=_NextPart_001_01C8B105.B2A81F68 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Comments on "IPFIX Export per SCTP Stream"

Benoit, all,

I've reviewed the per-stream draft. Overall I like the draft and consider= =20it ready for adoption as WG item. Comments below:

General Comment:
As already said during the IPFIX meeting in Philadelphia, I'd like to see= =20a section on the limitations of this method and a few more words on it= s applicability.
While the advantages are clearly listed, it is not clear
- to which set of applications this specification is targeted (this might= =20be added in 2.1 Applicability),
- which limitations the method has.


2. The introduction summarises the IPFIX protocol and then jumps to listi= ng the advantages offered by this draft's specification. It would be nice= =20and would help readability to have another paragraph between the two d= escribing what the method in this draft is about.

3.1.1, 3rd paragraph:
Typos "...no way of knowing the which Template ID..."
"...now matter..."

3.1.2:
from Sequence Number Field --> from the Sequence Number Field

4.1, 4th paragraph:
The second sentence "If not sent reliably...", is not very clea= r. Rewording might help

4.4, 4th paragraph, last sentence:
"If the SCTP stream only  contains Data Records from a single T= emplate ID, the Data Records for that Template ID can be calculated."= ;
--> Do you mean "the loss for the Data Records...can be calculate= d"?

5., 4th paragraph:
all IPFIX Message --> all IPFIX Messages

5., 5th paragraph:
Figure 3 show --> Figure 3 shows
an Template --> a Template

Hope it helps.

Sorry for the delay in posting these comments,

cheers,
Elisa

************= *************************************************************************= *************
E-mail=20 Confidentiality Notice and Disclaimer.

This e-mail and any files transmitted with it are confiden= tial and=20 are intended solely for the use of the individual or entity to which they= =20are=20 addressed. Access to this e-mail by anyone else is unauthorised. If you a= re not=20 the intended recipient, any disclosure, copying, distribution or any acti= on=20 taken or omitted to be taken in reliance on it, is prohibited.
E-mail= =20 messages are not necessarily secure.
Hitachi does not accept responsi= bility=20 for any changes made to this message after it was sent.
Hitachi checks= =20 outgoing e-mail messages for the presence of computer viruses.=20
*********************************************************************= *****************************=20

------_=_NextPart_001_01C8B105.B2A81F68-- --===============0904097403== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ IPFIX mailing list IPFIX@ietf.org https://www.ietf.org/mailman/listinfo/ipfix --===============0904097403==-- From ipfix-bounces@ietf.org Thu May 8 08:23:00 2008 Return-Path: X-Original-To: ipfix-archive@lists.ietf.org Delivered-To: ietfarch-ipfix-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C13153A72F6; Thu, 8 May 2008 08:22:13 -0700 (PDT) X-Original-To: ipfix@core3.amsl.com Delivered-To: ipfix@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3B0983A72C7 for ; Thu, 8 May 2008 08:21:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] 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 fMpi4-wn8Zck for ; Thu, 8 May 2008 08:21:26 -0700 (PDT) Received: from gatekeeper.hitachi-eu.com (gatekeeper.hitachi-eu.com [194.36.128.25]) by core3.amsl.com (Postfix) with ESMTP id 335E528C2C9 for ; Thu, 8 May 2008 06:19:34 -0700 (PDT) X-ASG-Debug-ID: 1210249141-5a0201110000-urGyNO X-Barracuda-URL: http://mhd-bar.hitachi-eu.com:8000/cgi-bin/mark.cgi Received: from mhd-mta-int.hitachi-eu.com (localhost [127.0.0.1]) by gatekeeper.hitachi-eu.com (Spam Firewall) with ESMTP id 87A1D2B6C9A for ; Thu, 8 May 2008 13:19:01 +0100 (BST) Received: from mhd-mta-int.hitachi-eu.com ([193.39.225.234]) by gatekeeper.hitachi-eu.com with ESMTP id ugaJIvbz8LRUWaFc for ; Thu, 08 May 2008 13:19:01 +0100 (BST) X-ASG-Whitelist: Client Received: from MHDEXC99.adhel.hitachi-eu.com (Not Verified[193.39.227.52]) by mhd-mta-int.hitachi-eu.com with MailMarshal (v6, 2, 1, 3252) id ; Thu, 08 May 2008 12:19:01 +0000 Received: from mhdexcb.adhel.hitachi-eu.com ([193.39.227.47]) by MHDEXC99.adhel.hitachi-eu.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 8 May 2008 13:19:01 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 X-ASG-Orig-Subj: Comments on "IPFIX Export per SCTP Stream" Date: Thu, 8 May 2008 13:19:01 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Comments on "IPFIX Export per SCTP Stream" Thread-Index: AcixBbKgi2t9qqGCS1SA5QfP+eTbZA== From: "Boschi, Elisa" To: X-OriginalArrivalTime: 08 May 2008 12:19:01.0113 (UTC) FILETIME=[B2B3A690:01C8B105] X-Barracuda-Connect: UNKNOWN[193.39.225.234] X-Barracuda-Start-Time: 1210249141 X-Barracuda-Virus-Scanned: by HEU SPAM Firewall - MHD at hitachi-eu.com Subject: [IPFIX] Comments on "IPFIX Export per SCTP Stream" X-BeenThere: ipfix@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IPFIX WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0904097403==" Sender: ipfix-bounces@ietf.org Errors-To: ipfix-bounces@ietf.org This is a multi-part message in MIME format. --===============0904097403== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C8B105.B2A81F68" This is a multi-part message in MIME format. ------_=_NextPart_001_01C8B105.B2A81F68 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Benoit, all, I've reviewed the per-stream draft. Overall I like the draft and consider= =20it ready for adoption as WG item. Comments below: General Comment: As already said during the IPFIX meeting in Philadelphia, I'd like to see= =20a section on the limitations of this method and a few more words on it= s applicability.=20 While the advantages are clearly listed, it is not clear=20 - to which set of applications this specification is targeted (this might= =20be added in 2.1 Applicability),=20 - which limitations the method has. =20 2. The introduction summarises the IPFIX protocol and then jumps to listi= ng the advantages offered by this draft's specification. It would be nice= =20and would help readability to have another paragraph between the two d= escribing what the method in this draft is about. 3.1.1, 3rd paragraph: Typos "...no way of knowing the which Template ID..." "...now matter..." 3.1.2: from Sequence Number Field --> from the Sequence Number Field 4.1, 4th paragraph: The second sentence "If not sent reliably...", is not very clear. Rewordi= ng might help 4.4, 4th paragraph, last sentence: "If the SCTP stream only contains Data Records from a single Template ID= , the Data Records for that Template ID can be calculated." --> Do you mean "the loss for the Data Records...can be calculated"? 5., 4th paragraph: all IPFIX Message --> all IPFIX Messages 5., 5th paragraph: Figure 3 show --> Figure 3 shows an Template --> a Template Hope it helps. Sorry for the delay in posting these comments, cheers, Elisa *************************************************************************= *************************=20 E-mail Confidentiality Notice and Disclaimer.=20 This e-mail and any files transmitted with it are confidential and are in= tended solely for the use=20 of the individual or entity to which they are addressed. Access to this e= -mail by anyone else is=20 unauthorised. If you are not the intended recipient, any disclosure, copy= ing, distribution or any action taken or omitted to be taken in reliance on it, is prohibited. E-m= ail messages are not=20 necessarily secure. Hitachi does not accept responsibility for any change= s made to this message=20 after it was sent.=20 Hitachi checks outgoing e-mail messages for the presence of computer viru= ses.=20 *************************************************************************= ************************* ------_=_NextPart_001_01C8B105.B2A81F68 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Comments on "IPFIX Export per SCTP Stream"

Benoit, all,

I've reviewed the per-stream draft. Overall I like the draft and consider= =20it ready for adoption as WG item. Comments below:

General Comment:
As already said during the IPFIX meeting in Philadelphia, I'd like to see= =20a section on the limitations of this method and a few more words on it= s applicability.
While the advantages are clearly listed, it is not clear
- to which set of applications this specification is targeted (this might= =20be added in 2.1 Applicability),
- which limitations the method has.


2. The introduction summarises the IPFIX protocol and then jumps to listi= ng the advantages offered by this draft's specification. It would be nice= =20and would help readability to have another paragraph between the two d= escribing what the method in this draft is about.

3.1.1, 3rd paragraph:
Typos "...no way of knowing the which Template ID..."
"...now matter..."

3.1.2:
from Sequence Number Field --> from the Sequence Number Field

4.1, 4th paragraph:
The second sentence "If not sent reliably...", is not very clea= r. Rewording might help

4.4, 4th paragraph, last sentence:
"If the SCTP stream only  contains Data Records from a single T= emplate ID, the Data Records for that Template ID can be calculated."= ;
--> Do you mean "the loss for the Data Records...can be calculate= d"?

5., 4th paragraph:
all IPFIX Message --> all IPFIX Messages

5., 5th paragraph:
Figure 3 show --> Figure 3 shows
an Template --> a Template

Hope it helps.

Sorry for the delay in posting these comments,

cheers,
Elisa

************= *************************************************************************= *************
E-mail=20 Confidentiality Notice and Disclaimer.

This e-mail and any files transmitted with it are confiden= tial and=20 are intended solely for the use of the individual or entity to which they= =20are=20 addressed. Access to this e-mail by anyone else is unauthorised. If you a= re not=20 the intended recipient, any disclosure, copying, distribution or any acti= on=20 taken or omitted to be taken in reliance on it, is prohibited.
E-mail= =20 messages are not necessarily secure.
Hitachi does not accept responsi= bility=20 for any changes made to this message after it was sent.
Hitachi checks= =20 outgoing e-mail messages for the presence of computer viruses.=20
*********************************************************************= *****************************=20

------_=_NextPart_001_01C8B105.B2A81F68-- --===============0904097403== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ IPFIX mailing list IPFIX@ietf.org https://www.ietf.org/mailman/listinfo/ipfix --===============0904097403==-- From fishheadclan@yahoo.com Mon May 12 03:54:32 2008 Return-Path: X-Original-To: ietfarch-ipfix-archive@core3.amsl.com Delivered-To: ietfarch-ipfix-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 36D3D3A67F9; Mon, 12 May 2008 03:54:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -58.786 X-Spam-Level: X-Spam-Status: No, score=-58.786 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FH_HOST_EQ_D_D_D_D=0.765, HELO_EQ_IP_ADDR=1.119, HOST_EQ_CPE=0.979, HOST_MISMATCH_COM=0.311, HTML_MESSAGE=0.001, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, URIBL_BLACK=20, URIBL_JP_SURBL=10, 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 BYoXWThinoWs; Mon, 12 May 2008 03:54:31 -0700 (PDT) Received: from [75.176.172.202] (cpe-075-176-172-202.sc.res.rr.com [75.176.172.202]) by core3.amsl.com (Postfix) with ESMTP id BCD653A67A6; Mon, 12 May 2008 03:54:24 -0700 (PDT) Received: from [75.176.172.202] by a.mx.mail.yahoo.com; Mon, 12 May 2008 05:54:27 -0500 Message-ID: <01c8b3f4$a31c6b80$caacb04b@fishheadclan> From: "Google AdWords-noreply" To: Subject: Your Account with Google AdWords. Date: Mon, 12 May 2008 05:54:27 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01C8B3F4.A31C6B80" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4927.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200 This is a multi-part message in MIME format. ------=_NextPart_000_0007_01C8B3F4.A31C6B80 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable -------------------------------------------------------------------------= ---- Dear Google AdWords Customer, We were unable to process your payment. Your ads will be suspended soon unless we can process your payment. To prevent your ads from being suspended, please update your payment info= rmation. Please sign in to your account at http://adwords.google.com/select/login, and update your payment information. -------------------------------------------------------------------------= ---------------- This message was sent from a notification-only email address that does not accept incoming email. Please do not reply to this message. -------------------------------------------------------------------------= ----------------- We look forward to providing you with the most effective advertising avai= lable. Thank you for choosing AdWords. ------=_NextPart_000_0007_01C8B3F4.A31C6B80 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable -------------------------------------------------------------------------= ----------------
Dear Google AdWords Customer,

We were unable to process your payment.
Your ads will be suspended soon unless we can process your payment.
To prevent your ads from being suspended, please update your payment info= rmation.

Please sign in
to your account at http://adwords.google.com/select/login,
and update your payment information.

-------------------------------------------------------------------------= ---
This message was sent from a notification-only email address that does not accept incoming email. Please do not reply to this message.
-------------------------------------------------------------------------= -------
------=_NextPart_000_0007_01C8B3F4.A31C6B80-- From ipfix-bounces@ietf.org Mon May 12 20:30:05 2008 Return-Path: X-Original-To: ipfix-archive@lists.ietf.org Delivered-To: ietfarch-ipfix-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3CCFF3A6BBF; Mon, 12 May 2008 20:30:05 -0700 (PDT) X-Original-To: ipfix@ietf.org Delivered-To: ipfix@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 161593A6BB7; Mon, 12 May 2008 20:30:02 -0700 (PDT) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20080513033002.161593A6BB7@core3.amsl.com> Date: Mon, 12 May 2008 20:30:02 -0700 (PDT) Cc: ipfix@ietf.org Subject: [IPFIX] I-D Action:draft-ietf-ipfix-mediators-problem-statement-00.txt X-BeenThere: ipfix@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IPFIX WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ipfix-bounces@ietf.org Errors-To: ipfix-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP Flow Information Export Working Group of the IETF. Title : IPFIX Mediation: Problem Statement Author(s) : A. Kobayashi, et al. Filename : draft-ietf-ipfix-mediators-problem-statement-00.txt Pages : 22 Date : 2008-05-12 Flow-based measurement is currently a popular method for traffic monitoring. To construct a measurement system, an IPFIX mediation device (IPFIX Mediator), which reroutes, filters, aggregates, or modifies Flow information, may help scalability and several other purposes. This document describes the applicability of an IPFIX Mediator and the problems that the IPFIX Mediator might encounter. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipfix-mediators-problem-statement-00.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-ipfix-mediators-problem-statement-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2008-05-12202758.I-D@ietf.org> --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ IPFIX mailing list IPFIX@ietf.org https://www.ietf.org/mailman/listinfo/ipfix --NextPart-- From ipfix-bounces@ietf.org Mon May 12 20:30:05 2008 Return-Path: X-Original-To: ipfix-archive@optimus.ietf.org Delivered-To: ietfarch-ipfix-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3CCFF3A6BBF; Mon, 12 May 2008 20:30:05 -0700 (PDT) X-Original-To: ipfix@ietf.org Delivered-To: ipfix@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 161593A6BB7; Mon, 12 May 2008 20:30:02 -0700 (PDT) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20080513033002.161593A6BB7@core3.amsl.com> Date: Mon, 12 May 2008 20:30:02 -0700 (PDT) Cc: ipfix@ietf.org Subject: [IPFIX] I-D Action:draft-ietf-ipfix-mediators-problem-statement-00.txt X-BeenThere: ipfix@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IPFIX WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ipfix-bounces@ietf.org Errors-To: ipfix-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP Flow Information Export Working Group of the IETF. Title : IPFIX Mediation: Problem Statement Author(s) : A. Kobayashi, et al. Filename : draft-ietf-ipfix-mediators-problem-statement-00.txt Pages : 22 Date : 2008-05-12 Flow-based measurement is currently a popular method for traffic monitoring. To construct a measurement system, an IPFIX mediation device (IPFIX Mediator), which reroutes, filters, aggregates, or modifies Flow information, may help scalability and several other purposes. This document describes the applicability of an IPFIX Mediator and the problems that the IPFIX Mediator might encounter. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipfix-mediators-problem-statement-00.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-ipfix-mediators-problem-statement-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2008-05-12202758.I-D@ietf.org> --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ IPFIX mailing list IPFIX@ietf.org https://www.ietf.org/mailman/listinfo/ipfix --NextPart-- From ipfix-bounces@ietf.org Wed May 14 18:31:40 2008 Return-Path: X-Original-To: ipfix-archive@lists.ietf.org Delivered-To: ietfarch-ipfix-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0A8703A6855; Wed, 14 May 2008 18:31:40 -0700 (PDT) X-Original-To: ipfix@core3.amsl.com Delivered-To: ipfix@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A7CC13A684D for ; Wed, 14 May 2008 18:31:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.188 X-Spam-Level: X-Spam-Status: No, score=-2.188 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HOST_MISMATCH_COM=0.311, RDNS_DYNAMIC=0.1] 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 K9XNojn6YbeV for ; Wed, 14 May 2008 18:31:37 -0700 (PDT) Received: from mail.nttv6.net (mail.nttv6.net [IPv6:2001:fa8::25]) by core3.amsl.com (Postfix) with ESMTP id 4FCDA3A6855 for ; Wed, 14 May 2008 18:31:37 -0700 (PDT) Received: from [127.0.0.1] (dhcp-3-188.nttv6.com [192.47.163.188]) by mail.nttv6.net (8.14.3/8.14.1) with ESMTP id m4F1VbhK052734 for ; Thu, 15 May 2008 10:31:38 +0900 (JST) (envelope-from akoba@nttv6.net) Date: Thu, 15 May 2008 10:34:52 +0900 From: ATSUSHI KOBAYASHI 8 To: ipfix@ietf.org In-Reply-To: <20080513033002.161593A6BB7@core3.amsl.com> References: <20080513033002.161593A6BB7@core3.amsl.com> Message-Id: <20080515101056.471F.17391CF2@nttv6.net> MIME-Version: 1.0 X-Mailer: Becky! ver. 2.45.02 [ja] X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (mail.nttv6.net [192.16.178.5]); Thu, 15 May 2008 10:31:38 +0900 (JST) Subject: Re: [IPFIX] I-D Action:draft-ietf-ipfix-mediators-problem-statement-00.txt X-BeenThere: ipfix@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IPFIX WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ipfix-bounces@ietf.org Errors-To: ipfix-bounces@ietf.org Dear all, Thanks to co-authors and editing meeting members in IETF-71, I have written up the first version IPFIX Mediation problem statement draft. Thank you for your contribution. This draft is related to all of IPFIX Mediation, such as aggregation, anonymization, collector selection and flow selection, including problems in large-scale network. Your comments are welcome at any time. Next, I will try to edit a framework draft followed by this draft. Atsushi KOBAYASHI On Mon, 12 May 2008 20:30:02 -0700 (PDT) Internet-Drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the IP Flow Information Export Working Group of the IETF. > > > Title : IPFIX Mediation: Problem Statement > Author(s) : A. Kobayashi, et al. > Filename : draft-ietf-ipfix-mediators-problem-statement-00.txt > Pages : 22 > Date : 2008-05-12 > > Flow-based measurement is currently a popular method for traffic > monitoring. To construct a measurement system, an IPFIX mediation > device (IPFIX Mediator), which reroutes, filters, aggregates, or > modifies Flow information, may help scalability and several other > purposes. This document describes the applicability of an IPFIX > Mediator and the problems that the IPFIX Mediator might encounter. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-ipfix-mediators-problem-statement-00.txt > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. --- Atsushi KOBAYASHI NTT Information Sharing Platform Lab. tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637 _______________________________________________ IPFIX mailing list IPFIX@ietf.org https://www.ietf.org/mailman/listinfo/ipfix From ipfix-bounces@ietf.org Wed May 14 18:31:40 2008 Return-Path: X-Original-To: ipfix-archive@optimus.ietf.org Delivered-To: ietfarch-ipfix-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0A8703A6855; Wed, 14 May 2008 18:31:40 -0700 (PDT) X-Original-To: ipfix@core3.amsl.com Delivered-To: ipfix@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A7CC13A684D for ; Wed, 14 May 2008 18:31:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.188 X-Spam-Level: X-Spam-Status: No, score=-2.188 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HOST_MISMATCH_COM=0.311, RDNS_DYNAMIC=0.1] 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 K9XNojn6YbeV for ; Wed, 14 May 2008 18:31:37 -0700 (PDT) Received: from mail.nttv6.net (mail.nttv6.net [IPv6:2001:fa8::25]) by core3.amsl.com (Postfix) with ESMTP id 4FCDA3A6855 for ; Wed, 14 May 2008 18:31:37 -0700 (PDT) Received: from [127.0.0.1] (dhcp-3-188.nttv6.com [192.47.163.188]) by mail.nttv6.net (8.14.3/8.14.1) with ESMTP id m4F1VbhK052734 for ; Thu, 15 May 2008 10:31:38 +0900 (JST) (envelope-from akoba@nttv6.net) Date: Thu, 15 May 2008 10:34:52 +0900 From: ATSUSHI KOBAYASHI 8 To: ipfix@ietf.org In-Reply-To: <20080513033002.161593A6BB7@core3.amsl.com> References: <20080513033002.161593A6BB7@core3.amsl.com> Message-Id: <20080515101056.471F.17391CF2@nttv6.net> MIME-Version: 1.0 X-Mailer: Becky! ver. 2.45.02 [ja] X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (mail.nttv6.net [192.16.178.5]); Thu, 15 May 2008 10:31:38 +0900 (JST) Subject: Re: [IPFIX] I-D Action:draft-ietf-ipfix-mediators-problem-statement-00.txt X-BeenThere: ipfix@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IPFIX WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ipfix-bounces@ietf.org Errors-To: ipfix-bounces@ietf.org Dear all, Thanks to co-authors and editing meeting members in IETF-71, I have written up the first version IPFIX Mediation problem statement draft. Thank you for your contribution. This draft is related to all of IPFIX Mediation, such as aggregation, anonymization, collector selection and flow selection, including problems in large-scale network. Your comments are welcome at any time. Next, I will try to edit a framework draft followed by this draft. Atsushi KOBAYASHI On Mon, 12 May 2008 20:30:02 -0700 (PDT) Internet-Drafts@ietf.org wrote: > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the IP Flow Information Export Working Group of the IETF. > > > Title : IPFIX Mediation: Problem Statement > Author(s) : A. Kobayashi, et al. > Filename : draft-ietf-ipfix-mediators-problem-statement-00.txt > Pages : 22 > Date : 2008-05-12 > > Flow-based measurement is currently a popular method for traffic > monitoring. To construct a measurement system, an IPFIX mediation > device (IPFIX Mediator), which reroutes, filters, aggregates, or > modifies Flow information, may help scalability and several other > purposes. This document describes the applicability of an IPFIX > Mediator and the problems that the IPFIX Mediator might encounter. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-ipfix-mediators-problem-statement-00.txt > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. --- Atsushi KOBAYASHI NTT Information Sharing Platform Lab. tel:+81-(0)422-59-3978 fax:+81-(0)422-59-5637 _______________________________________________ IPFIX mailing list IPFIX@ietf.org https://www.ietf.org/mailman/listinfo/ipfix From ipfix-bounces@ietf.org Tue May 20 06:24:34 2008 Return-Path: X-Original-To: ipfix-archive@lists.ietf.org Delivered-To: ietfarch-ipfix-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 66A0A28C296; Tue, 20 May 2008 06:24:34 -0700 (PDT) X-Original-To: ipfix@ietf.org Delivered-To: ipfix@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 30) id F2ABE28C286; Tue, 20 May 2008 06:24:31 -0700 (PDT) X-idtracker: yes From: The IESG To: IETF-Announce Message-Id: <20080520132431.F2ABE28C286@core3.amsl.com> Date: Tue, 20 May 2008 06:24:31 -0700 (PDT) Cc: Internet Architecture Board , ipfix chair , ipfix mailing list , RFC Editor Subject: [IPFIX] Document Action: 'Guidelines for IP Flow Information eXport (IPFIX) Testing' to Informational RFC X-BeenThere: ipfix@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IPFIX WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ipfix-bounces@ietf.org Errors-To: ipfix-bounces@ietf.org The IESG has approved the following document: - 'Guidelines for IP Flow Information eXport (IPFIX) Testing ' as an Informational RFC This document is the product of the IP Flow Information Export Working Group. The IESG contact persons are Dan Romascanu and Ron Bonica. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipfix-testing-05.txt Technical Summary This document presents a list of tests for implementers of IP Flow Information Export (IPFIX) compliant Exporting Processes and Collecting Processes. This document specifies guidelines for a series of tests that can be run on the IPFIX Exporting Process and Collecting Process in order to probe the conformity and robustness of the IPFIX protocol implementations. These tests cover all important functions, in order to gain a level of confidence in the IPFIX implementation. Therefore they allow the implementer to perform interoperability or plug tests with other IPFIX Exporting Processes and Collecting Processes. Working Group Summary The IPFIX Working Group is in consensus in favor of publcihing this document. Like the 'IPFIX Implementation Guidelines' document, this document draws on experience gained from IPFIX interopability events. It will be useful to implementors who need to enusre that their IPFIX implementations really do work correctly. Document Quality The document is based on experience gained at interoperability events. It was extensively reviewed within the IPFIX Working Group, and in the PSAMP WG. Dan Romascanu reviewed the document as AD. Joel Halpern reviewed for GenART and his extensive comments were used to generate the final version of the document. Personnel Nevil Brownlee is the PROTO shepherd. Dan Romascanu is the shepherding AD. RFC Editor Note RFC Editor, please make the following changes: 1) add to section 1 (before 1.1) the following text: NEW: The tests can be executed in a testbed environment or on a live network. However, care should be taken regarding the "stress/load test" and the "temporary network disconnect", as they might impact other systems in the network. We recommend that these specific tests should be executed only in a testbed environment. 2) In section 3.1.1 OLD: The transmitted data might be observed on-line with an appropriate packet sniffing tool, such as Wireshark (www.wireshark.org). NEW: The transmitted data might be observed on-line with an appropriate packet sniffing tool. 3) in section 3.4.1: OLD: The tester must check and if necessary improve the software so that the Templates and the associated Data Records are correctly received and decoded by the Collecting Process. NEW: The tester must check that the Templates and the associated Data Records are correctly received and decoded by the Collecting Process. 4) In Section 3.7.1: OLD The tester must configure consistent forward (A, AAAA) and reverse (PTR) DNS records for each host in the test on a DNS server used by the hosts for name resolution. NEW The tester must configure consistent forward (A, AAAA) DNS records for each host in the test on a DNS server used by the hosts for name resolution. Note that there is no need to configure reverse (PTR) DNS records for the hosts, as no part of the protocol uses reverse lookups. _______________________________________________ IPFIX mailing list IPFIX@ietf.org https://www.ietf.org/mailman/listinfo/ipfix From ipfix-bounces@ietf.org Tue May 20 06:24:34 2008 Return-Path: X-Original-To: ipfix-archive@optimus.ietf.org Delivered-To: ietfarch-ipfix-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 66A0A28C296; Tue, 20 May 2008 06:24:34 -0700 (PDT) X-Original-To: ipfix@ietf.org Delivered-To: ipfix@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 30) id F2ABE28C286; Tue, 20 May 2008 06:24:31 -0700 (PDT) X-idtracker: yes From: The IESG To: IETF-Announce Message-Id: <20080520132431.F2ABE28C286@core3.amsl.com> Date: Tue, 20 May 2008 06:24:31 -0700 (PDT) Cc: Internet Architecture Board , ipfix chair , ipfix mailing list , RFC Editor Subject: [IPFIX] Document Action: 'Guidelines for IP Flow Information eXport (IPFIX) Testing' to Informational RFC X-BeenThere: ipfix@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IPFIX WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ipfix-bounces@ietf.org Errors-To: ipfix-bounces@ietf.org The IESG has approved the following document: - 'Guidelines for IP Flow Information eXport (IPFIX) Testing ' as an Informational RFC This document is the product of the IP Flow Information Export Working Group. The IESG contact persons are Dan Romascanu and Ron Bonica. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipfix-testing-05.txt Technical Summary This document presents a list of tests for implementers of IP Flow Information Export (IPFIX) compliant Exporting Processes and Collecting Processes. This document specifies guidelines for a series of tests that can be run on the IPFIX Exporting Process and Collecting Process in order to probe the conformity and robustness of the IPFIX protocol implementations. These tests cover all important functions, in order to gain a level of confidence in the IPFIX implementation. Therefore they allow the implementer to perform interoperability or plug tests with other IPFIX Exporting Processes and Collecting Processes. Working Group Summary The IPFIX Working Group is in consensus in favor of publcihing this document. Like the 'IPFIX Implementation Guidelines' document, this document draws on experience gained from IPFIX interopability events. It will be useful to implementors who need to enusre that their IPFIX implementations really do work correctly. Document Quality The document is based on experience gained at interoperability events. It was extensively reviewed within the IPFIX Working Group, and in the PSAMP WG. Dan Romascanu reviewed the document as AD. Joel Halpern reviewed for GenART and his extensive comments were used to generate the final version of the document. Personnel Nevil Brownlee is the PROTO shepherd. Dan Romascanu is the shepherding AD. RFC Editor Note RFC Editor, please make the following changes: 1) add to section 1 (before 1.1) the following text: NEW: The tests can be executed in a testbed environment or on a live network. However, care should be taken regarding the "stress/load test" and the "temporary network disconnect", as they might impact other systems in the network. We recommend that these specific tests should be executed only in a testbed environment. 2) In section 3.1.1 OLD: The transmitted data might be observed on-line with an appropriate packet sniffing tool, such as Wireshark (www.wireshark.org). NEW: The transmitted data might be observed on-line with an appropriate packet sniffing tool. 3) in section 3.4.1: OLD: The tester must check and if necessary improve the software so that the Templates and the associated Data Records are correctly received and decoded by the Collecting Process. NEW: The tester must check that the Templates and the associated Data Records are correctly received and decoded by the Collecting Process. 4) In Section 3.7.1: OLD The tester must configure consistent forward (A, AAAA) and reverse (PTR) DNS records for each host in the test on a DNS server used by the hosts for name resolution. NEW The tester must configure consistent forward (A, AAAA) DNS records for each host in the test on a DNS server used by the hosts for name resolution. Note that there is no need to configure reverse (PTR) DNS records for the hosts, as no part of the protocol uses reverse lookups. _______________________________________________ IPFIX mailing list IPFIX@ietf.org https://www.ietf.org/mailman/listinfo/ipfix From ipfix-bounces@ietf.org Tue May 20 21:04:53 2008 Return-Path: X-Original-To: ipfix-archive@optimus.ietf.org Delivered-To: ietfarch-ipfix-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EBD3328C96D; Tue, 20 May 2008 21:04:52 -0700 (PDT) X-Original-To: ipfix@core3.amsl.com Delivered-To: ipfix@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 927323A6F4E for ; Tue, 20 May 2008 21:04:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.844 X-Spam-Level: X-Spam-Status: No, score=-1.844 tagged_above=-999 required=5 tests=[AWL=0.756, BAYES_00=-2.599] 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 LBhfaA2OwTgG for ; Tue, 20 May 2008 21:04:49 -0700 (PDT) Received: from nj300815-nj-outbound.avaya.com (nj300815-nj-outbound.net.avaya.com [198.152.12.100]) by core3.amsl.com (Postfix) with ESMTP id 0BA4228D62B for ; Tue, 20 May 2008 09:52:40 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.27,516,1204520400"; d="scan'208";a="119902079" Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by nj300815-nj-outbound.avaya.com with ESMTP; 20 May 2008 12:52:41 -0400 X-IronPort-AV: E=Sophos;i="4.27,516,1204520400"; d="scan'208";a="198139404" Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 20 May 2008 12:52:40 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 20 May 2008 18:52:38 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Document Action: 'Guidelines for IP Flow Information eXport (IPFIX) Testing' to Informational RFC Thread-Index: Aci6fQAN0f2pkACxT0qO8Wd1ZfPi0AAHM0XQ From: "Romascanu, Dan (Dan)" To: Subject: [IPFIX] FW: Document Action: 'Guidelines for IP Flow Information eXport (IPFIX) Testing' to Informational RFC X-BeenThere: ipfix@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IPFIX WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ipfix-bounces@ietf.org Errors-To: ipfix-bounces@ietf.org Congratulations and thanks to the Editors, Chairs and the whole Working Group. Dan -----Original Message----- From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-bounces@ietf.org] On Behalf Of The IESG Sent: Tuesday, May 20, 2008 4:25 PM To: IETF-Announce Cc: Internet Architecture Board; ipfix chair; ipfix mailing list; RFC Editor Subject: Document Action: 'Guidelines for IP Flow Information eXport (IPFIX) Testing' to Informational RFC The IESG has approved the following document: - 'Guidelines for IP Flow Information eXport (IPFIX) Testing ' as an Informational RFC This document is the product of the IP Flow Information Export Working Group. The IESG contact persons are Dan Romascanu and Ron Bonica. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipfix-testing-05.txt Technical Summary This document presents a list of tests for implementers of IP Flow Information Export (IPFIX) compliant Exporting Processes and Collecting Processes. This document specifies guidelines for a series of tests that can be run on the IPFIX Exporting Process and Collecting Process in order to probe the conformity and robustness of the IPFIX protocol implementations. These tests cover all important functions, in order to gain a level of confidence in the IPFIX implementation. Therefore they allow the implementer to perform interoperability or plug tests with other IPFIX Exporting Processes and Collecting Processes. Working Group Summary The IPFIX Working Group is in consensus in favor of publcihing this document. Like the 'IPFIX Implementation Guidelines' document, this document draws on experience gained from IPFIX interopability events. It will be useful to implementors who need to enusre that their IPFIX implementations really do work correctly. Document Quality The document is based on experience gained at interoperability events. It was extensively reviewed within the IPFIX Working Group, and in the PSAMP WG. Dan Romascanu reviewed the document as AD. Joel Halpern reviewed for GenART and his extensive comments were used to generate the final version of the document. Personnel Nevil Brownlee is the PROTO shepherd. Dan Romascanu is the shepherding AD. RFC Editor Note RFC Editor, please make the following changes: 1) add to section 1 (before 1.1) the following text: NEW: The tests can be executed in a testbed environment or on a live network. However, care should be taken regarding the "stress/load test" and the "temporary network disconnect", as they might impact other systems in the network. We recommend that these specific tests should be executed only in a testbed environment. 2) In section 3.1.1 OLD: The transmitted data might be observed on-line with an appropriate packet sniffing tool, such as Wireshark (www.wireshark.org). NEW: The transmitted data might be observed on-line with an appropriate packet sniffing tool. 3) in section 3.4.1: OLD: The tester must check and if necessary improve the software so that the Templates and the associated Data Records are correctly received and decoded by the Collecting Process. NEW: The tester must check that the Templates and the associated Data Records are correctly received and decoded by the Collecting Process. 4) In Section 3.7.1: OLD The tester must configure consistent forward (A, AAAA) and reverse (PTR) DNS records for each host in the test on a DNS server used by the hosts for name resolution. NEW The tester must configure consistent forward (A, AAAA) DNS records for each host in the test on a DNS server used by the hosts for name resolution. Note that there is no need to configure reverse (PTR) DNS records for the hosts, as no part of the protocol uses reverse lookups. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce _______________________________________________ IPFIX mailing list IPFIX@ietf.org https://www.ietf.org/mailman/listinfo/ipfix From ipfix-bounces@ietf.org Tue May 20 21:04:53 2008 Return-Path: X-Original-To: ipfix-archive@lists.ietf.org Delivered-To: ietfarch-ipfix-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EBD3328C96D; Tue, 20 May 2008 21:04:52 -0700 (PDT) X-Original-To: ipfix@core3.amsl.com Delivered-To: ipfix@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 927323A6F4E for ; Tue, 20 May 2008 21:04:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.844 X-Spam-Level: X-Spam-Status: No, score=-1.844 tagged_above=-999 required=5 tests=[AWL=0.756, BAYES_00=-2.599] 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 LBhfaA2OwTgG for ; Tue, 20 May 2008 21:04:49 -0700 (PDT) Received: from nj300815-nj-outbound.avaya.com (nj300815-nj-outbound.net.avaya.com [198.152.12.100]) by core3.amsl.com (Postfix) with ESMTP id 0BA4228D62B for ; Tue, 20 May 2008 09:52:40 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.27,516,1204520400"; d="scan'208";a="119902079" Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by nj300815-nj-outbound.avaya.com with ESMTP; 20 May 2008 12:52:41 -0400 X-IronPort-AV: E=Sophos;i="4.27,516,1204520400"; d="scan'208";a="198139404" Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 20 May 2008 12:52:40 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 20 May 2008 18:52:38 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Document Action: 'Guidelines for IP Flow Information eXport (IPFIX) Testing' to Informational RFC Thread-Index: Aci6fQAN0f2pkACxT0qO8Wd1ZfPi0AAHM0XQ From: "Romascanu, Dan (Dan)" To: Subject: [IPFIX] FW: Document Action: 'Guidelines for IP Flow Information eXport (IPFIX) Testing' to Informational RFC X-BeenThere: ipfix@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IPFIX WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ipfix-bounces@ietf.org Errors-To: ipfix-bounces@ietf.org Congratulations and thanks to the Editors, Chairs and the whole Working Group. Dan -----Original Message----- From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-bounces@ietf.org] On Behalf Of The IESG Sent: Tuesday, May 20, 2008 4:25 PM To: IETF-Announce Cc: Internet Architecture Board; ipfix chair; ipfix mailing list; RFC Editor Subject: Document Action: 'Guidelines for IP Flow Information eXport (IPFIX) Testing' to Informational RFC The IESG has approved the following document: - 'Guidelines for IP Flow Information eXport (IPFIX) Testing ' as an Informational RFC This document is the product of the IP Flow Information Export Working Group. The IESG contact persons are Dan Romascanu and Ron Bonica. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipfix-testing-05.txt Technical Summary This document presents a list of tests for implementers of IP Flow Information Export (IPFIX) compliant Exporting Processes and Collecting Processes. This document specifies guidelines for a series of tests that can be run on the IPFIX Exporting Process and Collecting Process in order to probe the conformity and robustness of the IPFIX protocol implementations. These tests cover all important functions, in order to gain a level of confidence in the IPFIX implementation. Therefore they allow the implementer to perform interoperability or plug tests with other IPFIX Exporting Processes and Collecting Processes. Working Group Summary The IPFIX Working Group is in consensus in favor of publcihing this document. Like the 'IPFIX Implementation Guidelines' document, this document draws on experience gained from IPFIX interopability events. It will be useful to implementors who need to enusre that their IPFIX implementations really do work correctly. Document Quality The document is based on experience gained at interoperability events. It was extensively reviewed within the IPFIX Working Group, and in the PSAMP WG. Dan Romascanu reviewed the document as AD. Joel Halpern reviewed for GenART and his extensive comments were used to generate the final version of the document. Personnel Nevil Brownlee is the PROTO shepherd. Dan Romascanu is the shepherding AD. RFC Editor Note RFC Editor, please make the following changes: 1) add to section 1 (before 1.1) the following text: NEW: The tests can be executed in a testbed environment or on a live network. However, care should be taken regarding the "stress/load test" and the "temporary network disconnect", as they might impact other systems in the network. We recommend that these specific tests should be executed only in a testbed environment. 2) In section 3.1.1 OLD: The transmitted data might be observed on-line with an appropriate packet sniffing tool, such as Wireshark (www.wireshark.org). NEW: The transmitted data might be observed on-line with an appropriate packet sniffing tool. 3) in section 3.4.1: OLD: The tester must check and if necessary improve the software so that the Templates and the associated Data Records are correctly received and decoded by the Collecting Process. NEW: The tester must check that the Templates and the associated Data Records are correctly received and decoded by the Collecting Process. 4) In Section 3.7.1: OLD The tester must configure consistent forward (A, AAAA) and reverse (PTR) DNS records for each host in the test on a DNS server used by the hosts for name resolution. NEW The tester must configure consistent forward (A, AAAA) DNS records for each host in the test on a DNS server used by the hosts for name resolution. Note that there is no need to configure reverse (PTR) DNS records for the hosts, as no part of the protocol uses reverse lookups. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce _______________________________________________ IPFIX mailing list IPFIX@ietf.org https://www.ietf.org/mailman/listinfo/ipfix From ipfix-bounces@ietf.org Wed May 21 04:56:54 2008 Return-Path: X-Original-To: ipfix-archive@optimus.ietf.org Delivered-To: ietfarch-ipfix-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A49043A67E5; Wed, 21 May 2008 04:56:54 -0700 (PDT) X-Original-To: ipfix@core3.amsl.com Delivered-To: ipfix@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 698F53A67DB for ; Wed, 21 May 2008 04:56:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] 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 CyY1A6epAS5I for ; Wed, 21 May 2008 04:56:52 -0700 (PDT) Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 402BD3A67E5 for ; Wed, 21 May 2008 04:56:52 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.27,520,1204498800"; d="scan'208";a="9508726" Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 21 May 2008 13:56:54 +0200 Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m4LBus6l019069; Wed, 21 May 2008 13:56:54 +0200 Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m4LBusmJ001808; Wed, 21 May 2008 11:56:54 GMT Received: from [144.254.153.34] (dhcp-144-254-153-34.cisco.com [144.254.153.34]) by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id m4LBurM21432; Wed, 21 May 2008 12:56:53 +0100 (BST) Message-ID: <48340E05.70900@cisco.com> Date: Wed, 21 May 2008 12:56:53 +0100 From: Paul Aitken User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9 MIME-Version: 1.0 To: "Romascanu, Dan" References: In-Reply-To: DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=222; t=1211371014; x=1212235014; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=paitken@cisco.com; z=From:=20Paul=20Aitken=20 |Subject:=20Re=3A=20[IPFIX]=20FW=3A=20Document=20Action=3A= 20'Guidelines=20for=20IP=20Flow=20Information=0A=20eXport=20 (IPFIX)=20Testing'=20to=20Informational=20RFC |Sender:=20; bh=3CiqrnEpnd5m6T0RCvmg4rY4QCsgAfQsJfWgr7P//Zk=; b=wJfn9oyavD+ewyFVcyQ2Fi0skFm2dUkJbUm+mj0bKzacEgkTZMuroUt6ob fFcR/V1kJl8aITH2BW6whE5voZKrZfASFaU6EvbFsAa7WNIJZq31Xpe8tKjp saoRiTXaxY; Authentication-Results: ams-dkim-2; header.From=paitken@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; ); Cc: ipfix@ietf.org Subject: Re: [IPFIX] FW: Document Action: 'Guidelines for IP Flow Information eXport (IPFIX) Testing' to Informational RFC X-BeenThere: ipfix@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IPFIX WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ipfix-bounces@ietf.org Errors-To: ipfix-bounces@ietf.org > Congratulations and thanks to the Editors, Chairs and the whole Working > Group. Thanks Dan for your help getting this draft through the final stages. -- Paul Aitken Cisco Systems Ltd, EdiFrom ipfix-bounces@ietf.org Wed May 21 04:56:54 2008 Return-Path: X-Original-To: ipfix-archive@lists.ietf.org Delivered-To: ietfarch-ipfix-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A49043A67E5; Wed, 21 May 2008 04:56:54 -0700 (PDT) X-Original-To: ipfix@core3.amsl.com Delivered-To: ipfix@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 698F53A67DB for ; Wed, 21 May 2008 04:56:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] 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 CyY1A6epAS5I for ; Wed, 21 May 2008 04:56:52 -0700 (PDT) Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 402BD3A67E5 for ; Wed, 21 May 2008 04:56:52 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.27,520,1204498800"; d="scan'208";a="9508726" Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 21 May 2008 13:56:54 +0200 Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m4LBus6l019069; Wed, 21 May 2008 13:56:54 +0200 Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m4LBusmJ001808; Wed, 21 May 2008 11:56:54 GMT Received: from [144.254.153.34] (dhcp-144-254-153-34.cisco.com [144.254.153.34]) by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id m4LBurM21432; Wed, 21 May 2008 12:56:53 +0100 (BST) Message-ID: <48340E05.70900@cisco.com> Date: Wed, 21 May 2008 12:56:53 +0100 From: Paul Aitken User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9 MIME-Version: 1.0 To: "Romascanu, Dan" References: In-Reply-To: DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=222; t=1211371014; x=1212235014; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=paitken@cisco.com; z=From:=20Paul=20Aitken=20 |Subject:=20Re=3A=20[IPFIX]=20FW=3A=20Document=20Action=3A= 20'Guidelines=20for=20IP=20Flow=20Information=0A=20eXport=20 (IPFIX)=20Testing'=20to=20Informational=20RFC |Sender:=20; bh=3CiqrnEpnd5m6T0RCvmg4rY4QCsgAfQsJfWgr7P//Zk=; b=wJfn9oyavD+ewyFVcyQ2Fi0skFm2dUkJbUm+mj0bKzacEgkTZMuroUt6ob fFcR/V1kJl8aITH2BW6whE5voZKrZfASFaU6EvbFsAa7WNIJZq31Xpe8tKjp saoRiTXaxY; Authentication-Results: ams-dkim-2; header.From=paitken@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; ); Cc: ipfix@ietf.org Subject: Re: [IPFIX] FW: Document Action: 'Guidelines for IP Flow Information eXport (IPFIX) Testing' to Informational RFC X-BeenThere: ipfix@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IPFIX WG discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ipfix-bounces@ietf.org Errors-To: ipfix-bounces@ietf.org > Congratulations and thanks to the Editors, Chairs and the whole Working > Group. Thanks Dan for your help getting this draft through the final stages. -- Paul Aitken Cisco Systems Ltd, Edinbnburgh, Scotland. _______________________________________________ IPFIX mailing list IPFIX@ietf.org https://www.ietf.org/mailman/listinfo/ipfix urgh, Scotland. _______________________________________________ IPFIX mailing list IPFIX@ietf.org https://www.ietf.org/mailman/listinfo/ipfix From ipfkaium@ld.net Wed May 21 23:32:29 2008 Return-Path: X-Original-To: ietfarch-ipfix-archive@core3.amsl.com Delivered-To: ietfarch-ipfix-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 361C63A6849 for ; Wed, 21 May 2008 23:32:29 -0700 (PDT) X-Quarantine-ID: X-Virus-Scanned: amavisd-new at amsl.com X-Amavis-Alert: BAD HEADER, Non-encoded 8-bit data (char AE hex): From: VIAGRA \256 Official Site [...] X-Spam-Flag: NO X-Spam-Score: -32.059 X-Spam-Level: X-Spam-Status: No, score=-32.059 tagged_above=-999 required=5 tests=[BAYES_60=1, GB_I_LETTER=-2, HELO_EQ_DSL=1.129, HELO_EQ_PL=1.135, HOST_EQ_PL=1.95, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_3=0.001, MANGLED_OFF=2.3, MIME_8BIT_HEADER=0.3, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, SARE_FROM_DRUGS=1.666, SARE_UNI=0.591, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_SC_SURBL=10, 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 Y-0pRpWbbn5R for ; Wed, 21 May 2008 23:32:28 -0700 (PDT) Received: from eka27.internetdsl.tpnet.pl (eka27.internetdsl.tpnet.pl [83.15.108.27]) by core3.amsl.com (Postfix) with SMTP id A509B3A6839 for ; Wed, 21 May 2008 23:32:27 -0700 (PDT) Content-Return: allowed X-Mailer: devMail.Net (3.0.1854.22234-2) Message-Id: <20080522093255.5467.qmail@eka27.internetdsl.tpnet.pl> To: Subject: Dear ipfix-archive@lists.ietf.org May 87% 0FF From: VIAGRA ® Official Site MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: 7bit Date: Wed, 21 May 2008 23:32:27 -0700 (PDT)
Click Here!
About this mailing:
You are receiving this e-mail because you subscribed to MSN Featured Offers. Microsoft respects your privacy. If you do not wish to receive this MSN Featured Offers e-mail, please click the "Unsubscribe" link below. This will not unsubscribe you from e-mail communications from third-party advertisers that may appear in MSN Feature Offers. This shall not constitute an offer by MSN. MSN shall not be responsible or liable for the advertisers' content nor any of the goods or service advertised. Prices and item availability subject to change without notice.

©2008 Microsoft | Unsubscribe | More Newsletters | Privacy

Microsoft Corporation, One Microsoft Way, Redmond, WA 98052
From 20ldorobek@csisd.org Thu May 22 21:19:59 2008 Return-Path: <20ldorobek@csisd.org> X-Original-To: ietfarch-ipfix-archive@core3.amsl.com Delivered-To: ietfarch-ipfix-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 44B603A68A6 for ; Thu, 22 May 2008 21:19:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.232 X-Spam-Level: X-Spam-Status: No, score=-0.232 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_HCC=4.295, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_CLUBINTERNET=0.781, HELO_EQ_DSL=1.129, HELO_EQ_FR=0.35, HOST_EQ_CLUBINTERNET=0.663, HTML_MESSAGE=0.001, HTML_MIME_NO_HTML_TAG=0.097, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, SARE_FROM_DRUGS=1.666, SUBJ_ALL_CAPS=2.077, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_SC_SURBL=10, URIBL_WS_SURBL=10, 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 U7WNs00nplf6 for ; Thu, 22 May 2008 21:19:57 -0700 (PDT) Received: from ble76-1-89-80-206-56.dsl.club-internet.fr (ble76-1-89-80-206-56.dsl.club-internet.fr [89.80.206.56]) by core3.amsl.com (Postfix) with SMTP id BC9E73A6C5B for ; Thu, 22 May 2008 21:19:49 -0700 (PDT) Message-Id: <20080523071957.22239.qmail@ble76-1-89-80-206-56.dsl.club-internet.fr> To: Subject: RE: SALE 89% OFF From: VIAGRA INC MIME-Version: 1.0 Content-Type: text/html Date: Thu, 22 May 2008 21:19:49 -0700 (PDT)