IETF Logo Mail Archive

Re: [OPSAWG] FW: I-D Action:draft-ietf-opsawg-syslog-alarm-00.txt

"Seely, Ted A [CTO]" <Ted.A.Seely@sprint.com> Tue, 29 July 2008 17:41 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 647373A6B59; Tue, 29 Jul 2008 10:41:57 -0700 (PDT)
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 2BB893A6B7E for <opsawg@core3.amsl.com>; Tue, 29 Jul 2008 10:41:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 uinn67OESGi3 for <opsawg@core3.amsl.com>; Tue, 29 Jul 2008 10:41:55 -0700 (PDT)
Received: from VA3EHSOBE006.bigfish.com (outbound-va3.frontbridge.com [216.32.180.16]) by core3.amsl.com (Postfix) with ESMTP id 3B4F63A67AB for <opsawg@ietf.org>; Tue, 29 Jul 2008 10:40:43 -0700 (PDT)
Received: from mail143-va3-R.bigfish.com (10.7.14.246) by VA3EHSOBE006.bigfish.com (10.7.40.26) with Microsoft SMTP Server id 8.1.240.5; Tue, 29 Jul 2008 17:40:55 +0000
Received: from mail143-va3 (localhost.localdomain [127.0.0.1]) by mail143-va3-R.bigfish.com (Postfix) with ESMTP id 520C2F28890; Tue, 29 Jul 2008 17:40:55 +0000 (UTC)
X-BigFish: VS-27(z37d4lz542N936eQ936fQ9371M8a89ihzzzz1033ILz2fh6bh43j61h)
X-Spam-TCS-SCL: 0:0
X-FB-SS: 5,5,
Received: by mail143-va3 (MessageSwitch) id 1217353253460111_18127; Tue, 29 Jul 2008 17:40:53 +0000 (UCT)
Received: from plss1400.corp.sprint.com (unknown [144.230.162.53]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail143-va3.bigfish.com (Postfix) with ESMTP id 5BD7D22006D; Tue, 29 Jul 2008 17:40:53 +0000 (UTC)
Received: from pdawh01a.ad.sprint.com (PDAWH01A.corp.sprint.com [144.226.110.69]) by plss1400.corp.sprint.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id m6THeoqO025344; Tue, 29 Jul 2008 12:40:52 -0500 (CDT)
Received: from PDAWM04C.ad.sprint.com ([144.226.111.27]) by pdawh01a.ad.sprint.com ([144.226.110.69]) with mapi; Tue, 29 Jul 2008 12:40:51 -0500
From: "Seely, Ted A [CTO]" <Ted.A.Seely@sprint.com>
To: Sharon Chisholm <schishol@nortel.com>, "opsawg@ietf.org" <opsawg@ietf.org>
Date: Tue, 29 Jul 2008 12:40:49 -0500
Thread-Topic: [OPSAWG] FW: I-D Action:draft-ietf-opsawg-syslog-alarm-00.txt
Thread-Index: AcjXe2H/4FnmnCHPTA2j9YO3L7aM3AZ0/uswABS301Q=
Message-ID: <C4B4CE61.7403%ted.a.seely@sprint.com>
In-Reply-To: <713043CE8B8E1348AF3C546DBE02C1B415A80C1F@zcarhxm2.corp.nortel.com>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
Subject: Re: [OPSAWG] FW: I-D Action:draft-ietf-opsawg-syslog-alarm-00.txt
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: multipart/mixed; boundary="===============1619608960=="
Sender: opsawg-bounces@ietf.org
Errors-To: opsawg-bounces@ietf.org

I have heard zero comments to the negative regarding this on the mailing list, so I see why not.  However I believe protocol requires that we do so on the ML after the  meeting.

Ted



________________________________
From: Sharon Chisholm <schishol@nortel.com>
Date: Tue, 29 Jul 2008 02:48:03 -0500
To: <opsawg@ietf.org>
Subject: [OPSAWG] FW:  I-D Action:draft-ietf-opsawg-syslog-alarm-00.txt

Hi

Can we bring this to working group last call or are there open issues
that we feel we need to address first.

Sharon

-----Original Message-----
From: opsawg-bounces@ietf.org [mailto:opsawg-bounces@ietf.org] On Behalf
Of Internet-Drafts@ietf.org
Sent: Wednesday, June 25, 2008 2:45 PM
To: i-d-announce@ietf.org
Cc: opsawg@ietf.org
Subject: [OPSAWG] I-D Action:draft-ietf-opsawg-syslog-alarm-00.txt

A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Operations and Management Area Working
Group Working Group of the IETF.


        Title           : Alarms in SYSLOG
        Author(s)       : S. Chisholm, R. Gerhards
        Filename        : draft-ietf-opsawg-syslog-alarm-00.txt
        Pages           : 11
        Date            : 2008-06-19

This document describes how to send alarm information in syslog.  It
includes the mapping of ITU perceived severities onto syslog message
fields.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-opsawg-syslog-alarm-00.tx
t

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.


_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg

v2.23.0 | Report a Bug | By Email