draft-perrault-behave-natv2-mib-01 is almost ready.
I considered in the past and rejected in my own mind a per-subscriber
control on whether statistics are enabled or not for that subscriber. I
rejected it thinking that the impact on processor consumption would be
minimal, after the processor looked up the subscriber data in the first
place. I've changed my mind for two reasons: first, that I probably made
too many assumptions about implementation, and secondly, because the
impact on storage requirements for per-subscriber statistics would be
potentially huge if such a control were available.
I therefore propose the following:
1) In the description of the CGN application scenario (Section 3.4 of
draft-perrault-behave-natv2-mib-00), add the following sentence:
"An implementation MAY limit the number of subscribers for which
collection of statistics is enabled at any one time."
2) Add the following object to natv2SubscriberTable:
natv2SubscriberCountersEnabled OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"If true(1), accumulation of statistics in the counters for
this subscriber is enabled and the current values of the
counters can be presented to the manager. If false(1)
(default), accumulation of statistics in the counters for
this subscriber is disabled and the values presented to the
manager MUST be zero regardless of their actual value.
Whenever the value of this object changes,
natv2SubscriberDiscontinuityTime MUST be updated to the time
of change."
::= { natv2SubscriberEntry xx }
Comments?
Tom Taylor
_______________________________________________
OPSAWG mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/opsawg
