Message Size

Status

[back]

-protocol specifies a message size limit of 1024 characters, but also assumes that message of this size can always be transmitted without fragemention. In the real world, datagram based transport mappings will probably not be able to assure that the message will not become fragmented. Must this issue be addressed in the context of -protocol? If so, what is the best solution?

Status: OPEN

Discussion Milestones

• Rainer Gerhards [2004-02-11] creates this issue based on a discussion with Anton Okmianski.
• Anton Okmianski [2004-02-11] recommends that the message size should be oriented on the UDP max size of 64kb and fragmentation left to the lower layers.
• Rainer Gerhards [2004-02-12] explains why he thinks fragmentation should be left in -protocol and the size be limited. Rainer also quotes a past thread relating to this issue here.
• Rainer Gerhards [2004-02-12] sums up what looked than as an interim concensus (nobody objected at *that* time;))
• Devin Kowatch [2004-02-20] says message size is a transport issue and -protocol should not describe it. Then, the transport mapping must ensure that any-size messages can be transmitted (multi-part messaging must be described in each transport mapping that needs it). Devin's post was long, the relevant text is around the middle of it. Please note that this post actually was related to a different initial issue - but it applies here, too.
• Anton Okmianski [2004-04-20] tells us that he needs a limit for -transport.
• Rainer Gerhards [2004-02-21] agrees on a high limit.

This page last updated: Tue Sep 25 13:32:29 2007.
For content issues, contact rgerhards-at-adiscon.com - for legal issues, please contact Adiscon who is the legal owner and publisher of this web site.
Visit our topic pages for practical information on syslog.
Raw Mail Archive: [threaded] [by date] [search]