Re: [PSAMP] Concluding the PSAM WG and moving the remaining work item to the IPFIX WG charter

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Wed, 17 June 2009 20:42 UTC

Return-Path: <dromasca@avaya.com>
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 6F1293A6AD4; Wed, 17 Jun 2009 13:42:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150, 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 20HUld9gWdX1; Wed, 17 Jun 2009 13:42:24 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 7E2063A6AB4; Wed, 17 Jun 2009 13:42:24 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,239,1243828800"; d="scan'208";a="174269126"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 17 Jun 2009 16:42:35 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 17 Jun 2009 16:42:35 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 17 Jun 2009 22:42:22 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04017D2F22@307622ANEX5.global.avaya.com>
In-Reply-To: <C65F0EE4.6D50B%Quittek@nw.neclab.eu>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Concluding the PSAM WG and moving the remaining work item to the IPFIX WG charter
Thread-Index: AcnvgNcTDmN0YTA0zUKyt9t4T6yGqAACap7A
References: <C65F0EE4.6D50B%Quittek@nw.neclab.eu>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Juergen Quittek <Quittek@nw.neclab.eu>
Cc: IETF PSAMP Working Group <psamp@ietf.org>, IETF IPFIX Working Group <ipfix@ietf.org>
Subject: Re: [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 20:42:25 -0000

This is fine and I support the move. 

Can you please forward me a revised IPFIX charter with the PSAMP MIB
added?

It would be a good opportunity to adjust milestones if necessary. 

Dan
 

> -----Original Message-----
> From: Juergen Quittek [mailto:Quittek@nw.neclab.eu] 
> Sent: Wednesday, June 17, 2009 10:22 PM
> To: Romascanu, Dan (Dan)
> Cc: Nevil Brownlee; IETF PSAMP Working Group; IETF IPFIX Working Group
> Subject: Concluding the PSAM WG and moving the remaining work 
> item to the IPFIX WG charter
> 
> 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
>