Not sure which bits of MIME you have in mind but I like the term Content-Transfer-Encoding, I like the list of such encodings, I like the list of charsets and I like the way that the user/application gets to choose a suitable delimiter for the various parts rather than have the protocol designer impose an unsuitable one. What don't I like? the term charset, but I think that is too well embedded to avoid.
Oh and I love the way that the protocol proper is ASCII encoded, so easy to read and display unlike markup languages, binary encodings etc etc And I think its guidance about what to do when fields are absent or corrupt is good, leading to a good chance of interoperability. Tom Petch ----- Original Message ----- From: "Rainer Gerhards" <[EMAIL PROTECTED]> To: "Tom Petch" <[EMAIL PROTECTED]>; "Chris Lonvick" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, December 01, 2005 2:25 PM Subject: RE: [Syslog] #5 - character encoding (was: Consensus?) Well... let me rephrase it slightly ;) After -protocol is finished, we could actually do something like syslog-mime, which could then describe this as an optional feature. Might even not be as crazy as it sounds - at least if I look what has been suggested so far. syslog-mime might be a solution for some of these needs.... Rainer > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Rainer Gerhards > Sent: Thursday, December 01, 2005 12:45 PM > To: Tom Petch; Chris Lonvick > Cc: [EMAIL PROTECTED] > Subject: RE: [Syslog] #5 - character encoding (was: Consensus?) > > Tom, WG > > I am *not* kidding. If we go for an encoding header, why not > use MIME? > > Rainer > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of Tom Petch > > Sent: Thursday, December 01, 2005 10:05 AM > > To: Chris Lonvick > > Cc: [EMAIL PROTECTED] > > Subject: Re: [Syslog] #5 - character encoding (was: Consensus?) > > > > ----- Original Message ----- > > From: "Chris Lonvick" <[EMAIL PROTECTED]> > > To: "Rainer Gerhards" <[EMAIL PROTECTED]> > > Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > > Sent: Wednesday, November 30, 2005 2:18 PM > > Subject: RE: [Syslog] #5 - character encoding (was: Consensus?) > > > > > Hi Rainer, > > > > > > Let's use this email as an example. :) There is no > > indication that I'm > > > using US-ASCII encoding or that I'm writing in English. > > > > Actually, Chris, there is; when I receive this e-mail, the > > header contains > > > > Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed > > > > so implicitly or explicitly you are telling me it is US-ASCII > > > > By contrast, e-mails from Rainer, contain > > > > Content-Type: text/plain; charset="iso-8859-1" > > Content-Transfer-Encoding: quoted-printable > > > > This reply is in charset="iso-8859-1" but by default, my > > Windows MUA replies in > > the charset the message came in, so that > > replying to you I could not then spell Müller properly which > > I could do to > > Rainer. On the > > other hand, when replying to you, Windows inserts > to denote > > the incoming text > > which it suppresses when I reply to Rainer. And some e-mails > > I receive are not > > in US-ASCII but lack the charset= in which case the display > > on screen is > > somewhat or totally corrupted. > > > > So MIME does an ok job but can be fooled by the rest of the > > system; if we can do > > that well with syslog, we should be proud of ourselves. > > > > Tom Petch > > > > > > _______________________________________________ > > Syslog mailing list > > Syslog@lists.ietf.org > > https://www1.ietf.org/mailman/listinfo/syslog > > > > _______________________________________________ > Syslog mailing list > Syslog@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/syslog > _______________________________________________ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog
