IP Forwarding Table MIB
RFC 4292
Yes
No Objection
Recuse
Note: This ballot was opened for revision 07 and is now closed.
(Bert Wijnen; former steering group member) (was No Objection, Discuss) Yes
(Thomas Narten; former steering group member) Yes
(Alex Zinin; former steering group member) (was Discuss) No Objection
(Allison Mankin; former steering group member) No Objection
(Harald Alvestrand; former steering group member) No Objection
(Jon Peterson; former steering group member) No Objection
(Ned Freed; former steering group member) No Objection
Nits: No IPR boilerplate Idle musing: This document, like so many other MIB documents, has a largely useless table of contents: There's a few entries for pages 1-7 and 30-33 but nothing for the majority of the specification, which of course is the MIB itself. I wonder... Wouldn't it be useful to have a way of adding TOC entries for the various sections within the MIB itself? Would it be worth a note to see if XML2RFC could be extended this way? Mind you, I only find TOCs useful when looking at printed versions of the document, and the intersection of MIBs and scanning printed specifications might be so small as not to be worth it. Comments?
(Russ Housley; former steering group member) No Objection
(Steven Bellovin; former steering group member) No Objection
Network map data is useful for far more than denial of service. I'd just delete that phrase.
(Ted Hardie; former steering group member) No Objection
I think the Editor's contact info in ipForward MODULE-IDENTITY and the Author's addresses section are out of date (right, Margaret?)
(Bill Fenner; former steering group member) Recuse
(Margaret Cullen; former steering group member) Recuse