Chris --
I have to point out that my original proposal at the IETF46 BOF was based
on a 3Com plan to provide secure managment access for products of a LAN
Systems division that no longer exists in the same form. As far as I
know, the plan no longer exists either. It's quite possible that IPSEC
solutions make more sense even in the short run for serious security
problems, and that the weak security solution I proposed is of little
interest to anyone building real products now. I agree with Chris C. that
a full-lifecycle solution is the real goal, and if the authenticated
syslog draft is blocking it I'm happy to withdraw its present incarnation.
John has made substantial progress in refining procedures for its use, but
most of this doesn't have much to do with syslog and could possibly apply
to the XML encoding Chris C proposed. I don't think the constraints of
the initial charter should block this good work.
Alex Brown <[EMAIL PROTECTED]> +1 617 504 8761 http://www.msg.com/~abrown
On Thu, 9 Nov 2000, Chris Lonvick wrote:
> At 10:44 AM 11/9/00 -0500, Chris Calabrese wrote:
>
>
> >3. It's not clear to me whether syslog-auth is needed
> >at all once Syslog-Reliable can do confidentiality and integrity.
> >More discussion is needed on this topic.
>
> The simple answer is: cuz it's in the Charter. ;-)
>
> Later,
> Chris
>
