From MAILER-DAEMON Mon Nov 28 10:58:03 2005 Date: 28 Nov 2005 10:58:03 -0600 From: Mail System Internal Data Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA Message-ID: <1133197083@linux.local> X-IMAP: 1133196728 0000000008 Status: RO This text is part of the internal format of your mail folder, and is not a real message. It is created automatically by the mail system software. If deleted, important folder data will be lost, and it will be re-created with the data reset to initial values. From syslog-sec-bounces@willers.employees.org Mon Aug 22 18:52:13 2005 Return-Path: X-Original-To: lonvick@localhost Delivered-To: lonvick@localhost.linux.local Received: from localhost (localhost [127.0.0.1]) by linux.local (Postfix) with ESMTP id 4B76219046 for ; Mon, 22 Aug 2005 18:52:13 -0500 (CDT) Received: from email.cisco.com [171.70.151.132] by localhost with IMAP (fetchmail-6.2.3) for lonvick@localhost (single-drop); Mon, 22 Aug 2005 18:52:13 -0500 (CDT) Received: from xbh-sjc-231.amer.cisco.com ([128.107.191.100]) by xmb-sjc-227.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Sun, 7 Aug 2005 15:03:00 -0700 Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Sun, 7 Aug 2005 15:03:02 -0700 Received: from rtp-core-1.cisco.com (64.102.124.12) by rtp-iport-2.cisco.com with ESMTP; 07 Aug 2005 18:03:03 -0400 X-IronPort-AV: i="3.95,173,1120449600"; d="scan'208"; a="65562508:sNHT59535430" Received: from sj-inbound-d.cisco.com (sj-inbound-d.cisco.com [128.107.243.13]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j77M2dTA014429; Sun, 7 Aug 2005 18:02:46 -0400 (EDT) Received: from willers.employees.org (192.83.249.36) by sj-inbound-d.cisco.com with ESMTP; 07 Aug 2005 15:02:44 -0700 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-IronPort-AV: i="3.95,173,1120460400"; d="scan'208"; a="99808243:sNHT17096612" Received: from willers.employees.org (localhost.employees.org [IPv6:::1]) by willers.employees.org (Postfix) with ESMTP id B95A25C764; Sun, 7 Aug 2005 15:02:39 -0700 (PDT) X-Original-To: syslog-sec@employees.org Delivered-To: syslog-sec@employees.org Received: from sj-iport-3.cisco.com (sj-iport-3-in.cisco.com [171.71.176.72]) by willers.employees.org (Postfix) with ESMTP id 181225C72A for ; Sun, 7 Aug 2005 14:02:39 -0700 (PDT) Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-3.cisco.com with ESMTP; 07 Aug 2005 14:02:38 -0700 X-IronPort-AV: i="3.95,173,1120460400"; d="scan'208"; a="329946239:sNHT30829124" Received: from sjc-cde-003.cisco.com (sjc-cde-003.cisco.com [171.71.162.81]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j77L2a0K028482; Sun, 7 Aug 2005 14:02:37 -0700 (PDT) Date: Sun, 7 Aug 2005 14:02:36 -0700 (PDT) From: Chris Lonvick To: housley@vigilsec.com, hartmans-ietf@mit.edu Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Sun, 07 Aug 2005 14:08:24 -0700 Cc: syslog-sec@employees.org Subject: [Syslog-sec] Request for publication of draft-ietf-syslog-protocol-14.txt X-BeenThere: syslog-sec@www.employees.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: "Mailing list for the syslog Working Group in the IETF." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: syslog-sec-bounces@willers.employees.org Errors-To: syslog-sec-bounces@willers.employees.org X-PMX-Version: 4.7.1.128075 X-from-outside-Cisco: 128.107.243.13 X-OriginalArrivalTime: 07 Aug 2005 22:03:02.0139 (UTC) FILETIME=[C7A124B0:01C59B9B] Status: RO X-Status: X-Keywords: X-UID: 2 Security ADs, Having passed a WG Last Call, draft-ietf-syslog-protocol-14.txt is ready for AD review. [Area] SECURITY [WG] syslog [I-D] draft-ietf-syslog-protocol-14.txt [Qver] draft-ietf-proto-wgchair-doc-shepherding-05.txt [Shep] Chris Lonvick The WG last call turned up no additional comments or discussion. 1.a) Have the chairs personally reviewed this version of the Internet Draft (ID), and in particular, do they believe this ID is ready to forward to the IESG for publication? Yes. 1.b) Has the document had adequate review from both key WG members and key non-WG members? Do you have any concerns about the depth or breadth of the reviews that have been performed? Adequate review has occurred from WG members, and it has been reviewed by others. I am satisfied about the level of review. 1.c) Do you have concerns that the document needs more review from a particular (broader) perspective (e.g., security, operational complexity, someone familiar with AAA, etc.)? No. 1.d) Do you have any specific concerns/issues with this document that you believe the ADs and/or IESG should be aware of? For example, perhaps you are uncomfortable with certain parts of the document, or have concerns whether there really is a need for it. In any event, if your issues have been discussed in the WG and the WG has indicated it that it still wishes to advance the document, detail those concerns in the write-up. No. 1.e) How solid is the WG consensus behind this document? Does it represent the strong concurrence of a few individuals, with others being silent, or does the WG as a whole understand and agree with it? There is strong consensus to publish this document. 1.f) Has anyone threatened an appeal or otherwise indicated extreme discontent? If so, please summarise the areas of conflict in separate email to the Responsible Area Director. No. 1.g) Have the chairs verified that the document adheres to all of the ID nits? (see http://www.ietf.org/ID-Checklist.html). Section 9.1 and 9.2 state that the IANA must "maintain" a registry. This needs to be changed to state that the IANA is requested to "create" a registry for the described values. The author can make this minor change when working with the RFC Editor. 1.h) Is the document split into normative and informative references? Are there normative references to IDs, where the IDs are not also ready for advancement or are otherwise in an unclear state? (note here that the RFC editor will not publish an RFC with normative references to IDs, it will delay publication until all such IDs are also ready for publication as RFCs.) The references are split into normative and informational references. The document is dependent upon draft-ietf-syslog-transport-udp-05.txt but that is being submitted along with this document. 1.ijk) Write-up section: * Technical Summary This document describes the syslog protocol, which is used to convey event notification messages. This protocol utilizes a layered architecture, which allows the use of any number of transport protocols for transmission of syslog messages. It also provides a message format that allows vendor-specific extensions to be provided in a structured way. * Working Group Summary The consensus of the working group was to publish this as a standards-track document. * Protocol Quality It is possible that there are implementations of this document in various stages of completion at this time. Some equipment vendors have indicated interest in supporting this document, and some non-commercial implementations are also expected. === _______________________________________________ Syslog-sec mailing list Syslog-sec@www.employees.org http://www.employees.org/mailman/listinfo/syslog-sec From syslog-sec-bounces@willers.employees.org Mon Aug 22 18:52:13 2005 Return-Path: X-Original-To: lonvick@localhost Delivered-To: lonvick@localhost.linux.local Received: from localhost (localhost [127.0.0.1]) by linux.local (Postfix) with ESMTP id B643E19046 for ; Mon, 22 Aug 2005 18:52:13 -0500 (CDT) Received: from email.cisco.com [171.70.151.132] by localhost with IMAP (fetchmail-6.2.3) for lonvick@localhost (single-drop); Mon, 22 Aug 2005 18:52:13 -0500 (CDT) Received: from xbh-sjc-211.amer.cisco.com ([171.70.151.144]) by xmb-sjc-227.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Sun, 7 Aug 2005 15:04:47 -0700 Received: from sj-iport-2.cisco.com ([171.71.176.71]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Sun, 7 Aug 2005 15:04:33 -0700 Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-2.cisco.com with ESMTP; 07 Aug 2005 15:04:47 -0700 Received: from sj-inbound-a.cisco.com (sj-inbound-a.cisco.com [128.107.234.204]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j77M4HQX020607; Sun, 7 Aug 2005 15:04:37 -0700 (PDT) Received: from willers.employees.org (192.83.249.36) by sj-inbound-a.cisco.com with ESMTP; 07 Aug 2005 15:04:42 -0700 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-IronPort-AV: i="3.95,173,1120460400"; d="scan'208"; a="157692433:sNHT17211416" Received: from willers.employees.org (localhost.employees.org [IPv6:::1]) by willers.employees.org (Postfix) with ESMTP id C33565C79C; Sun, 7 Aug 2005 15:04:40 -0700 (PDT) X-Original-To: syslog-sec@employees.org Delivered-To: syslog-sec@employees.org Received: from sj-iport-3.cisco.com (sj-iport-3-in.cisco.com [171.71.176.72]) by willers.employees.org (Postfix) with ESMTP id 196275C75A for ; Sun, 7 Aug 2005 14:02:52 -0700 (PDT) Received: from sj-core-5.cisco.com (171.71.177.238) by sj-iport-3.cisco.com with ESMTP; 07 Aug 2005 14:02:52 -0700 X-IronPort-AV: i="3.95,173,1120460400"; d="scan'208"; a="329946260:sNHT30044796" Received: from sjc-cde-003.cisco.com (sjc-cde-003.cisco.com [171.71.162.81]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j77L2nop016474; Sun, 7 Aug 2005 14:02:50 -0700 (PDT) Date: Sun, 7 Aug 2005 14:02:49 -0700 (PDT) From: Chris Lonvick To: housley@vigilsec.com, hartmans-ietf@mit.edu Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Sun, 07 Aug 2005 14:08:24 -0700 Cc: syslog-sec@employees.org Subject: [Syslog-sec] Request for publication of draft-ietf-syslog-transport-udp-05.txt X-BeenThere: syslog-sec@www.employees.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: "Mailing list for the syslog Working Group in the IETF." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: syslog-sec-bounces@willers.employees.org Errors-To: syslog-sec-bounces@willers.employees.org X-PMX-Version: 4.7.1.128075 X-from-outside-Cisco: 128.107.234.204 X-OriginalArrivalTime: 07 Aug 2005 22:04:33.0273 (UTC) FILETIME=[FDF31690:01C59B9B] Status: RO X-Status: X-Keywords: X-UID: 3 Security ADs, Having passed a WG Last Call, draft-ietf-syslog-transport-udp-05.txt is ready for AD review. [Area] SECURITY [WG] syslog [I-D] draft-ietf-syslog-transport-udp-05.txt [Qver] draft-ietf-proto-wgchair-doc-shepherding-05.txt [Shep] Chris Lonvick The WG last call turned up no additional comments or discussion. 1.a) Have the chairs personally reviewed this version of the Internet Draft (ID), and in particular, do they believe this ID is ready to forward to the IESG for publication? Yes. 1.b) Has the document had adequate review from both key WG members and key non-WG members? Do you have any concerns about the depth or breadth of the reviews that have been performed? Adequate review has occurred from WG members, and it has been reviewed by others. I am satisfied about the level of review. 1.c) Do you have concerns that the document needs more review from a particular (broader) perspective (e.g., security, operational complexity, someone familiar with AAA, etc.)? No. 1.d) Do you have any specific concerns/issues with this document that you believe the ADs and/or IESG should be aware of? For example, perhaps you are uncomfortable with certain parts of the document, or have concerns whether there really is a need for it. In any event, if your issues have been discussed in the WG and the WG has indicated it that it still wishes to advance the document, detail those concerns in the write-up. No. 1.e) How solid is the WG consensus behind this document? Does it represent the strong concurrence of a few individuals, with others being silent, or does the WG as a whole understand and agree with it? There is strong consensus to publish this document. 1.f) Has anyone threatened an appeal or otherwise indicated extreme discontent? If so, please summarise the areas of conflict in separate email to the Responsible Area Director. No. 1.g) Have the chairs verified that the document adheres to all of the ID nits? (see http://www.ietf.org/ID-Checklist.html). Yes. 1.h) Is the document split into normative and informative references? Are there normative references to IDs, where the IDs are not also ready for advancement or are otherwise in an unclear state? (note here that the RFC editor will not publish an RFC with normative references to IDs, it will delay publication until all such IDs are also ready for publication as RFCs.) The references are split into normative and informational references. The document is dependant upon draft-ietf-syslog-protocol-14.txt but that is being submitted along with this document. 1.ijk) Write-up section: * Technical Summary This document describes the transport for syslog messages over UDP/ IPv4 or UDP/IPv6. The syslog protocol layered architecture provides for support of any number of transport mappings. However, for interoperability purposes, syslog protocol implementors are required to support this transport protocol. * Working Group Summary The consensus of the working group was to publish this as a standards-track document. * Protocol Quality It is possible that there are implementations of this document in various stages of completion at this time. Some equipment vendors have indicated interest in supporting this document, and some non-commercial implementations are also expected. === _______________________________________________ Syslog-sec mailing list Syslog-sec@www.employees.org http://www.employees.org/mailman/listinfo/syslog-sec From syslog-sec-bounces@willers.employees.org Mon Aug 22 18:52:16 2005 Return-Path: X-Original-To: lonvick@localhost Delivered-To: lonvick@localhost.linux.local Received: from localhost (localhost [127.0.0.1]) by linux.local (Postfix) with ESMTP id E0F4119046 for ; Mon, 22 Aug 2005 18:52:15 -0500 (CDT) Received: from email.cisco.com [171.70.151.132] by localhost with IMAP (fetchmail-6.2.3) for lonvick@localhost (single-drop); Mon, 22 Aug 2005 18:52:15 -0500 (CDT) Received: from xbh-sjc-221.amer.cisco.com ([128.107.191.63]) by xmb-sjc-227.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 10 Aug 2005 09:27:38 -0700 Received: from sj-iport-5.cisco.com ([171.68.10.87]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 10 Aug 2005 09:27:37 -0700 Received: from sj-core-3.cisco.com (171.68.223.137) by sj-iport-5.cisco.com with ESMTP; 10 Aug 2005 09:27:39 -0700 X-IronPort-AV: i="3.96,97,1122879600"; d="scan'208"; a="203983648:sNHT56171072" Received: from sj-inbound-d.cisco.com (sj-inbound-d.cisco.com [128.107.243.13]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id j7AGQlZO017957; Wed, 10 Aug 2005 09:27:32 -0700 (PDT) Received: from willers.employees.org (192.83.249.36) by sj-inbound-d.cisco.com with ESMTP; 10 Aug 2005 09:27:27 -0700 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-IronPort-AV: i="3.96,97,1122879600"; d="scan'208"; a="100706050:sNHT21354436" Received: from willers.employees.org (localhost.employees.org [IPv6:::1]) by willers.employees.org (Postfix) with ESMTP id 0D3155C7F7; Wed, 10 Aug 2005 09:27:23 -0700 (PDT) X-Original-To: syslog-sec@employees.org Delivered-To: syslog-sec@employees.org Received: from sj-iport-2.cisco.com (sj-iport-2-in.cisco.com [171.71.176.71]) by willers.employees.org (Postfix) with ESMTP id 508375C831 for ; Wed, 10 Aug 2005 09:23:39 -0700 (PDT) Received: from sj-core-5.cisco.com (171.71.177.238) by sj-iport-2.cisco.com with ESMTP; 10 Aug 2005 09:23:39 -0700 Received: from sjc-cde-003.cisco.com (sjc-cde-003.cisco.com [171.71.162.81]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j7AGNbop013722 for ; Wed, 10 Aug 2005 09:23:37 -0700 (PDT) Date: Wed, 10 Aug 2005 09:23:37 -0700 (PDT) From: Chris Lonvick To: syslog-sec@employees.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Wed, 10 Aug 2005 09:27:21 -0700 Cc: Subject: [Syslog-sec] 3195bis - anyone doing COOKED? X-BeenThere: syslog-sec@www.employees.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: "Mailing list for the syslog Working Group in the IETF." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: syslog-sec-bounces@willers.employees.org Errors-To: syslog-sec-bounces@willers.employees.org X-PMX-Version: 4.7.1.128075 X-from-outside-Cisco: 128.107.243.13 X-OriginalArrivalTime: 10 Aug 2005 16:27:37.0901 (UTC) FILETIME=[6BE35DD0:01C59DC8] Status: RO X-Status: X-Keywords: X-UID: 4 Hi Folks, I've asked Marshall Rose and Darren New to update RFC 3195 with respect to syslog-protocol. There are some implementations of RAW but I need to ask if anyone either has an implementation of COOKED, or is planning on doing an implementation of COOKED? If so, then your comments on the document will be greatly appreciated. If not, we should consider removing it from the document. (Note on the RFC process: An RFC that has a REQUIRED feature that no one is implementing will not have an easy time moving from a Draft Standard to a Proposed Standard. It would then be very difficult for it to become a Full Standard. If no one is going to do COOKED we should remove it from the document so that implementations can claim compliance with the full specification.) Thanks, Chris _______________________________________________ Syslog-sec mailing list Syslog-sec@www.employees.org http://www.employees.org/mailman/listinfo/syslog-sec From glen.f.marshall@siemens.com Mon Aug 22 18:52:16 2005 Return-Path: X-Original-To: lonvick@localhost Delivered-To: lonvick@localhost.linux.local Received: from localhost (localhost [127.0.0.1]) by linux.local (Postfix) with ESMTP id 7C07519046 for ; Mon, 22 Aug 2005 18:52:16 -0500 (CDT) Received: from email.cisco.com [171.70.151.132] by localhost with IMAP (fetchmail-6.2.3) for lonvick@localhost (single-drop); Mon, 22 Aug 2005 18:52:16 -0500 (CDT) Received: from xbh-sjc-211.amer.cisco.com ([171.70.151.144]) by xmb-sjc-227.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 10 Aug 2005 09:46:47 -0700 Received: from ind-iport-1.cisco.com ([64.104.129.195]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 10 Aug 2005 09:47:54 -0700 Received: from india-core-1.cisco.com (64.104.129.221) by ind-iport-1.cisco.com with ESMTP; 10 Aug 2005 22:21:36 -0700 Received: from sj-inbound-b.cisco.com (sj-inbound-b.cisco.com [128.107.234.205]) by india-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j7AGiibh016065 for ; Wed, 10 Aug 2005 16:46:31 GMT Received: from ns.shs.siemens.com (HELO mlvv9n2x.shs.siemens.com) (64.46.248.225) by sj-inbound-b.cisco.com with ESMTP; 10 Aug 2005 09:46:22 -0700 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-IronPort-AV: i="3.96,97,1122879600"; d="scan'208"; a="90565603:sNHT19844388" Received: from mlvv9n2x.shs.siemens.com (localhost.localdomain [127.0.0.1]) by localhost.shs.siemens.com (Postfix) with ESMTP id AE87944140 for ; Wed, 10 Aug 2005 12:46:21 -0400 (EDT) Received: from mlvv9n1x.shs.siemens.com (unknown [165.226.204.25]) by mlvv9n2x.shs.siemens.com (Postfix) with ESMTP id 8D6A244162 for ; Wed, 10 Aug 2005 12:46:21 -0400 (EDT) Received: from MLVV9MBA.ww005.siemens.net (mlvv9mba.smshsc.net [165.226.204.44]) by mlvv9n1x.shs.siemens.com (8.12.11/8.12.11) with ESMTP id j7AGkLDh005172 for ; Wed, 10 Aug 2005 12:46:21 -0400 Received: from MLVV099a.ww005.siemens.net ([165.226.248.184]) by 165.226.204.44 with InterScan Messaging Security Suite; Wed, 10 Aug 2005 12:45:05 -0400 Received: by mlvv099a.ww005.siemens.net with Internet Mail Service (5.5.2657.72) id ; Wed, 10 Aug 2005 12:46:19 -0400 Message-ID: From: Marshall Glen To: "'Chris Lonvick'" Cc: syslog-sec@employees.org Subject: RE: [Syslog-sec] 3195bis - anyone doing COOKED? Date: Wed, 10 Aug 2005 12:46:12 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain X-PMX-Version: 4.7.1.128075 X-from-outside-Cisco: 128.107.234.205 X-OriginalArrivalTime: 10 Aug 2005 16:47:54.0551 (UTC) FILETIME=[41116C70:01C59DCB] Status: RO X-Status: X-Keywords: X-UID: 5 Chris, The IHE implementation specification for RFC 3881 specifies COOKED. See http://www.ihe.net/Technical_Framework/upload/IHE_ITI_Node_Authentication_Se curity_2004_08-15.pdf It has been implemented already. Glen Marshall -----Original Message----- From: Chris Lonvick [mailto:clonvick@cisco.com] Sent: Wednesday, August 10, 2005 12:24 PM To: syslog-sec@employees.org Subject: [Syslog-sec] 3195bis - anyone doing COOKED? Hi Folks, I've asked Marshall Rose and Darren New to update RFC 3195 with respect to syslog-protocol. There are some implementations of RAW but I need to ask if anyone either has an implementation of COOKED, or is planning on doing an implementation of COOKED? If so, then your comments on the document will be greatly appreciated. If not, we should consider removing it from the document. (Note on the RFC process: An RFC that has a REQUIRED feature that no one is implementing will not have an easy time moving from a Draft Standard to a Proposed Standard. It would then be very difficult for it to become a Full Standard. If no one is going to do COOKED we should remove it from the document so that implementations can claim compliance with the full specification.) Thanks, Chris _______________________________________________ Syslog-sec mailing list Syslog-sec@www.employees.org http://www.employees.org/mailman/listinfo/syslog-sec ------------------------------------------------------------------------------- This message and any included attachments are from Siemens Medical Solutions USA, Inc. and are intended only for the addressee(s). The information contained herein may include trade secrets or privileged or otherwise confidential information. Unauthorized review, forwarding, printing, copying, distributing, or using such information is strictly prohibited and may be unlawful. If you received this message in error, or have reason to believe you are not authorized to receive it, please promptly delete this message and notify the sender by e-mail with a copy to Central.SecurityOffice@shs.siemens.com Thank you From syslog-sec-bounces@willers.employees.org Mon Aug 22 18:52:17 2005 Return-Path: X-Original-To: lonvick@localhost Delivered-To: lonvick@localhost.linux.local Received: from localhost (localhost [127.0.0.1]) by linux.local (Postfix) with ESMTP id 0514719046 for ; Mon, 22 Aug 2005 18:52:17 -0500 (CDT) Received: from email.cisco.com [171.70.151.132] by localhost with IMAP (fetchmail-6.2.3) for lonvick@localhost (single-drop); Mon, 22 Aug 2005 18:52:17 -0500 (CDT) Received: from xbh-sjc-231.amer.cisco.com ([128.107.191.100]) by xmb-sjc-227.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 10 Aug 2005 09:57:32 -0700 Received: from ind-iport-1.cisco.com ([64.104.129.195]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 10 Aug 2005 09:57:32 -0700 Received: from india-core-1.cisco.com (64.104.129.221) by ind-iport-1.cisco.com with ESMTP; 10 Aug 2005 22:32:09 -0700 Received: from sj-inbound-a.cisco.com (sj-inbound-a.cisco.com [128.107.234.204]) by india-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j7AGtdbc017943; Wed, 10 Aug 2005 16:56:57 GMT Received: from willers.employees.org (192.83.249.36) by sj-inbound-a.cisco.com with ESMTP; 10 Aug 2005 09:57:04 -0700 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-IronPort-AV: i="3.96,97,1122879600"; d="scan'208"; a="159417270:sNHT16268204" Received: from willers.employees.org (localhost.employees.org [IPv6:::1]) by willers.employees.org (Postfix) with ESMTP id 8F5CE5C7CE; Wed, 10 Aug 2005 09:57:02 -0700 (PDT) X-Original-To: syslog-sec@employees.org Delivered-To: syslog-sec@employees.org Received: from ipx10102.ipxserver.de (mailin.adiscon.com [80.190.240.92]) by willers.employees.org (Postfix) with ESMTP id 87E145C7A2 for ; Wed, 10 Aug 2005 09:57:00 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by ipx10102.ipxserver.de (Postfix) with ESMTP id E08D71B00ED for ; Wed, 10 Aug 2005 18:57:06 +0200 (CEST) Received: from ipx10102.ipxserver.de ([127.0.0.1]) by localhost (ipx10102 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 31729-08 for ; Wed, 10 Aug 2005 18:56:47 +0200 (CEST) Received: from fmint2.intern.adiscon.com (pd95b68d5.dip0.t-ipconnect.de [217.91.104.213]) by ipx10102.ipxserver.de (Postfix) with ESMTP id 3664A1B0075 for ; Wed, 10 Aug 2005 18:56:47 +0200 (CEST) Received: from grfint2.intern.adiscon.com ([172.19.0.6]) by fmint2.intern.adiscon.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 10 Aug 2005 18:56:37 +0200 Subject: RE: [Syslog-sec] 3195bis - anyone doing COOKED? Date: Wed, 10 Aug 2005 18:56:35 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message-ID: <577465F99B41C842AAFBE9ED71E70ABA0E3880@grfint2.intern.adiscon.com> X-MS-Has-Attach: Content-class: urn:content-classes:message X-MS-TNEF-Correlator: X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Thread-Topic: [Syslog-sec] 3195bis - anyone doing COOKED? Thread-Index: AcWdyHw6fWgoOrfQQqOx+AsFJSxrBwAA5/Ow From: "Rainer Gerhards" To: X-OriginalArrivalTime: 10 Aug 2005 16:56:38.0007 (UTC) FILETIME=[79127870:01C59DCC] X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at adiscon.com Cc: X-BeenThere: syslog-sec@www.employees.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: "Mailing list for the syslog Working Group in the IETF." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: syslog-sec-bounces@willers.employees.org Errors-To: syslog-sec-bounces@willers.employees.org X-PMX-Version: 4.7.1.128075 X-from-outside-Cisco: 128.107.234.204 Status: RO X-Status: X-Keywords: X-UID: 6 Chris, I have at least a partial implementation in liblogging (http://www.liblogging.org). I think its currently in the CVS version only (lack of demand), but I am in the process of moving it into the main branch. Once done, our intension is to include COOKED into our windows based apps and probably in our linux syslogd-replacement (rsyslog - www.rsyslog.com), too. The hardest part of COOKED is the relay procesing, I think there could be some room for additional compliance levels. I'll try to prepare a larger message, but I thought I provide some quick facts. I need to leave the office now and will not be in tomorrow. Rainer > -----Original Message----- > From: syslog-sec-bounces@www.employees.org=20 > [mailto:syslog-sec-bounces@www.employees.org] On Behalf Of=20 > Chris Lonvick > Sent: Wednesday, August 10, 2005 6:24 PM > To: syslog-sec@employees.org > Subject: [Syslog-sec] 3195bis - anyone doing COOKED? >=20 > Hi Folks, >=20 > I've asked Marshall Rose and Darren New to update RFC 3195=20 > with respect to > syslog-protocol. There are some implementations of RAW but I=20 > need to ask > if anyone either has an implementation of COOKED, or is=20 > planning on doing > an implementation of COOKED? If so, then your comments on=20 > the document > will be greatly appreciated. If not, we should consider=20 > removing it from > the document. >=20 > (Note on the RFC process: An RFC that has a REQUIRED feature=20 > that no one > is implementing will not have an easy time moving from a=20 > Draft Standard to > a Proposed Standard. It would then be very difficult for it=20 > to become a > Full Standard. If no one is going to do COOKED we should=20 > remove it from > the document so that implementations can claim compliance=20 > with the full > specification.) >=20 > Thanks, > Chris > _______________________________________________ > Syslog-sec mailing list > Syslog-sec@www.employees.org > http://www.employees.org/mailman/listinfo/syslog-sec >=20 _______________________________________________ Syslog-sec mailing list Syslog-sec@www.employees.org http://www.employees.org/mailman/listinfo/syslog-sec