[Syslog] FW: syslog WG status for saag

["Chris Lonvick (clonvick)" <clonvick at cisco.com>]

Hi Folks,

An update for the group which David submitted to our ADs thFrom syslog-bounces at ietf.org  Fri Nov 21 12:51:59 2008
Return-Path: <syslog-bounces at ietf.org>
X-Original-To: syslog-archive at megatron.ietf.org
Delivered-To: ietfarch-syslog-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C10DD3A6982;
	Fri, 21 Nov 2008 12:51:59 -0800 (PST)
X-Original-To: syslog at core3.amsl.com
Delivered-To: syslog at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 110553A6982
	for <syslog at core3.amsl.com>; Fri, 21 Nov 2008 12:51:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id KbNl7BDXbGcc for <syslog at core3.amsl.com>;
	Fri, 21 Nov 2008 12:51:58 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72])
	by core3.amsl.com (Postfix) with ESMTP id 14CC93A67D1
	for <syslog at ietf.org>; Fri, 21 Nov 2008 12:51:58 -0800 (PST)
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-3.cisco.com with ESMTP; 21 Nov 2008 20:51:56 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id mALKpurX014056
	for <syslog at ietf.org>; Fri, 21 Nov 2008 12:51:56 -0800
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id mALKps7i026782
	for <syslog at ietf.org>; Fri, 21 Nov 2008 20:51:54 GMT
Received: from xmb-sjc-227.amer.cisco.com ([128.107.191.43]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
	Fri, 21 Nov 2008 12:51:56 -0800
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft Exchange V6.5
X-OriginalArrivalTime: 19 Nov 2008 19:58:50.0171 (UTC)
	FILETIME=[3D9D10B0:01C94A81]
X-IronPort-AV: E=Sophos;i="4.33,633,1220227200";    d="scan'208";a="64554534"
X-from-outside-Cisco: 76.96.62.24
Authentication-Results: sj-dkim-2; header.From=clonvick at cisco.com;
	dkim=neutral ( ssp=~; );
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AoUBAA//I0lMYD4YkWdsb2JhbACTVwEBAQEJCwoHEQO/TIJ5
X-Authority-Analysis: v=1.0 c=1 a?CevR5wZ_972ZnjHD0A:9
	a=_ZSevkjTG7tdcSJkFByofdijguEA:4 a=si9q_4b84H0A:10
	a=hPjdaMEvmhQA:10 aPe4U0PicR4A:10
Content-class: urn:content-classes:message
Date: Fri, 21 Nov 2008 12:51:44 -0800
Message-ID: <1BA601B02314084980FE9D0630FE9793053F8D36 at xmb-sjc-227.amer.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: syslog WG status for saag
Thread-Index: AclKgSu/5BKeKNAwRIeVGWM0pEiuFwBmcp1q
From: "Chris Lonvick (clonvick)" <clonvick at cisco.com>
To: <syslog at ietf.org>
Subject: [Syslog] FW: syslog WG status for saag
X-BeenThere: syslog at ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Security Issues in Network Event Logging <syslog.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/syslog>,
	<mailto:syslog-request at ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/syslog>
List-Post: <mailto:syslog at ietf.org>
List-Help: <mailto:syslog-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/syslog>,
	<mailto:syslog-request at ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="==============16560674=="
Sender: syslog-bounces at ietf.org
Errors-To: syslog-bounces at ietf.org

This is a multi-part message in MIME format.

Title: FW: syslog WG status for saag

Hi Folks,

An update for the group which David submitted to our ADs this week.

David and I stopped by the RFC Editor's desk yesterday.  We asked about our 4 documents and were assured that they are all going to be placed into AUTH48 this week.  Also, draft-ietf-ipcdn-pktc-eventmess-14.txt has dependencies upon our documents which have been cleared and so is also going forward.

This leaves us with our final piece of work which is syslog-sign.  Alex has been addressing the comments from the list and will put out a new draft (hopefully) next week.  Let's focus on this and get 'er done.  Since there are several changes, we don't want to point out each one, but will ask people to review the document and verify that your issue(s) has been resolved.  As always, please send in a note to the list after review to let us know that we have WG consensus on it.

Thanks,
Chris and David



 -----Original Message-----
From:   David Harrington [mailto:ietfdbh at comcast.net]
Sent:   Wednesday, November 19, 2008 11:58 AM Pacific Standard Time
To:     'Pasi Eronen'; 'Tim Polk'
Cc:     Chris Lonvick (clonvick)
Subject:        syslog WG status for saag

Hi,

The syslog WG did not meet at ietf73.

The protocol, udp, and tls doc tls documents are in the RFC-Editor queue, and
auth48 should start this week. The syslog-sign document is in AD
review, and a new revision should be published within a week. We
expect one more revision will be needed, mostly for editorial fixes.

The chairs recommend that once this work completes, the syslog WG be
closed.

There is one charter item not completed - a MIB module. The WG
believes syslog.conf is widely used and appropriate for configuration.
Existing applications already provide log analysis. Due to OS
differences in syslog approaches, a single standard MIB module is
problematic for monitoring syslog statistics and state. Other
syslog-related data modeling is being done in the OPSAWG WG. MIB
modules for monitoring syslog state be developed in the OPSAWG WG,
where operators can help define what information and format would be
most useful to them.

David Harrington
dbharrington at comcast.net
ietfdbh at comcast.net
dharrington at huawei.com

_______________________________________________
Syslog mailing list
Syslog at ietf.org
https://www.ietf.org/mailman/listinfo/syslog