PROTECTED]
Subject: Re: [Syslog] WGLC: draft-ietf-syslog-tc-mib-02
David,
Thanks for the text. I have done some minor editorial
changes and word-smithing to fit it into the context. It
reads as follows:
For interoperability and backwards compatibility reasons,
the mapping specified
David,
Thanks for the text. I have done some minor editorial
changes and word-smithing to fit it into the context. It
reads as follows:
For interoperability and backwards compatibility reasons,
the mapping specified in this document between a label
which represents a Facility or a Severity,
Hi,
This message officially starts the Syslog Working Group Last Call for
the following document:
Textual Conventions for Syslog Management
(draft-ietf-syslog-tc-mib-02.txt)
ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-ietf-syslog-tc
-mib-02.txt
The Working Group Last Call for these
Hi,
I reviewed this document.
It passes IDnits and libsmi checks.
The security considerations is appropriate to documents containing
only TCs.
The document appears to meet the guidelines of RFC4181 for MIB
documents.
One reference (to protocol-21) is out of date and can be fixed during
AUTH48
Hi,
Please append the following paragraphs to section 2 Background, and
please add these paragraphs to the comment text in the MIB itself that
describe Textual Conventions. A reference should be added in the
section 2 text for the APPNAME SDE with a pointer to the protocol
document.
For
