RE: Comments on draft-ietf-ipcdn-pktc-eventmess-04.txt

This is especially important on the MTA side as the device usually has more
limited resources for local events storage. Having local events throttled on
the MTA will also allow the MSOs to fine-tune the logging system as a whole
and to reduce the risk of the events being lost.

Eugene.

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of
Randy Presuhn
Sent: Thursday, August 18, 2005 3:59 PM
To: [email protected]
Subject: Re: [ipcdn] Comments on draft-ietf-ipcdn-pktc-eventmess-04.txt

Hi -

> From: "Sumanth Channabasappa" <[email protected]>
> To: "Jean-Francois Mule" <[email protected]>; "Nakanishi 
> Greg-MGI8179" <[email protected]>; <[email protected]>
> 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





_______________________________________________
IPCDN mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/ipcdn