To: 'Chris Lonvick'
Cc: [EMAIL PROTECTED]
Subject: RE: -international: trailer
Chris:
Sounds reasonable. Let's get the other stuff completed first.
Anton.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chris Lonvick
Sent: Tuesday, February 10
Let's not try to create a protocol just to standardzie something not
directly related to the internet. If you want to develop a parser and
have the parser accepted as a standard why don't you just develop it
as open source, say, on sourceforge?
Just for the records: I plan to include support
.
Thanks,
Chris
Anton.
-Original Message-
From: Rainer Gerhards [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 10, 2004 12:15 PM
To: Andrew Ross; Harrington, David; Anton Okmianski;
[EMAIL PROTECTED]
Subject: RE: -international: trailer
Hi All,
I am a bit sad
]
Subject: RE: -international: trailer
Hi All,
I am a bit sad that I use Andrew's message to say this...
but Andrew
has just made an important point that enlightens me on David's
thought that those CLRs (crappy little rules [I like this term])
really cause trouble. So
it is today.
Rainer
-Original Message-
From: Andrew Ross [mailto:[EMAIL PROTECTED]
Sent: Sunday, February 08, 2004 12:52 AM
To: Rainer Gerhards; 'Harrington, David'; 'Anton Okmianski';
[EMAIL PROTECTED]
Subject: RE: -international: trailer
It is not just the 0x00 that we have
Gerhards [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 10, 2004 12:15 PM
To: Andrew Ross; Harrington, David; Anton Okmianski;
[EMAIL PROTECTED]
Subject: RE: -international: trailer
Hi All,
I am a bit sad that I use Andrew's message to say this... but
Andrew has
just made an important point
David:
I am really struggling with that restriction not to
standardize syslog
storage in IETF. It diminishes the value of the syslog protocol as
people can't write a standard syslog parser.
I'm not sure I understand why you feel this. Assuming you are
parsing what was sent on the wire,
Okmianski [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 10, 2004 5:04 PM
To: 'Harrington, David'; 'Rainer Gerhards'; 'Andrew Ross';
'[EMAIL PROTECTED]'
Subject: RE: -international: trailer
David:
I am really struggling with that restriction not to
standardize syslog
storage in IETF
David,
thanks for your wake-up call...
I believe we should move to UTF-8 to allow operators who
UTF-8 is actually a MUST in syslog-protocol.
I have to admit that I did not fully understand UNICODE until now... I
always read RFC 2279 (UTF-8 encoding). It specifies (page 2):
- Character values
-- Forwarded message --
Date: Fri, 6 Feb 2004 12:02:14 -0500
From: Anton Okmianski [EMAIL PROTECTED]
To: 'Rainer Gerhards' [EMAIL PROTECTED],
'Harrington, David' [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: RE: -international: trailer
Rainer:
I am still tempted to allow
PROTECTED]
Subject: RE: -international: trailer
I have a concern about making C-compatibility a requirement of
-protocol. I understand the concern about the amount of work
implementors may need to do, and it spotential impact on adoption.
However, I think this is a red herring.
I know that we
:24 AM
To: Harrington, David; Anton Okmianski; [EMAIL PROTECTED]
Subject: RE: -international: trailer
David,
thanks for your wake-up call...
I believe we should move to UTF-8 to allow operators who
UTF-8 is actually a MUST in syslog-protocol.
I have to admit that I did not fully
Anton:
I am still tempted to allow only octets in the range of 1..255. ;)
I think at least technically this restriction is possible because 0x00
never appears as part of any characters encoded as multi-octet
characters in UTF-8. See table here:
: Rainer Gerhards [mailto:[EMAIL PROTECTED]
Sent: Friday, February 06, 2004 11:51 AM
To: Anton Okmianski; Harrington, David; [EMAIL PROTECTED]
Subject: RE: -international: trailer
Anton:
I agree with your conclusion that we need to support all
Unicode/UTF. I
also think that doing any kind
the implementors solve their own
implementation problems.
dbh
-Original Message-
From: Rainer Gerhards [mailto:[EMAIL PROTECTED]
Sent: Friday, February 06, 2004 12:14 PM
To: Anton Okmianski; Harrington, David; [EMAIL PROTECTED]
Subject: RE: -international: trailer
Anton:
I am still tempted
: -international: trailer
Hi,
I see our messages crossed in transit. You've already
researched whether 0x00 occurs in UTF-8.
I have a concern about making C-compatibility a requirement
of -protocol. I understand the concern about the amount of
work implementors may need to do, and it spotential impact
In short: I have a strong preference that we should insist on
non-control-chars only. Escaping MUST be done by the (original) sender.
Agreed
I am about to mandate that they MUST implement a way to store raw
message data - for signed messages. Again, if we don't mandate this, we
have a
Rainer:
Oct 11 22:14:15 myhost2 su: Message with line break\nbefore end
ah, ok, so solaris does this processing, obviously when writing
to the file. That would mean that we would need to apply escaping
to the free form part of the text, too. Not a bad idea...
Especially as I think the \x
18 matches
Mail list logo
