IETF Logo Mail Archive

Re: [OPSAWG] WG adoption of SNMP <-> SYSLOG mapping documents

"Alexander Clemm (alex)" <alex@cisco.com> Mon, 24 November 2008 21:38 UTC

Return-Path: <opsawg-bounces@ietf.org>
X-Original-To: opsawg-archive@optimus.ietf.org
Delivered-To: ietfarch-opsawg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E62603A6A64; Mon, 24 Nov 2008 13:38:07 -0800 (PST)
X-Original-To: opsawg@core3.amsl.com
Delivered-To: opsawg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4FAE63A69C1 for <opsawg@core3.amsl.com>; Mon, 24 Nov 2008 13:38:07 -0800 (PST)
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 BhS-xZyv9FtJ for <opsawg@core3.amsl.com>; Mon, 24 Nov 2008 13:38:06 -0800 (PST)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 53B163A68F3 for <opsawg@ietf.org>; Mon, 24 Nov 2008 13:38:06 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.33,661,1220227200"; d="scan'208";a="109373413"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-1.cisco.com with ESMTP; 24 Nov 2008 21:38:04 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id mAOLc47P027741; Mon, 24 Nov 2008 13:38:04 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id mAOLc41D008871; Mon, 24 Nov 2008 21:38:04 GMT
Received: from xmb-sjc-236.amer.cisco.com ([128.107.191.121]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 24 Nov 2008 13:38:04 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 24 Nov 2008 13:38:05 -0800
Message-ID: <85B2F271FDF6B949B3672BA5A7BB62FB06C2A43B@xmb-sjc-236.amer.cisco.com>
In-Reply-To: <20081120200500.GA2973@elstar.local>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [OPSAWG] WG adoption of SNMP <-> SYSLOG mapping documents
Thread-Index: AclLS1jVjAP0L960Q8ajyU5PDMjoSgDMTDsQ
References: <20081120200500.GA2973@elstar.local>
From: "Alexander Clemm (alex)" <alex@cisco.com>
To: j.schoenwaelder@jacobs-university.de, opsawg@ietf.org
X-OriginalArrivalTime: 24 Nov 2008 21:38:04.0275 (UTC) FILETIME=[EE99FC30:01C94E7C]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1892; t=1227562684; x=1228426684; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=alex@cisco.com; z=From:=20=22Alexander=20Clemm=20(alex)=22=20<alex@cisco.com > |Subject:=20RE=3A=20[OPSAWG]=20WG=20adoption=20of=20SNMP=20 <->=20SYSLOG=20mapping=20documents |Sender:=20; bh=uHk2JyZ7KIMAJSTx7diIL4spNL8TyDak3tYR+R543Fo=; b=ckUDM8gVGj1su1qFy1LzJa148Gcl3wBm19VGZ+rXwOqy0h5S8fzboshA1f CND27sNvn0LNkYXCZUHTuLDKotMGtVF/i3yfNSCmdq8dSNifFh8efv8l0/NK 3LX1SDfMaM;
Authentication-Results: sj-dkim-3; header.From=alex@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; );
Subject: Re: [OPSAWG] WG adoption of SNMP <-> SYSLOG mapping documents
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: opsawg-bounces@ietf.org
Errors-To: opsawg-bounces@ietf.org

I believe I mentioned this before to the chairs, but for what it's
worth, I'll state it here again "publicly" that I strongly support this
work.  I believe solutions for this issue are needed and think it would
be best to have solutions that are championed by the WG.  

Regards
--- Alex 

-----Original Message-----
From: opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.org] On Behalf
Of Juergen Schoenwaelder
Sent: Thursday, November 20, 2008 12:05 PM
To: opsawg@ietf.org
Subject: [OPSAWG] WG adoption of SNMP <-> SYSLOG mapping documents

Hi,

the chairs of this WG need to decide whether there is support for
adopting (a) a document defining a new SD-ID to represent SNMP
notifications in SYSLOG [1] and (b) a document defining a MIB module
representing SYSLOG messages [2]. For an overview, see the
presentation slides form the Dublin meeting [3].

I believe that the documents are already pretty mature and can likely
go through the WG relatively quickly. There has been quite some
support for this work in Dublin and Rainer Gerhards expressed his
support on the list. I am aware that some people did contact the
chairs directly expressing their support but it might make things
easier to move this forward if people can actually express their
support here.

Thanks,

/js

[1] http://tools.ietf.org/html/draft-marinov-syslog-snmp-02 
    (15 pages)
[2] http://tools.ietf.org/html/draft-schoenw-syslog-msg-mib-01 
    (18 pages)
[3] http://www.ietf.org/proceedings/08jul/slides/opsawg-1.pdf

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg
_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg

v2.23.0 | Report a Bug | By Email