to:[EMAIL PROTECTED] On Behalf Of Glenn
> Mansfield Keeni
> Sent: Thursday, November 24, 2005 5:33 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [Syslog] Revised proposed charter
>
> Chris,
> You seem to have dropped the last deliverable which is
> in good shape
>
[EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Anton
> Okmianski (aokmians)
> Sent: Wednesday, November 23, 2005 12:29 PM
> To: Chris Lonvick (clonvick); [EMAIL PROTECTED]
> Subject: RE: [Syslog] Revised proposed charter
>
> Chris:
>
> This is fine, b
I support this clarification.
Anton.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Tom Petch
> Sent: Saturday, November 26, 2005 4:23 AM
> To: Chris Lonvick (clonvick); [EMAIL PROTECTED]
> Subject: Re: [Syslog] Revise
> I see it the other way round. If the charter can be specific, it should
> be, to keep the subsequent discussion focussed on the more contentious
> areas. Based on the > post-Vancouver discussion, I see no alternative
> to including and if that is the case, then we should nail that
> down now.
- Original Message -
From: "Darren Reed" <[EMAIL PROTECTED]>
To: "Tom Petch" <[EMAIL PROTECTED]>
Cc: "Chris Lonvick" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Saturday, November 26, 2005 12:39 PM
Subject: Re: [Syslog] Revised
Why?
Because the community implementing syslog protocol things seems to be
ignoring what the group has been doing.
This may be because they're unaware of the work or because it is being
regarded as a "WTF?!" and doing their own thing.
Most people seem to be ignoring 3195. Lets learn from that
[ Charset ISO-8859-1 unsupported, converting... ]
> Based on the discussions of the past few days, the one detail that I would add
> to the charter is about and backward compatability, something along the
> lines of
>
> While compatability with existing syslog systems is desirable, research shows
nvick" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, November 23, 2005 6:05 PM
Subject: [Syslog] Revised proposed charter
> Hi All,
>
> v2 of proposed charter ===
>
> Syslog is a de-facto standard for logging system events. However, the
> protoco
- Original Message -
From: "Darren Reed" <[EMAIL PROTECTED]>
To: "Tom Petch" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, November 25, 2005 11:35 PM
Subject: Re: [Syslog] Revised proposed charter
> [ Charset ISO-8859-1 unsupported
Chris,
Let me have a go at rewriting the charter...
> The goal of this working group is to address the security and integrity
> problems, and to standardize the syslog protocol, transport, and a select
> set of mechanisms in a manner that considers the ease of migration between
> and the co-ex
[ Charset ISO-8859-1 unsupported, converting... ]
> [tp] Strange, I was thiinking quite the opposite, that we had a fragile
> consensus which disappeared in
> Vancouver and has not been refound. Looking back at the messages posted
> in the past few days, about what should be in the header in what
Tom Petch
- Original Message -
From: "Alexander Clemm (alex)" <[EMAIL PROTECTED]>
To: "Anton Okmianski (aokmians)" <[EMAIL PROTECTED]>; "Chris Lonvick
(clonvick)" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, November 2
t: Thursday, November 24, 2005 5:42 PM
Subject: RE: [Syslog] Revised proposed charter
>
> OK - sorry 'bout that.
>
> Glenn - please update it and get it into the ID repository.
>
> All - who will commit to reviewing this document? I will need someone to
> commit to thi
t one. I agree with Glenn that
> this should be
> > in the charter.
> >
> > Rainer
> >
> >> -Original Message-
> >> From: [EMAIL PROTECTED]
> >> [mailto:[EMAIL PROTECTED] On Behalf Of Glenn
> >> Mansfield Keeni
> >>
ps, I have overlooked that one. I agree with Glenn that this should be
in the charter.
Rainer
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Glenn
Mansfield Keeni
Sent: Thursday, November 24, 2005 11:33 AM
To: [EMAIL PROTECTED]
Subject: Re: [Syslog] Re
: [EMAIL PROTECTED]
> Subject: Re: [Syslog] Revised proposed charter
>
> Chris,
> You seem to have dropped the last deliverable which is
> in good shape
>
> > - A MIB definition for syslog will be produced.
>
> I would strongly recommend that we include it. It i
Chris,
You seem to have dropped the last deliverable which is in good shape
> - A MIB definition for syslog will be produced.
I would strongly recommend that we include it. It is an important aspect
of the protocol. Some effort has gone into it. And it is the least
controversial [there a
f Of Anton Okmianski
(aokmians)
Sent: Wednesday, November 23, 2005 9:29 AM
To: Chris Lonvick (clonvick); [EMAIL PROTECTED]
Subject: RE: [Syslog] Revised proposed charter
Chris:
This is fine, but does not include all the other specific details we
agreed on and as such is not different from what we had be
> Also, sorry if I missed some earlier discussions on signing
> messages. Proposed charter mentions source authentication.
> For TCP mappings (such as BEEP), TLS already provides
> authentication and encryption. SSH transport would provide
> similar facilities. Is there an overlap here? Is mes
age-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Chris
> Lonvick (clonvick)
> Sent: Wednesday, November 23, 2005 12:05 PM
> To: [EMAIL PROTECTED]
> Subject: [Syslog] Revised proposed charter
>
> Hi All,
>
> v2 of proposed charter ===
>
I fully agreee.
Rainer
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Chris Lonvick
> Sent: Wednesday, November 23, 2005 6:05 PM
> To: [EMAIL PROTECTED]
> Subject: [Syslog] Revised proposed charter
>
> Hi All,
>
&g
Hi All,
v2 of proposed charter ===
Syslog is a de-facto standard for logging system events. However, the
protocol component of this event logging system has not been formally
documented. While the protocol has been very useful and scalable, it has
some known security problems which wer
22 matches
Mail list logo
