Chris:
I think having SD-ID with [enc="utf-8" lang="English"] may be a good
approach. If different language use utf-8 encoding, then "lang=" can
distinguish it.
Also want to clarify that you suggest that if the message is in ASCII,
it will not required SD-ID, but for all other encodings, SD-ID w
Hello,
I just wanted to let you all know that I have submitted a new draft of
syslog sign, as the old one was about to expire. The new draft should
appear shortly if it hasn't already; here is a summary of the changes
and updates that were made.
The changes were along the lines of what was pre
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 : Signed syslog Messages
Author(s) : J. Kelsey, et al.
Filename
Darren,
I am not long enough with the IETF to know how much trouble it is to
recharter - but I think whatever it is, it is acceptable. You very
correctly said that we need to do baby steps. And as a matter of past
discussions, it seems to be necessary to explicitely exclude some things
to get the
Chris,
I think that is a good compromise. It would also enable us to convey the
enconding information if we have it (anyhow, in that case it would be
more smarter to convert to UTF-8, but that's not yet important).
Rainer
> -Original Message-
> From: Chris Lonvick [mailto:[EMAIL PROTECTE
Are we happy to recharter when these are done to cover TCP ?
Darren
___
Syslog mailing list
Syslog@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/syslog
> Hi Rainer,
>
> Why don't we look at it from the other direction? We could state that any
> encoding is acceptable - for ease-of-use/migration with existing syslog
> implementations. It is RECOMMENDED that UTF-8 be used. When it is
> used, an SD-ID element will be REQUIRED. e.g. - [enc="ut
Hi Rainer,
Why don't we look at it from the other direction? We could state that any
encoding is acceptable - for ease-of-use/migration with existing syslog
implementations. It is RECOMMENDED that UTF-8 be used. When it is
used, an SD-ID element will be REQUIRED. e.g. - [enc="utf-8" lang="
Hi Rainer,
I've already sent my comments to Sam including the v2 of the charter. I'm
still waiting on feedback from him. The proposed charter below looks
good.
Please do send your comments to him. As he said, it's good to send them
to the WG list as well.
Thanks,
Chris
On Tue, 29 Nov 2
Chris, WG:
as you are probably aware, Sam's deadline for comments about the future
of this WG is quickly approaching (it is December, 1st). I plan to
formally update my comment. To do so, I would like to know if we have
reached consensus on the charter.
I have taken the liberty to merge some cha
Chris & WG,
> > #5 Character encoding in MSG: due to my proof-of-concept
> > implementation, I have raised the (ugly) question if we need
> > to allow encodings other than UTF-8. Please note that this
> > question arises from needs introduced by e.g. POSIX. So we
> > can't easily argue the
Darren & WG:
I have used this morning to compile a short list of currently existing
and deployed syslogds. As I suggested, I have sent several messages to
them. I suggest you have a look at the results at
http://www.syslog.cc/ietf/existing-syslog.html
I do not see much in that result backing
12 matches
Mail list logo
