[Syslog] RFC 5674 on Alarms in Syslog (fwd)

Chris Lonvick <clonvick@cisco.com> Wed, 28 October 2009 19:31 UTC

Return-Path: <clonvick@cisco.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 83CD53A6836 for <syslog@core3.amsl.com>; Wed, 28 Oct 2009 12:31:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.224
X-Spam-Level:
X-Spam-Status: No, score=-6.224 tagged_above=-999 required=5 tests=[AWL=-0.225, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, 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 VuESxa45ft57 for <syslog@core3.amsl.com>; Wed, 28 Oct 2009 12:31:56 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 1E5953A6940 for <syslog@ietf.org>; Wed, 28 Oct 2009 12:31:56 -0700 (PDT)
Authentication-Results: sj-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmYFAEs56EqrR7H+/2dsb2JhbACQGgGyPJgthD8E
X-IronPort-AV: E=Sophos;i="4.44,641,1249257600"; d="scan'208";a="218878716"
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-2.cisco.com with ESMTP; 28 Oct 2009 19:32:11 +0000
Received: from sjc-cde-011.cisco.com (sjc-cde-011.cisco.com [171.69.16.68]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id n9SJWBfV017003 for <syslog@ietf.org>; Wed, 28 Oct 2009 19:32:11 GMT
Date: Wed, 28 Oct 2009 12:32:11 -0700
From: Chris Lonvick <clonvick@cisco.com>
To: syslog@ietf.org
Message-ID: <Pine.GSO.4.63.0910281231220.4624@sjc-cde-011.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Subject: [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:31:59 -0000

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