Re: [Syslog] RFC 5674 on Alarms in Syslog (fwd)
"Rainer Gerhards" <rgerhards@hq.adiscon.com> Wed, 28 October 2009 19:58 UTC
Return-Path: <rgerhards@hq.adiscon.com>
X-Original-To: syslog@core3.amsl.com
Delivered-To: syslog@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EA6E228C0CE for <syslog@core3.amsl.com>; Wed, 28 Oct 2009 12:58:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_93=0.6]
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 T1xFFh56E-gI for <syslog@core3.amsl.com>; Wed, 28 Oct 2009 12:58:56 -0700 (PDT)
Received: from mailin.adiscon.com (hetzner.adiscon.com [85.10.198.18]) by core3.amsl.com (Postfix) with ESMTP id CDEA83A691E for <syslog@ietf.org>; Wed, 28 Oct 2009 12:58:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailin.adiscon.com (Postfix) with ESMTP id 1C744241C019; Wed, 28 Oct 2009 20:45:02 +0100 (CET)
Received: from mailin.adiscon.com ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 113gW2aj-Tgt; Wed, 28 Oct 2009 20:45:01 +0100 (CET)
Received: from GRFEXC.intern.adiscon.com (p54AC55D3.dip.t-dialin.net [84.172.85.211]) by mailin.adiscon.com (Postfix) with ESMTP id 6192C241C001; Wed, 28 Oct 2009 20:45:01 +0100 (CET)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 28 Oct 2009 20:59:08 +0100
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5
Message-ID: <9B6E2A8877C38245BFB15CC491A11DA71032EE@GRFEXC.intern.adiscon.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Syslog] RFC 5674 on Alarms in Syslog (fwd)
Thread-Index: AcpYBWwqAGQzCzxwS5+ilVYe+5BrSwAA4DcA
References: <Pine.GSO.4.63.0910281231220.4624@sjc-cde-011.cisco.com>
From: Rainer Gerhards <rgerhards@hq.adiscon.com>
To: Chris Lonvick <clonvick@cisco.com>, syslog@ietf.org
Subject: Re: [Syslog] RFC 5674 on Alarms in Syslog (fwd)
X-BeenThere: syslog@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Security Issues in Network Event Logging <syslog.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/syslog>, <mailto:syslog-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/syslog>
List-Post: <mailto:syslog@ietf.org>
List-Help: <mailto:syslog-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/syslog>, <mailto:syslog-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Oct 2009 19:58:57 -0000
Hi Chris, Thanks - but it really was Sharon who brought this forward and did the vast majority of work. I primarily helped it to bootstrap :) Thanks, Sharon! Rainer > -----Original Message----- > From: syslog-bounces@ietf.org > [mailto:syslog-bounces@ietf.org] On Behalf Of Chris Lonvick > Sent: Wednesday, October 28, 2009 8:32 PM > To: syslog@ietf.org > Subject: [Syslog] RFC 5674 on Alarms in Syslog (fwd) > > Hi Folks, > > Just passing this along. Congratulations to Sharon and Reiner. > > Best regards, > Chris > > ---------- Forwarded message ---------- > Date: Wed, 28 Oct 2009 12:19:21 -0700 (PDT) > From: rfc-editor@rfc-editor.org > To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org > Cc: opsawg@ietf.org, rfc-editor@rfc-editor.org > Subject: RFC 5674 on Alarms in Syslog > > > A new Request for Comments is now available in online RFC libraries. > > > RFC 5674 > > Title: Alarms in Syslog > Author: S. Chisholm, R. Gerhards > Status: Standards Track > Date: October 2009 > Mailbox: schishol@nortel.com, > rgerhards@adiscon.com > Pages: 7 > Characters: 13837 > Updates/Obsoletes/SeeAlso: None > > I-D Tag: draft-ietf-opsawg-syslog-alarm-02.txt > > URL: http://www.rfc-editor.org/rfc/rfc5674.txt > > This document describes how to send alarm information in syslog. It > includes the mapping of ITU perceived severities onto syslog message > fields. It also includes a number of alarm-specific SD-PARAM > definitions from X.733 and the IETF Alarm MIB. [STANDARDS TRACK] > > This document is a product of the Operations and Management > Area Working Group Working Group of the IETF. > > This is now a Proposed Standard Protocol. > > STANDARDS TRACK: This document specifies an Internet standards track > protocol for the Internet community,and requests discussion > and suggestions > for improvements. Please refer to the current edition of the Internet > Official Protocol Standards (STD 1) for the standardization state and > status of this protocol. Distribution of this memo is unlimited. > > This announcement is sent to the IETF-Announce and rfc-dist lists. > To subscribe or unsubscribe, see > http://www.ietf.org/mailman/listinfo/ietf-announce > http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist > > For searching the RFC series, see > http://www.rfc-editor.org/rfcsearch.html. > For downloading RFCs, see http://www.rfc-editor.org/rfc.html. > > Requests for special distribution should be addressed to either the > author of the RFC in question, or to > rfc-editor@rfc-editor.org. Unless > specifically noted otherwise on the RFC itself, all RFCs are for > unlimited distribution. > > > The RFC Editor Team > USC/Information Sciences Institute > > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://www.ietf.org/mailman/listinfo/ietf-announce > _______________________________________________ > Syslog mailing list > Syslog@ietf.org > https://www.ietf.org/mailman/listinfo/syslog >
- [Syslog] RFC 5674 on Alarms in Syslog (fwd) Chris Lonvick
- Re: [Syslog] RFC 5674 on Alarms in Syslog (fwd) Rainer Gerhards