Last Call Review of draft-perrault-behave-natv2-mib-03
review-perrault-behave-natv2-mib-03-opsdir-lc-jiang-2015-05-04-00
Request | Review of | draft-perrault-behave-natv2-mib |
---|---|---|
Requested revision | No specific revision (document currently at 05) | |
Type | Last Call Review | |
Team | Ops Directorate (opsdir) | |
Deadline | 2015-04-29 | |
Requested | 2015-04-05 | |
Authors | Simon Perreault , Tina Tsou (Ting ZOU) , Senthil Sivakumar , Tom Taylor | |
I-D last updated | 2015-05-04 | |
Completed reviews |
Genart Last Call review of -03
by Suresh Krishnan
(diff)
Secdir Last Call review of -03 by Takeshi Takahashi (diff) Opsdir Last Call review of -03 by Sheng Jiang (diff) |
|
Assignment | Reviewer | Sheng Jiang |
State | Completed | |
Request | Last Call review on draft-perrault-behave-natv2-mib by Ops Directorate Assigned | |
Reviewed revision | 03 (document currently at 05) | |
Result | Has issues | |
Completed | 2015-05-04 |
review-perrault-behave-natv2-mib-03-opsdir-lc-jiang-2015-05-04-00
Hi, I have reviewed this document as part of the Operational directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written with the intent of improving the operational aspects of the IETF drafts. Comments that are not addressed in last call may be included in AD reviews during the IESG review. Document editors and WG chairs should treat these comments just like any other last call comments. This Standards Track document defines a new version of NATV2-MIB for monitoring the NAT devices. It is intended to replace module NAT-MIB (RFC 4008). However, deprecating all objects in NAT-MIB (v1) is by a companion document draft-perrault-behave-deprecate-nat-mib-v1. This document is well written. While I am not a MIB expert, my review does not include the detailed design of MIB objects. This document does require another review by MIB expertise or MIB doctor. I have some minor comments as follow: 1) On page 31, as it defined natv2SubscriberThresholdPortMapEntriesHigh OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-write STATUS current DESCRIPTION "Notification threshold for total number of port mappings active for this subscriber. Whenever natv2SubscriberPortMapEntries is updated, if it equals or exceeds natv2SubscriberThresholdPortMapEntriesHigh, the notification natv2NotificationSubscriberPortMappingEntriesHigh is triggered, unless the notification is disabled by setting the threshold to 0. Reporting is subject to the minimum inter-notification interval given by natv2SubscriberNotificationInterval. If multiple notifications are triggered during one interval, the agent MUST report only the one containing the highest value of natv2SubscriberPortMapEntries and discard the others." DEFVAL { 0 } ::= { natv2SubscriberEntry 16 } It needs a sentence to describe that the threshold is default to set 0. 2) On page 55, it is missing the definition of the natv2PoolEntry 13. The continuous numbers jumped from 12 to 14. 3) On page 57, why not to define the natv2PoolRange objects into the natv2PoolTable? These objects should be part of the natv2Pool objects. Best regards, Sheng