Re: [Syslog] [Editorial Errata Reported] RFC5424 (2682)

"t.petch" <ietfc@btconnect.com> Tue, 11 January 2011 11:44 UTC

Return-Path: <ietfc@btconnect.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 48A2428C122 for <syslog@core3.amsl.com>; Tue, 11 Jan 2011 03:44:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.799
X-Spam-Level:
X-Spam-Status: No, score=-2.799 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599]
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 438NIpu5Jg1E for <syslog@core3.amsl.com>; Tue, 11 Jan 2011 03:44:48 -0800 (PST)
Received: from mail.btconnect.com (c2bthomr13.btconnect.com [213.123.20.131]) by core3.amsl.com (Postfix) with ESMTP id CE2A128C152 for <syslog@ietf.org>; Tue, 11 Jan 2011 03:44:47 -0800 (PST)
Received: from host217-44-202-158.range217-44.btcentralplus.com (HELO pc6) ([217.44.202.158]) by c2bthomr13.btconnect.com with SMTP id BGY48743; Tue, 11 Jan 2011 11:46:58 +0000 (GMT)
Message-ID: <00e401cbb17c$68868ae0$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: <rgerhards@adiscon.com>
References: <20110108075856.89752E0717@rfc-editor.org>
Date: Tue, 11 Jan 2011 11:43:31 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Neutral-1, source=Queried, refid=tid=0001.0A0B0301.4D2C432D.0124, actions=tag
X-Junkmail-Status: score=10/50, host=c2bthomr13.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0203.4D2C4336.0109, ss=1, fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=single engine
X-Junkmail-IWF: false
Cc: syslog@ietf.org
Subject: Re: [Syslog] [Editorial Errata Reported] RFC5424 (2682)
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: Tue, 11 Jan 2011 11:44:49 -0000

Oh dear:-(

Looks like a good correction to me.

(nb I have stripped off all the addressees which I will get bounces for; they
will need restoring for whatever conclusion we reach)

Tom Petch

----- Original Message -----
From: "RFC Errata System" <rfc-editor@rfc-editor.org>;
To: <rgerhards@adiscon.com>;; <turners@ieca.com>;; <tim.polk@nist.gov>;;
<ietfdbh@comcast.net>;; <clonvick@cisco.com>;
Cc: <syslog@ietf.org>;; <iamvic@rambler.ru>;; <rfc-editor@rfc-editor.org>;
Sent: Saturday, January 08, 2011 8:58 AM
Subject: [Syslog] [Editorial Errata Reported] RFC5424 (2682)


>
> The following errata report has been submitted for RFC5424,
> "The Syslog Protocol".
>
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=5424&eid=2682
>
> --------------------------------------
> Type: Editorial
> Reported by: VicTor Smirnoff <iamvic@rambler.ru>;
>
> Section: 6.2.1.
>
> Original Text
> -------------
>  15             clock daemon (note 2)
> (...)
>  Table 1.  Syslog Message Facilities
>
>
>
> Corrected Text
> --------------
>  15             clock daemon
> (...)
>  Table 1.  Syslog Message Facilities
>
>
> Notes
> -----
> Note 2 isn't present in this document. It's an artefact from RFC 3164.
>
> 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.
>
> --------------------------------------
> RFC5424 (draft-ietf-syslog-protocol-23)
> --------------------------------------
> Title               : The Syslog Protocol
> Publication Date    : March 2009
> Author(s)           : R. Gerhards
> Category            : PROPOSED STANDARD
> Source              : Security Issues in Network Event Logging
> Area                : Security
> Stream              : IETF
> Verifying Party     : IESG
> _______________________________________________
> Syslog mailing list
> Syslog@ietf.org
> https://www.ietf.org/mailman/listinfo/syslog