From syslog-bounces@lists.ietf.org Mon Mar 05 18:51:55 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HOMx9-0006gC-6s; Mon, 05 Mar 2007 18:50:51 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HOMwq-00062q-Jg; Mon, 05 Mar 2007 18:50:32 -0500 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HOMwq-0001jW-8z; Mon, 05 Mar 2007 18:50:32 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 35C8A2ACB0; Mon, 5 Mar 2007 23:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HOMwL-0000xK-Uv; Mon, 05 Mar 2007 18:50:01 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Mon, 05 Mar 2007 18:50:01 -0500 X-Spam-Score: -2.5 (--) X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6 Cc: syslog@ietf.org Subject: [Syslog] I-D ACTION:draft-ietf-syslog-device-mib-15.txt X-BeenThere: syslog@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Security Issues in Network Event Logging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: syslog-bounces@lists.ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Security Issues in Network Event Logging Working Group of the IETF. Title : Syslog Management Information Base Author(s) : G. Keeni Filename : draft-ietf-syslog-device-mib-15.txt Pages : 47 Date : 2007-3-5 This memo defines a portion of the Management Information Base (MIB), the Syslog MIB, for use with network management protocols in the Internet community. In particular, the Syslog MIB will be used to monitor and control syslog applications. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-syslog-device-mib-15.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-syslog-device-mib-15.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-syslog-device-mib-15.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-3-5150630.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-syslog-device-mib-15.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-syslog-device-mib-15.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-3-5150630.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog --NextPart-- From syslog-bounces@lists.ietf.org Tue Mar 13 00:29:44 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HQycb-0008Bd-Jk; Tue, 13 Mar 2007 00:28:25 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HQycZ-0008BU-Se for syslog@ietf.org; Tue, 13 Mar 2007 00:28:23 -0400 Received: from szxga01-in.huawei.com ([61.144.161.53]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HQycU-0004IE-UW for syslog@ietf.org; Tue, 13 Mar 2007 00:28:23 -0400 Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JET007BSQXYMW@szxga01-in.huawei.com> for syslog@ietf.org; Tue, 13 Mar 2007 12:25:11 +0800 (CST) Received: from huawei.com ([172.24.1.6]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JET004W0QXXH4@szxga01-in.huawei.com> for syslog@ietf.org; Tue, 13 Mar 2007 12:25:10 +0800 (CST) Received: from Harrington73653 (c-24-128-104-207.hsd1.nh.comcast.net [24.128.104.207]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0JET00KU6QXJS7@szxml02-in.huawei.com>; Tue, 13 Mar 2007 12:25:09 +0800 (CST) Date: Tue, 13 Mar 2007 00:24:55 -0400 From: David Harrington In-reply-to: <85B2F271FDF6B949B3672BA5A7BB62FB0339EE7A@xmb-sjc-236.amer.cisco.com> To: "'Alexander Clemm (alex)'" , syslog@ietf.org Message-id: <00ff01c76527$902bada0$0600a8c0@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-Mailer: Microsoft Office Outlook 11 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Thread-index: AcdkxMji6PWl1UeNRqCBGK501HY2pAAASvVwAAsu4cAAAC5+sA== References: <85B2F271FDF6B949B3672BA5A7BB62FB03167B98@xmb-sjc-236.amer.cisco.com> <85B2F271FDF6B949B3672BA5A7BB62FB0332B72D@xmb-sjc-236.amer.cisco.com> <006401c764c6$4addcaa0$0600a8c0@china.huawei.com> <85B2F271FDF6B949B3672BA5A7BB62FB0339EE7A@xmb-sjc-236.amer.cisco.com> X-Spam-Score: 0.0 (/) X-Scan-Signature: ba0d4c5f57f7c289496fce758bbf4798 Cc: Subject: [Syslog] RE: syslog-sign X-BeenThere: syslog@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Security Issues in Network Event Logging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: syslog-bounces@lists.ietf.org Hi, A new revision of syslog-sign will be published soon. Here are some comments, mostly editorial, on the new draft. Line 218: "with with" Line 229: "could be also be" Line 343: (section 3) eliminate the second sentence:"The syslog protocol therefore MUST be supported by implementations of this specification." This does not appear to be justified for use of RFC2119 keywords, if the sign protocol can also be used with non-syslog protocols. (and if not, then some text gives the impression you are advocating such a thing). Line 350 "described in RFC xxxx [11]. MAY make changes to a syslog packet. " eliminate the period after [11]. Line 376: s/the contents of the messages is/the content of the messages is/ Line 410: s/as such// Line 411: s/SD ELEMENT, as defined in RFC xxxx [11],/SD ELEMENT/ Section 4.2.1 Should we also define a hash algorithm value 2 to represent SHA-256? 4.2.4 - what extra considerations? 4.2.6 s/between 1 and 99/1 through 99/ 5.3 s/Note that// (remove this everywhere please) 5.3.1 s/per RFC xxxx [11] // (this is needed for the first reference, and not needed afterwards.) 5.3.1 s/as such// (remove this everywhere please) 5.3.1 s/, as defined in RFC xxx [1]],// (this is needed for the first reference, and not needed afterwards.) 5.3.1 s/In addition,// 5.3.1 s/to be compliant with RFC xxxx [11]// 5.3.1 s/for consistency reasons/for consistency/ 5.3.1 s/(but not required)// 5.3.1 s/Likewise,// 5.3.1 s/per the definitions that follow in the next section// 5.3.2 s/Like a Signature Block,// 5.3.2 s/per RFC xxx [11]// 5.3.2.1 s/as such,// 5.3.2.3 s/Also,// Section 5.3.1.x - if these are al;reday defined in section 4.2.x, why are we duplicating the information here? Can we eliminate the redundant text? 7.1 d. could use some wordsmithing. 8.2 s/as (per RFC xxxx [11])/since/ 8.2. s/to to/to/ 8.2 s/In this case, as in all others,// 8.2 s/Similarly// 8.2 s/Finally// 8.2 what does malfunction mean? Can we rephrase to what a receiver must do? 8.3 "That fact" - what fact? 8.3 "maintain doubt"? 8.3 - this section needs wordsmithing 8.4 s/may/might/ 8.4 s/However// 8.5 s/may/might/ 8.5 s/However// 8.4 and 8.5 would beneift from active voice rather than passive voice: "a reviewer can determine if ... by examining the information contained in Signature Blocks" 8.6 s/This document acknowledges that// 8.6 s/proper// 8.6 "allows a reviewer" would be better in active voice: A reviewer can determine .... By ..." 8.6 s/also// 8.7 s/Related to the above, syslog messages delivered over UDP not only may be lost, but they may also arrive out of sequence./Syslog messages delivered over UDP might be lost or delivered out of sequence./ 8.7 "allows a reviewer" => "A reviewer can determine ... By ..." 8.7 s/Beyond that,// 8.7 "... May help ..." => "A reviewer can determine the order of messages, and which messages were delivered out of order, by examining the information in the Signature Block, and any timestamp information in the message. Other sections - use "might" rather than "may"; MAY is a RFC2119 reserved word related to interoperability. 8.9 s/Generally this has had the benefit of allowing/This allows/ 8.10 s/It is conceivable that an attacker may/An attacker might/ 8.10 s/In that case,// 8.11 s/An attacker may be able to overwhelm a receiver by sending it invalid Signature Block messages. If the receiver is attempting to process these messages online, this attack may consume all available resources./An attacker might send invalid Signature Block messages to overwhelm the receiver's processing capability and consume all available resources./ 8.11 Do we want to make this implementation choice RECOMMENDED? Does this really belong in this document? s/As with any system,// s/may also just/might/ s/Nothing in this protocol attempts to eliminate/This protocol does not prevent/ s/Indeed,// s/In fact,// 8.12 do we really need this is this document? Couldn't this be done with almost any protocol? IANA Considerations should be succinct instruction to IANA about registries we want them to create, and values we want them to assign, and instructions about how values should be assigned in the future, that are specific to this document. This should NOT be the place where we describe in detail WHY we need these things; that should be in other sections. Eliminate the first paragraph. s/Specifically,// s/with regards to RFC xxx [11],// s/instructed/requested/ "appropriate registry" - you need to identify which is the apporpriate registry, if it already exists. If it does not exist, you need to request that IANA create a registry. It is the WG's responsibility to understand why we need these things, not IANA's; It is IANA's responsibility to create registries and add entries within the 2434-style guidance the WG decides should be applied. Please format these into table form, similar to existing registries found at www.iana.org so IANA can simply cut-and-paste the registries or registry entries you are requesting. "This document also upholds ..." Why are we asking to reserve the facilites and severities values, and doing so from this document? Is that something specific to syslog-sign? All the sections in IANA considerations should be reduced to tables that can be cut and pasted into the registry documents by IANA, without them needing to understand why we have each table or each value. For each new registry, identify how future extsnions are handled as per 2434. Authors' addresses are listed twice in the document. Can Informational documents be Normative? dbh > -----Original Message----- > From: Alexander Clemm (alex) [mailto:alex@cisco.com] > Sent: Monday, March 12, 2007 6:08 PM > To: David Harrington > Cc: Chris Lonvick (clonvick) > Subject: RE: syslog-sign > > Hello David, > > sure, here you go > > In case you have additional comments, I will hold off > submitting to the > ID Editor until I hear from you, or tomorrow noon (Pacific time), > whichever comes first - ok? > > Best regards > --- Alex > > -----Original Message----- > From: David Harrington [mailto:dharrington@huawei.com] > Sent: Monday, March 12, 2007 9:49 AM > To: Alexander Clemm (alex) > Subject: RE: syslog-sign > > Hi Alex, > > Can you send me a copy of the text file and the source? > > Thanks, > dbh > > > -----Original Message----- > > From: Chris Lonvick [mailto:clonvick@cisco.com] > > Sent: Monday, March 12, 2007 12:38 PM > > To: Alexander Clemm (alex) > > Cc: dharrington@huawei.com > > Subject: RE: syslog-sign > > > > Hi Alex, > > > > Please submit it to the ID Editor. > > > > Many thanks, > > Chris > > > > On Sun, 11 Mar 2007, Alexander Clemm (alex) wrote: > > > > > Hello Chris, > > > > > > please find enclosed > > > > > > In summary: > > > - References to RFC 3164 and 3195 have been removed; syslog-sign > now > > > presupposes syslog-protocol. > > > - syslog-sign does not mandate values for the APP-NAME, > MSGID, and > > > PROCID fields. (It does suggest that whichever values > are chosen, > > > SHOULD be consistent.) Likewise, the vlaue for the PRI field is > now > > > merely a recommendation. > > > > > > Some minor updates beyond those, such as changing "bytes" > > to "octets". > > > I'll send a more detailed response with replies to your and > Rainer's > > > review messages (which are the superset of all the comments) > later. > > > > > > Please advise how to proceed from here. > > > > > > Thanks > > > --- Alex > > > > > > -----Original Message----- > > > From: Chris Lonvick (clonvick) > > > Sent: Wednesday, March 07, 2007 12:06 PM > > > To: Alexander Clemm (alex) > > > Subject: Re: syslog-sign > > > > > > Hi Alex, > > > > > > Any update? > > > > > > Thanks, > > > Chris > > > > > > On Mon, 19 Feb 2007, Alexander Clemm (alex) wrote: > > > > > >> Hi Chris, > > >> > > >> apologies for the delay and keeping quiet for so long. I > > am keeping > > >> extremely busy with GMI so didn't get to send you the > > revised writeup > > >> on syslog-sign yet, although it's been resting heavily on > > my mind as a > > > > > >> thing-I-must-do-if-I-can-figure-out-how-to-get-to-it. I > > have finally > > >> a weekend coming up that is free of commitments, so I am > > planning to > > >> get this to you by the morning of Monday (of next week - 2/26). > > >> Hopefully this will still work for you... > > >> > > >> Best regards > > >> --- Alex > > >> > > > > > > _______________________________________________ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog From syslog-bounces@lists.ietf.org Tue Mar 13 00:30:42 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HQyeg-0001Ig-CB; Tue, 13 Mar 2007 00:30:34 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HQyef-0001E3-6H for syslog@ietf.org; Tue, 13 Mar 2007 00:30:33 -0400 Received: from alnrmhc11.comcast.net ([204.127.225.91]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HQyeZ-0005eP-8k for syslog@ietf.org; Tue, 13 Mar 2007 00:30:32 -0400 Received: from harrington73653 (failure[24.128.104.207]) by comcast.net (alnrmhc11) with SMTP id <20070313043026b11009vlhge>; Tue, 13 Mar 2007 04:30:26 +0000 From: "David Harrington" To: Date: Tue, 13 Mar 2007 00:30:02 -0400 Message-ID: <010001c76528$50e1eff0$0600a8c0@china.huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 Thread-Index: AcdlJ7P20IKko5mMS9iVpUqEkLlhxA== X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Cc: Subject: [Syslog] Note to editors X-BeenThere: syslog@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Security Issues in Network Event Logging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: syslog-bounces@lists.ietf.org Hi, We have crossed into 2007. Please make sure any copyrights in your document reflect 2007, not 2006. This includes the standard copyright, but also internal copyrights in MIB modules, etc. Please make sure the IPR boilerplate and any other copyrights have been updated to RFC 4748, which recognizes the IETF Trust. Thanks, David Harrington dharrington@huawei.com dbharrington@comcast.net ietfdbh@comcast.net _______________________________________________ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog From syslog-bounces@lists.ietf.org Tue Mar 13 14:19:05 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRBZO-0004MV-W1; Tue, 13 Mar 2007 14:17:59 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRBZN-0004MQ-9K for syslog@ietf.org; Tue, 13 Mar 2007 14:17:57 -0400 Received: from sj-iport-6.cisco.com ([171.71.176.117]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HRBZK-0002qp-TU for syslog@ietf.org; Tue, 13 Mar 2007 14:17:57 -0400 Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-6.cisco.com with ESMTP; 13 Mar 2007 11:17:54 -0700 X-IronPort-AV: i="4.14,280,1170662400"; d="scan'208"; a="120944611:sNHT49248036" Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l2DIHsOR012037; Tue, 13 Mar 2007 11:17:54 -0700 Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l2DIHnYS017371; Tue, 13 Mar 2007 18:17:54 GMT Received: from xmb-sjc-236.amer.cisco.com ([128.107.191.121]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 13 Mar 2007 11:17:51 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Syslog] Note to editors Date: Tue, 13 Mar 2007 11:17:50 -0700 Message-ID: <85B2F271FDF6B949B3672BA5A7BB62FB0339F1C6@xmb-sjc-236.amer.cisco.com> In-Reply-To: <010001c76528$50e1eff0$0600a8c0@china.huawei.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Syslog] Note to editors Thread-Index: AcdlJ7P20IKko5mMS9iVpUqEkLlhxAAc4zTg References: <010001c76528$50e1eff0$0600a8c0@china.huawei.com> From: "Alexander Clemm \(alex\)" To: "David Harrington" , X-OriginalArrivalTime: 13 Mar 2007 18:17:51.0304 (UTC) FILETIME=[E95F9480:01C7659B] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1052; t=1173809874; x=1174673874; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=alex@cisco.com; z=From:=20=22Alexander=20Clemm=20\(alex\)=22=20 |Subject:=20RE=3A=20[Syslog]=20Note=20to=20editors |Sender:=20; bh=mnMujWxWxC46nW5sU5EmHQRTg+g/rdqSvsLsILVvysY=; b=bOdEogi5ZTj1IvnyFUmls1xc6XCWXrAGmWwjMT3LA0Xu0Wi61KXAr7JDpCh/WpHNOdzDF0rv iscM5O/5+53fLdnTKApxcDDmpABgBZw1YYrdkPvV/ujmmX+OwhsbMw1TAYkrjP1En1rfZOIxvT i/hbFWPrmO5eYFy7aTWrjcJYM=; Authentication-Results: sj-dkim-1; header.From=alex@cisco.com; dkim=pass (si g from cisco.com/sjdkim1004 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb Cc: X-BeenThere: syslog@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Security Issues in Network Event Logging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: syslog-bounces@lists.ietf.org David, I am using the xml2rfc tool, which inserts these automatically. However, the copyright statement does show 2006, not 2007, when I generate the draft now. =20 What would you like to do? It seems preferrable that IETF should get xml2rfc updated. =20 Thanks --- Alex=20 -----Original Message----- From: David Harrington [mailto:ietfdbh@comcast.net]=20 Sent: Monday, March 12, 2007 9:30 PM To: syslog@ietf.org Subject: [Syslog] Note to editors Hi, We have crossed into 2007.=20 Please make sure any copyrights in your document reflect 2007, not 2006. This includes the standard copyright, but also internal copyrights in MIB modules, etc. Please make sure the IPR boilerplate and any other copyrights have been updated to RFC 4748, which recognizes the IETF Trust. Thanks, David Harrington dharrington@huawei.com dbharrington@comcast.net ietfdbh@comcast.net _______________________________________________ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog _______________________________________________ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog From syslog-bounces@lists.ietf.org Tue Mar 13 16:53:47 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRDzA-0000uU-MH; Tue, 13 Mar 2007 16:52:44 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRDz9-0000uN-62 for syslog@ietf.org; Tue, 13 Mar 2007 16:52:43 -0400 Received: from dsl093-068-160.sfo1.dsl.speakeasy.net ([66.93.68.160] helo=merrymeet.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HRDz7-000148-Mx for syslog@ietf.org; Tue, 13 Mar 2007 16:52:43 -0400 Received: from keys.merrymeet.com (dsl093-068-161.sfo1.dsl.speakeasy.net [66.93.68.161]) (Authenticated sender: jon) by merrymeet.com (Postfix) with ESMTP id D5C5E5A79FE; Tue, 13 Mar 2007 13:52:36 -0700 (PDT) Received: from [63.251.255.205] ([63.251.255.205]) by keys.merrymeet.com (PGP Universal service); Tue, 13 Mar 2007 13:52:36 -0700 X-PGP-Universal: processed; by keys.merrymeet.com on Tue, 13 Mar 2007 13:52:36 -0700 In-Reply-To: <85B2F271FDF6B949B3672BA5A7BB62FB0339F1C6@xmb-sjc-236.amer.cisco.com> References: <010001c76528$50e1eff0$0600a8c0@china.huawei.com> <85B2F271FDF6B949B3672BA5A7BB62FB0339F1C6@xmb-sjc-236.amer.cisco.com> Mime-Version: 1.0 (Apple Message framework v752.3) Message-Id: <25D787BE-2597-444B-B473-44D84F99C169@callas.org> From: Jon Callas Subject: Re: [Syslog] Note to editors Date: Tue, 13 Mar 2007 13:52:28 -0700 To: Alexander Clemm ((alex)) X-Mailer: Apple Mail (2.752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.1 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 Cc: syslog@ietf.org X-BeenThere: syslog@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Security Issues in Network Event Logging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: syslog-bounces@lists.ietf.org On Mar 13, 2007, at 11:17 AM, Alexander Clemm ((alex)) wrote: > David, > > I am using the xml2rfc tool, which inserts these automatically. > However, the copyright statement does show 2006, not 2007, when I > generate the draft now. > > What would you like to do? It seems preferrable that IETF should get > xml2rfc updated. > Given that copyright law says that the copyright is valid for the life of the authors plus 75 years on a document with a lifespan of six months, this is not a burning issue. Jon _______________________________________________ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog From syslog-bounces@lists.ietf.org Tue Mar 13 20:44:27 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRHaB-0000sJ-Ib; Tue, 13 Mar 2007 20:43:11 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRHaA-0000rR-4p for syslog@ietf.org; Tue, 13 Mar 2007 20:43:10 -0400 Received: from szxga02-in.huawei.com ([61.144.161.54]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HRHa8-000442-Iy for syslog@ietf.org; Tue, 13 Mar 2007 20:43:10 -0400 Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JEV004VWBAW51@szxga02-in.huawei.com> for syslog@ietf.org; Wed, 14 Mar 2007 08:42:33 +0800 (CST) Received: from huawei.com ([172.24.1.18]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0JEV00BO7BAW2G@szxga02-in.huawei.com> for syslog@ietf.org; Wed, 14 Mar 2007 08:42:32 +0800 (CST) Received: from m19684 ([10.111.12.128]) by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0JEV00GEYBASQQ@szxml03-in.huawei.com> for syslog@ietf.org; Wed, 14 Mar 2007 08:42:32 +0800 (CST) Date: Wed, 14 Mar 2007 08:42:27 +0800 From: Miao Fuyou Subject: RE: [Syslog] Note to editors In-reply-to: <85B2F271FDF6B949B3672BA5A7BB62FB0339F1C6@xmb-sjc-236.amer.cisco.com> To: "'Alexander Clemm (alex)'" , 'David Harrington' , syslog@ietf.org Message-id: <002801c765d1$a4489960$800c6f0a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Mailer: Microsoft Office Outlook 11 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Thread-index: AcdlJ7P20IKko5mMS9iVpUqEkLlhxAAc4zTgAA16cVA= X-Spam-Score: 0.0 (/) X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135 Cc: X-BeenThere: syslog@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Security Issues in Network Event Logging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: syslog-bounces@lists.ietf.org Hi, I reckon this happens because the "date" in the "front" part of the XML file is not updated. Or you could use the web to do the conversion: xml.resource.org. Regards, Miao > -----Original Message----- > From: Alexander Clemm (alex) [mailto:alex@cisco.com] > Sent: Wednesday, March 14, 2007 2:18 AM > To: David Harrington; syslog@ietf.org > Subject: RE: [Syslog] Note to editors > > David, > > I am using the xml2rfc tool, which inserts these automatically. > However, the copyright statement does show 2006, not 2007, > when I generate the draft now. > > What would you like to do? It seems preferrable that IETF should get > xml2rfc updated. > > Thanks > --- Alex > > -----Original Message----- > From: David Harrington [mailto:ietfdbh@comcast.net] > Sent: Monday, March 12, 2007 9:30 PM > To: syslog@ietf.org > Subject: [Syslog] Note to editors > > Hi, > > We have crossed into 2007. > > Please make sure any copyrights in your document reflect > 2007, not 2006. > This includes the standard copyright, but also internal > copyrights in MIB modules, etc. > > Please make sure the IPR boilerplate and any other copyrights > have been updated to RFC 4748, which recognizes the IETF Trust. > > Thanks, > David Harrington > dharrington@huawei.com > dbharrington@comcast.net > ietfdbh@comcast.net > > > > _______________________________________________ > Syslog mailing list > Syslog@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/syslog > > _______________________________________________ > Syslog mailing list > Syslog@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/syslog > _______________________________________________ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog From syslog-bounces@lists.ietf.org Tue Mar 13 23:53:15 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRKWu-0003ZK-GW; Tue, 13 Mar 2007 23:52:00 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRKWt-0003W9-7i for syslog@ietf.org; Tue, 13 Mar 2007 23:51:59 -0400 Received: from alnrmhc11.comcast.net ([204.127.225.91]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HRKWr-0007py-0W for syslog@ietf.org; Tue, 13 Mar 2007 23:51:59 -0400 Received: from harrington73653 (failure[24.128.104.207]) by comcast.net (alnrmhc11) with SMTP id <20070314035156b11009v6gpe>; Wed, 14 Mar 2007 03:51:56 +0000 From: "David Harrington" To: "'Jon Callas'" , "'Alexander Clemm \(\(alex\)\)'" References: <010001c76528$50e1eff0$0600a8c0@china.huawei.com> <85B2F271FDF6B949B3672BA5A7BB62FB0339F1C6@xmb-sjc-236.amer.cisco.com> <25D787BE-2597-444B-B473-44D84F99C169@callas.org> Subject: RE: [Syslog] Note to editors Date: Tue, 13 Mar 2007 23:51:31 -0400 Message-ID: <014b01c765ec$19cf9430$0600a8c0@china.huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <25D787BE-2597-444B-B473-44D84F99C169@callas.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 Thread-Index: AcdlsYgUevCBZnkLTrisMQlUcEPC3wAOkLMg X-Spam-Score: 0.0 (/) X-Scan-Signature: 52e1467c2184c31006318542db5614d5 Cc: syslog@ietf.org X-BeenThere: syslog@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Security Issues in Network Event Logging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: syslog-bounces@lists.ietf.org It is a burning issue if the internet-drafts editor refuses to publish the document because the copyright does not have the current year. And I have no intention of debating this rule. dbh > -----Original Message----- > From: Jon Callas [mailto:jon@callas.org] > Sent: Tuesday, March 13, 2007 4:52 PM > To: Alexander Clemm ((alex)) > Cc: David Harrington; syslog@ietf.org > Subject: Re: [Syslog] Note to editors > > > On Mar 13, 2007, at 11:17 AM, Alexander Clemm ((alex)) wrote: > > > David, > > > > I am using the xml2rfc tool, which inserts these automatically. > > However, the copyright statement does show 2006, not 2007, when I > > generate the draft now. > > > > What would you like to do? It seems preferrable that IETF > should get > > xml2rfc updated. > > > > Given that copyright law says that the copyright is valid for the > life of the authors plus 75 years on a document with a lifespan of > six months, this is not a burning issue. > > Jon > > _______________________________________________ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog From syslog-bounces@lists.ietf.org Tue Mar 13 23:53:15 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRKWw-0003a4-Kt; Tue, 13 Mar 2007 23:52:02 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRKWv-0003Zz-JZ for syslog@ietf.org; Tue, 13 Mar 2007 23:52:01 -0400 Received: from alnrmhc11.comcast.net ([204.127.225.91]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HRKWu-0007py-Al for syslog@ietf.org; Tue, 13 Mar 2007 23:52:01 -0400 Received: from harrington73653 (failure[24.128.104.207]) by comcast.net (alnrmhc11) with SMTP id <20070314035157b11009v6gqe>; Wed, 1From syslog-bounces@lists.ietf.org Tue Mar 13 23:53:15 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRKWu-0003ZK-GW; Tue, 13 Mar 2007 23:52:00 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRKWt-0003W9-7i for syslog@ietf.org; Tue, 13 Mar 2007 23:51:59 -0400 Received: from alnrmhc11.comcast.net ([204.127.225.91]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HRKWr-0007py-0W for syslog@ietf.org; Tue, 13 Mar 2007 23:51:59 -0400 Received: from harrington73653 (failure[24.128.104.207]) by comcast.net (alnrmhc11) with SMTP id <20070314035156b11009v6gpe>; Wed, 14 Mar 2007 03:51:56 +0000 From: "David Harrington" To: "'Jon Callas'" , "'Alexander Clemm \(\(alex\)\)'" References: <010001c76528$50e1eff0$0600a8c0@china.huawei.com> <85B2F271FDF6B949B3672BA5A7BB62FB0339F1C6@xmb-sjc-236.amer.cisco.com> <25D787BE-2597-444B-B473-44D84F99C169@callas.org> Subject: RE: [Syslog] Note to editors Date: Tue, 13 Mar 2007 23:51:31 -0400 Message-ID: <014b01c765ec$19cf9430$0600a8c0@china.huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <25D787BE-2597-444B-B473-44D84F99C169@callas.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 Thread-Index: AcdlsYgUevCBZnkLTrisMQlUcEPC3wAOkLMg X-Spam-Score: 0.0 (/) X-Scan-Signature: 52e1467c2184c31006318542db5614d5 Cc: syslog@ietf.org X-BeenThere: syslog@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Security Issues in Network Event Logging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: syslog-bounces@lists.ietf.org It is a burning issue if the internet-drafts editor refuses to publish the document because the copyright does not have the current year. And I have no intention of debating this rule. dbh > -----Original Message----- > From: Jon Callas [mailto:jon@callas.org] > Sent: Tuesday, March 13, 2007 4:52 PM > To: Alexander Clemm ((alex)) > Cc: David Harrington; syslog@ietf.org > Subject: Re: [Syslog] Note to editors > > > On Mar 13, 2007, at 11:17 AM, Alexander Clemm ((alex)) wrote: > > > David, > > > > I am using the xml2rfc tool, which inserts these automatically. > > However, the copyright statement does show 2006, not 2007, when I > > generate the draft now. > > > > What would you like to do? It seems preferrable that IETF > should get > > xml2rfc updated. > > > > Given that copyright law says that the copyright is valid for the > life of the authors plus 75 years on a document with a lifespan of > six months, this is not a burning issue. > > Jon > > _______________________________________________ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog From syslog-bounces@lists.ietf.org Tue Mar 13 23:53:15 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRKWw-0003a4-Kt; Tue, 13 Mar 2007 23:52:02 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRKWv-0003Zz-JZ for syslog@ietf.org; Tue, 13 Mar 2007 23:52:01 -0400 Received: from alnrmhc11.comcast.net ([204.127.225.91]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HRKWu-0007py-Al for syslog@ietf.org; Tue, 13 Mar 2007 23:52:01 -0400 Received: from harrington73653 (failure[24.128.104.207]) by comcast.net (alnrmhc11) with SMTP id <20070314035157b11009v6gqe>; Wed, 14 Mar 2007 03:51:57 +0000 From: "David Harrington" To: "'Miao Fuyou'" , "'Alexander Clemm \(alex\)'" , References: <85B2F271FDF6B949B3672BA5A7BB62FB0339F1C6@xmb-sjc-236.amer.cisco.com> <002801c765d1$a4489960$800c6f0a@china.huawei.com> Subject: RE: [Syslog] Note to editors Date: Tue, 13 Mar 2007 23:51:31 -0400 Message-ID: <014c01c765ec$1a2ca850$0600a8c0@china.huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <002801c765d1$a4489960$800c6f0a@china.huawei.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 Thread-Index: AcdlJ7P20IKko5mMS9iVpUqEkLlhxAAc4zTgAA16cVAABoe5oA== X-Spam-Score: 0.0 (/) X-Scan-Signature: f66b12316365a3fe519e75911daf28a8 Cc: X-BeenThere: syslog@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Security Issues in Network Event Logging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: syslog-bounces@lists.ietf.org Hi, Actually, all you need to provide is the year in the field. Xml2rfc will automatically use the day and month that it is run. The web version will use 2006 if is specified in the file. dbh > -----Original Message----- > From: Miao Fuyou [mailto:miaofy@huawei.com] > Sent: Tuesday, March 13, 2007 8:42 PM > To: 'Alexander Clemm (alex)'; 'David Harrington'; syslog@ietf.org > Subject: RE: [Syslog] Note to editors > > Hi, > > I reckon this happens because the "date" in the "front" part > of the XML file > is not updated. > > > > Or you could use the web to do the conversion: xml.resource.org. > > Regards, > Miao > > > -----Original Message----- > > From: Alexander Clemm (alex) [mailto:alex@cisco.com] > > Sent: Wednesday, March 14, 2007 2:18 AM > > To: David Harrington; syslog@ietf.org > > Subject: RE: [Syslog] Note to editors > > > > David, > > > > I am using the xml2rfc tool, which inserts these automatically. > > However, the copyright statement does show 2006, not 2007, > > when I generate the draft now. > > > > What would you like to do? It seems preferrable that IETF > should get > > xml2rfc updated. > > > > Thanks > > --- Alex > > > > -----Original Message----- > > From: David Harrington [mailto:ietfdbh@comcast.net] > > Sent: Monday, March 12, 2007 9:30 PM > > To: syslog@ietf.org > > Subject: [Syslog] Note to editors > > > > Hi, > > > > We have crossed into 2007. > > > > Please make sure any copyrights in your document reflect > > 2007, not 2006. > > This includes the standard copyright, but also internal > > copyrights in MIB modules, etc. > > > > Please make sure the IPR boilerplate and any other copyrights > > have been updated to RFC 4748, which recognizes the IETF Trust. > > > > Thanks, > > David Harrington > > dharrington@huawei.com > > dbharrington@comcast.net > > ietfdbh@comcast.net > > > > > > > > _______________________________________________ > > Syslog mailing list > > Syslog@lists.ietf.org > > https://www1.ietf.org/mailman/listinfo/syslog > > > > _______________________________________________ > > Syslog mailing list > > Syslog@lists.ietf.org > > https://www1.ietf.org/mailman/listinfo/syslog > > > > > _______________________________________________ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog 4 Mar 2007 03:51:57 +0000 From: "David Harrington" To: "'Miao Fuyou'" , "'Alexander Clemm \(alex\)'" , References: <85B2F271FDF6B949B3672BA5A7BB62FB0339F1C6@xmb-sjc-236.amer.cisco.com> <002801c765d1$a4489960$800c6f0a@china.huawei.com> Subject: RE: [Syslog] Note to editors Date: Tue, 13 Mar 2007 23:51:31 -0400 Message-ID: <014c01c765ec$1a2ca850$0600a8c0@china.huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <002801c765d1$a4489960$800c6f0a@china.huawei.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 Thread-Index: AcdlJ7P20IKko5mMS9iVpUqEkLlhxAAc4zTgAA16cVAABoe5oA== X-Spam-Score: 0.0 (/) X-Scan-Signature: f66b12316365a3fe519e75911daf28a8 Cc: X-BeenThere: syslog@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Security Issues in Network Event Logging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: syslog-bounces@lists.ietf.org Hi, Actually, all you need to provide is the year in the field. Xml2rfc will automatically use the day and month that it is run. The web version will use 2006 if is specified in the file. dbh > -----Original Message----- > From: Miao Fuyou [mailto:miaofy@huawei.com] > Sent: Tuesday, March 13, 2007 8:42 PM > To: 'Alexander Clemm (alex)'; 'David Harrington'; syslog@ietf.org > Subject: RE: [Syslog] Note to editors > > Hi, > > I reckon this happens because the "date" in the "front" part > of the XML file > is not updated. > > > > Or you could use the web to do the conversion: xml.resource.org. > > Regards, > Miao > > > -----Original Message----- > > From: Alexander Clemm (alex) [mailto:alex@cisco.com] > > Sent: Wednesday, March 14, 2007 2:18 AM > > To: David Harrington; syslog@ietf.org > > Subject: RE: [Syslog] Note to editors > > > > David, > > > > I am using the xml2rfc tool, which inserts these automatically. > > However, the copyright statement does show 2006, not 2007, > > when I generate the draft now. > > > > What would you like to do? It seems preferrable that IETF > should get > > xml2rfc updated. > > > > Thanks > > --- Alex > > > > -----Original Message----- > > From: David Harrington [mailto:ietfdbh@comcast.net] > > Sent: Monday, March 12, 2007 9:30 PM > > To: syslog@ietf.org > > Subject: [Syslog] Note to editors > > > > Hi, > > > > We have crossed into 2007. > > > > Please make sure any copyrights in your document reflect > > 2007, not 2006. > > This includes the standard copyright, but also internal > > copyrights in MIB modules, etc. > > > > Please make sure the IPR boilerplate and any other copyrights > > have been updated to RFC 4748, which recognizes the IETF Trust. > > > > Thanks, > > David Harrington > > dharrington@huawei.com > > dbharrington@comcast.net > > ietfdbh@comcast.net > > > > > > > > _______________________________________________ > > Syslog mailing list > > Syslog@lists.ietf.org > > https://www1.ietf.org/mailman/listinfo/syslog > > > > _______________________________________________ > > Syslog mailing list > > Syslog@lists.ietf.org > > https://www1.ietf.org/mailman/listinfo/syslog > > > > > _______________________________________________ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog From syslog-bounces@lists.ietf.org Thu Mar 15 13:30:54 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRtlO-0004SH-3O; Thu, 15 Mar 2007 13:29:18 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HRtlN-0004SA-15 for syslog@ietf.org; Thu, 15 Mar 2007 13:29:17 -0400 Received: from blaster.systems.pipex.net ([62.241.163.7]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HRtlG-0000C2-Kr for syslog@ietf.org; Thu, 15 Mar 2007 13:29:16 -0400 Received: from pc6 (1Cust132.tnt1.lnd4.gbr.da.uu.net [62.188.130.132]) by blaster.systems.pipex.net (Postfix) with SMTP id 04833E0004F6; Thu, 15 Mar 2007 17:28:53 +0000 (GMT) Message-ID: <02e801c7671e$b52180a0$0601a8c0@pc6> From: "tom.petch" To: "David Harrington" , "'Alexander Clemm (alex)'" , References: <85B2F271FDF6B949B3672BA5A7BB62FB03167B98@xmb-sjc-236.amer.cisco.com><85B2F271FDF6B949B3672BA5A7BB62FB0332B72D@xmb-sjc-236.amer.cisco.com><006401c764c6$4addcaa0$0600a8c0@china.huawei.com><85B2F271FDF6B949B3672BA5A7BB62FB0339EE7A@xmb-sjc-236.amer.cisco.com> <00ff01c76527$902bada0$0600a8c0@china.huawei.com> Subject: Re: [Syslog] RE: syslog-sign Date: Thu, 15 Mar 2007 09:37:44 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Spam-Score: 0.2 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Cc: X-BeenThere: syslog@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "tom.petch" List-Id: Security Issues in Network Event Logging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: syslog-bounces@lists.ietf.org See RFC3967 Tom Petch ----- Original Message ----- From: "David Harrington" To: "'Alexander Clemm (alex)'" ; Sent: Tuesday, March 13, 2007 5:24 AM Subject: [Syslog] RE: syslog-sign > Hi, > > Can Informational documents be Normative? > > dbh > > _______________________________________________ > Syslog mailing list > Syslog@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/syslog _______________________________________________ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog From syslog-bounces@lists.ietf.org Fri Mar 16 13:57:49 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HSGfd-0001Ir-SP; Fri, 16 Mar 2007 13:56:53 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HSGfc-0001Ig-Bu for syslog@ietf.org; Fri, 16 Mar 2007 13:56:52 -0400 Received: from sj-iport-6.cisco.com ([171.71.176.117]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HSGfX-00084S-SY for syslog@ietf.org; Fri, 16 Mar 2007 13:56:52 -0400 Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-6.cisco.com with ESMTP; 16 Mar 2007 10:56:47 -0700 Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id l2GHul3N009498; Fri, 16 Mar 2007 10:56:47 -0700 Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l2GHujZd008683; Fri, 16 Mar 2007 17:56:47 GMT Received: from xmb-sjc-236.amer.cisco.com ([128.107.191.121]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 16 Mar 2007 10:56:42 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 16 Mar 2007 10:56:40 -0700 Message-ID: <85B2F271FDF6B949B3672BA5A7BB62FB0340AD40@xmb-sjc-236.amer.cisco.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-ietf-syslog-sign-21.txt Thread-Index: Acbc8+g/jZl4SDWATEChWON8ntejRg+UxBmAEysQjbA= References: From: "Alexander Clemm \(alex\)" To: X-OriginalArrivalTime: 16 Mar 2007 17:56:42.0383 (UTC) FILETIME=[7446D9F0:01C767F4] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3600; t=1174067807; x=1174931807; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=alex@cisco.com; z=From:=20=22Alexander=20Clemm=20\(alex\)=22=20 |Subject:=20draft-ietf-syslog-sign-21.txt |Sender:=20; bh=uUL1k4oZDz/2Gdy8E3dHrtIitM1g+g83N432sZBaFCg=; b=bRv0tYqcoRWa4p1s5B8orzzXUuZa5Xzl3lJ1+/fLA2DM/xYNoajX8ICyxmWReuV2NzZvAQYf pxlmw7giFPApIC76W51B3pTIiSs1sY+D6clbwRRiDTQIU/hgIZpLvH0U; Authentication-Results: sj-dkim-4; header.From=alex@cisco.com; dkim=pass (si g from cisco.com/sjdkim4002 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024 Cc: dbharrington@comcast.net Subject: [Syslog] draft-ietf-syslog-sign-21.txt X-BeenThere: syslog@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Security Issues in Network Event Logging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: syslog-bounces@lists.ietf.org Hello, I have just submitted syslog-sign-21, which should be posted shortly. =20 Here is the summary of changes, based on the review comments:=20 * The new draft reflects the decision by the working group to drop support for RFC 3164 and 3195, instead require syslog protocol. The previous draft allowed for both possibilities. The various sections have been updated accordingly. =20 * The draft still requires support for messages of 2048 octets minimum length, reflecting recommendations for the support of messages of according length on syslog receiver (and syslog relay) side. =20 * Section 4.1, section 5.3.1: The specifications of Signature From syslog-bounces@lists.ietf.org Fri Mar 16 13:57:49 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HSGfd-0001Ir-SP; Fri, 16 Mar 2007 13:56:53 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HSGfc-0001Ig-Bu for syslog@ietf.org; Fri, 16 Mar 2007 13:56:52 -0400 Received: from sj-iport-6.cisco.com ([171.71.176.117]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HSGfX-00084S-SY for syslog@ietf.org; Fri, 16 Mar 2007 13:56:52 -0400 Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-6.cisco.com with ESMTP; 16 Mar 2007 10:56:47 -0700 Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id l2GHul3N009498; Fri, 16 Mar 2007 10:56:47 -0700 Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l2GHujZd008683; Fri, 16 Mar 2007 17:56:47 GMT Received: from xmb-sjc-236.amer.cisco.com ([128.107.191.121]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 16 Mar 2007 10:56:42 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 16 Mar 2007 10:56:40 -0700 Message-ID: <85B2F271FDF6B949B3672BA5A7BB62FB0340AD40@xmb-sjc-236.amer.cisco.com> In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-ietf-syslog-sign-21.txt Thread-Index: Acbc8+g/jZl4SDWATEChWON8ntejRg+UxBmAEysQjbA= References: From: "Alexander Clemm \(alex\)" To: X-OriginalArrivalTime: 16 Mar 2007 17:56:42.0383 (UTC) FILETIME=[7446D9F0:01C767F4] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3600; t=1174067807; x=1174931807; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=alex@cisco.com; z=From:=20=22Alexander=20Clemm=20\(alex\)=22=20 |Subject:=20draft-ietf-syslog-sign-21.txt |Sender:=20; bh=uUL1k4oZDz/2Gdy8E3dHrtIitM1g+g83N432sZBaFCg=; b=bRv0tYqcoRWa4p1s5B8orzzXUuZa5Xzl3lJ1+/fLA2DM/xYNoajX8ICyxmWReuV2NzZvAQYf pxlmw7giFPApIC76W51B3pTIiSs1sY+D6clbwRRiDTQIU/hgIZpLvH0U; Authentication-Results: sj-dkim-4; header.From=alex@cisco.com; dkim=pass (si g from cisco.com/sjdkim4002 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024 Cc: dbharrington@comcast.net Subject: [Syslog] draft-ietf-syslog-sign-21.txt X-BeenThere: syslog@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Security Issues in Network Event Logging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: syslog-bounces@lists.ietf.org Hello, I have just submitted syslog-sign-21, which should be posted shortly. =20 Here is the summary of changes, based on the review comments:=20 * The new draft reflects the decision by the working group to drop support for RFC 3164 and 3195, instead require syslog protocol. The previous draft allowed for both possibilities. The various sections have been updated accordingly. =20 * The draft still requires support for messages of 2048 octets minimum length, reflecting recommendations for the support of messages of according length on syslog receiver (and syslog relay) side. =20 * Section 4.1, section 5.3.1: The specifications of Signature Block messages and Certificate Block messages have been updated to no longer include a value as requirement for APP-NAME, MSGID, and PROCID, per discussion on the mailer. The specification has been updated to establish that the differentiating feature (that makes a Signature Block message a Signature Block message and a Certificate Block message a Certificate Block message) is the presence of Structured Data of the respective type (with the respective SD-ID). =20 * Section 4.1, section 5.3.1: Having said that, the specifications of the Signature Block and Certificate Block messages now state that whichever values an implementation chooses for APP-NAME, MSGID, and PROCID, that these values SHOULD be applied consistently. =20 * Section 4.1, section 5.3.1: The requirement for a PRI of 110 for the Signature Block and Certificate Block messages has been changed from a MUST to a RECOMMENDED, per the same rational that the defining feature now is the Structured Data only. =20 * Section 4.2.1: Added a value to the hash algorithm field to allow for SHA256 as hash algorithm. =20 * Section 4.2.1: Moved the description of the semantics of the protocol version field from the IANA considerations section into this section; rephrased the way in which extensibility beyond 9 values for hash algorithm and signature scheme can be achieved; clarified that the values for hash algorithm and signature scheme are protocol version dependent. =20 * Section 4.2.5: Meaning of Message Number is clarified: message number is relative to signature group. Also, Message Number behavior when it reaches 9999999999 is clarified (it simply latches; a "latched" number can be distinguished from a "non-latched" number by virtue of the Global Block Counter). =20 * References to bytes have been changed to octets, as requested per Rainer's review. =20 * Section 5.2: The time stamp is now required per syslog protocol, not just per RFC 3339. =20 * Section 5.3.2.6: Fragment length can be expressed with one to four octets, not one to three. (Also reflected in table in 5.3.2) * IANA considerations: removed the mention of APP-NAME, MSGID per bullet items above. Rewrote most of the considerations and requested registries as appropriate. =20 * References: removed UDP, RFC 3164, and RFC 3195 references. Moved RFC 4648, draft-ietf-syslog-protocol-19.txt, draft-ietf-syslog-transport-udp-08.txt, and draft-ietf-syslog-transport-tls-06.rxt references to normative references. =20 Other comments: * Rainer had suggested to allow for 999 sig groups in case of SG=3D3, instead of 192. While technically this would be possible, it appears that it unnecessarily makes the implementation more complex because the restriction (999 vs. 192) would become context dependent, as opposed to context independent, with no real tangible benefit. =20 =20 Best regards --- Alex _______________________________________________ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog From syslog-bounces@lists.ietf.org Fri Mar 16 13:57:49 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HSGf5-0001Dc-1Y; Fri, 16 Mar 2007 13:56:19 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HSGf4-0001DW-2B for syslog@ietf.org; Fri, 16 Mar 2007 13:56:18 -0400 Received: from sj-iport-6.cisco.com ([171.71.176.117]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HSGf2-00080w-MO for syslog@ietf.org; Fri, 16 Mar 2007 13:56:18 -0400 Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-6.cisco.com with ESMTP; 16 Mar 2007 10:56:16 -0700 Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l2GHuGL9013842; Fri, 16 Mar 2007 10:56:16 -0700 Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l2GHtxFE020275; Fri, 16 Mar 2007 17:56:16 GMBlock messages and Certificate Block messages have been updated to no longer include a value as requirement for APP-NAME, MSGID, and PROCID, per discussion on the mailer. The specification has been updated to establish that the differentiating feature (that makes a Signature Block message a Signature Block message and a Certificate Block message a Certificate Block message) is the presence of Structured Data of the respective type (with the respective SD-ID). =20 * Section 4.1, section 5.3.1: Having said that, the specifications of the Signature Block and Certificate Block messages now state that whichever values an implementation chooses for APP-NAME, MSGID, and PROCID, that these values SHOULD be applied consistently. =20 * Section 4.1, section 5.3.1: The requirement for a PRI of 110 for the Signature Block and Certificate Block messages has been changed from a MUST to a RECOMMENDED, per the same rational that the defining feature now is the Structured Data only. =20 * Section 4.2.1: Added a value to the hash algorithm field to allow for SHA256 as hash algorithm. =20 * Section 4.2.1: Moved the description of the semantics of the protocol version field from the IANA considerations section into this section; rephrased the way in which extensibility beyond 9 values for hash algorithm and signature scheme can be achieved; clarified that the values for hash algorithm and signature scheme are protocol version dependent. =20 * Section 4.2.5: Meaning of Message Number is clarified: message number is relative to signature group. Also, Message Number behavior when it reaches 9999999999 is clarified (it simply latches; a "latched" number can be distinguished from a "non-latched" number by virtue of the Global Block Counter). =20 * References to bytes have been changed to octets, as requested per Rainer's review. =20 * Section 5.2: The time stamp is now required per syslog protocol, not just per RFC 3339. =20 * Section 5.3.2.6: Fragment length can be expressed with one to four octets, not one to three. (Also reflected in table in 5.3.2) * IANA considerations: removed the mention of APP-NAME, MSGID per bullet items above. Rewrote most of the considerations and requested registries as appropriate. =20 * References: removed UDP, RFC 3164, and RFC 3195 references. Moved RFC 4648, draft-ietf-syslog-protocol-19.txt, draft-ietf-syslog-transport-udp-08.txt, and draft-ietf-syslog-transport-tls-06.rxt references to normative references. =20 Other comments: * Rainer had suggested to allow for 999 sig groups in case of SG=3D3, instead of 192. While technically this would be possible, it appears that it unnecessarily makes the implementation more complex because the restriction (999 vs. 192) would become context dependent, as opposed to context independent, with no real tangible benefit. =20 =20 Best regards --- Alex _______________________________________________ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog From syslog-bounces@lists.ietf.org Fri Mar 16 13:57:49 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HSGf5-0001Dc-1Y; Fri, 16 Mar 2007 13:56:19 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HSGf4-0001DW-2B for syslog@ietf.org; Fri, 16 Mar 2007 13:56:18 -0400 Received: from sj-iport-6.cisco.com ([171.71.176.117]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HSGf2-00080w-MO for syslog@ietf.org; Fri, 16 Mar 2007 13:56:18 -0400 Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-6.cisco.com with ESMTP; 16 Mar 2007 10:56:16 -0700 Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l2GHuGL9013842; Fri, 16 Mar 2007 10:56:16 -0700 Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l2GHtxFE020275; Fri, 16 Mar 2007 17:56:16 GMT Received: from xmb-sjc-236.amer.cisco.com ([128.107.191.121]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 16 Mar 2007 10:56:13 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Syslog] Note to editors Date: Fri, 16 Mar 2007 10:56:12 -0700 Message-ID: <85B2F271FDF6B949B3672BA5A7BB62FB0340AD3F@xmb-sjc-236.amer.cisco.com> In-Reply-To: <014c01c765ec$1a2ca850$0600a8c0@china.huawei.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Syslog] Note to editors Thread-Index: AcdlJ7P20IKko5mMS9iVpUqEkLlhxAAc4zTgAA16cVAABoe5oACCMAVA References: <85B2F271FDF6B949B3672BA5A7BB62FB0339F1C6@xmb-sjc-236.amer.cisco.com> <002801c765d1$a4489960$800c6f0a@china.huawei.com> <014c01c765ec$1a2ca850$0600a8c0@china.huawei.com> From: "Alexander Clemm \(alex\)" To: "David Harrington" , "Miao Fuyou" , X-OriginalArrivalTime: 16 Mar 2007 17:56:13.0733 (UTC) FILETIME=[63333550:01C767F4] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3036; t=1174067776; x=1174931776; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=alex@cisco.com; z=From:=20=22Alexander=20Clemm=20\(alex\)=22=20 |Subject:=20RE=3A=20[Syslog]=20Note=20to=20editors |Sender:=20; bh=HFxk/G47KyqKgBqzfLMt48Vnf8co+Q6np/6zvOHSTjc=; b=GLlCjGEFHkBZtr4k6ViS3HHq1tqSpt+rLBYDhhGR7VPTzVc1h/ecnVOAoG1T8p1iKdXdFul+ ipaMxs+IOJFCSfexk8pFuZlRXOVWYJHSfuqxVoWkiVvie65CjUupdHEw; Authentication-Results: sj-dkim-3; header.From=alex@cisco.com; dkim=pass (si g from cisco.com/sjdkim3002 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5 Cc: X-BeenThere: syslog@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Security Issues in Network Event Logging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: syslog-bounces@lists.ietf.org Well, the issue is fixed. =20 Turns out there is some strange behavior: I did have in the field, which generated the 2006 Copyright statement anyway. However, adding the day specifically (day=3D"15") did the trick. Go figure. =20 I just posted the updated draft, separate note to follow momentarily. =20 --- Alex -----Original Message----- From: David Harrington [mailto:ietfdbh@comcast.net]=20 Sent: Tuesday, March 13, 2007 8:52 PM To: 'Miao Fuyou'; Alexander Clemm (alex); syslog@ietf.org Subject: RE: [Syslog] Note to editors Hi, Actually, all you need to provide is the year in the field. Xml2rfc will automatically use the day and month that it is run. The web version will use 2006 if is specified in = the file. dbh > -----Original Message----- > From: Miao Fuyou [mailto:miaofy@huawei.com] > Sent: Tuesday, March 13, 2007 8:42 PM > To: 'Alexander Clemm (alex)'; 'David Harrington'; syslog@ietf.org > Subject: RE: [Syslog] Note to editors >=20 > Hi, >=20 > I reckon this happens because the "date" in the "front" part of the=20 > XML file is not updated. >=20 > >=20 > Or you could use the web to do the conversion: xml.resource.org. >=20 > Regards, > Miao >=20 > > -----Original Message----- > > From: Alexander Clemm (alex) [mailto:alex@cisco.com] > > Sent: Wednesday, March 14, 2007 2:18 AM > > To: David Harrington; syslog@ietf.org > > Subject: RE: [Syslog] Note to editors > >=20 > > David, > >=20 > > I am using the xml2rfc tool, which inserts T Received: from xmb-sjc-236.amer.cisco.com ([128.107.191.121]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 16 Mar 2007 10:56:13 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Syslog] Note to editors Date: Fri, 16 Mar 2007 10:56:12 -0700 Message-ID: <85B2F271FDF6B949B3672BA5A7BB62FB0340AD3F@xmb-sjc-236.amer.cisco.com> In-Reply-To: <014c01c765ec$1a2ca850$0600a8c0@china.huawei.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Syslog] Note to editors Thread-Index: AcdlJ7P20IKko5mMS9iVpUqEkLlhxAAc4zTgAA16cVAABoe5oACCMAVA References: <85B2F271FDF6B949B3672BA5A7BB62FB0339F1C6@xmb-sjc-236.amer.cisco.com> <002801c765d1$a4489960$800c6f0a@china.huawei.com> <014c01c765ec$1a2ca850$0600a8c0@china.huawei.com> From: "Alexander Clemm \(alex\)" To: "David Harrington" , "Miao Fuyou" , X-OriginalArrivalTime: 16 Mar 2007 17:56:13.0733 (UTC) FILETIME=[63333550:01C767F4] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3036; t=1174067776; x=1174931776; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=alex@cisco.com; z=From:=20=22Alexander=20Clemm=20\(alex\)=22=20 |Subject:=20RE=3A=20[Syslog]=20Note=20to=20editors |Sender:=20; bh=HFxk/G47KyqKgBqzfLMt48Vnf8co+Q6np/6zvOHSTjc=; b=GLlCjGEFHkBZtr4k6ViS3HHq1tqSpt+rLBYDhhGR7VPTzVc1h/ecnVOAoG1T8p1iKdXdFul+ ipaMxs+IOJFCSfexk8pFuZlRXOVWYJHSfuqxVoWkiVvie65CjUupdHEw; Authentication-Results: sj-dkim-3; header.From=alex@cisco.com; dkim=pass (si g from cisco.com/sjdkim3002 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5 Cc: X-BeenThere: syslog@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Security Issues in Network Event Logging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: syslog-bounces@lists.ietf.org Well, the issue is fixed. =20 Turns out there is some strange behavior: I did have in the field, which generated the 2006 Copyright statement anyway. However, adding the day specifically (day=3D"15") did the trick. Go figure. =20 I just posted the updated draft, separate note to follow momentarily. =20 --- Alex -----Original Message----- From: David Harrington [mailto:ietfdbh@comcast.net]=20 Sent: Tuesday, March 13, 2007 8:52 PM To: 'Miao Fuyou'; Alexander Clemm (alex); syslog@ietf.org Subject: RE: [Syslog] Note to editors Hi, Actually, all you need to provide is the year in the field. Xml2rfc will automatically use the day and month that it is run. The web version will use 2006 if is specified in = the file. dbh > -----Original Message----- > From: Miao Fuyou [mailto:miaofy@huawei.com] > Sent: Tuesday, March 13, 2007 8:42 PM > To: 'Alexander Clemm (alex)'; 'David Harrington'; syslog@ietf.org > Subject: RE: [Syslog] Note to editors >=20 > Hi, >=20 > I reckon this happens because the "date" in the "front" part of the=20 > XML file is not updated. >=20 > >=20 > Or you could use the web to do the conversion: xml.resource.org. >=20 > Regards, > Miao >=20 > > -----Original Message----- > > From: Alexander Clemm (alex) [mailto:alex@cisco.com] > > Sent: Wednesday, March 14, 2007 2:18 AM > > To: David Harrington; syslog@ietf.org > > Subject: RE: [Syslog] Note to editors > >=20 > > David, > >=20 > > I am using the xml2rfc tool, which inserts these automatically. > > However, the copyright statement does show 2006, not 2007, when I=20 > > generate the draft now. > >=20 > > What would you like to do? It seems preferrable that IETF > should get > > xml2rfc updated. =20 > >=20 > > Thanks > > --- Alex > >=20 > > -----Original Message----- > > From: David Harrington [mailto:ietfdbh@comcast.net] > > Sent: Monday, March 12, 2007 9:30 PM > > To: syslog@ietf.org > > Subject: [Syslog] Note to editors > >=20 > > Hi, > >=20 > > We have crossed into 2007.=20 > >=20 > > Please make sure any copyrights in your document reflect 2007, not=20 > > 2006. > > This includes the standard copyright, but also internal copyrights=20 > > in MIB modules, etc. > >=20 > > Please make sure the IPR boilerplate and any other copyrights have=20 > > been updated to RFC 4748, which recognizes the IETF Trust. > >=20 > > Thanks, > > David Harrington > > dharrington@huawei.com > > dbharrington@comcast.net > > ietfdbh@comcast.net > >=20 > >=20 > >=20 > > _______________________________________________ > > Syslog mailing list > > Syslog@lists.ietf.org > > https://www1.ietf.org/mailman/listinfo/syslog > >=20 > > _______________________________________________ > > Syslog mailing list > > Syslog@lists.ietf.org > > https://www1.ietf.org/mailman/listinfo/syslog > >=20 >=20 >=20 >=20 _______________________________________________ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog these automatically. > > However, the copyright statement does show 2006, not 2007, when I=20 > > generate the draft now. > >=20 > > What would you like to do? It seems preferrable that IETF > should get > > xml2rfc updated. =20 > >=20 > > Thanks > > --- Alex > >=20 > > -----Original Message----- > > From: David Harrington [mailto:ietfdbh@comcast.net] > > Sent: Monday, March 12, 2007 9:30 PM > > To: syslog@ietf.org > > Subject: [Syslog] Note to editors > >=20 > > Hi, > >=20 > > We have crossed into 2007.=20 > >=20 > > Please make sure any copyrights in your document reflect 2007, not=20 > > 2006. > > This includes the standard copyright, but also internal copyrights=20 > > in MIB modules, etc. > >=20 > > Please make sure the IPR boilerplate and any other copyrights have=20 > > been updated to RFC 4748, which recognizes the IETF Trust. > >=20 > > Thanks, > > David Harrington > > dharrington@huawei.com > > dbharrington@comcast.net > > ietfdbh@comcast.net > >=20 > >=20 > >=20 > > _______________________________________________ > > Syslog mailing list > > Syslog@lists.ietf.org > > https://www1.ietf.org/mailman/listinfo/syslog > >=20 > > _______________________________________________ > > Syslog mailing list > > Syslog@lists.ietf.org > > https://www1.ietf.org/mailman/listinfo/syslog > >=20 >=20 >=20 >=20 _______________________________________________ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog From syslog-bounces@lists.ietf.org Mon Mar 19 10:52:52 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HTJC1-0003Yd-48; Mon, 19 Mar 2007 10:50:37 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HTJBw-0003M9-Mr; Mon, 19 Mar 2007 10:50:32 -0400 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HTJBw-0007fB-DR; Mon, 19 Mar 2007 10:50:32 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 575F62ACB4; Mon, 19 Mar 2007 14:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HTJBS-0005pe-3S; Mon, 19 Mar 2007 10:50:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Mon, 19 Mar 2007 10:50:02 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1 Cc: syslog@ietf.org Subject: [Syslog] I-D ACTION:draft-ietf-syslog-transport-udp-09.txt X-BeenThere: syslog@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Security Issues in Network Event Logging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: syslog-bounces@lists.ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Security Issues in Network Event Logging Working Group of the IETF. Title : Transmission of syslog messages over UDP Author(s) : A. Okmianski Filename : draft-ietf-syslog-transport-udp-09.txt Pages : 10 Date : 2007-3-19 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 implementers are required to support this transport mapping. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-syslog-transport-udp-09.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-syslog-transport-udp-09.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-syslog-transport-udp-09.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-3-19084952.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-syslog-transport-udp-09.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-syslog-transport-udp-09.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-3-19084952.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog --NextPart-- From syslog-bounces@lists.ietf.org Tue Mar 20 06:37:24 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HTbgL-0007ts-EG; Tue, 20 Mar 2007 06:35:09 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HTbgK-0007tf-A7 for syslog@ietf.org; Tue, 20 Mar 2007 06:35:08 -0400 Received: from hetzner.adiscon.com ([85.10.201.79]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HTbgJ-00047E-1X for syslog@ietf.org; Tue, 20 Mar 2007 06:35:08 -0400 Received: from localhost (localhost [127.0.0.1]) by hetzner.adiscon.com (Postfix) with ESMTP id 33A5D27C071; Tue, 20 Mar 2007 11:32:51 +0100 (CET) Received: from hetzner.adiscon.com ([127.0.0.1]) by localhost (hetzner [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 18277-03; Tue, 20 Mar 2007 11:32:51 +0100 (CET) Received: from fmint2.intern.adiscon.com (pd95b68d5.dip0.t-ipconnect.de [217.91.104.213]) by hetzner.adiscon.com (Postfix) with ESMTP id D942927C06E; Tue, 20 Mar 2007 11:32:50 +0100 (CET) Received: from grfint2.intern.adiscon.com ([172.19.0.6]) by fmint2.intern.adiscon.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 20 Mar 2007 11:34:53 +0100 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Syslog] draft-ietf-syslog-sign-21.txt X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Tue, 20 Mar 2007 11:34:41 +0100 Message-ID: <577465F99B41C842AAFBE9ED71E70ABA1F92AC@grfint2.intern.adiscon.com> In-Reply-To: <85B2F271FDF6B949B3672BA5A7BB62FB0340AD40@xmb-sjc-236.amer.cisco.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Syslog] draft-ietf-syslog-sign-21.txt Thread-Index: Acbc8+g/jZl4SDWATEChWON8ntejRg+UxBmAEysQjbAAufnt4A== References: <85B2F271FDF6B949B3672BA5A7BB62FB0340AD40@xmb-sjc-236.amer.cisco.com> From: "Rainer Gerhards" To: "Alexander Clemm (alex)" , X-OriginalArrivalTime: 20 Mar 2007 10:34:53.0302 (UTC) FILETIME=[65491960:01C76ADB] X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at adiscon.com X-Spam-Score: 0.1 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Cc: dbharrington@comcast.net X-BeenThere: syslog@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Security Issues in Network Event Logging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: syslog-bounces@lists.ietf.org I am finally back. I was distracted from some really urgent "physical world" local matters, sorry for the silence... > * Rainer had suggested to allow for 999 sig groups in case of SG=3D3, > instead of 192. While technically this would be possible, it appears > that it unnecessarily makes the implementation more complex because the > restriction (999 vs. 192) would become context dependent, as opposed to > context independent, with no real tangible benefit. I agree to this. 192 should be sufficient. Rainer _______________________________________________ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog From syslog-bounces@lists.ietf.org Tue Mar 20 15:52:29 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HTkMN-0003bd-2D; Tue, 20 Mar 2007 15:51:07 -0400 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HTkLr-00033r-BZ; Tue, 20 Mar 2007 15:50:36 -0400 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HTkLp-0005gv-40; Tue, 20 Mar 2007 15:50:35 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 9837B2ACBF; Tue, 20 Mar 2007 19:50:02 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HTkLK-0005uW-Am; Tue, 20 Mar 2007 15:50:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Tue, 20 Mar 2007 15:50:02 -0400 X-Spam-Score: -2.5 (--) X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6 Cc: syslog@ietf.org Subject: [Syslog] I-D ACTION:draft-ietf-syslog-sign-21.txt X-BeenThere: syslog@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Security Issues in Network Event Logging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: syslog-bounces@lists.ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Security Issues in Network Event Logging Working Group of the IETF. Title : Signed syslog Messages Author(s) : J. Kelsey, et al. Filename : draft-ietf-syslog-sign-21.txt Pages : 36 Date : 2007-3-20 This document describes a mechanism to add origin authentication, message integrity, replay resistance, message sequencing, and detection of missing messages to the transmitted syslog messages. This specification is intended to be used in conjunction with the work defined in RFC xxxx, "The syslog Protocol". A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-syslog-sign-21.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-syslog-sign-21.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-syslog-sign-21.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-3-20104457.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-syslog-sign-21.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-syslog-sign-21.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-3-20104457.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog --NextPart-- From necojp@citiz.net Sun Mar 25 23:27:13 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HVfrV-0008SX-5f for SYSLOG-ARCHIVE@LISTS.IETF.ORG; Sun, 25 Mar 2007 23:27:13 -0400 Received: from [221.210.37.138] (helo=a-net.ne.jp) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HVfrE-0005ie-Qz for SYSLOG-ARCHIVE@LISTS.IETF.ORG; Sun, 25 Mar 2007 23:27:13 -0400 Received: from zcvgls4 (unknown [165.5.39.57]) by smtp66 (Coremail) with SMTP id LdcyRhrFeSWOC9tY.1 for ; Mon, 26 Mar 2007 11:26:55 +0800 (CST) X-Originating-IP: [165.5.39.57] Subject: =?iso-2022-jp?B?GyRCM2QkakBaJEMkPyUrJXMlMSUkJHIkNDR1Sz4kRyQ5JCshKRsoQg==?= From: =?shift-jis?B?aW5mb3JtYXRpb24=?= To: X-Mailer: Microsoft Outlook Express MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-Spam-Score: 0.9 (/) X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22 それとも、本気の恋？ http://yokm.effers.com/celeb/ 当サイトなら、そのどちらもOKです！ まずはちょこっと覗いてみてください。 日本最大級のコミュニティスペース！ それが『恋の記念日』なのです。 ★いまなら無料ポイント発行中！ http://yokm.effers.com/celeb/ ┌─────────────────────── │ 配信停止はコチラまで。 │ DeliveryStop │ max@orange07.flnet.org │ │【配信停止手続きの際は】 │必ず件名に「配信停止」とお書き下さい。 │件名に「配信停止」と記載されていない場合は処理が行えません。 │尚、停止には数日間ほどお時間をいただく場合がございます。 │停止まで数日、数回メールが送信されることがございますが、 │何卒ご了承ください。 └─────────────────────── From necojp@citiz.net Mon Mar 26 03:01:15 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HVjCd-0007za-Qf for SYSLOG-ARCHIVE@LISTS.IETF.ORG; Mon, 26 Mar 2007 03:01:15 -0400 Received: from [221.210.38.100] (helo=a-net.ne.jp) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HVjCb-0004sW-Mr for SYSLOG-ARCHIVE@LISTS.IETF.ORG; Mon, 26 Mar 2007 03:01:15 -0400 Received: from cmkvduanlu3 (unknown [111.216.186.32]) by smtp82 (Coremail) with SMTP id nw7haqW3qhOYKD7o.1 for ; Mon, 26 Mar 2007 15:01:12 +0800 (CST) X-Originating-IP: [111.216.186.32] Subject: =?iso-2022-jp?B?GyRCJCpDTiRpJDtAX0RqGyhC?= From: =?shift-jis?B?aW5mb3JtYXRpb24=?= To: X-Mailer: Microsoft Outlook Express MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-Spam-Score: 3.6 (+++) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f いますぐ使える無料ポイントを発行しました。 http://yokm.effers.com/celeb/ ┌─────────────────────── │ 配信停止はコチラまで。 │ DeliveryStop │ max@orange07.flnet.org │ │【配信停止手続きの際は】 │必ず件名に「配信停止」とお書き下さい。 │件名に「配信停止」と記載されていない場合は処理が行えません。 │尚、停止には数日間ほどお時間をいただく場合がございます。 │停止まで数日、数回メールが送信されることがございますが、 │何卒ご了承ください。 └─────────────────────── From necojp@citiz.net Mon Mar 26 07:59:54 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HVnre-0005hW-Aj for SYSLOG-ARCHIVE@LISTS.IETF.ORG; Mon, 26 Mar 2007 07:59:54 -0400 Received: from [221.210.37.53] (helo=a-net.ne.jp) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HVnrZ-0008MV-VT for SYSLOG-ARCHIVE@LISTS.IETF.ORG; Mon, 26 Mar 2007 07:59:54 -0400 Received: from aftzqh1 (unknown [14.181.162.246]) by smtp78 (Coremail) with SMTP id fTDhA0FhpTwMd3NE.1 for ; Mon, 26 Mar 2007 19:59:48 +0800 (CST) X-Originating-IP: [14.181.162.246] Subject: =?iso-2022-jp?B?GyRCJCYhPCRzIUQbKEI=?= From: =?shift-jis?B?aW5mb3JtYXRpb24=?= To: X-Mailer: Microsoft Outlook Express MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-Spam-Score: 0.0 (/) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d 最近、トキめいてますか・・・？ 人生には、癒しが必要ですよね・・・ まずは、ココらでほっと一息つきましょうよ！ 頑張りすぎは、体に毒ですよ（´・ω・`） http://yokm.effers.com/celeb/ あ、いますぐ使える無料ポイントがいまなら発行中なので、 ちょろっと息抜きしちゃってください。 えっと、一応出会いの掲示板なんですけど、アナタ好みの 理想の方がきっと見つかるはずです！ …はずですとか弱気なこと意って、すみません… まずは無料ポイントを使って覗いてみてくださいッ！ ┌─────────────────────── │ 配信停止はコチラまで。 │ DeliveryStop │ max@orange07.flnet.org │ │【配信停止手続きの際は】 │必ず件名に「配信停止」とお書き下さい。 │件名に「配信停止」と記載されていない場合は処理が行えません。 │尚、停止には数日間ほどお時間をいただく場合がございます。 │停止まで数日、数回メールが送信されることがございますが、 │何卒ご了承ください。 └─────────────────────── From syslog-bounces@lists.ietf.org Sat Mar 31 12:17:25 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HXgFK-0005iE-OP; Sat, 31 Mar 2007 12:16:06 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HXgFJ-0005i9-Qr for syslog@ietf.org; Sat, 31 Mar 2007 12:16:05 -0400 Received: from rwcrmhc14.comcast.net ([204.127.192.84]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HXgFI-0004wr-Hu for syslog@ietf.org; Sat, 31 Mar 2007 12:16:05 -0400 Received: from harrington73653 (c-24-128-104-207.hsd1.nh.comcast.net[24.128.104.207]) by comcast.net (rwcrmhc14) with SMTP id <20070331161603m1400im6r8e>; Sat, 31 Mar 2007 16:16:03 +0000 From: "David Harrington" To: Date: Sat, 31 Mar 2007 12:15:20 -0400 Message-ID: <04d701c773af$da22c010$0600a8c0@china.huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 Thread-Index: Acdzr1e2kKfXE8smQJuIIqpRfG0I2g== X-Spam-Score: 0.0 (/) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 Cc: 'Sam Hartman' Subject: [Syslog] new scheduke X-BeenThere: syslog@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Security Issues in Network Event Logging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: syslog-bounces@lists.ietf.org Hi, Chris and I discussed a schedule, and this is what we would like to see accomplished. The protocol and tls docs should be republished within a week; These are the proposed final revisions of the document to be submitted to the rfc editor. Please speak up if you have **strong objection** to these technical specifications as written. sign and mib and bis have been published recently; we need WG reviews for these documents. Please review these documents asap. april - shepherd udp to rfc editor april - republish, final WG proof, then shepherd protocol to rfc editor april - republish, final WG proof, then shepherd tls to rfc editor april - WGLC for sign-21 april - submit sign to iesg april - WG review of mib-15 may - WGLC for mib-16 june - submit mib to iesg may - WG review for bis june - WGLC for bis july - submit bis to iesg Thanks, David Harrington dharrington@huawei.com dbharrington@comcast.net ietfdbh@comcast.net _______________________________________________ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog