Mapping Simple Network Management Protocol (SNMP) Notifications to SYSLOG Messages
Note: This ballot was opened for revision 05 and is now closed.
(Dan Romascanu) Yes
(Jari Arkko) No Objection
(Ron Bonica) No Objection
(Ross Callon) No Objection
(Lisa Dusseault) No Objection
(Lars Eggert) (was Discuss) No Objection
Section 3.1., paragraph 1: > which correponds to "Notice: normal but significant condition". If Nit: s/correponds/corresponds/ Section 3.2., paragraph 7: > NULL = "" zero-length char-val (You can just remove NULL everywhere, I think.)
(Pasi Eronen) No Objection
(Adrian Farrel) No Objection
(Russ Housley) No Objection
Alexey Melnikov (was Discuss) No Objection
In Section 7: The SNMP architecture supports an access control mechanism ensuring that SNMP notifications are only sent to receivers who are authorized to receive the notification. Network operators using this mapping of SNMP notifications to SYSLOG messages should enforce a consistent s/should/SHOULD ? policy preventing people from accessing SNMP notifications via the SYSLOG mapping that would otherwise not be accessible.