draft-ietf-syslog-protocol-03

[back to syslog-protocol]

This draft has been submitted on 2004-02-16 to the IETF Draft editor, but has not yet been officially published. In theory, changes can occur once it is published. If in doubt, consult the official IETF registry (this comment will be removed as soon as I become aware of  official publishing).

Additional Information

• This draft was a rather quick, but complete edit to meet the timeline for the Seoul meeting draft submission cutoff date. For this reason, not everything was fully discussed on the WG mailing list. It can be changed at any time ;)

Changelog

I might have forgotten to list a minor change, but these are the most important ones:

• general text-cleanup. Abstract and Intro modified. I noticed some old text survived in the begininng of section 4, removed that, some typos caught, probably twice as much added ;)
• section 3, transport mappings clarified, section 3.1, UDP transport required [see issue 10]
• maximum syslog message size is now 1280 bytes (I assume this *is* the minimum IPv6 MTU, had no time to check) [see issue 11]  ... oops, sorry folks, accidently I removed the max size altogether ... shame on me for rushing. 1280 will be back in in -protocol-04 ;)
• section 4.2 - MSG - now specifies UTF-8 including including all control characters [see issue 9]
• section 4, TRAILER has been removed [see issue 6]
• section 6, multi-part messages heavily changed. Name change from fragmentation to "multi-part messaging", more definitions, hopefully clearer description (some of the term names are *really* lenghty - advise on better terms is taken thankfully).
• section 7, definition of structured data element IDs (and semantics) added
• section 7.1 - time - tries to solve issue 12
• section 7.2 - orgin - tries to provide a way to preserve originator IP addresses inside the message. "origin" is also a key element when relay RFC 3164 operations will be described (I didn't manage to get this into the -03 version).
• section 8, "relay operations" added, but so far it is more or less empty.
• section 9, "security considerations" cleaned up.
• section 9.1 - diagnostic logging - added as a security consideration. Comments on this are highly appreciated. This was not previously discussed on the WG mailing list

Downloads

• Plain Text
• NROFF source
• HTML

This page last updated: Tue Oct 11 16:35:25 2011.
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]