Mapping Simple Network Management Protocol (SNMP) Notifications to SYSLOG Messages
draft-ietf-opsawg-syslog-snmp-05
Yes
(Dan Romascanu)
No Objection
(Adrian Farrel)
(Jari Arkko)
(Lisa Dusseault)
(Pasi Eronen)
(Robert Sparks)
(Ron Bonica)
(Ross Callon)
(Russ Housley)
(Tim Polk)
Note: This ballot was opened for revision 05 and is now closed.
Lars Eggert
(was Discuss)
No Objection
Comment
(2009-08-11)
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.)
Dan Romascanu Former IESG member
Yes
Yes
()
Adrian Farrel Former IESG member
No Objection
No Objection
()
Alexey Melnikov Former IESG member
(was Discuss)
No Objection
No Objection
(2009-08-14)
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.
Jari Arkko Former IESG member
No Objection
No Objection
()
Lisa Dusseault Former IESG member
No Objection
No Objection
()
Pasi Eronen Former IESG member
No Objection
No Objection
()
Robert Sparks Former IESG member
No Objection
No Objection
()
Ron Bonica Former IESG member
No Objection
No Objection
()
Ross Callon Former IESG member
No Objection
No Objection
()
Russ Housley Former IESG member
No Objection
No Objection
()
Tim Polk Former IESG member
No Objection
No Objection
()