Hi, You should also keep in mind, for SNMP/syslog interaction, that SNMP/UDP messages should not be fragmented if possible, to handle the case when some packets are dropped.
To claim compliance with the standard, implementors must support messages up to and including 484 octets. They are encouraged to support larger sizes up to 1472 octets. The 1472 number is the largest SNMP message that will fit into an Ethernet packet without forcing fragmentation, if I remember correctly. dbh > -----Original Message----- > From: Rainer Gerhards [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 11, 2004 11:57 AM > To: [EMAIL PROTECTED]; Anton Okmianski > Subject: syslog message size and fragmentation > > Hi WG, > > I had an off-list discussion with Anton that lead to the > discovery of a > new issue in -protocol, that of message fragmentation. -protocol > specifies a message size limit of 1024 characters, but also > assumes that > message of this size can always be transmitted without (transport) > fragemention. In the real world, datagram based transport > mappings will > probably not be able to assure that the message will not become > fragmented. The MTU can at least be as low as 576 bytes. > > Must this issue be addressed in the context of -protocol? If > so, what is > the best solution? > > Thanks, > Rainer > > >
