From disman-bounces@ietf.org Tue Jan 6 19:38:55 2009 Return-Path: X-Original-To: disman-archive@megatron.ietf.org Delivered-To: ietfarch-disman-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D6F1E3A69AC; Tue, 6 Jan 2009 19:38:55 -0800 (PST) X-Original-To: disman@core3.amsl.com Delivered-To: disman@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 882F03A67AC for ; Tue, 6 Jan 2009 14:12:19 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.264 X-Spam-Level: X-Spam-Status: No, score=-1.264 tagged_above=-999 required=5 tests=[AWL=-0.123, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ltWkumdb5QtS for ; Tue, 6 Jan 2009 14:12:18 -0800 (PST) Received: from prattle.redback.com (prattle.redback.com [155.53.12.9]) by core3.amsl.com (Postfix) with ESMTP id BD3F03A6452 for ; Tue, 6 Jan 2009 14:12:18 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com (Postfix) with ESMTP id 2A41C5BAF8; Tue, 6 Jan 2009 14:12:06 -0800 (PST) Received: from prattle.redback.com ([127.0.0.1]) by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 20711-07; Tue, 6 Jan 2009 14:12:06 -0800 (PST) Received: from [155.53.44.238] (nurnberg.redback.com [155.53.44.238]) by prattle.redback.com (Postfix) with ESMTP id 129EB5BAF7; Tue, 6 Jan 2009 14:12:06 -0800 (PST) Message-ID: <4963D735.4@redback.com> Date: Tue, 06 Jan 2009 14:12:05 -0800 From: Michael Thatcher User-Agent: Thunderbird 2.0.0.6 (X11/20070728) MIME-Version: 1.0 To: disman@ietf.org Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at redback.com X-Mailman-Approved-At: Tue, 06 Jan 2009 19:38:54 -0800 Subject: [Disman] another error in the examples in rfc3877 X-BeenThere: disman@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Distributed Management List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: disman-bounces@ietf.org Errors-To: disman-bounces@ietf.org in section 6.1, the values given for alarmModelSpecificPointer and  ituAlarmGenericModel are, respectively, "ituAlarmEntry.x.y" and "alarmModelEntry.x.y".
However, alarmModelSpecificPointer and ituAlarmGenericModel are type RowPointer so they should point to the 1st available object in the row which are, respectively, ituAlarmEventType and alarmModelNotificationId.

miket
 From disman@audubon.org Fri Jan 9 09:04:39 2009 Return-Path: X-Original-To: ietfarch-disman-archive@core3.amsl.com Delivered-To: ietfarch-disman-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7FD733A6B36 for ; Fri, 9 Jan 2009 09:04:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -66.885 X-Spam-Level: X-Spam-Status: No, score=-66.885 tagged_above=-999 required=5 tests=[BAYES_80=2, FH_HOST_EQ_D_D_D_D=0.765, HELO_MISMATCH_COM=0.553, HTML_IMAGE_ONLY_04=2.041, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_1=0.001, MIME_HTML_ONLY=1.457, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, SARE_HTML_IMG_ONLY=1.666, SARE_SUB_ONLINE_DRUG=1.666, URIBL_SBL=20, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hnuHg8OZcFky for ; Fri, 9 Jan 2009 09:04:39 -0800 (PST) Received: from mta.email.webmd.com (ppp-94-69-170-27.home.otenet.gr [94.69.170.27]) by core3.amsl.com (Postfix) with SMTP id 9F2683A6881 for ; Fri, 9 Jan 2009 09:04:38 -0800 (PST) Message-ID: From: "Doctor Ruby" Reply-To: "WebMD " To: disman-archive@lists.ietf.org Subject: ruls #79836 Internet Online Drugstore oizr MIME-Version: 1.0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit Date: Fri, 9 Jan 2009 09:04:38 -0800 (PST)
From dislocate_psych@yahoo.co.jp Fri Jan 9 09:05:42 2009 Return-Path: X-Original-To: ietfarch-disman-archive@core3.amsl.com Delivered-To: ietfarch-disman-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 66EF23A69D7 for ; Fri, 9 Jan 2009 09:05:42 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -19.568 X-Spam-Level: X-Spam-Status: No, score=-19.568 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HOST_EQ_D_D_D_D=0.765, HELO_MISMATCH_COM=0.553, HOST_EQ_PL=1.95, HTML_IMAGE_ONLY_04=2.041, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_1=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, SARE_HTML_IMG_ONLY=1.666, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_SC_SURBL=10, URIBL_WS_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vErQuxSL3tZD for ; Fri, 9 Jan 2009 09:05:41 -0800 (PST) Received: from mta.email.webmd.com (ip-88-199-177-99.tczew.net.pl [88.199.177.99]) by core3.amsl.com (Postfix) with SMTP id 78FBD3A67EE for ; Fri, 9 Jan 2009 09:05:40 -0800 (PST) Content-Return: allowed X-Mailer: CME-V6.5.4.3; MSN Message-Id: <20090109070527.3691.qmail@mta.email.webmd.com> From: "Doctor William Lewis Terens, MD" To: disman-archive@ietf.org Subject:&&&&19067746 Sexual Health & Medicine &h&e MIME-Version: 1.0 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Date: Fri, 9 Jan 2009 09:05:40 -0800 (PST)
From disman-bounces@ietf.org Fri Jan 9 16:30:40 2009 Return-Path: X-Original-To: disman-archive@megatron.ietf.org Delivered-To: ietfarch-disman-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5AD9D28C130; Fri, 9 Jan 2009 16:30:40 -0800 (PST) X-Original-To: disman@core3.amsl.com Delivered-To: disman@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E2FBB28C130; Fri, 9 Jan 2009 16:30:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.571 X-Spam-Level: X-Spam-Status: No, score=-2.571 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tLQf3ItsYfNG; Fri, 9 Jan 2009 16:30:37 -0800 (PST) Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by core3.amsl.com (Postfix) with ESMTP id BC91C3A6767; Fri, 9 Jan 2009 16:30:37 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=akH8GhjMpgI7uFDIuo0WxyyQEX7KCf/zZl3cX6OLwTubgPJqzfc+BaaDOI8YKmO3; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP; Received: from [68.165.5.216] (helo=oemcomputer) by elasmtp-banded.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from ) id 1LLRk7-0005qQ-Ro; Fri, 09 Jan 2009 19:30:24 -0500 Message-ID: <001701c972bb$07177b40$6801a8c0@oemcomputer> From: "Randy Presuhn" To: "Disman" , , "LTRU Working Group" References: <20090108203120.GC29175@isi.edu> Date: Fri, 9 Jan 2009 16:33:14 -0800 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.1478 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478 X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8886924630f8852f173508c2e6a4479aa42046374945d92b3f8350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 68.165.5.216 Subject: [Disman] Fwd: RFC Errata Update for Working Group Chairs X-BeenThere: disman@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Distributed Management List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: disman-bounces@ietf.org Errors-To: disman-bounces@ietf.org Hi - Updated information on RFC errata .... Randy =========================================== From: RFC Editor Date: Thu, Jan 8, 2009 at 12:31 PM Subject: RFC Errata Update for Working Group Chairs To: wgchairs@ietf.org Cc: RFC Editor WG chairs, We have made some updates to the RFC errata system and would like to inform you of the new features and explain how these features may impact your working group. 1) We'd like to bring your attention to the improved search for RFC errata on http://www.rfc-editor.org/errata.php. You can search by WG acronym and other information. Please contact your Area Director if you find errata reports that need correction. For example, the Type (Editorial/Technical) may be incorrect. Area Directors can log in to verify errata in RFCs produced by the IETF stream, so if you want to to recommend that a report be Verified/Rejected/Held, then please let the relevant AD know. (For the meanings of Status and Type for RFC errata, please see http://www.rfc-editor.org/status_type_desc.html.) 2) Previously, the initial report message was sent to the authors of the RFC and the relevant WG chairs and ADs when the RFC was a product of a WG. The IESG has suggested that the WG mailing list be CC'ed on these messages, and we have implemented this feature. For example, grow@ietf.org would now be CC'ed on the message below. The idea is to notify the WG of the new report and potentially initiate a discussion of the validity of the report among those who are familiar with the content. This will allow the verifier to update the erratum so that its Status and Notes capture the conclusion of any discussion. Please distribute this information to your working groups as you see fit, and let us know if you have any comments or concerns. Thank you. RFC Editor From disman-bounces@ietf.org Fri Jan 9 16:35:36 2009 Return-Path: X-Original-To: disman-archive@megatron.ietf.org Delivered-To: ietfarch-disman-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CFC8E3A6B07; Fri, 9 Jan 2009 16:35:36 -0800 (PST) X-Original-To: disman@core3.amsl.com Delivered-To: disman@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7139A3A6A56 for ; Fri, 9 Jan 2009 16:35:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.649 X-Spam-Level: X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[AWL=-0.909, BAYES_20=-0.74] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LOc5oz0mtcJh for ; Fri, 9 Jan 2009 16:35:34 -0800 (PST) Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by core3.amsl.com (Postfix) with ESMTP id 1C7A93A6B07 for ; Fri, 9 Jan 2009 16:35:34 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=oYWsK9yHtn5anBI0NunZkje7smoja8f9SbEk4Tj/EoQFOu8plN8UwmLhn3TtafkU; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP; Received: from [68.165.5.216] (helo=oemcomputer) by elasmtp-banded.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from ) id 1LLRou-0002hW-Al for disman@ietf.org; Fri, 09 Jan 2009 19:35:20 -0500 Message-ID: <001b01c972bb$b96318e0$6801a8c0@oemcomputer> From: "Randy Presuhn" To: References: <4963D735.4@redback.com> Date: Fri, 9 Jan 2009 16:38:13 -0800 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.1478 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478 X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8886924630f8852f173b78a396c154bb03301d407fec1c01630350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 68.165.5.216 Subject: Re: [Disman] another error in the examples in rfc3877 X-BeenThere: disman@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Distributed Management List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: disman-bounces@ietf.org Errors-To: disman-bounces@ietf.org Hi - > From: "Michael Thatcher" > To: > Sent: Tuesday, January 06, 2009 2:12 PM > Subject: [Disman] another error in the examples in rfc3877 > > in section 6.1, the values given for alarmModelSpecificPointer and > ituAlarmGenericModel are, respectively, "ituAlarmEntry.x.y" and > "alarmModelEntry.x.y". > However, alarmModelSpecificPointer and ituAlarmGenericModel > are type RowPointer so they should point to the 1st available object > in the row which are, respectively, ituAlarmEventType and alarmModelNotificationId. ... My recollection (which may be faulty) was that this was deliberate, to illustrate the concept of the pointer, rather than the detail. While "ituAlarmEventType.x.y" might be more correct, I'm not sure that it's more enlightening. But I'd love to hear from the authors and folks who have (tried) to implement this spec. Randy From disman-bounces@ietf.org Fri Jan 9 17:16:48 2009 Return-Path: X-Original-To: disman-archive@megatron.ietf.org Delivered-To: ietfarch-disman-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 12E923A6B09; Fri, 9 Jan 2009 17:16:48 -0800 (PST) X-Original-To: disman@core3.amsl.com Delivered-To: disman@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D2C7E3A6B09 for ; Fri, 9 Jan 2009 17:16:46 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.984 X-Spam-Level: X-Spam-Status: No, score=-1.984 tagged_above=-999 required=5 tests=[AWL=0.615, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QTS3BB7ohCjn for ; Fri, 9 Jan 2009 17:16:46 -0800 (PST) Received: from prattle.redback.com (prattle.redback.com [155.53.12.9]) by core3.amsl.com (Postfix) with ESMTP id 2A3383A6767 for ; Fri, 9 Jan 2009 17:16:46 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by prattle.redback.com (Postfix) with ESMTP id CB68081F90B; Fri, 9 Jan 2009 17:16:32 -0800 (PST) Received: from prattle.redback.com ([127.0.0.1]) by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 07011-06; Fri, 9 Jan 2009 17:16:32 -0800 (PST) Received: from [155.53.44.238] (nurnberg.redback.com [155.53.44.238]) by prattle.redback.com (Postfix) with ESMTP id AB50A81F909; Fri, 9 Jan 2009 17:16:32 -0800 (PST) Message-ID: <4967F6F0.3020806@redback.com> Date: Fri, 09 Jan 2009 17:16:32 -0800 From: Michael Thatcher User-Agent: Thunderbird 2.0.0.6 (X11/20070728) MIME-Version: 1.0 To: Randy Presuhn References: <4963D735.4@redback.com> <001b01c972bb$b96318e0$6801a8c0@oemcomputer> In-Reply-To: <001b01c972bb$b96318e0$6801a8c0@oemcomputer> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at redback.com Cc: disman@ietf.org Subject: Re: [Disman] another error in the examples in rfc3877 X-BeenThere: disman@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Distributed Management List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: disman-bounces@ietf.org Errors-To: disman-bounces@ietf.org well the rfc says it's an "example". I expect the example to use valid values unless otherwise documented. Particularly when someone (like a test group) may use it to generate tests for validity. miket Randy Presuhn wrote: > Hi - > > >> From: "Michael Thatcher" >> To: >> Sent: Tuesday, January 06, 2009 2:12 PM >> Subject: [Disman] another error in the examples in rfc3877 >> >> in section 6.1, the values given for alarmModelSpecificPointer and >> ituAlarmGenericModel are, respectively, "ituAlarmEntry.x.y" and >> "alarmModelEntry.x.y". >> However, alarmModelSpecificPointer and ituAlarmGenericModel >> are type RowPointer so they should point to the 1st available object >> in the row which are, respectively, ituAlarmEventType and alarmModelNotificationId. >> > ... > > My recollection (which may be faulty) was that this was deliberate, to > illustrate the concept of the pointer, rather than the detail. While > "ituAlarmEventType.x.y" might be more correct, I'm not sure that > it's more enlightening. But I'd love to hear from the authors and > folks who have (tried) to implement this spec. > > Randy > > > From disman-bounces@ietf.org Tue Jan 13 21:56:57 2009 Return-Path: X-Original-To: disman-archive@megatron.ietf.org Delivered-To: ietfarch-disman-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E80FE3A6820; Tue, 13 Jan 2009 21:56:56 -0800 (PST) X-Original-To: disman@core3.amsl.com Delivered-To: disman@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E8A963A680D for ; Tue, 13 Jan 2009 21:56:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.215 X-Spam-Level: X-Spam-Status: No, score=-1.215 tagged_above=-999 required=5 tests=[AWL=-0.105, BAYES_05=-1.11] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GyC3QGJudVby for ; Tue, 13 Jan 2009 21:56:54 -0800 (PST) Received: from elasmtp-scoter.atl.sa.earthlink.net (elasmtp-scoter.atl.sa.earthlink.net [209.86.89.67]) by core3.amsl.com (Postfix) with ESMTP id A0BED3A6820 for ; Tue, 13 Jan 2009 21:56:54 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=JaRVnz5l/AYVYR3O6NBEzAkRE6jdg/5Hw/PBH2c4SHf+eZ4JHHN6tXtt5gv3ejoJ; h=Received:Message-ID:From:To:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP; Received: from [68.166.38.202] (helo=oemcomputer) by elasmtp-scoter.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from ) id 1LMyk3-00089o-PC for disman@ietf.org; Wed, 14 Jan 2009 00:56:40 -0500 Message-ID: <003101c9760d$4b879940$6801a8c0@oemcomputer> From: "Randy Presuhn" To: "Disman" Date: Tue, 13 Jan 2009 21:59:41 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1478 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478 X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8886924630f8852f1739b243beab43807f481c632c6444e46f0350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 68.166.38.202 Subject: [Disman] Fw: [Technical Errata Reported] RFC3877 (1652) X-BeenThere: disman@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Distributed Management List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: disman-bounces@ietf.org Errors-To: disman-bounces@ietf.org Hi - I'm not sure why this didn't automatically go to the disman mailing list, but here it is. Comments? Randy ----- Original Message ----- > From: "RFC Errata System" > To: ; ; ; ; > Cc: ; > Sent: Tuesday, January 13, 2009 8:23 PM > Subject: [Technical Errata Reported] RFC3877 (1652) > > > The following errata report has been submitted for RFC3877, > "Alarm Management Information Base (MIB)". > > -------------------------------------- > You may review the report below and at: > http://www.rfc-editor.org/errata_search.php?rfc=3877&eid=1652 > > -------------------------------------- > Type: Technical > Reported by: Brian Bidulock > > Section: 5.4 > > Original Text > ------------- > alarmModelState -> ituAlarmPerceivedSeverity 1 -> clear (1) 2 -> indeterminate (2) 3 -> warning (6) 4 -> minor (5) 5 -> major (4) 6 -> critical (3) > > Corrected Text > -------------- > alarmModelState -> ituAlarmPerceivedSeverity 1 -> clear (1) 2 -> warning (6) 3 -> indeterminate (2) 4 -> minor (5) 5 -> major (4) 6 -> critical (3) > > Notes > ----- > alarmModelState requires that the states be defined from less severe to more severe; however, under ITU-T PerceivedSeverity from ITU-T Rec. X.721 | ISO/IEC 10165-2 "indeterminate" is more severe than "warning". This change corrects the order to match the requirement for order of severity for alarmModelState. > > Instructions: > ------------- > This errata is currently posted as "Reported". If necessary, please > use "Reply All" to discuss whether it should be verified or > rejected. When a decision is reached, the verifying party (IESG) > can log in to change the status and edit the report, if necessary. > > -------------------------------------- > RFC3877 (draft-ietf-disman-alarm-mib-18) > -------------------------------------- > Title : Alarm Management Information Base (MIB) > Publication Date : September 2004 > Author(s) : S. Chisholm, D. Romascanu > Category : PROPOSED STANDARD > Source : Distributed Management > Area : Operations and Management > Stream : IETF > Verifying Party : IESG From disman-bounces@ietf.org Wed Jan 14 11:49:28 2009 Return-Path: X-Original-To: disman-archive@megatron.ietf.org Delivered-To: ietfarch-disman-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D7D5628C1E2; Wed, 14 Jan 2009 11:49:28 -0800 (PST) X-Original-To: disman@core3.amsl.com Delivered-To: disman@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DD8F03A686A for ; Wed, 14 Jan 2009 11:49:27 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.382 X-Spam-Level: X-Spam-Status: No, score=-2.382 tagged_above=-999 required=5 tests=[AWL=0.217, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZjiL6gOG3twY for ; Wed, 14 Jan 2009 11:49:27 -0800 (PST) Received: from elasmtp-scoter.atl.sa.earthlink.net (elasmtp-scoter.atl.sa.earthlink.net [209.86.89.67]) by core3.amsl.com (Postfix) with ESMTP id 8205B28C1F0 for ; Wed, 14 Jan 2009 11:49:26 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=L5UiojSQSptAVCPtHK1COtzKxDScwhM2sejga/GaAiVboJluXzl9H66IWdsh3myH; h=Received:Message-ID:From:To:Cc:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP; Received: from [66.167.204.246] (helo=oemcomputer) by elasmtp-scoter.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from ) id 1LNBjj-0005RA-EL; Wed, 14 Jan 2009 14:49:11 -0500 Message-ID: <007401c97681$99ebdc80$6801a8c0@oemcomputer> From: "Randy Presuhn" To: "Disman" References: <200901140423.n0E4N8cf018248@boreas.isi.edu> <6A65FDF4-AB43-4F1E-9D19-246A329B9254@isi.edu> Date: Wed, 14 Jan 2009 11:52:14 -0800 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.1478 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478 X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8886924630f8852f173d79a71d390d3d6f58e1426bf74861b5c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 66.167.204.246 Cc: Alice Hagens Subject: Re: [Disman] [Technical Errata Reported] RFC3877 (1652) X-BeenThere: disman@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Distributed Management List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: disman-bounces@ietf.org Errors-To: disman-bounces@ietf.org Hi - More errata. I don't know why this is not being automatically sent to the old WG mailing list. Randy > From: "Alice Hagens" > To: ; "Dan ((Dan)) Romascanu" ; "Ron Bonica" ; > Cc: ; "RFC Errata System" > Sent: Wednesday, January 14, 2009 9:49 AM > Subject: Re: [Technical Errata Reported] RFC3877 (1652) > > Please note that line breaks have been added to the Original/ > Corrected text of this report, as shown below and at: > http://www.rfc-editor.org/errata_search.php?rfc=3877&eid=1652 > > Type: Technical > Reported by: Brian Bidulock > > Section: 5.4 > > Original Text > ------------- > > alarmModelState -> ituAlarmPerceivedSeverity > 1 -> clear (1) > 2 -> indeterminate (2) > 3 -> warning (6) > 4 -> minor (5) > 5 -> major (4) > 6 -> critical (3) > > Corrected Text > -------------- > > alarmModelState -> ituAlarmPerceivedSeverity > 1 -> clear (1) > 2 -> warning (6) > 3 -> indeterminate (2) > 4 -> minor (5) > 5 -> major (4) > 6 -> critical (3) > > Notes > ----- > alarmModelState requires that the states be defined from less severe > to more severe; however, under ITU-T PerceivedSeverity from ITU-T > Rec. X.721 | ISO/IEC 10165-2 "indeterminate" is more severe than > "warning". This change corrects the order to match the requirement > for order of severity for alarmModelState. > > Thank you. > > RFC Editor/ah > > On Jan 13, 2009, at 8:23 PM, RFC Errata System wrote: > > > > > The following errata report has been submitted for RFC3877, > > "Alarm Management Information Base (MIB)". > > > > -------------------------------------- > > You may review the report below and at: > > http://www.rfc-editor.org/errata_search.php?rfc=3877&eid=1652 > > > > -------------------------------------- > > Type: Technical > > Reported by: Brian Bidulock > > > > Section: 5.4 > > > > Original Text > > ------------- > > alarmModelState -> ituAlarmPerceivedSeverity 1 - > > > clear (1) 2 -> indeterminate > > (2) 3 -> warning (6) 4 - > > > minor (5) 5 -> major (4) > > 6 -> critical (3) > > > > Corrected Text > > -------------- > > alarmModelState -> ituAlarmPerceivedSeverity 1 - > > > clear (1) 2 -> warning (6) > > 3 -> indeterminate (2) 4 -> > > minor (5) 5 -> major (4) 6 - > > > critical (3) > > > > Notes > > ----- > > alarmModelState requires that the states be defined from less > > severe to more severe; however, under ITU-T PerceivedSeverity from > > ITU-T Rec. X.721 | ISO/IEC 10165-2 "indeterminate" is more severe > > than "warning". This change corrects the order to match the > > requirement for order of severity for alarmModelState. > > > > Instructions: > > ------------- > > This errata is currently posted as "Reported". If necessary, please > > use "Reply All" to discuss whether it should be verified or > > rejected. When a decision is reached, the verifying party (IESG) > > can log in to change the status and edit the report, if necessary. > > > > -------------------------------------- > > RFC3877 (draft-ietf-disman-alarm-mib-18) > > -------------------------------------- > > Title : Alarm Management Information Base (MIB) > > Publication Date : September 2004 > > Author(s) : S. Chisholm, D. Romascanu > > Category : PROPOSED STANDARD > > Source : Distributed Management > > Area : Operations and Management > > Stream : IETF > > Verifying Party : IESG > From disman-bounces@ietf.org Wed Jan 14 11:54:09 2009 Return-Path: X-Original-To: disman-archive@megatron.ietf.org Delivered-To: ietfarch-disman-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2B31A28C1F2; Wed, 14 Jan 2009 11:54:09 -0800 (PST) X-Original-To: disman@core3.amsl.com Delivered-To: disman@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 229E028C1BB; Wed, 14 Jan 2009 11:54:08 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.413 X-Spam-Level: X-Spam-Status: No, score=-2.413 tagged_above=-999 required=5 tests=[AWL=0.186, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vNA57FL7lXge; Wed, 14 Jan 2009 11:54:07 -0800 (PST) Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by core3.amsl.com (Postfix) with ESMTP id BDD2B3A6A33; Wed, 14 Jan 2009 11:54:06 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=G7RZZdGRt0UKMTcPzZ57zchw5j0T6LHQDDxwbAuoIqg3wfv1vOJypFQmf8kZFiby; h=Received:Message-ID:From:To:Cc:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP; Received: from [66.167.204.246] (helo=oemcomputer) by elasmtp-banded.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from ) id 1LNBoF-0007dJ-Mr; Wed, 14 Jan 2009 14:53:52 -0500 Message-ID: <007d01c97682$424ae380$6801a8c0@oemcomputer> From: "Randy Presuhn" To: "LTRU Working Group" Date: Wed, 14 Jan 2009 11:56:56 -0800 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.1478 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478 X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8886924630f8852f1733045f6fe2ee56ae74d8a155e025816f2350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 66.167.204.246 Cc: agentx@ietf.org, Disman Subject: [Disman] Fw: ANNOUNCEMENT: The IETF Trustees invite your review and comments on a proposed Work-Around to the Pre-5378 Problem X-BeenThere: disman@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Distributed Management List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: disman-bounces@ietf.org Errors-To: disman-bounces@ietf.org Hi - Forwarded or your information. If you'd like to respond or discuss, please do so on the ietf@ietf.org list. Randy ----- Original Message ----- > From: "Russ Housley" > To: > Sent: Wednesday, January 14, 2009 8:00 AM > Subject: Re: ANNOUNCEMENT: The IETF Trustees invite your review and comments on a proposed Work-Around to the Pre-5378 Problem > > WG Chairs: > > Please make sure that your WG, and especially your document authors, > are aware of this situation. Please follow the discussion on the > IETF Discussion list, and keep the WG informed about the way forward > as it develops. > > Thanks, > Russ > > > >From: "Ed Juskevicius" > >To: "'IETF Discussion'" , , > > , , , > > > >Date: Thu, 8 Jan 2009 16:43:50 -0500 > >Cc: 'Trustees' > >Subject: [Trustees] ANNOUNCEMENT: The IETF Trustees invite your review and > > comments on a proposed Work-Around to the Pre-5378 Problem > > > >The purpose of this message is twofold: > > > >1) To summarize the issues that some members of our community > > have experienced since the publication of RFC 5378 in November 2008, > > and > >2) To invite community review and discussion on a potential work-around > > being considered by the IETF Trustees. > > > >Some I-D authors are having difficulty implementing RFC 5378. An > >example of the difficulty is as follows: > > > > - an author wants to include pre-5378 content in a new submission > > or contribution to the IETF, but > > - s/he is not certain that all of the author(s) of the earlier > > material have agreed to license it to the IETF Trust according > > to RFC 5378. > > > >If an I-D author includes pre-5378 material in a new document, then s/he > >must represent or warrant that all of the authors who created the > >pre-5378 material have granted rights for that material to the IETF Trust. > >If s/he cannot make this assertion, then s/he has a problem. > > > >This situation has halted the progression of some Internet-Drafts and > >interrupted the publication of some RFCs. The Trustees of the IETF Trust > >are investigating ways to implement a temporary work-around so that IETF > >work can continue to progress. A permanent solution to this "pre-5378 > >problem" may require an update to RFC 5378, for example new work by the > >community to create a 5378-bis document. > > > >The remainder of this message provides an outline of the temporary work- > >around being considered by the Trustees. > > > >RFC 5378 sections 1.j and 5.3.c provide the IETF Trust with the > >authority to develop legend text for authors to use in situations where > >they wish to limit the granting of rights to modify and prepare > >derivatives of the documents they submit. The Trustees used this > >authority in 2008 to develop and adopt the current "Legal Provisions > >Relating to IETF Documents" which are posted at: > >http://trustee.ietf.org/license-info/. > > > >The Trustees are now considering the creation of optional new legend text > >which could be used by authors experiencing the "pre-5378 problem". > > > >The new legend text, if implemented, would do the following: > > > > a. Provide Authors and Contributors with a way to identify (to the > > IETF Trust) that their contributions contain material from pre-5378 > > documents for which RFC 5378 rights to modify the material outside > > the IETF standards process may not have been granted, and > > > > b. Provide the IETF Trust and the community with a clear indication > > of every document containing pre-5378 content and having the > > "pre-5378 problem". > > > >So, how could the creation and use of some new legend text help people > >work-around the pre-5378 problem? > > > >The proposed answer is as follows: > > > > 1. Anyone having a contribution with the "pre-5378" problem should add > > new legend text to the contribution, to clearly flag that it includes > > pre-5378 material for which all of the rights needed under RFC 5378 > > may not have been granted, and > > > > 2. The IETF Trust will consider authors and contributors (with the > > pre-5378 problem) to have met their RFC 5378 obligations if the > > new legend text appears on their documents, and > > > > 3. Authors and contributors should only resort to adding the new > > legend text to their documents (per #1) if they cannot develop > > certainty that all of the author(s) of pre-5378 material in > > their documents have agreed to license the pre-5378 content to > > the IETF Trust according to RFC 5378. > > > >The proposed wording for the new legend text is now available for your > >review and comments in section 6.c.iii of a draft revision to the > >IETF Trust's "Legal Provisions Relating to IETF Documents" located at > >http://trustee.ietf.org/policyandprocedures.html. > > > >Please note that the above document also contains new text in section 5.c > >dealing with "License Limitations". > > > >If your review and feedback on this proposed work-around is positive, > >then the new text may be adopted by the Trustees in early February 2009, > >and then be published as an official revision to the Legal Provisions > >document. If so adopted, Internet-Drafts with pre-5378 material may > >advance within the Internet standards process and get published as RFCs > >where otherwise qualified to do so. Unless covered by sections 6.c.i or > >6.c.ii, authors of documents in which there is no pre-5378 > >material must provide a RFC 5378 license with no limitation on > >modifications outside the IETF standards process. > > > >The IETF Trust will not grant the right to modify or prepare derivative > >works of any specific RFC or other IETF Contribution outside the IETF > >standards process until RFC 5378 rights pertaining to that document have > >been obtained from all authors and after compliance by the IETF Trust > >with RFC 5377. The Trustees will establish one or more mechanisms by > >which authors of pre-5378 documents may grant RFC 5378 rights. > > > >The Trustees hereby invite your review, comments and suggestions on this > >proposed work-around to the "pre-5378 problem". The period for this review > >is 30 days. Microsoft WORD and PDF versions of the proposed revisions are > >attached to this message. Copies are also available on the IETF Trust > >website under the heading "DRAFT Policy and Procedures Being Developed" at: > >http://trustee.ietf.org/policyandprocedures.html > > > >All feedback submitted before the end of February 7th will be considered by > >the Trustees. A decision on whether to move forward with this proposal will > >be made and communicated to you before the end of February 15th. > > > >Please give this your attention. > > > >Regards and Happy New Year ! > > > >Ed Juskevicius, on behalf of the IETF Trustees > >edj.etc@gmail.com > From disman-bounces@ietf.org Wed Jan 14 16:25:10 2009 Return-Path: X-Original-To: disman-archive@megatron.ietf.org Delivered-To: ietfarch-disman-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DA1773A686A; Wed, 14 Jan 2009 16:25:08 -0800 (PST) X-Original-To: disman@core3.amsl.com Delivered-To: disman@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3F2113A67AE for ; Wed, 14 Jan 2009 16:25:07 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.95 X-Spam-Level: X-Spam-Status: No, score=-1.95 tagged_above=-999 required=5 tests=[AWL=0.649, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VX99nFNtlCsZ for ; Wed, 14 Jan 2009 16:25:04 -0800 (PST) Received: from elasmtp-kukur.atl.sa.earthlink.net (elasmtp-kukur.atl.sa.earthlink.net [209.86.89.65]) by core3.amsl.com (Postfix) with ESMTP id 65BB73A686A for ; Wed, 14 Jan 2009 16:25:04 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=VbLKIp4J40RWh5RSlUIPmFgs7AiQ232h2nFGVTvfQCobR6PeWBnpVHEZBoWPOa2e; h=Received:Message-ID:From:To:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP; Received: from [68.166.189.43] (helo=oemcomputer) by elasmtp-kukur.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from ) id 1LNG2T-0004pn-8x for disman@ietf.org; Wed, 14 Jan 2009 19:24:49 -0500 Message-ID: <000401c976a8$1c4c1020$6801a8c0@oemcomputer> From: "Randy Presuhn" To: "Disman" Date: Wed, 14 Jan 2009 16:27:54 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1478 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478 X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8886924630f8852f173d0adae8d528f83449d218e4d55a77cbe350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 68.166.189.43 Subject: [Disman] Fw: [Technical Errata Reported] RFC3877 (1652) X-BeenThere: disman@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Distributed Management List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: disman-bounces@ietf.org Errors-To: disman-bounces@ietf.org Hi - fwd fyi Randy ----- Original Message ----- > From: "Brian F. G. Bidulock" > To: "Alice Hagens" > Cc: ; "Dan ((Dan)) Romascanu" ; "Ron Bonica" ; ; "RFC Errata System" > Sent: Wednesday, January 14, 2009 1:44 PM > Subject: Re: [Technical Errata Reported] RFC3877 (1652) > > Alice, > > Thanks for the line breaks. It appeared fine on the preview > and when it was submitted it swallowed them. There was no > ability to edit after that... > > Also, the following is from GDMOs for ITU-T Rec. M.3100 (2005): > > alarmStatus ATTRIBUTE > WITH ATTRIBUTE SYNTAX ASN1DefinedTypesModule.AlarmStatus; > MATCHES FOR EQUALITY; > BEHAVIOUR > alarmStatusBehaviour BEHAVIOUR > DEFINED AS > "The Alarm Status attribute type indicates the > occurrence of an abnormal condition relating to an > object. This attribute may also function as a summary > indicator of alarm conditions associated with a > specific resource. It is used to indicate the > existence of an alarm condition, a pending alarm > condition such as threshold situations, or (when used > as a summary indicator) the highest severity of > active alarm conditions. When used as a summary > indicator, the order of severity (from highest to > lowest) is: > > activeReportable-Critical > activeReportable-Major > activeReportable-Minor > activeReportable-Indeterminate > activeReportable-Warning > activePending > cleared.";; > REGISTERED AS { m3100Attribute 6 }; > > --brian > > On Wed, 14 Jan 2009, Alice Hagens wrote: > > > Please note that line breaks have been added to the Original/ > > Corrected text of this report, as shown below and at: > > http://www.rfc-editor.org/errata_search.php?rfc=3877&eid=1652 > > > > Type: Technical > > Reported by: Brian Bidulock > > > > Section: 5.4 > > > > Original Text > > ------------- > > > > alarmModelState -> ituAlarmPerceivedSeverity > > 1 -> clear (1) > > 2 -> indeterminate (2) > > 3 -> warning (6) > > 4 -> minor (5) > > 5 -> major (4) > > 6 -> critical (3) > > > > Corrected Text > > -------------- > > > > alarmModelState -> ituAlarmPerceivedSeverity > > 1 -> clear (1) > > 2 -> warning (6) > > 3 -> indeterminate (2) > > 4 -> minor (5) > > 5 -> major (4) > > 6 -> critical (3) > > > > Notes > > ----- > > alarmModelState requires that the states be defined from less severe > > to more severe; however, under ITU-T PerceivedSeverity from ITU-T > > Rec. X.721 | ISO/IEC 10165-2 "indeterminate" is more severe than > > "warning". This change corrects the order to match the requirement > > for order of severity for alarmModelState. > > > > Thank you. > > > > RFC Editor/ah > > > > On Jan 13, 2009, at 8:23 PM, RFC Errata System wrote: > > > > > > > >The following errata report has been submitted for RFC3877, > > >"Alarm Management Information Base (MIB)". > > > > > >-------------------------------------- > > >You may review the report below and at: > > >http://www.rfc-editor.org/errata_search.php?rfc=3877&eid=1652 > > > > > >-------------------------------------- > > >Type: Technical > > >Reported by: Brian Bidulock > > > > > >Section: 5.4 > > > > > >Original Text > > >------------- > > >alarmModelState -> ituAlarmPerceivedSeverity 1 - > > >> clear (1) 2 -> indeterminate > > >(2) 3 -> warning (6) 4 - > > >> minor (5) 5 -> major (4) > > >6 -> critical (3) > > > > > >Corrected Text > > >-------------- > > >alarmModelState -> ituAlarmPerceivedSeverity 1 - > > >> clear (1) 2 -> warning (6) > > >3 -> indeterminate (2) 4 -> > > >minor (5) 5 -> major (4) 6 - > > >> critical (3) > > > > > >Notes > > >----- > > >alarmModelState requires that the states be defined from less > > >severe to more severe; however, under ITU-T PerceivedSeverity from > > >ITU-T Rec. X.721 | ISO/IEC 10165-2 "indeterminate" is more severe > > >than "warning". This change corrects the order to match the > > >requirement for order of severity for alarmModelState. > > > > > >Instructions: > > >------------- > > >This errata is currently posted as "Reported". If necessary, please > > >use "Reply All" to discuss whether it should be verified or > > >rejected. When a decision is reached, the verifying party (IESG) > > >can log in to change the status and edit the report, if necessary. > > > > > >-------------------------------------- > > >RFC3877 (draft-ietf-disman-alarm-mib-18) > > >-------------------------------------- > > >Title : Alarm Management Information Base (MIB) > > >Publication Date : September 2004 > > >Author(s) : S. Chisholm, D. Romascanu > > >Category : PROPOSED STANDARD > > >Source : Distributed Management > > >Area : Operations and Management > > >Stream : IETF > > >Verifying Party : IESG > > -- > Brian F. G. Bidulock ¦ The reasonable man adapts himself to the ¦ > bidulock@openss7.org ¦ world; the unreasonable one persists in ¦ > http://www.openss7.org/ ¦ trying to adapt the world to himself. ¦ > ¦ Therefore all progress depends on the ¦ > ¦ unreasonable man. -- George Bernard Shaw ¦ From disman-bounces@ietf.org Wed Jan 14 16:45:22 2009 Return-Path: X-Original-To: disman-archive@megatron.ietf.org Delivered-To: ietfarch-disman-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 044523A6AB4; Wed, 14 Jan 2009 16:45:22 -0800 (PST) X-Original-To: disman@core3.amsl.com Delivered-To: disman@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4F8683A6A93; Wed, 14 Jan 2009 16:45:21 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.05 X-Spam-Level: X-Spam-Status: No, score=-2.05 tagged_above=-999 required=5 tests=[AWL=0.549, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 88LaItV9IvSF; Wed, 14 Jan 2009 16:45:20 -0800 (PST) Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) by core3.amsl.com (Postfix) with ESMTP id 7C9473A6963; Wed, 14 Jan 2009 16:45:20 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=OO6Zmh4ER7QZ4XVPLKSXrkSIaevqx7Bm4E8nfuUCDLXCQpN2xVE3/Tfmkvo8oeYc; h=Received:Message-ID:From:To:Cc:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP; Received: from [68.166.189.43] (helo=oemcomputer) by elasmtp-mealy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from ) id 1LNGM5-0004XO-JH; Wed, 14 Jan 2009 19:45:05 -0500 Message-ID: <005701c976aa$f19bb080$6801a8c0@oemcomputer> From: "Randy Presuhn" To: "LTRU Working Group" References: <007d01c97682$424ae380$6801a8c0@oemcomputer> Date: Wed, 14 Jan 2009 16:48:11 -0800 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.1478 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478 X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d8886924630f8852f1733c1ad1aef096d70b21be0e6f8bc5fe25350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 68.166.189.43 Cc: agentx@ietf.org, Disman Subject: Re: [Disman] [Ltru] Fw: ANNOUNCEMENT: The IETF Trustees invite your review andcomments on a proposed Work-Around to the Pre-5378 Problem X-BeenThere: disman@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Distributed Management List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: disman-bounces@ietf.org Errors-To: disman-bounces@ietf.org Hi - In case you haven't been following the discussion, here's a helpful distillation by Marshall Eubanks: The WG Chairs have been asked to make their WG aware of this issue. This is a complicated subject, but the executive summary is that if you have an Internet-draft that quotes substantially from one or more older RFCs (ones with a publication date pre-November 11, 2008), and you did not write this earlier work yourself (or you wrote it while with another company), you need to be aware of the likely difficulty of obtaining RFC5378 clearances for your new work, and also to be aware that a work-around is on the way. The work-around should be in place to allow submissions to the San Francisco IETF well before the normal deadlines. Again, please direct any followup discussion to ietf@ietf.org Randy From onea@alignmark.com Thu Jan 15 18:58:43 2009 Return-Path: X-Original-To: ietfarch-disman-archive@core3.amsl.com Delivered-To: ietfarch-disman-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5CC7C3A63EC for ; Thu, 15 Jan 2009 18:58:43 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -13.623 X-Spam-Level: X-Spam-Status: No, score=-13.623 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, FM_DDDD_TIMES_2=1.999, GB_I_LETTER=-2, HELO_DYNAMIC_HCC=4.295, HELO_DYNAMIC_IPADDR2=4.395, HELO_EQ_BR=0.955, HELO_EQ_DSL=1.129, HELO_EQ_TELESP=1.245, HOST_EQ_BR=1.295, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_3=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_PBL=0.905, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, SARE_RECV_SPAM_DOMN02=1.666, SARE_UNI=0.591, TVD_RCVD_IP=1.931, URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SA97iZwIEne7 for ; Thu, 15 Jan 2009 18:58:37 -0800 (PST) Received: from 189-47-114-141.dsl.telesp.net.br (189-47-114-141.dsl.telesp.net.br [189.47.114.141]) by core3.amsl.com (Postfix) with SMTP id 8A8A73A67D4 for ; Thu, 15 Jan 2009 18:58:36 -0800 (PST) To: Subject: from admin From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20090116025836.8A8A73A67D4@core3.amsl.com> Date: Thu, 15 Jan 2009 18:58:36 -0800 (PST)
About this mailing:
You are receiving this e-mail because you subscribed to MSN Featured Offers. Microsoft respects your privacy. If you do not wish to receive this MSN Featured Offers e-mail, please click the "Unsubscribe" link below. This will not unsubscribe you from e-mail communications from third-party advertisers that may appear in MSN Feature Offers. This shall not constitute an offer by MSN. MSN shall not be responsible or liable for the advertisers' content nor any of the goods or service advertised. Prices and item availability subject to change without notice.

©2008 Microsoft | Unsubscribe | More Newsletters | Privacy

Microsoft Corporation, One Microsoft Way, Redmond, WA 39997
From mail@agence-plage.com Fri Jan 23 04:58:56 2009 Return-Path: X-Original-To: ietfarch-disman-archive@core3.amsl.com Delivered-To: ietfarch-disman-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4FE343A68BC for ; Fri, 23 Jan 2009 04:58:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -64.314 X-Spam-Level: X-Spam-Status: No, score=-64.314 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, FM_DDDD_TIMES_2=1.999, GB_I_LETTER=-2, HELO_DYNAMIC_IPADDR2=4.395, HTML_IMAGE_ONLY_32=1.778, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RCVD_IN_XBL=3.033, RDNS_DYNAMIC=0.1, TVD_RCVD_IP=1.931, URIBL_JP_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3DIGOzT3pd+v for ; Fri, 23 Jan 2009 04:58:55 -0800 (PST) Received: from 140-69-124-91.pool.ukrtel.net (140-69-124-91.pool.ukrtel.net [91.124.69.140]) by core3.amsl.com (Postfix) with SMTP id 7EB9D3A6867 for ; Fri, 23 Jan 2009 04:58:48 -0800 (PST) To: Subject: InterScan MSS Notification From: MIME-Version: 1.0 Importance: High Content-Type: text/html Message-Id: <20090123125851.7EB9D3A6867@core3.amsl.com> Date: Fri, 23 Jan 2009 04:58:48 -0800 (PST)
We ship Worldwide! To all countries! To all destinations!
Click Here!

To unsubscribe from this mailing list, please log in to www.achievementsmell.com, click on "My Account", click "Update" to edit your registration details and uncheck the "Receive Newsletter?" check box.
Or unsubscribe at http://achievementsmell.com/faq.php

Privacy Statement | Terms & Conditions | Contact

BRANDKEYWORD Ltd.
Tower Bridge Business Complex. Unit 3, B194. 045 Clements Road. London. SE94 5DG

© 2006-2009 BRANDKEYWORD, Ltd. All Rights Reserved

From dismas1@rocketmail.com Fri Jan 30 01:29:37 2009 Return-Path: X-Original-To: ietfarch-disman-archive@core3.amsl.com Delivered-To: ietfarch-disman-archive@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9734C3A68F8 for ; Fri, 30 Jan 2009 01:29:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -30.636 X-Spam-Level: X-Spam-Status: No, score=-30.636 tagged_above=-999 required=5 tests=[BAYES_99=3.5, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, GB_H_CANADIAN=0.5, GB_H_PHARMACY=1, GB_PHARMACY=1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, HTML_SHORT_LINK_IMG_3=0.001, MIME_HTML_ONLY=1.457, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E4_51_100=1.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.1, URIBL_BLACK=20, URIBL_JP_SURBL=10, URIBL_OB_SURBL=10, URIBL_SC_SURBL=10, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rx1kxFgZFkbB for ; Fri, 30 Jan 2009 01:29:33 -0800 (PST) Received: from amerblind.outbound.ed10.com (209-154-112-92.pool.ukrtel.net [92.112.154.209]) by core3.amsl.com (Postfix) with SMTP id 8B86F3A6768 for ; Fri, 30 Jan 2009 01:29:32 -0800 (PST) Content-Return: allowed X-Mailer: devMail.Net (3.0.1854.22234-2) To: disman-archive@ietf.org Subject: RE: Canadian Pharmacy Message 6702962 From: disman-archive@ietf.org MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: 7bit Message-Id: <20090130092932.8B86F3A6768@core3.amsl.com> Date: Fri, 30 Jan 2009 01:29:32 -0800 (PST)