Re: [OPSAWG] WG adoption of SNMP <-> SYSLOG mapping documents
"tom.petch" <cfinss@dial.pipex.com> Tue, 10 February 2009 18:18 UTC
Return-Path: <cfinss@dial.pipex.com>
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 B485E3A69DF for <opsawg@core3.amsl.com>; Tue, 10 Feb 2009 10:18:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.85
X-Spam-Level:
X-Spam-Status: No, score=-0.85 tagged_above=-999 required=5 tests=[AWL=-0.809, BAYES_05=-1.11, DATE_IN_PAST_06_12=1.069]
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 5u5X1NiIFi8F for <opsawg@core3.amsl.com>; Tue, 10 Feb 2009 10:18:48 -0800 (PST)
Received: from mk-outboundfilter-2.mail.uk.tiscali.com (mk-outboundfilter-2.mail.uk.tiscali.com [212.74.114.38]) by core3.amsl.com (Postfix) with ESMTP id 4A3DD3A6A99 for <opsawg@ietf.org>; Tue, 10 Feb 2009 10:18:48 -0800 (PST)
X-Trace: 185131691/mk-outboundfilter-2.mail.uk.tiscali.com/PIPEX/$PIPEX-ACCEPTED/pipex-customers/62.188.100.69/None/cfinss@dial.pipex.com
X-SBRS: None
X-RemoteIP: 62.188.100.69
X-IP-MAIL-FROM: cfinss@dial.pipex.com
X-MUA: Microsoft Outlook Express 6.00.2800.1106Produced By Microsoft MimeOLE V6.00.2800.1106
X-IP-BHB: Once
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlUFACBUkUk+vGRF/2dsb2JhbABFgwAtFooTtwUJjx0BBoJcgTcG
X-IronPort-AV: E=Sophos;i="4.38,187,1233532800"; d="scan'208";a="185131691"
X-IP-Direction: IN
Received: from 1cust69.tnt1.lnd9.gbr.da.uu.net (HELO allison) ([62.188.100.69]) by smtp.pipex.tiscali.co.uk with SMTP; 10 Feb 2009 18:18:49 +0000
Message-ID: <000701c98ba3$7ebe4a60$0601a8c0@allison>
From: "tom.petch" <cfinss@dial.pipex.com>
To: j.schoenwaelder@jacobs-university.de, opsawg@ietf.org
References: <20081120200500.GA2973@elstar.local>
Date: Tue, 10 Feb 2009 12:31:26 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Subject: Re: [OPSAWG] WG adoption of SNMP <-> SYSLOG mapping documents
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: "tom.petch" <cfinss@dial.pipex.com>
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/mail-archive/web/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>
X-List-Received-Date: Tue, 10 Feb 2009 18:18:49 -0000
In syslog-msg-mib, is the value of an SD-PARAM stored with or without the escaping? syslog needs the escapes because of the syntax of the syslog message, BER.1 does not so they could be removed. Tom Petch ----- Original Message ----- From: "Juergen Schoenwaelder" <j.schoenwaelder@jacobs-university.de> To: <opsawg@ietf.org> Sent: Thursday, November 20, 2008 9:05 PM 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] WG adoption of SNMP <-> SYSLOG mapping d… Juergen Schoenwaelder
- Re: [OPSAWG] WG adoption of SNMP <-> SYSLOG mappi… Aiko Pras
- Re: [OPSAWG] WG adoption of SNMP <-> SYSLOG mappi… David Partain
- Re: [OPSAWG] WG adoption of SNMP <-> SYSLOG mappi… Martin Bjorklund
- Re: [OPSAWG] WG adoption of SNMP <-> SYSLOG mappi… Natale, Bob
- Re: [OPSAWG] WG adoption of SNMP <-> SYSLOG mappi… Alexander Clemm (alex)
- Re: [OPSAWG] WG adoption of SNMP <-> SYSLOG mappi… Juergen Quittek
- Re: [OPSAWG] WG adoption of SNMP <-> SYSLOG mappi… Rainer Gerhards
- Re: [OPSAWG] WG adoption of SNMP <-> SYSLOG mappi… Mehmet Ersue
- Re: [OPSAWG] WG adoption of SNMP <-> SYSLOG mappi… Benoit Claise
- Re: [OPSAWG] WG adoption of SNMP <-> SYSLOG mappi… Yuquan Tracy Jiang (jiangy)
- Re: [OPSAWG] WG adoption of SNMP <-> SYSLOG mappi… tom.petch
- Re: [OPSAWG] WG adoption of SNMP <-> SYSLOG mappi… Juergen Schoenwaelder
- Re: [OPSAWG] WG adoption of SNMP <-> SYSLOG mappi… tom.petch