[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
We crafted section 2.6 (Efficient Bulk Data
Transfer) to allow for the possibility of bulk
notifications, though the only example given is
of bulk retrieval. To my knowledge, there has
been less discussion and implementation
experience with bulk notifications than with bulk
retrieval. I would like to explore this more
before embedding specifics in the requirements.
And the details will probably fit better in the
upcoming draft on bulk transfer rather than in
the general requirements document.
From: email@example.com [mailto:firstname.lastname@example.org]On Behalf Of
Sent: Saturday, March 10, 2001 12:35 PM
To: Glenn Waters
Cc: EOS WG (E-mail)
Subject: Re: draft-ietf-eos-requirements-00
What about in section 2 adding a new sub-section something like:
Large Notification messages
Managed systems may have a large amount of data to be sent in several
varbinds as an SNMP Trap or Inform message. It would be good to provide
as much information as is helpful for fault isolation and repair in a
Trap or Inform, eliminating issues of time latency when using trap
directed polling for fault handling.
Requirements of this feature are:
o For an agent to be able to send a Trap or Inform that would exceed the
MTU size of a UDP-based PDU.
Glenn Waters wrote:
> Attached is the first cut of the requirements document for the
> Evolution of SNMP Working Group. This document will be the basis of
> discussion for the WG meeting coming up. Input and comments gladly
> accepted on the list and during the upcoming meeting.
> Cheers, /gww
Director, Software Development
Longitude Systems, Inc.
15000 Conference Center Drive
Chantilly, VA 20151