[PSAMP] Concluding the PSAM WG and moving the remaining work item to the IPFIX WG charter
"Juergen Quittek" <Quittek@nw.neclab.eu> Wed, 17 June 2009 19:25 UTC
Return-Path: <Quittek@nw.neclab.eu>
X-Original-To: psamp@core3.amsl.com
Delivered-To: psamp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 18C0728C2DF; Wed, 17 Jun 2009 12:25:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 nkVs+WR-Bn-b; Wed, 17 Jun 2009 12:25:41 -0700 (PDT)
Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41]) by core3.amsl.com (Postfix) with ESMTP id B9A9F28C2DA; Wed, 17 Jun 2009 12:25:40 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp0.neclab.eu (Postfix) with ESMTP id F17B52C01C8EC; Wed, 17 Jun 2009 21:25:51 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas2.office)
Received: from smtp0.neclab.eu ([127.0.0.1]) by localhost (atlas2.office [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CtcBX52wiG8Q; Wed, 17 Jun 2009 21:25:51 +0200 (CEST)
Received: from VENUS.office (mx1.office [192.168.24.3]) by smtp0.neclab.eu (Postfix) with ESMTP id B12422C019196; Wed, 17 Jun 2009 21:25:31 +0200 (CEST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: from 10.7.0.54 ([10.7.0.54]) by VENUS.office ([192.168.24.102]) with Microsoft Exchange Server HTTP-DAV ; Wed, 17 Jun 2009 19:25:31 +0000
MIME-Version: 1.0
Content-class: urn:content-classes:message
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="B_3328118500_1049239"
Date: Wed, 17 Jun 2009 21:21:40 +0200
Message-ID: <C65F0EE4.6D50B%Quittek@nw.neclab.eu>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
Thread-Topic: Concluding the PSAM WG and moving the remaining work item to the IPFIX WG charter
Thread-Index: AcnvgNcTDmN0YTA0zUKyt9t4T6yGqA==
From: Juergen Quittek <Quittek@nw.neclab.eu>
To: Dan Romascanu <dromasca@avaya.com>
Cc: IETF PSAMP Working Group <psamp@ietf.org>, IETF IPFIX Working Group <ipfix@ietf.org>
Subject: [PSAMP] Concluding the PSAM WG and moving the remaining work item to the IPFIX WG charter
X-BeenThere: psamp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This mailing list is used for discussion within the IETF packet sampling \(PSAMP\) WG" <psamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/psamp>, <mailto:psamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/psamp>
List-Post: <mailto:psamp@ietf.org>
List-Help: <mailto:psamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/psamp>, <mailto:psamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jun 2009 19:25:43 -0000
Dear Dan and Ron, I'm writing you with two hats on, the one of the PSAMP WG chair and the one of the IPFIX WG co-chair. As discussed at the IPFIX session in San Francisco, we plan to conclude the PSAMP WG and move the one remaining work item to the IPFIX WG. The PSAMP WG has published all its planned documents except for the PSAMP MIB module. It does not seem reasonable to keep the WG alive just for finishing this single document. Most of the PSAMP WG members are also members of the IPFIX WG. The remaining work can be completed in the IPFIX WG. Therefore I propose to conclude the PSAMP WG and at the same time to extend the IPFIX WG charter by adding the following text: 6. The PSAMP WG has developed a protocol for reporting observed packets. The PSAMP protocol is an extension of the IPFIX protocol. The IPFIX WG will develop a MIB module for monitoring PSAMP implementations. The new MIB module will be an extension of the IPFIX MIB module. with the new milestones Jan 2010 Submit final version of PSAMP MIB module In the current PSAMP charter, the PSAMP MIB module work item is described as follows: 6. Configuration and Management. Define a packet sampler MIB to reside at the network element, including parameters for packet selection, packet report and stream format, and export. Select or define a communication protocol to configure/read this MIB. This old text included monitoring and configuration. However, the PSAMP WG as well as the IPFIX WG have consensus on using MIB modules rather for monitoring than for configuration. Configuration of PSAMP implementations is already covered by an existing IPFIX work item: the Configuration Data Model for IPFIX and PSAMP (draft-ietf-ipfix-configuration-model). Therefore, the item to be added to the IPFIX charter would cover monitoring only. The suggested extension of the IPFIX charter was discussed at the last IPFIX session in San Francisco without any objection. Thanks, Juergen
- [PSAMP] Concluding the PSAM WG and moving the rem… Juergen Quittek
- Re: [PSAMP] Concluding the PSAM WG and moving the… Romascanu, Dan (Dan)
- Re: [PSAMP] Concluding the PSAM WG and moving the… Juergen Quittek