IETF Logo Mail Archive

RE: [ipcdn] Re: [psg.com #471] Expert review comments on draft-ie tf-ipcdn-doc sisevent-mib-03

"Jean-Francois Mule" <jf.mule@cablelabs.com> Tue, 03 August 2004 18:43 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01523 for <ipcdn-archive@ietf.org>; Tue, 3 Aug 2004 14:43:47 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bs4JR-0007Ps-SU for ipcdn-archive@ietf.org; Tue, 03 Aug 2004 14:47:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bs47A-00061M-Kr; Tue, 03 Aug 2004 14:34:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bs3um-0003lH-2L for ipcdn@megatron.ietf.org; Tue, 03 Aug 2004 14:21:32 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29135 for <ipcdn@ietf.org>; Tue, 3 Aug 2004 14:21:30 -0400 (EDT)
Received: from ondar.cablelabs.com ([192.160.73.61]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bs3xs-0006sb-JQ for ipcdn@ietf.org; Tue, 03 Aug 2004 14:24:46 -0400
Received: from srvxchg.cablelabs.com (srvxchg.cablelabs.com [10.5.0.20]) by ondar.cablelabs.com (8.12.10/8.12.10) with ESMTP id i73IKvqm013273; Tue, 3 Aug 2004 12:20:57 -0600 (MDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [ipcdn] Re: [psg.com #471] Expert review comments on draft-ie tf-ipcdn-doc sisevent-mib-03
Date: Tue, 03 Aug 2004 12:20:56 -0600
Message-ID: <CD6CE349CFD30D40BF5E13B3E0D84804063BFC@srvxchg.cablelabs.com>
Thread-Topic: [ipcdn] Re: [psg.com #471] Expert review comments on draft-ie tf-ipcdn-doc sisevent-mib-03
Thread-Index: AcR4/rFqX0Mb+ImdRTiSjts5/h9magAFQ7zwAByUfjA=
From: Jean-Francois Mule <jf.mule@cablelabs.com>
To: Fred Oko <Fred@stargus.com>, Nakanishi Greg-MGI8179 <gnakanishi@motorola.com>, ipcdn@ietf.org, DOCSIS OSS Majordomo List <docsis-oss@cablelabs.com>
X-Approved: ondar
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ipcdn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP over Cable Data Network <ipcdn.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>, <mailto:ipcdn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipcdn@ietf.org>
List-Help: <mailto:ipcdn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipcdn>, <mailto:ipcdn-request@ietf.org?subject=subscribe>
Sender: ipcdn-bounces@ietf.org
Errors-To: ipcdn-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: quoted-printable

Fred Oko wrote:
> For point1, we are talking at most 100 extra bytes, and on average
> closer to 50 -- fairly insignificant in the grand scheme of things
> unless we would send a ton of these notifications which should not be
> common. But admittedly a large % inefficiency when considering the
> entire PDU w/o event text is not much more than 100 bytes.

Thank you for your input. Do you or anybody have any actual counts of the number of such messages we typically get at the node/network level in 1 hour?

Based on the issues raised for simple NMS apps, trap exploders and alike using event level to properly route those msgs, I would really like to have a sense of whether this is a theoritical argument or whether we better be concerned about the verbose msgs.

Jean-François 

_______________________________________________
IPCDN mailing list
IPCDN@ietf.org
https://www1.ietf.org/mailman/listinfo/ipcdn

v2.46.0 | Report a Bug | By Email | System Status