[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [ipcdn] Comments on draft-ietf-ipcdn-pktc-eventmess-04.txt
That is probably a problem inherited from RFC 2669 where those objects
were derived
docsDevEvThrottleAdminStatus OBJECT-TYPE
SYNTAX INTEGER {
unconstrained(1),
maintainBelowThreshold(2),
stopAtThreshold(3),
inhibited(4)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Controls the transmission of traps and syslog messages
with respect to the trap pacing threshold.
....
I believe an event is throttle by the rate of events the system is
handling not the manifestation of them as outputs (I think this is
Randy's point)
Then, the dispatch flag (AND/OR local/syslog/snmp notif) is applied to
whatever target protocols are intended after the event rate throttling
In other words, throttling only regulates the rate of events to be
handled over dispatchers, the manifestation of "events on the wire"
depends on how targets are configured. As an example in SNMPv3 a
notification may match in the snmpNotifyTable n targets as traps and/or
informs:
Some figures:
If you wan to throttle one event per minute and you have a match of
2 trap targets and 1 Inform target (receiver off) with 3 retries
You can see up to 5 notifications on the wire per minute. ( not the 1
per minute you have though it will)
Unfortunately RFC 2669 had a monolithic perception of things and was
before SNMPv3 multiple targets were adopted. We didn't mentioned in
DOCSIS what happen with local log explicitly probably following the
rationale of the Throttle MIB objects, but I believe that is
inappropriate. There is no MUST requirements that says local-log events
MUST not be throttle.
, so that's probably the rationale of leave local-log throttle as
vendor dependent (?)
Or just normalize explicitly the requirement for local-log also be
throttled ( I can think on that option as my preference, others may have
a different perception)
Eduardo
-----Original Message-----
From: Randy Presuhn [mailto:randy_presuhn at mindspring.com]
Sent: Tuesday, October 18, 2005 8:36 PM
To: ipcdn at ietf.org
Subject: Re: [ipcdn] Comments on draft-ietf-ipcdn-pktc-eventmess-04.txt
Hi -
> From: "Sumanth Channabasappa" <sumanth at cablelabs.com>
> To: <ipcdn at ietf.org>
> Sent: Tuesday, October 18, 2005 2:58 PM
> Subject: RE: [ipcdn] Comments on
draft-ietf-ipcdn-pktc-eventmess-04.txt
...
> I haven't received any comments on the clarifications requested (dated
> 10/07, enclosed in this email). Can I assume acceptance (status quo)
on
> #1 and #2?
You must have missed my response from two months ago:
|From: ipcdn-bounces at ietf.org [mailto:ipcdn-bounces at ietf.org] On Behalf
Of
|Randy Presuhn
|Sent: Thursday, August 18, 2005 3:59 PM
|To: ipcdn at ietf.org
|Subject: Re: [ipcdn] Comments on draft-ietf-ipcdn-pktc-eventmess-04.txt
|
|Hi -
|
|> From: "Sumanth Channabasappa" <sumanth at cablelabs.com>
|> To: "Jean-Francois Mule" <jf.mule at cablelabs.com>; "Nakanishi
|> Greg-MGI8179" <gnakanishi at motorola.com>; <ipcdn at ietf.org>
|> Sent: Thursday, August 18, 2005 11:46 AM
|> Subject: RE: [ipcdn] Comments on
|> draft-ietf-ipcdn-pktc-eventmess-04.txt
|...
|> 8) pktcDevEvThrottleAdminStatus
|> - The description makes mention of throttling events using SNMP and
|> Syslog. What about the local log? Are events written to the local
|> log not subject to throttling?
|...
|
|I'd suggest that if we don't leave it up to the implementation, that it
would
|be best for throttling to affect all destinations equally. Swamped
logs are
|the same kind of problem, whether on the local system or a remote one.
|
|Randy
The code issuing a notification, which is where the DESCRIPTION clause
would lead implementors to put the throttling logic, would in a
reasonably
modular environment have no knowledge of whether it is going to a local
log, delivery over some protocol, or whatever.
Randy
_______________________________________________
IPCDN mailing list
IPCDN at ietf.org
https://www1.ietf.org/mailman/listinfo/ipcdn
_______________________________________________
IPCDN mailing list
IPCDN at ietf.org
https://www1.ietf.org/mailman/listinfo/ipcdn