From mailman-bounces@ietf.org Wed Dec 1 06:08:41 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13655 for ; Wed, 1 Dec 2004 06:08:41 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZSR2-0005Z3-Tn for syslog-archive@ietf.org; Wed, 01 Dec 2004 06:14:13 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZRm6-0000Xt-K0 for syslog-archive@ietf.org; Wed, 01 Dec 2004 05:31:54 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: lists.ietf.org mailing list memberships reminder From: mailman-owner@ietf.org To: syslog-archive@ietf.org X-No-Archive: yes Message-ID: Date: Wed, 01 Dec 2004 05:19:55 -0500 Precedence: bulk X-BeenThere: mailman@lists.ietf.org X-Mailman-Version: 2.1.5 List-Id: Mailman site list X-List-Administrivia: yes Sender: mailman-bounces@ietf.org Errors-To: mailman-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5 Content-Transfer-Encoding: 7bit This is a reminder, sent out once a month, about your lists.ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, mailman-request@lists.ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. ********************************************************************** NOTE WELL: Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to: o the IETF plenary session, o any IETF working group or portion thereof, o the IESG, or any member thereof on behalf of the IESG, o the IAB or any member thereof on behalf of the IAB, o any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, o the RFC Editor or the Internet-Drafts function All IETF Contributions are subject to the rules of RFC 3667 and RFC 3668. Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice. Please consult RFC 3667 for details. ******************************************************************************* If you have questions, problems, comments, etc, send them to mailman-owner@lists.ietf.org. Thanks! Passwords for syslog-archive@ietf.org: List Password // URL ---- -------- syslog@lists.ietf.org abzuka https://www1.ietf.org/mailman/options/syslog/syslog-archive%40ietf.org From mailman-bounces@willers.employees.org Wed Dec 1 08:11:43 2004 Received: from willers.employees.org (willers.employees.org [192.83.249.36]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25648 for ; Wed, 1 Dec 2004 08:11:43 -0500 (EST) Received: from willers.employees.org (localhost.employees.org [127.0.0.1]) by willers.employees.org (Postfix) with ESMTP id 38A1A5CEEC for ; Wed, 1 Dec 2004 05:05:13 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: www.employees.org mailing list memberships reminder From: mailman-owner@willers.employees.org To: syslog-archive@ietf.org X-No-Archive: yes Message-ID: Date: Wed, 01 Dec 2004 05:01:14 -0800 Precedence: bulk X-BeenThere: mailman@www.employees.org X-Mailman-Version: 2.1.4 List-Id: mailman.www.employees.org X-List-Administrivia: yes Sender: mailman-bounces@willers.employees.org Errors-To: mailman-bounces@willers.employees.org Content-Transfer-Encoding: 7bit This is a reminder, sent out once a month, about your www.employees.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, mailman-request@www.employees.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. If you have questions, problems, comments, etc, send them to mailman-owner@www.employees.org. Thanks! Passwords for syslog-archive@lists.ietf.org: List Password // URL ---- -------- syslog-sec@www.employees.org widuza http://www.employees.org/mailman/options/syslog-sec/syslog-archive%40lists.ietf.org From syslog-sec-bounces@willers.employees.org Wed Dec 8 13:57:14 2004 Received: from willers.employees.org (willers.employees.org [192.83.249.36]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23921 for ; Wed, 8 Dec 2004 13:57:13 -0500 (EST) Received: from willers.employees.org (localhost.employees.org [127.0.0.1]) by willers.employees.org (Postfix) with ESMTP id 52ED45C810; Wed, 8 Dec 2004 10:57:11 -0800 (PST) X-Original-To: syslog-sec@employees.org Delivered-To: syslog-sec@employees.org Received: from ipx10102.ipxserver.de (ipx10102.ipxserver.de [80.190.240.92]) by willers.employees.org (Postfix) with ESMTP id 790B05C7AA for ; Wed, 8 Dec 2004 09:32:28 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by ipx10102.ipxserver.de (Postfix) with ESMTP id 1F8A61B00AA for ; Wed, 8 Dec 2004 18:32:18 +0100 (CET) Received: from ipx10102.ipxserver.de ([127.0.0.1]) by localhost (ipx10102 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 16420-05 for ; Wed, 8 Dec 2004 18:32:14 +0100 (CET) Received: from fmint2.intern.adiscon.com (pD95B68D5.dip0.t-ipconnect.de [217.91.104.213]) by ipx10102.ipxserver.de (Postfix) with ESMTP id 6CA9C1B0007 for ; Wed, 8 Dec 2004 18:32:14 +0100 (CET) Received: from grfint2.intern.adiscon.com ([172.19.0.6]) by fmint2.intern.adiscon.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 8 Dec 2004 18:37:43 +0100 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Date: Wed, 8 Dec 2004 18:37:41 +0100 Message-ID: <577465F99B41C842AAFBE9ED71E70ABA06164E@grfint2.intern.adiscon.com> Thread-Topic: Message ID in the header Thread-Index: AcTdTJ442qxVX0jsQB+/k9ZTjZd81A== From: "Rainer Gerhards" To: X-OriginalArrivalTime: 08 Dec 2004 17:37:43.0390 (UTC) FILETIME=[9F594FE0:01C4DD4C] X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at adiscon.com X-Mailman-Approved-At: Wed, 08 Dec 2004 10:57:10 -0800 Subject: [Syslog-sec] Message ID in the header 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 Content-Transfer-Encoding: quoted-printable Hi list, finalizing syslog-protocol, I realized that SENDER-NAME/-INST is actually NOT really what TAG was. One usage of TAG was to provide the SENDER-NAME/-INST information. But it also had an other use: It often served as a message ID (something like "PIX-3333-3"). We do NOT (yet) have anything like a message ID in the message header. At least for me, I was so focussed on the new semantics that I overlooked the other common use for TAG. So we have another issue: do we need to include a message ID in the header? Should we drop it altogether? Or should we add an defined structured data ID? Comments are appreciated. Rainer _______________________________________________ Syslog-sec mailing list Syslog-sec@www.employees.org http://www.employees.org/mailman/listinfo/syslog-sec From syslog-sec-bounces@willers.employees.org Wed Dec 8 16:31:04 2004 Received: from willers.employees.org (willers.employees.org [192.83.249.36]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04915 for ; Wed, 8 Dec 2004 16:31:03 -0500 (EST) Received: from willers.employees.org (localhost.employees.org [127.0.0.1]) by willers.employees.org (Postfix) with ESMTP id 1D2A85C770; Wed, 8 Dec 2004 13:31:01 -0800 (PST) X-Original-To: syslog-sec@employees.org Delivered-To: syslog-sec@employees.org Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by willers.employees.org (Postfix) with ESMTP id C2A735C722 for ; Wed, 8 Dec 2004 11:07:14 -0800 (PST) Received: from rtp-core-2.cisco.com (64.102.124.13) by rtp-iport-2.cisco.com with ESMTP; 08 Dec 2004 14:07:14 -0500 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== Received: from aokmiansw2k01 (che-vpn-cluster-2-98.cisco.com [10.86.242.98]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iB8J7BA6019922; Wed, 8 Dec 2004 14:07:12 -0500 (EST) Message-Id: <200412081907.iB8J7BA6019922@rtp-core-2.cisco.com> From: "Anton Okmianski" To: "'Rainer Gerhards'" , Subject: RE: [Syslog-sec] Message ID in the header Date: Wed, 8 Dec 2004 14:07:13 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4942.400 thread-index: AcTdTJ442qxVX0jsQB+/k9ZTjZd81AAC/TBw In-Reply-To: <577465F99B41C842AAFBE9ED71E70ABA06164E@grfint2.intern.adiscon.com> X-Mailman-Approved-At: Wed, 08 Dec 2004 13:31:00 -0800 X-BeenThere: syslog-sec@www.employees.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: aokmians@cisco.com 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 Content-Transfer-Encoding: 7bit I support adding a separate field for message ID. This would make it more readily available for filtering (easier parsing) than if it were part of a structured content. I think it should be optional. Thanks, Anton. -----Original Message----- From: syslog-sec-bounces@willers.employees.org [mailto:syslog-sec-bounces@willers.employees.org] On Behalf Of Rainer Gerhards Sent: Wednesday, December 08, 2004 12:38 PM To: syslog-sec@employees.org Subject: [Syslog-sec] Message ID in the header Hi list, finalizing syslog-protocol, I realized that SENDER-NAME/-INST is actually NOT really what TAG was. One usage of TAG was to provide the SENDER-NAME/-INST information. But it also had an other use: It often served as a message ID (something like "PIX-3333-3"). We do NOT (yet) have anything like a message ID in the message header. At least for me, I was so focussed on the new semantics that I overlooked the other common use for TAG. So we have another issue: do we need to include a message ID in the header? Should we drop it altogether? Or should we add an defined structured data ID? Comments are appreciated. Rainer _______________________________________________ Syslog-sec mailing list Syslog-sec@www.employees.org http://www.employees.org/mailman/listinfo/syslog-sec _______________________________________________ Syslog-sec mailing list Syslog-sec@www.employees.org http://www.employees.org/mailman/listinfo/syslog-sec From syslog-sec-bounces@willers.employees.org Thu Dec 9 00:04:47 2004 Received: from willers.employees.org (willers.employees.org [192.83.249.36]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA03531 for ; Thu, 9 Dec 2004 00:04:47 -0500 (EST) Received: from willers.employees.org (localhost.employees.org [127.0.0.1]) by willers.employees.org (Postfix) with ESMTP id B46305C763; Wed, 8 Dec 2004 21:04:48 -0800 (PST) X-Original-To: syslog-sec@employees.org Delivered-To: syslog-sec@employees.org Received: from relay03.pair.com (relay03.pair.com [209.68.5.17]) by willers.employees.org (Postfix) with SMTP id 88BBA5C766 for ; Wed, 8 Dec 2004 15:26:45 -0800 (PST) Received: (qmail 96032 invoked from network); 8 Dec 2004 23:26:41 -0000 Received: from unknown (HELO Kiwi2000) (unknown) by unknown with SMTP; 8 Dec 2004 23:26:41 -0000 X-pair-Authenticated: 203.98.6.246 From: "Andrew Ross" To: "'Rainer Gerhards'" , Subject: RE: [Syslog-sec] Message ID in the header Date: Thu, 9 Dec 2004 12:26:40 +1300 Organization: Kiwi Enterprises Message-ID: <001d01c4dd7d$5fc8eb70$1101a8c0@Kiwi2000> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Importance: Normal In-Reply-To: <200412081907.iB8J7BA6019922@rtp-core-2.cisco.com> X-Mailman-Approved-At: Wed, 08 Dec 2004 21:04:47 -0800 X-BeenThere: syslog-sec@www.employees.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: andrew@kiwisyslog.com 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 Content-Transfer-Encoding: 7bit I'll second that. Anything that makes parsing the messages easier to achieve is good. Andrew -----Original Message----- From: syslog-sec-bounces@www.employees.org [mailto:syslog-sec-bounces@www.employees.org] On Behalf Of Anton Okmianski Sent: Thursday, 9 December 2004 8:07 a.m. To: 'Rainer Gerhards'; syslog-sec@employees.org Subject: RE: [Syslog-sec] Message ID in the header I support adding a separate field for message ID. This would make it more readily available for filtering (easier parsing) than if it were part of a structured content. I think it should be optional. Thanks, Anton. -----Original Message----- From: syslog-sec-bounces@willers.employees.org [mailto:syslog-sec-bounces@willers.employees.org] On Behalf Of Rainer Gerhards Sent: Wednesday, December 08, 2004 12:38 PM To: syslog-sec@employees.org Subject: [Syslog-sec] Message ID in the header Hi list, finalizing syslog-protocol, I realized that SENDER-NAME/-INST is actually NOT really what TAG was. One usage of TAG was to provide the SENDER-NAME/-INST information. But it also had an other use: It often served as a message ID (something like "PIX-3333-3"). We do NOT (yet) have anything like a message ID in the message header. At least for me, I was so focussed on the new semantics that I overlooked the other common use for TAG. So we have another issue: do we need to include a message ID in the header? Should we drop it altogether? Or should we add an defined structured data ID? Comments are appreciated. Rainer _______________________________________________ Syslog-sec mailing list Syslog-sec@www.employees.org http://www.employees.org/mailman/listinfo/syslog-sec _______________________________________________ Syslog-sec mailing list Syslog-sec@www.employees.org http://www.employees.org/mailman/listinfo/syslog-sec _______________________________________________ Syslog-sec mailing list Syslog-sec@www.employees.org http://www.employees.org/mailman/listinfo/syslog-sec