From owner-snmpv3@lists.tislabs.com Wed Nov 5 23:27:01 2003 Received: from lists.tislabs.com (portal.tislabs.com [192.94.214.101]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA09572 for ; Wed, 5 Nov 2003 23:27:01 -0500 (EST) Received: by lists.tislabs.com (8.9.1/8.9.1) id WAA26279 Wed, 5 Nov 2003 22:12:33 -0500 (EST) To: ietf@ietf.org Cc: snmpv3@lists.tislabs.com Subject: BOF Announcement: A Session-based Security Model for SNMP From: Wes Hardaker Organization: Sparta Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAGFBMVEXotKX87e8eDA4GAQbQgmlzNycHAwizYkruzul2AAACaUlEQVR4nFXUTW/jIBAGYFI56jWutuq1S9b2dddW6dWtQFxbq4jzwq73Glmg+fv7DiT9QJGS+GEGhiER67TWEQ5CtOeh21ZcIIbmOPq5QvMZYlyV6u+/gsJLTSrGIL/CxEPxQuPAcP0JYlQsq3x5B3UJmUaEyB6yZ+CQ+pwXCzKsbXtbIhg4KtZypPz+AVGtlxH69c87qAqRY6Rc5QUmZMGeAj+TfVjjUwE1lflKys5JGXpM+V0hltqCJ0qL7Plkft4wRM6lxi5p3Wyy7O7fB8TgtdZivxy5rvAB6wSYhbA9vn+GOCaOEGJRPO2mHgk+q1Chyf0Up3AG0NjhOXI19ogEFziq6M+ZtN3kUZ13NW4qUCprC3CW668C06M5jihON1Vsjq8F1CPJB8LINNeQfscwxUEvAwM5Xghvsq2pBr3hnKhbDIrMS3cBRDx70uS9JW2dy667gM0AbZFFmyvn3GOBGB8wG9kppaSNz357LaCmUdtSny5LU9qeCrglvJmyH20TwkjnXQE0usscIWayCWZJ7OpZ4QbUVGRnhuTub3cMYRk99oSplDIfibzfn0FyXyk7z8XThuvC0P/dGCwee7O8aZJBmh0vPixy0NrYhDaR02aR3W0BbyT6h23OB5Hzybj+DOm5w6XCOZG13p5Oh/bursJVh9S+bBiFnPCDuntpcTH080AO+7GlW1i3bRphBM04dZ2dI6yMLjmGFqnIok/cB1YU8sJAACTeuHOd5+lumQHfDM6KyLqEm4aWkkcc1m4PqBewZxBZOg44lT+aJiexDteewboiVhxAjSHxQwhiYJEdCR6tMN1/uckirDRNbsgAAAAASUVORK5CYII= Date: Wed, 05 Nov 2003 19:21:48 -0800 Message-ID: User-Agent: Gnus/5.1003 (Gnus v5.10.3) XEmacs/21.5 (brussels sprouts, linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-snmpv3@lists.tislabs.com Precedence: bulk Session Based Security Model for SNMPv3 BOF (sbsm) Wednesday, November 12 at 1530-1730 ================================== BOF CHAIRS: Wes Hardaker David Perkins READING MATERIAL: draft-hardaker-snmp-session-sm-00.txt From the Abstract: This document describes a Session Based Security Model (SBSM) for use within the Simple Network Management Protocol (SNMP). The security model is designed to establish a "session" between two interacting hosts, over which SNMP operations can be sent. It provides a number of security properties not previously available in [currently] defined SNMP security models, such as public key based authentication, limited life-time keying, and the ability to make use of previously implemented and deployed security infrastructures for purposes of identification and authentication. AGENDA: Draft agenda for the BOF: ---------------------------------------------------------------------- Agenda Bashing 5 min Introduction to the problem space 10 min draft-hardaker-snmp-session-sm-00.txt 20 min Discussion remaining time Mailing Lists: sbsm@machshav.com To (un)subscribe: sbsm-request@machshav.com Archive and general information: https://www.machshav.com/mailman/listinfo/sbsm Description of Working Group: The SBSM working group will focus on creating a new session-based security model [for SNMPv3] that will meet the security and operational needs of network administrators. Work Items - A document describing a session-based security model for the SNMPv3's protocol. Goals and Milestones: Mar 04 Initial draft(s) defining the SBSM security model to be completed so reference implementations can begin. Nov 04 Work submitted to the IESG to publish as a proposed standard RFC. -- Wes Hardaker Sparta From owner-snmpv3@lists.tislabs.com Mon Nov 10 05:25:44 2003 Received: from lists.tislabs.com (portal.gw.tislabs.com [192.94.214.101]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA14939 for ; Mon, 10 Nov 2003 05:25:44 -0500 (EST) Received: by lists.tislabs.com (8.9.1/8.9.1) id EAA26193 Mon, 10 Nov 2003 04:14:49 -0500 (EST) Reply-To: From: "Kamaraj P" To: "'Snmpv3-wg (E-mail)'" Subject: Clarification in SNMPv3 standard VACM mib Date: Mon, 10 Nov 2003 14:58:36 +0530 Message-ID: <002601c3a76d$0566c180$6704060a@future.futsoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 In-Reply-To: <7D5D48D2CAA3D84C813F5B154F43B15502C833AA@nl0006exch001u.nl.lucent.com> Importance: Normal Sender: owner-snmpv3@lists.tislabs.com Precedence: bulk Content-Transfer-Encoding: 7bit Hi All, I am compiling Standard VACM mib ( RFC 3415) with LIBSMI Tool. Iam getting this compilation error " 1. index element `vacmViewTreeFamilySubtree' of row `vacmViewTreeFamilyEntry' should but cannot have a size restriction 2. index of row `vacmViewTreeFamilyEntry' can exceed OID size limit by 46 subidentifier(s) " Whether this compilation error can be ignored or the standard mib should be updated (RFC 3415) ... Thanks In Advance Regards, Kamaraj *************************************************************************** This message is proprietary to Future Software Limited (FSL) and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. FSL accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus. *************************************************************************** From owner-snmpv3@lists.tislabs.com Mon Nov 10 12:32:54 2003 Received: from lists.tislabs.com (portal.gw.tislabs.com [192.94.214.101]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02223 for ; Mon, 10 Nov 2003 12:32:53 -0500 (EST) Received: by lists.tislabs.com (8.9.1/8.9.1) id LAA09501 Mon, 10 Nov 2003 11:13:51 -0500 (EST) Date: Mon, 10 Nov 2003 17:23:19 +0100 Message-Id: <200311101623.hAAGNJoQ006432@hansa.ibr.cs.tu-bs.de> From: Juergen Schoenwaelder To: kamarajp@future.futsoft.com CC: snmpv3@lists.tislabs.com In-reply-to: <002601c3a76d$0566c180$6704060a@future.futsoft.com> (kamarajp@future.futsoft.com) Subject: Re: Clarification in SNMPv3 standard VACM mib References: <002601c3a76d$0566c180$6704060a@future.futsoft.com> X-IBRFilter-SpamReport: 0 () X-Scanned-By: MIMEDefang 2.24 (www . roaringpenguin . com / mimedefang) Sender: owner-snmpv3@lists.tislabs.com Precedence: bulk >>>>> Kamaraj P writes: Kamaraj> Hi All, I am compiling Standard VACM mib ( RFC 3415) with Kamaraj> LIBSMI Tool. Iam getting this compilation error [...] Not all messages produced by smilint are errors - see the smilint(1) manual page for a description of the error levels and their meaning. There is in fact nothing wrong with the MIB in RFC 3415. /js -- Juergen Schoenwaelder International University Bremen P.O. Box 750 561, 28725 Bremen, Germany From owner-snmpv3@lists.tislabs.com Mon Nov 10 13:37:57 2003 Received: from lists.tislabs.com (portal.tislabs.com [192.94.214.101]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04774 for ; Mon, 10 Nov 2003 13:37:57 -0500 (EST) Received: by lists.tislabs.com (8.9.1/8.9.1) id MAA11104 Mon, 10 Nov 2003 12:00:31 -0500 (EST) Date: Mon, 10 Nov 2003 09:10:02 -0800 (PST) From: "David T. Perkins" X-Sender: dperkins@shell4.bayarea.net To: Kamaraj P cc: "'Snmpv3-wg (E-mail)'" Subject: Re: Clarification in SNMPv3 standard VACM mib In-Reply-To: <002601c3a76d$0566c180$6704060a@future.futsoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-snmpv3@lists.tislabs.com Precedence: bulk HI, It's not a problem. You just need to set the checking level the to appropriate value. On Mon, 10 Nov 2003, Kamaraj P wrote: > Hi All, > I am compiling Standard VACM mib ( RFC 3415) with LIBSMI Tool. > Iam getting this compilation error > " > 1. index element `vacmViewTreeFamilySubtree' of row > `vacmViewTreeFamilyEntry' should but cannot have a size restriction > 2. index of row `vacmViewTreeFamilyEntry' can exceed OID size limit by 46 > subidentifier(s) " > > Whether this compilation error can be ignored or the standard mib should be > updated (RFC 3415) ... > > Thanks In Advance > Regards, > Kamaraj Regards, /david t. perkins From owner-snmpv3@lists.tislabs.com Wed Nov 12 21:50:34 2003 Received: from lists.tislabs.com (portal.gw.tislabs.com [192.94.214.101]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23602 for ; Wed, 12 Nov 2003 21:50:33 -0500 (EST) Received: by lists.tislabs.com (8.9.1/8.9.1) id UAA12729 Wed, 12 Nov 2003 20:43:20 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: SBSM Date: Wed, 12 Nov 2003 20:52:32 -0500 Message-ID: <6D745637A7E0F94DA070743C55CDA9BA011399B6@NHROCMBX1.ets.enterasys.com> Thread-Topic: SBSM Thread-Index: AcOpZ/igUsSCRYM5SpSC+lug3/N01Q== From: "Harrington, David" To: X-OriginalArrivalTime: 13 Nov 2003 01:52:32.0973 (UTC) FILETIME=[CDCA27D0:01C3A988] X-pstn-version: pmps:sps_win32_1_1_0c1 pase:2.0 X-pstn-levels: (C:80.8653 M:99.5542 P:95.9108 R:95.9108 S:29.3479 ) X-pstn-settings: 4 (0.2500:0.7500) p:13 m:13 C:14 r:13 X-pstn-addresses: from forward (org good) Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by lists.tislabs.com id UAA12726 Sender: owner-snmpv3@lists.tislabs.com Precedence: bulk Content-Transfer-Encoding: 8bit Hi, During identity sharing, it was decided that it was better for the agent to identify and authenticate itself before the manager identified itself. Can you explain the thinking behind that design decision? dbh David Harrington dbh@enterasys.com Director, Network Management Architecture Office of the CTO, Enterasys Networks From owner-snmpv3@lists.tislabs.com Thu Nov 13 04:58:57 2003 Received: from lists.tislabs.com (portal.gw.tislabs.com [192.94.214.101]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18831 for ; Thu, 13 Nov 2003 04:58:57 -0500 (EST) Received: by lists.tislabs.com (8.9.1/8.9.1) id DAA25480 Thu, 13 Nov 2003 03:56:27 -0500 (EST) Reply-To: From: "Kamaraj P" To: "'David T. Perkins'" Cc: "'Snmpv3-wg (E-mail)'" , "'Senthil Gurusamy'" Subject: RE: Clarification in SNMPv3 standard VACM mib Date: Thu, 13 Nov 2003 14:39:30 +0530 Message-ID: <000201c3a9c5$d976d140$6704060a@future.futsoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Importance: Normal In-Reply-To: Sender: owner-snmpv3@lists.tislabs.com Precedence: bulk Content-Transfer-Encoding: 7bit Thanks for your response. How can I get rid of this warnings ? Thanks in Advance Regards, Kamaraj -----Original Message----- From: owner-snmpv3@lists.tislabs.com [mailto:owner-snmpv3@lists.tislabs.com]On Behalf Of David T. Perkins Sent: Monday, November 10, 2003 10:40 PM To: Kamaraj P Cc: 'Snmpv3-wg (E-mail)' Subject: Re: Clarification in SNMPv3 standard VACM mib HI, It's not a problem. You just need to set the checking level the to appropriate value. On Mon, 10 Nov 2003, Kamaraj P wrote: > Hi All, > I am compiling Standard VACM mib ( RFC 3415) with LIBSMI Tool. > Iam getting this compilation error > " > 1. index element `vacmViewTreeFamilySubtree' of row > `vacmViewTreeFamilyEntry' should but cannot have a size restriction > 2. index of row `vacmViewTreeFamilyEntry' can exceed OID size limit by 46 > subidentifier(s) " > > Whether this compilation error can be ignored or the standard mib should be > updated (RFC 3415) ... > > Thanks In Advance > Regards, > Kamaraj Regards, /david t. perkins *************************************************************************** This message is proprietary to Future Software Limited (FSL) and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. FSL accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus. *************************************************************************** From owner-snmpv3@lists.tislabs.com Thu Nov 13 05:47:55 2003 Received: from lists.tislabs.com (portal.gw.tislabs.com [192.94.214.101]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA20099 for ; Thu, 13 Nov 2003 05:47:54 -0500 (EST) Received: by lists.tislabs.com (8.9.1/8.9.1) id EAA27037 Thu, 13 Nov 2003 04:48:31 -0500 (EST) Date: Thu, 13 Nov 2003 10:57:57 +0100 Message-Id: <200311130957.hAD9vvhv031684@hansa.ibr.cs.tu-bs.de> From: Juergen Schoenwaelder To: kamarajp@future.futsoft.com CC: snmpv3@lists.tislabs.com In-reply-to: <000201c3a9c5$d976d140$6704060a@future.futsoft.com> (kamarajp@future.futsoft.com) Subject: Re: Clarification in SNMPv3 standard VACM mib References: <000201c3a9c5$d976d140$6704060a@future.futsoft.com> X-IBRFilter-SpamReport: 0 () X-Scanned-By: MIMEDefang 2.24 (www . roaringpenguin . com / mimedefang) Sender: owner-snmpv3@lists.tislabs.com Precedence: bulk >>>>> Kamaraj P writes: Kamaraj> Thanks for your response. How can I get rid of this warnings Kamaraj> ? This is really off-topic for this list. Anyway, I suggest you read the smilint(1) manual page - you may also want to read the smi_config(3) page which explains how you can actually modify the error/warning level at the message granularity. /js -- Juergen Schoenwaelder International University Bremen P.O. Box 750 561, 28725 Bremen, Germany From owner-snmpv3@lists.tislabs.com Thu Nov 13 22:48:15 2003 Received: from lists.tislabs.com (portal.tislabs.com [192.94.214.101]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09796 for ; Thu, 13 Nov 2003 22:48:15 -0500 (EST) Received: by lists.tislabs.com (8.9.1/8.9.1) id VAA27407 Thu, 13 Nov 2003 21:45:38 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: FW: SBSM Date: Thu, 13 Nov 2003 21:54:59 -0500 Message-ID: <6D745637A7E0F94DA070743C55CDA9BA011399F4@NHROCMBX1.ets.enterasys.com> Thread-Topic: FW: SBSM Thread-Index: AcOqV2MB8PFKsYx+TRmI0GRYUi47bwAAzlOA From: "Harrington, David" To: "Wes Hardaker" Cc: X-OriginalArrivalTime: 14 Nov 2003 02:55:00.0129 (UTC) FILETIME=[B1AE8910:01C3AA5A] X-pstn-version: pmps:sps_win32_1_1_0c1 pase:2.0 X-pstn-levels: (C:88.7295 M:99.5542 P:95.9108 R:95.9108 S:67.0394 ) X-pstn-settings: 4 (0.2500:0.2500) p:13 m:13 c:14 r:13 X-pstn-addresses: from forward (org good) Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by lists.tislabs.com id VAA27404 Sender: owner-snmpv3@lists.tislabs.com Precedence: bulk Content-Transfer-Encoding: 8bit What was the list address for SBSM discussion? dbh > -----Original Message----- > From: Wes Hardaker [mailto:hardaker@tislabs.com] > Sent: Thursday, November 13, 2003 8:31 PM > To: Harrington, David > Subject: Re: FW: SBSM > > > >>>>> On Thu, 13 Nov 2003 13:13:15 -0500, "Harrington, David" > said: > > David> I decided I could take it offline, so sent you mail for that > David> purpose. > > Ok, I'll answer in on the list. > > -- > Wes Hardaker > Sparta > From owner-snmpv3@lists.tislabs.com Thu Nov 13 23:16:25 2003 Received: from lists.tislabs.com (portal.tislabs.com [192.94.214.101]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA10702 for ; Thu, 13 Nov 2003 23:16:25 -0500 (EST) Received: by lists.tislabs.com (8.9.1/8.9.1) id WAA28670 Thu, 13 Nov 2003 22:22:20 -0500 (EST) To: "Harrington, David" Cc: Subject: Re: FW: SBSM References: <6D745637A7E0F94DA070743C55CDA9BA011399F4@NHROCMBX1.ets.enterasys.com> From: Wes Hardaker Organization: Sparta Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAGFBMVEXotKX87e8eDA4GAQbQgmlzNycHAwizYkruzul2AAACaUlEQVR4nFXUTW/jIBAGYFI56jWutuq1S9b2dddW6dWtQFxbq4jzwq73Glmg+fv7DiT9QJGS+GEGhiER67TWEQ5CtOeh21ZcIIbmOPq5QvMZYlyV6u+/gsJLTSrGIL/CxEPxQuPAcP0JYlQsq3x5B3UJmUaEyB6yZ+CQ+pwXCzKsbXtbIhg4KtZypPz+AVGtlxH69c87qAqRY6Rc5QUmZMGeAj+TfVjjUwE1lflKys5JGXpM+V0hltqCJ0qL7Plkft4wRM6lxi5p3Wyy7O7fB8TgtdZivxy5rvAB6wSYhbA9vn+GOCaOEGJRPO2mHgk+q1Chyf0Up3AG0NjhOXI19ogEFziq6M+ZtN3kUZ13NW4qUCprC3CW668C06M5jihON1Vsjq8F1CPJB8LINNeQfscwxUEvAwM5Xghvsq2pBr3hnKhbDIrMS3cBRDx70uS9JW2dy667gM0AbZFFmyvn3GOBGB8wG9kppaSNz357LaCmUdtSny5LU9qeCrglvJmyH20TwkjnXQE0usscIWayCWZJ7OpZ4QbUVGRnhuTub3cMYRk99oSplDIfibzfn0FyXyk7z8XThuvC0P/dGCwee7O8aZJBmh0vPixy0NrYhDaR02aR3W0BbyT6h23OB5Hzybj+DOm5w6XCOZG13p5Oh/bursJVh9S+bBiFnPCDuntpcTH080AO+7GlW1i3bRphBM04dZ2dI6yMLjmGFqnIok/cB1YU8sJAACTeuHOd5+lumQHfDM6KyLqEm4aWkkcc1m4PqBewZxBZOg44lT+aJiexDteewboiVhxAjSHxQwhiYJEdCR6tMN1/uckirDRNbsgAAAAASUVORK5CYII= Date: Thu, 13 Nov 2003 19:31:57 -0800 In-Reply-To: <6D745637A7E0F94DA070743C55CDA9BA011399F4@NHROCMBX1.ets.enterasys.com> (David Harrington's message of "Thu, 13 Nov 2003 21:54:59 -0500") Message-ID: User-Agent: Gnus/5.1003 (Gnus v5.10.3) XEmacs/21.5 (brussels sprouts, linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-snmpv3@lists.tislabs.com Precedence: bulk >>>>> On Thu, 13 Nov 2003 21:54:59 -0500, "Harrington, David" said: David> What was the list address for SBSM discussion? Here's the info. We'll answer your question on the new list instead of this one for topic appropriateness: Mailing Lists: sbsm@machshav.com To (un)subscribe: sbsm-request@machshav.com Archive and general information: https://www.machshav.com/mailman/listinfo/sbsm -- Wes Hardaker Sparta From owner-snmpv3@lists.tislabs.com Fri Nov 21 09:48:28 2003 Received: from lists.tislabs.com (portal.tislabs.com [192.94.214.101]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15580 for ; Fri, 21 Nov 2003 09:48:28 -0500 (EST) From: owner-snmpv3@lists.tislabs.com Received: by lists.tislabs.com (8.9.1/8.9.1) id IAA24918 Fri, 21 Nov 2003 08:25:53 -0500 (EST) Date: Fri, 21 Nov 2003 08:25:53 -0500 (EST) Message-Id: <200311211325.IAA24918@lists.tislabs.com> > From majordomo-owner Fri Nov 21 00:04:46 2003 [192.94.214.100]) by lists.tislabs.com (8.9.1/8.9.1) with ESMTP id AAA09900 Fri, 21 Nov 2003 00:04:46 -0500 (EST) nutshell.tislabs.com via csmap (V6.0) id srcAAA_0aq3v; Fri, 21 Nov 03 00:12:31 -0500 E-Mail VirusWall NT); Fri, 21 Nov 2003 00:16:44 -0500 indhubbhs01.ad.infosys.com with Microsoft SMTPSVC(5.0.2195.6713); Fri, 21 Nov 2003 10:40:40 +0530 BLRKECIMR01.ad.infosys.com with Microsoft SMTPSVC(5.0.2195.6713); Fri, 21 Nov 2003 10:40:40 +0530 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Subject: MIB Scalar to MIB Table conversion. Date: Fri, 21 Nov 2003 10:40:40 +0530 Message-ID: <755FA95DB839D211856B0008C7287D93104BE4A1@kecmsg02.ad.infosys.com> Thread-Topic: MIB Scalar to MIB Table conversion. Thread-Index: AcOv7c6M25hDt2SrTl2W7bwOwbvfyg== From: "poojan_tanna" To: X-OriginalArrivalTime: 21 Nov 2003 05:10:40.0382 (UTC) FILETIME=[CE8AD1E0:01C3AFED] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by lists.tislabs.com id AAA09901 Sender: owner-snmpv3@lists.tislabs.com Precedence: bulk Hi All, I want to convert a group of MIB Scalars into a single MIB Table of a propriety MIB. I am not sure how to go about it. The options that I can think: 1. Obsolote all MIB Scalars and create a new MIB Table with the new name of for each of the MIB Objects eventhough the functionality remain same for all them. 2. Deprecate all the existing MIB Scalars and continue to provide support. At the same time create a new MIB Table with the same set of MIB Objects with the name changed. 3. Comment out the existing MIB scalars. Define a new MIB Table with the same set of MIB Objects and keep the same name. It would be great if you can suggest me some document which discusses this conversion procedure. Thanks, Poojan. From owner-snmpv3@lists.tislabs.com Fri Nov 21 13:55:42 2003 Received: from lists.tislabs.com (portal.tislabs.com [192.94.214.101]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26616 for ; Fri, 21 Nov 2003 13:55:41 -0500 (EST) Received: by lists.tislabs.com (8.9.1/8.9.1) id MAA01077 Fri, 21 Nov 2003 12:10:22 -0500 (EST) Date: Fri, 21 Nov 2003 18:20:07 +0100 Message-Id: <200311211720.hALHK7hA005605@hansa.ibr.cs.tu-bs.de> From: Juergen Schoenwaelder To: "poojan_tanna" CC: snmpv3@lists.tislabs.com In-reply-to: <200311211325.IAA24918@lists.tislabs.com> (owner-snmpv3@lists.tislabs.com) References: <200311211325.IAA24918@lists.tislabs.com> X-IBRFilter-SpamReport: 0 () X-Scanned-By: MIMEDefang 2.24 (www . roaringpenguin . com / mimedefang) Sender: owner-snmpv3@lists.tislabs.com Precedence: bulk >>>>> owner-snmpv3 writes: poojan> I want to convert a group of MIB Scalars into a single MIB poojan> Table of a propriety MIB. poojan> I am not sure how to go about it. poojan> The options that I can think: 1. Obsolote all MIB Scalars and poojan> create a new MIB Table with the new name of for each of the poojan> MIB Objects eventhough the functionality remain same for all poojan> them. poojan> 2. Deprecate all the existing MIB Scalars and continue to poojan> provide support. At the same time create a new MIB Table with poojan> the same set of MIB Objects with the name changed. poojan> 3. Comment out the existing MIB scalars. Define a new MIB poojan> Table with the same set of MIB Objects and keep the same name. Option 3. has no advantage which I can see compared to option 1 and option 2 so I would advise not to do this. Whether you deprecate the scalars or obsolete them really depends on the question whether you can/want to still support them. If you can support them (in the sense that the semantics can still be satisfied), then you should just deprecate the scalars to get a smoother transition period. In other words: If you can still implement the scalars with the right semantics, I suggest to go for option 2. If the scalars just do not work anymore and applications really need to use the table objects, go for option 1. /js -- Juergen Schoenwaelder International University Bremen P.O. Box 750 561, 28725 Bremen, Germany From owner-snmpv3@lists.tislabs.com Mon Nov 24 13:05:50 2003 Received: from lists.tislabs.com (portal.tislabs.com [192.94.214.101]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19350 for ; Mon, 24 Nov 2003 13:05:49 -0500 (EST) Received: by lists.tislabs.com (8.9.1/8.9.1) id LAA04464 Mon, 24 Nov 2003 11:42:26 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: [midcom] MIDCOM Protocol Semantics <-> SNMPv3 Date: Mon, 24 Nov 2003 11:51:42 -0500 Message-ID: <6D745637A7E0F94DA070743C55CDA9BA013B1249@NHROCMBX1.ets.enterasys.com> Thread-Topic: [midcom] MIDCOM Protocol Semantics <-> SNMPv3 Thread-Index: AcOykt3NHbqQ5fv5Sp2/DGEgqVCexgAGC45w From: "Harrington, David" Cc: X-OriginalArrivalTime: 24 Nov 2003 16:51:42.0286 (UTC) FILETIME=[3CA146E0:01C3B2AB] X-pstn-version: pmps:sps_win32_1_1_0c1 pase:2.0 X-pstn-levels: (C:80.8653 M:99.5542 P:95.9108 R:95.9108 S:49.9234 ) X-pstn-settings: 4 (0.2500:0.7500) p:13 m:13 C:14 r:13 X-pstn-addresses: from forward (org good) Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by lists.tislabs.com id LAA04461 Sender: owner-snmpv3@lists.tislabs.com Precedence: bulk Content-Transfer-Encoding: 8bit Hi, This has been answered on the midcom WG mailing list. Please do not include the snmpv3 mailing list in further discussion. Thanks, Dbh David Harrington dbh@enterasys.com co-chair, IETF SNMPv3 WG (now concluded) > -----Original Message----- > From: Albrecht.Schwarz@alcatel.de > [mailto:Albrecht.Schwarz@alcatel.de] > Sent: Monday, November 24, 2003 8:56 AM > To: midcom@ietf.org > Cc: snmpv3@lists.tislabs.com > Subject: [midcom] MIDCOM Protocol Semantics <-> SNMPv3 > > > > > > > > Dear MIDCOM experts > > The "semantics draft" is now going for informational RFC in my > understanding. SNMPv3 was recommended as MIDCOM protocol end of last > year to my knowledge. > I'm wondering whether > (1) SNMPv3 is used as "MIDCOM protocol syntax" for the > "MIDCOM Protocol > Semantics"? > and > (2) if yes, will there be an additional "MIB plane" for provisioning > midcom boxes (besides the dynamic configuration actions according > "MIDCOM Protocol Semantics")? > > Thanks, > Albrecht Schwarz > ALCATEL > > > > > > > > > _______________________________________________ > midcom mailing list > midcom@ietf.org > https://www1.ietf.org/mailman/listinfo/midcom >