Team: This draft is essentially what you saw when I sent a preview. It incorporates some minor editorial updates and has one major change which has been suggested to me by several people.
It sets the minimum required message support at 507 bytes (for IPv4) instead of 65K. This means that implementations that don't wish to handle larger message sizes, don't have to implement the fragmentation at all. I think this solves the concerns many people voiced. Since fragmentation makes UDP even less reliable than it already is, it is probably not a good idea to force people to implement it if they decide that it is not a good model for their customers. This way, we have baseline interoperability, and for scenarios where large message support is needed, the administrators can use appropriate implementations which support it. The maximum size is still 16MB. I think it is important that we support (not necessarily require) ability to transmitting syslog messages of any size over any transport. I am not married to the 16MB number though if people want it lowered. Please provide comments on the draft. Thanks, Anton. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > [EMAIL PROTECTED] > Sent: Thursday, May 13, 2004 1:03 PM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: I-D ACTION:draft-ietf-syslog-transport-udp-01.txt > > > A New Internet-Draft is available from the on-line > Internet-Drafts directories. This draft is a work item of the > Security Issues in Network Event Logging Working Group of the IETF. > > Title : Transmission of syslog messages over UDP > Author(s) : A. Okmianski > Filename : draft-ietf-syslog-transport-udp-01.txt > Pages : 20 > Date : 2004-5-12 > > This document describes the transport for syslog messages over UDP/ > IPv4 or UDP/IPv6. While several transport mappings are envisioned > for the syslog protocol, syslog protocol implementors are > required to > support the transport mapping described in this document. This > transport specification overcomes limitations of UDP/IP > datagram size > by introducing support for fragmentation of large messages. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-syslog-transpor t-udp-01.txt To remove yourself from the I-D Announcement list, send a message to [EMAIL PROTECTED] with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-syslog-transport-udp-01.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: [EMAIL PROTECTED] In the body type: "FILE /internet-drafts/draft-ietf-syslog-transport-udp-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft.
