[OPSAWG] [Editorial Errata Reported] RFC5676 (1927)
RFC Errata System <rfc-editor@rfc-editor.org> Fri, 23 October 2009 18:37 UTC
Return-Path: <web-usrn@ISI.EDU>
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 F0C493A697A for <opsawg@core3.amsl.com>; Fri, 23 Oct 2009 11:37:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.197
X-Spam-Level:
X-Spam-Status: No, score=-17.197 tagged_above=-999 required=5 tests=[AWL=0.402, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
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 XbI3TZajkmLh for <opsawg@core3.amsl.com>; Fri, 23 Oct 2009 11:37:09 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 177883A6856 for <opsawg@ietf.org>; Fri, 23 Oct 2009 11:37:09 -0700 (PDT)
Received: from boreas.isi.edu (localhost [127.0.0.1]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n9NIaQuv012201; Fri, 23 Oct 2009 11:36:26 -0700 (PDT)
Received: (from web-usrn@localhost) by boreas.isi.edu (8.13.8/8.13.8/Submit) id n9NIaO14012178; Fri, 23 Oct 2009 11:36:24 -0700 (PDT)
Date: Fri, 23 Oct 2009 11:36:24 -0700
Message-Id: <200910231836.n9NIaO14012178@boreas.isi.edu>
To: j.schoenwaelder@jacobs-university.de, alex@cisco.com, akarmaka@cisco.com, dromasca@avaya.com, rbonica@juniper.net, sob@harvard.edu, ted.a.seely@sprint.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: web-usrn@boreas.isi.edu
X-Mailman-Approved-At: Sun, 25 Oct 2009 00:22:43 -0700
Cc: ah@TR-Sys.de, opsawg@ietf.org, rfc-editor@rfc-editor.org
Subject: [OPSAWG] [Editorial Errata Reported] RFC5676 (1927)
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/mail-archive/web/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>
X-List-Received-Date: Fri, 23 Oct 2009 18:37:10 -0000
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@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. Instructions: ------------- This errata is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- RFC5676 (draft-ietf-opsawg-syslog-msg-mib-06) -------------------------------------- Title : Definitions of Managed Objects for Mapping SYSLOG Messages to Simple Network Management Protocol (SNMP) Notifications Publication Date : October 2009 Author(s) : J. Schoenwaelder, A. Clemm, A. Karmakar Category : PROPOSED STANDARD Source : Operations and Management Area Working Group Area : Operations and Management Stream : IETF Verifying Party : IESG
- Re: [OPSAWG] [Editorial Errata Reported] RFC5676 … Juergen Schoenwaelder
- [OPSAWG] [Editorial Errata Reported] RFC5676 (192… RFC Errata System