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

["Eugene Nechamkin" <enechamkin at broadcom.com>]

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: 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





_______________________________________________
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