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.
Dan Romascanu Former IESG member
Yes
Yes
()
Unknown
Adrian Farrel Former IESG member
No Objection
No Objection
()
Unknown
Alexey Melnikov Former IESG member
(was Discuss)
No Objection
No Objection
(2009-08-14)
Unknown
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
()
Unknown
Lars Eggert Former IESG member
(was Discuss)
No Objection
No Objection
(2009-08-11)
Unknown
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.)
Lisa Dusseault Former IESG member
No Objection
No Objection
()
Unknown
Pasi Eronen Former IESG member
No Objection
No Objection
()
Unknown
Robert Sparks Former IESG member
No Objection
No Objection
()
Unknown
Ron Bonica Former IESG member
No Objection
No Objection
()
Unknown
Ross Callon Former IESG member
No Objection
No Objection
()
Unknown
Russ Housley Former IESG member
No Objection
No Objection
()
Unknown
Tim Polk Former IESG member
No Objection
No Objection
()
Unknown