[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [OPSAWG] [Editorial Errata Reported] RFC5676 (1927)
- To: RFC Errata System <rfc-editor at rfc-editor.org>
- Subject: Re: [OPSAWG] [Editorial Errata Reported] RFC5676 (1927)
- From: Juergen Schoenwaelder <j.schoenwaelder at jacobs-university.de>
- Date: Fri, 23 Oct 2009 21:59:18 +0200
- Cc: "ah at TR-Sys.de" <ah at TR-Sys.de>, "akarmaka at cisco.com" <akarmaka at cisco.com>, "opsawg at ietf.org" <opsawg at ietf.org>
- Delivered-to: opsawg at core3.amsl.com
- In-reply-to: <200910231836.n9NIaO14012178 at boreas.isi.edu>
- List-archive: <http://www.ietf.org/mail-archive/web/opsawg>
- List-help: <mailto:opsawg-request@ietf.org?subject=help>
- List-id: OPSA Working Group Mail List <opsawg.ietf.org>
- List-post: <mailto:opsawg@ietf.org>
- List-subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
- List-unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
- Mail-followup-to: RFC Errata System <rfc-editor at rfc-editor.org>, "alex at cisco.com" <alex at cisco.com>, "akarmaka at cisco.com" <akarmaka at cisco.com>, "dromasca at avaya.com" <dromasca at avaya.com>, "rbonica at juniper.net" <rbonica at juniper.net>, "sob at harvard.edu" <sob at harvard.edu>, "ted.a.seely at sprint.com" <ted.a.seely at sprint.com>, "ah at TR-Sys.de" <ah at TR-Sys.de>, "opsawg at ietf.org" <opsawg at ietf.org>
- References: <200910231836.n9NIaO14012178 at boreas.isi.edu>
- Reply-to: Juergen Schoenwaelder <j.schoenwaelder at jacobs-university.de>
- User-agent: Mutt/1.5.20 (2009-06-14)
On Fri, Oct 23, 2009 at 08:36:24PM +0200, RFC Errata System wrote:
>
> The following errata report has been submitted for RFC5676,
> "Definitions of Managed Objects for Mapping SYSLOG Messages to Simple Network Management Protocol (SNMP) Notifications".
>
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=5676&eid=1927
>
> --------------------------------------
> Type: Editorial
> Reported by: Alfred Hoenes <ah at TR-Sys.de>
>
> Section: 4, 3rd para
>
> Original Text
> -------------
> The MIB module is organized into a group of scalars and two tables.
> The syslogMsgControl group contains two scalars controlling the
> | maximum size of SYSLOG messages recorded in the tables and also
> controlling whether SNMP notifications are generated for SYSLOG
> messages.
>
>
> Corrected Text
> --------------
> The MIB module is organized into a group of scalars and two tables.
> The syslogMsgControl group contains two scalars controlling the
> | maximum number of SYSLOG messages recorded in the tables and also
> controlling whether SNMP notifications are generated for SYSLOG
> messages.
>
>
> Notes
> -----
> Rationale: possible confusion.
>
> "maximum size of SYSLOG messages recorded" conceptionally would
> relate to the SIZE of syslogMsgMsg OCTET STRING instances or the
> maximum value for syslogMsgSDParams instances, but the DESCRIPTION
> clause for the syslogMsgTableMaxSize OBJECT-TYPE in the MIB module
> in Section 7 clarifies that this object indicates the maximum
> *number* of entries in the syslogMsgTable and does not describe
> some filtering criterion (by size) of the SYSLOG messages recorded.
Yes, this is a typo in the text and the DESCRIPTION clause has it
correct.
/js
--
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/>