Re: [Syslog] draft-ietf-syslog-device-mib-07.txt
Glenn Mansfield Keeni <glenn@cysols.com> Thu, 26 January 2006 05:44 UTC
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F1zvv-0003Xj-4P; Thu, 26 Jan 2006 00:44:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F1zvt-0003Xb-1J for syslog@megatron.ietf.org; Thu, 26 Jan 2006 00:44:33 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA12606 for <syslog@ietf.org>; Thu, 26 Jan 2006 00:43:01 -0500 (EST)
Received: from waga.cysol.co.jp ([210.233.3.228]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F205i-00068f-8W for syslog@ietf.org; Thu, 26 Jan 2006 00:54:46 -0500
Received: from aso.priv.cysol.co.jp (aso.priv.cysol.co.jp [192.168.0.15]) by waga.cysol.co.jp (8.12.9/8.12.9) with ESMTP id k0Q5hwXj011131; Thu, 26 Jan 2006 14:43:58 +0900 (JST)
Received: from [127.0.0.1] (bert.priv.cysol.co.jp [192.168.0.254]) by aso.priv.cysol.co.jp (8.12.9/8.12.9) with ESMTP id k0Q5hu5x001927; Thu, 26 Jan 2006 14:43:58 +0900 (JST)
Message-ID: <43D8619C.5090302@cysols.com>
Date: Thu, 26 Jan 2006 14:43:56 +0900
From: Glenn Mansfield Keeni <glenn@cysols.com>
Organization: Cyber Solutions Inc.
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Tom Petch <nwnetworks@dial.pipex.com>
Subject: Re: [Syslog] draft-ietf-syslog-device-mib-07.txt
References: <577465F99B41C842AAFBE9ED71E70ABA0E416E@grfint2.intern.adiscon.com> <001601c61234$f7e335e0$0601a8c0@pc6> <43CEFB3A.4000806@cysols.com> <001001c61d9d$5a360b00$0601a8c0@pc6> <43D46CAA.8080403@cysols.com> <000801c620db$e8e842a0$0601a8c0@pc6>
In-Reply-To: <000801c620db$e8e842a0$0601a8c0@pc6>
X-Enigmail-Version: 0.86.1.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit
Cc: syslog@ietf.org
X-BeenThere: syslog@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Security Issues in Network Event Logging <syslog.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/syslog>, <mailto:syslog-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/syslog>
List-Post: <mailto:syslog@lists.ietf.org>
List-Help: <mailto:syslog-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/syslog>, <mailto:syslog-request@lists.ietf.org?subject=subscribe>
Sender: syslog-bounces@lists.ietf.org
Errors-To: syslog-bounces@lists.ietf.org
Tom,
>
>
> Getting there; recall that my initial problem is one of understanding what it is
> the MIB caters for. I had expected the MIB to cater for a pure Sender, in order
> to configure it with where to send what, and I am slightly suprised at that
> omission. As ever, it is a question of reaching rough consensus on questions
> like this.
Right. I will reword the answer.
The MIB serves to monitor entities that receive and/or forward syslog messages
e.g. the unix syslog daemon.
Note that the MIB allows us to monitor all the syslog messages even if we do not
monitor senders. [There is nothing in the MIB that prohibits one from monitoring
the senders for syslog messages, but it is better done by monitoring the entity
that receives syslog messages (from multiple entities) and forwards some of those
messages].
>
> Likewise, grouping is not something I am familiar with, seeing rather a single
> Collector with proprietary features behind it to filter, disseminate etc.
We are focussing on the simple and primary task of monitoring syslog messages from
syslog entities. The MIB will support several syslog daemons which are probably using
various transports (UDP{4|6}, TCP{4|6}, on standard and non-standard ports.). This
situation does arise in practice. I think that the MIB does take care of that nicely
using the concept of grouping.
One good way to look at the MIB is as a collection of knobs and dials. Then we can
ask
a. Do we need another knob or another dial
b. Do we need this knob or that dial
>
> Tom Petch
>
Cheers
Glenn
--
+----------------------------------------------------------+
Cyber Solutions Inc. Phone 022-303-4012
6-6-3, Minami Yoshinari Fax 022-303-4015
Aoba-ku, Sendai, Japan 989-3204 e-mail cyber@cysols.com
+----------------------------------------------------------+
_______________________________________________
Syslog mailing list
Syslog@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/syslog
- [Syslog] TIMESTAMP and leap seconds Rainer Gerhards
- RE: [Syslog] TIMESTAMP and leap seconds Andrew Ross
- [Syslog] draft-ietf-syslog-device-mib-07.txt Tom Petch
- Re: [Syslog] draft-ietf-syslog-device-mib-07.txt Glenn Mansfield Keeni
- Re: [Syslog] draft-ietf-syslog-device-mib-07.txt Tom Petch
- Re: [Syslog] draft-ietf-syslog-device-mib-07.txt Glenn Mansfield Keeni
- Re: [Syslog] draft-ietf-syslog-device-mib-07.txt Tom Petch
- Re: [Syslog] draft-ietf-syslog-device-mib-07.txt Glenn Mansfield Keeni
- Re: [Syslog] draft-ietf-syslog-device-mib-07.txt Tom Petch