From rpresuhn@peer.com Thu Oct 30 12:11:02 1997 Received: by dorothy.peer.com (1.39.111.2/16.2) id AA151712262 for ; Thu, 30 Oct 1997 12:11:02 -0800 Date: Thu, 30 Oct 1997 12:11:02 -0800 From: Randy Presuhn Return-Path: Message-Id: <199710302011.AA151712262@dorothy.peer.com> To: dfrancis@santa.cisco.com, sgudur@peer.com Subject: Re: New version of agentx Mib draft (02) Cc: agentx@peer.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi - (trying out the new exploder....) > Date: Wed, 29 Oct 1997 22:26:18 -0800 > From: dfrancis@santa.cisco.com (Dale Francisco) > Message-Id: <199710300626.WAA22532@marvell.cisco.com> > To: sgudur@peer.com > Subject: Re: New version of agentx Mib draft (02) > Cc: agentx@fv.com ... > (2) Error output from SMIC > -------------------------- > % smicng -CC -CW -CB -M 0 AGENTX-MIB.inc > > E: f(AGENTX-MIB.my), (1,4) SMI item "BITS" used in AGENTX-MIB, but not defined or imported This is a peculiarity of SMIC. There is no BITS production to import. BITS is part of the macro notation defined in RFC 1902 and 1903. Importing it would be rather like importing "DESCRIPTION". > E: f(AGENTX-MIB.my), (157,16) Index item "agentxConnIndex" must be defined with syntax that includes a range ... > E: f(AGENTX-MIB.my), (264,21) Index item "agentxSessionIndex" must be defined with syntax that includes a range ... > E: f(AGENTX-MIB.my), (428,21) Index item "agentxRegIndex" must be defined with syntax that includes a range ... Why on earth would ranges required for these indexes? The type definition of Unsigned32 (the type of these indexes) already is defined with both lower and upper bounds. Further constraints seem pointless. --------------------------------------------------------------------- Randy Presuhn BMC Software, Inc. (Silicon Valley Division) Voice: +1 408 556-0720 (Formerly PEER Networks) http://www.bmc.com Fax: +1 408 556-0735 1190 Saratoga Avenue, Suite 130 Email: rpresuhn@bmc.com San Jose, California 95129-3433 USA --------------------------------------------------------------------- In accordance with the BMC Communications Systems Use and Security Policy memo dated December 10, 1996, page 2, item (g) (the first of two), I explicitly state that although my affiliation with BMC may be apparent, implied, or provided, my opinions are not necessarily those of BMC Software and that all external representations on behalf of BMC must first be cleared with a member of "the top management team." --------------------------------------------------------------------- >From agentx-owner@fv.com Wed Oct 29 22:48:49 PST 1997 Received: from cashew.bmc.com by dorothy.peer.com with ESMTP (1.39.111.2/16.2) id AA181134128 for ; Wed, 29 Oct 1997 22:48:48 -0800 Return-Path: Received: (from uucp@localhost) by cashew.bmc.com (8.8.6/8.8.6) id AAA19540; Thu, 30 Oct 1997 00:48:46 -0600 (CST) Resent-From: agentx-owner@fv.com Received: from proto.fv.com(207.67.199.11) by cashew.bmc.com via smap (V2.0) id xma019537; Thu, 30 Oct 97 00:48:42 -0600 Received: from localhost (proto.fv.com [207.67.199.11]) by proto.fv.com (8.8.8/8.8.8) with ESMTP id WAA13680 for ; Wed, 29 Oct 1997 22:26:39 -0800 (PST) Comment: Posted to the agentx Mailing List To unsubscribe, send mail to agentx-request@proto.fv.com with "unsubscribe" in the Subject Resent-Date: Wed, 29 Oct 1997 22:26:39 -0800 Resent-Message-Id: <13678.878192799.1@proto.fv.com> Received: (from smusr@localhost) by proto.fv.com (8.8.8/8.8.8) id WAA13674 for X-agentx-local; Wed, 29 Oct 1997 22:26:39 -0800 (PST) X-Suppressed-X-Authentication-Warning: proto.fv.com: smusr set sender to agentx-owner using -f Received: from shekel.fv.com (shekel.fv.com [207.67.199.130]) by proto.fv.com (8.8.8/8.8.8) with ESMTP id WAA13671 for ; Wed, 29 Oct 1997 22:26:38 -0800 (PST) Received: from gauntlet.fv.com (gauntlet-in.fv.com [10.0.0.2]) by shekel.fv.com (8.8.8/8.8.8) with ESMTP id WAA13292 for ; Wed, 29 Oct 1997 22:26:37 -0800 (PST) Received: (from uucp@localhost) by gauntlet.fv.com (8.8.7/8.8.7) id WAA07170 for ; Wed, 29 Oct 1997 22:22:12 -0800 (PST) Received: from farley.cisco.com(204.179.2.54) by gauntlet.fv.com via smap (3.2) id xma007163; Wed, 29 Oct 97 22:21:54 -0800 Received: from santa.cisco.com (santa [171.69.187.12]) by farley.cisco.com (8.8.5-Cisco.1/8.6.5) with SMTP id WAA10122; Wed, 29 Oct 1997 22:25:55 -0800 (PST) Received: from marvell.cisco.com by santa.cisco.com (4.1/SMI-4.1) id AA27151; Wed, 29 Oct 97 22:26:19 PST Received: by marvell.cisco.com (SMI-8.6/SMI-SVR4) id WAA22532; Wed, 29 Oct 1997 22:26:18 -0800 Date: Wed, 29 Oct 1997 22:26:18 -0800 >From: dfrancis@santa.cisco.com (Dale Francisco) Message-Id: <199710300626.WAA22532@marvell.cisco.com> To: sgudur@peer.com Subject: Re: New version of agentx Mib draft (02) Cc: agentx@fv.com X-Suppressed-X-Sun-Charset: US-ASCII Status: RO Hi Smitha, I did a quick review of the latest AgentX MIB draft for style and spelling, and have some small suggestions for improvements. Also, I extracted the MIB and ran it through SMIC, and found some issues you may want to address. (Thanks to David Perkins for creating an incredibly useful tool.) I list below (1) the diff of the draft and my suggested style edits and (2) the error output from SMIC. If it would prove useful to you to have the edited text or the MIB I used (for line number info), I'd be happy to forward them to you. Thanks, Dale --- /// Dale Francisco Editor, AgentX WG \\\ Cisco Systems dfrancis@cisco.com /// 210 W Tasman Dr Bldg F voice: (408) 527-9787 \\\ San Jose CA 95134-1714 fax: (408) 527-2477 (1) Diff of draft and edited draft ---------------------------------- *** agentxmib.txt.orig Wed Oct 29 20:18:17 1997 --- agentxmib.txt Wed Oct 29 21:49:05 1997 *************** *** 98,99 **** ! - Identify the subagent's type, vendor, transport address, AgentX ! protocol version and other characteristics. --- 98,99 ---- ! - Identify each subagent's type, vendor, transport address, AgentX ! protocol version, and other characteristics. *************** *** 102 **** ! context in which the objects are registered and the priority of --- 102 ---- ! context in which the objects are registered, and the priority of *************** *** 124 **** ! provides information describing the master agent's agentx support, ! --- 124 ---- ! provides information describing the master agent's AgentX support, ! *************** *** 127 **** ! describing the current set of connections capable of carrying agentx ! --- 127 ---- ! describing the current set of connections capable of carrying AgentX ! *************** *** 154 **** ! which aagentxSessionConnIndex matches the value of the ! --- 154 ---- ! which agentxSessionConnIndex matches the value of the ! *************** *** 320,322 **** ! "The agentxConnectionTable tracks all current agentx transport ! ! connections. There may be zero, one, or more agentx sessions ! ! on a given agentx connection." ! --- 320,322 ---- ! "The agentxConnectionTable tracks all current AgentX transport ! ! connections. There may be zero, one, or more AgentX sessions ! ! on a given AgentX connection." ! *************** *** 346,347 **** ! single agentx transport connection. A conenction may be ! ! used to support zero or more agentx sessions. Entries come ! --- 346,347 ---- ! single AgentX transport connection. A connection may be ! ! used to support zero or more AgentX sessions. Entries come ! *************** *** 372 **** ! and, therefore, this entry was added to the table." ! --- 372,373 ---- ! and, therefore, its value when this entry was added to the ! table." *************** *** 563 **** ! therefore, this entry was added to the table." --- 564 ---- ! therefore, its value when this entry was added to the table." *************** *** 572 **** ! subagent. This will be equal to or less than the value of --- 573 ---- ! subagent. This will be less than or equal to the value of *************** *** 711 **** ! instance identifier." --- 712 ---- ! instance." *************** *** 731 **** ! or a partial object instance identifier." --- 732 ---- ! or a partial object instance." *************** *** 765 **** ! that default value (indicated by agentxSessionTimeout or --- 766 ---- ! that the default value (indicated by agentxSessionTimeout or *************** *** 972 **** ! or assist in its implmentation may be prepared, copied, published and | --- 973 ---- ! or assist in its implementation may be prepared, copied, published and | (2) Error output from SMIC -------------------------- % smicng -CC -CW -CB -M 0 AGENTX-MIB.inc E: f(AGENTX-MIB.my), (1,4) SMI item "BITS" used in AGENTX-MIB, but not defined or imported E: f(AGENTX-MIB.my), (157,16) Index item "agentxConnIndex" must be defined with syntax that includes a range W: f(AGENTX-MIB.my), (198,21) Item "agentxConnTransportAddr" should have SIZE specified W: f(AGENTX-MIB.my), (257,4) Sequence "AgentxSubagentEntry" and Row "agentxSessionEntry" should have related names E: f(AGENTX-MIB.my), (264,21) Index item "agentxSessionIndex" must be defined with syntax that includes a range E: f(AGENTX-MIB.my), (428,21) Index item "agentxRegIndex" must be defined with syntax that includes a range W: f(AGENTX-MIB.my), (452,19) Item "agentxRegContext" should have SIZE specified E: f(AGENTX-MIB.my), (558,10) Item "agentxConnIndex" in object-group "agentxMIBGroup" has access of "not-accessible" W: f(AGENTX-MIB.my), (9,27) "DisplayString" imported but not used *** 5 errors and 4 warnings in parsing ---------------- This e-mail message was sent to all subscribers to the agentx mailing list. To unsubscribe from this mailing list, please send mail to: agentx-request@proto.fv.com with Subject: unsubscribe your.address@your.domain (NOTE: Please do not reply to this message to unsubscribe. You must send your request to agentx-request@proto.fv.com Thank you.) From rpresuhn@peer.com Thu Oct 30 12:16:24 1997 Received: by dorothy.peer.com (1.39.111.2/16.2) id AA152722584 for ; Thu, 30 Oct 1997 12:16:24 -0800 Date: Thu, 30 Oct 1997 12:16:24 -0800 From: Randy Presuhn Return-Path: Message-Id: <199710302016.AA152722584@dorothy.peer.com> To: agentx@peer.com Subject: test - please ignore Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Test #1 of agentx@peer.com list - please ignore --------------------------------------------------------------------- Randy Presuhn BMC Software, Inc. (Silicon Valley Division) Voice: +1 408 556-0720 (Formerly PEER Networks) http://www.bmc.com Fax: +1 408 556-0735 1190 Saratoga Avenue, Suite 130 Email: rpresuhn@bmc.com San Jose, California 95129-3433 USA --------------------------------------------------------------------- In accordance with the BMC Communications Systems Use and Security Policy memo dated December 10, 1996, page 2, item (g) (the first of two), I explicitly state that although my affiliation with BMC may be apparent, implied, or provided, my opinions are not necessarily those of BMC Software and that all external representations on behalf of BMC must first be cleared with a member of "the top management team." --------------------------------------------------------------------- From sgudur@peer.com Thu Oct 30 12:36:03 1997 Received: from cashew.bmc.com by dorothy.peer.com with ESMTP (1.39.111.2/16.2) id AA154843762 for ; Thu, 30 Oct 1997 12:36:02 -0800 Return-Path: Received: (from uucp@localhost) by cashew.bmc.com (8.8.6/8.8.6) id OAA21901 for ; Thu, 30 Oct 1997 14:36:00 -0600 (CST) Received: from gauntlet.fv.com(207.67.199.118) by cashew.bmc.com via smap (V2.0) id xma021879; Thu, 30 Oct 97 14:35:31 -0600 Received: (from uucp@localhost) by gauntlet.fv.com (8.8.7/8.8.7) id MAA11773 for ; Thu, 30 Oct 1997 12:31:00 -0800 (PST) Received: from shekel.fv.com(207.67.199.130) by gauntlet.fv.com via smap (3.2) id xma011746; Thu, 30 Oct 97 12:30:30 -0800 Received: from gauntlet.fv.com (gauntlet-in.fv.com [10.0.0.2]) by shekel.fv.com (8.8.8/8.8.8) with ESMTP id MAA26417 for ; Thu, 30 Oct 1997 12:34:58 -0800 (PST) Received: (from uucp@localhost) by gauntlet.fv.com (8.8.7/8.8.7) id MAA11741 for ; Thu, 30 Oct 1997 12:30:29 -0800 (PST) Received: from mail-gw1.bmc.com(198.64.253.22) by gauntlet.fv.com via smap (3.2) id xma011721; Thu, 30 Oct 97 12:30:13 -0800 Received: (from uucp@localhost) by almond.bmc.com (8.8.6/8.8.6) id OAA08046 for ; Thu, 30 Oct 1997 14:34:38 -0600 (CST) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma008037; Thu, 30 Oct 97 14:34:27 -0600 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id OAA08702 for ; Thu, 30 Oct 1997 14:34:35 -0600 (CST) Received: from cherry.bmc.com(172.17.1.25) by dresden.bmc.com via smap (3.2) id xma008227; Thu, 30 Oct 97 14:34:06 -0600 Received: from dorothy.peer.com (dorothy.peer.com [192.146.153.65]) by cherry.bmc.com with ESMTP (8.7.5/8.7.3) id OAA21771; Thu, 30 Oct 1997 14:33:56 -0600 (CST) Received: by dorothy.peer.com (1.39.111.2/16.2) id AA154663635 for ; Thu, 30 Oct 1997 12:33:55 -0800 From: Smitha Gudur Message-Id: <199710302033.AA154663635@dorothy.peer.com> Subject: Re: New version of agentx Mib draft (02) To: dfrancis@santa.cisco.com Date: Thu, 30 Oct 1997 12:33:55 PST Cc: agentx@fv.com, sgudur@peer.com In-Reply-To: <199710300626.WAA22532@marvell.cisco.com>; from "Dale Francisco" at Oct 29, 97 10:26 pm X-Mailer: Elm [revision: 111.1] Hi, > > Hi Smitha, > > I did a quick review of the latest AgentX MIB draft > for style and spelling, and have some small suggestions > for improvements. Also, I extracted the MIB and ran it > through SMIC, and found some issues you may want to address. > (Thanks to David Perkins for creating an incredibly useful > tool.) > > I list below (1) the diff of the draft and my suggested style > edits and (2) the error output from SMIC. If it would prove > useful to you to have the edited text or the MIB I used (for > line number info), I'd be happy to forward them to you. > > Thanks, > Dale > > --- > /// Dale Francisco Editor, AgentX WG > \\\ Cisco Systems dfrancis@cisco.com > /// 210 W Tasman Dr Bldg F voice: (408) 527-9787 > \\\ San Jose CA 95134-1714 fax: (408) 527-2477 > > (1) Diff of draft and edited draft > ---------------------------------- > *** agentxmib.txt.orig Wed Oct 29 20:18:17 1997 > --- agentxmib.txt Wed Oct 29 21:49:05 1997 > *************** > *** 98,99 **** > ! - Identify the subagent's type, vendor, transport address, AgentX > ! protocol version and other characteristics. > --- 98,99 ---- > ! - Identify each subagent's type, vendor, transport address, AgentX > ! protocol version, and other characteristics. > *************** > *** 102 **** > ! context in which the objects are registered and the priority of > --- 102 ---- > ! context in which the objects are registered, and the priority of > *************** > *** 124 **** > ! provides information describing the master agent's agentx support, ! > --- 124 ---- > ! provides information describing the master agent's AgentX support, ! > *************** > *** 127 **** > ! describing the current set of connections capable of carrying agentx ! > --- 127 ---- > ! describing the current set of connections capable of carrying AgentX ! > *************** > *** 154 **** > ! which aagentxSessionConnIndex matches the value of the ! > --- 154 ---- > ! which agentxSessionConnIndex matches the value of the ! > *************** > *** 320,322 **** > ! "The agentxConnectionTable tracks all current agentx transport ! > ! connections. There may be zero, one, or more agentx sessions ! > ! on a given agentx connection." ! > --- 320,322 ---- > ! "The agentxConnectionTable tracks all current AgentX transport ! > ! connections. There may be zero, one, or more AgentX sessions ! > ! on a given AgentX connection." ! > *************** > *** 346,347 **** > ! single agentx transport connection. A conenction may be ! > ! used to support zero or more agentx sessions. Entries come ! > --- 346,347 ---- > ! single AgentX transport connection. A connection may be ! > ! used to support zero or more AgentX sessions. Entries come ! > *************** > *** 372 **** > ! and, therefore, this entry was added to the table." ! > --- 372,373 ---- > ! and, therefore, its value when this entry was added to the > ! table." > *************** > *** 563 **** > ! therefore, this entry was added to the table." > --- 564 ---- > ! therefore, its value when this entry was added to the table." > *************** > *** 572 **** > ! subagent. This will be equal to or less than the value of > --- 573 ---- > ! subagent. This will be less than or equal to the value of > *************** > *** 711 **** > ! instance identifier." > --- 712 ---- > ! instance." > *************** > *** 731 **** > ! or a partial object instance identifier." > --- 732 ---- > ! or a partial object instance." > *************** > *** 765 **** > ! that default value (indicated by agentxSessionTimeout or > --- 766 ---- > ! that the default value (indicated by agentxSessionTimeout or > *************** > *** 972 **** > ! or assist in its implmentation may be prepared, copied, published and | > --- 973 ---- > ! or assist in its implementation may be prepared, copied, published and | > > > > (2) Error output from SMIC > -------------------------- > % smicng -CC -CW -CB -M 0 AGENTX-MIB.inc > > E: f(AGENTX-MIB.my), (1,4) SMI item "BITS" used in AGENTX-MIB, but not defined or imported BITS needs to be imported. > E: f(AGENTX-MIB.my), (157,16) Index item "agentxConnIndex" must be defined with syntax that includes a range > W: f(AGENTX-MIB.my), (198,21) Item "agentxConnTransportAddr" should have SIZE specified > W: f(AGENTX-MIB.my), (257,4) Sequence "AgentxSubagentEntry" and Row "agentxSessionEntry" should have related names > E: f(AGENTX-MIB.my), (264,21) Index item "agentxSessionIndex" must be defined with syntax that includes a range > E: f(AGENTX-MIB.my), (428,21) Index item "agentxRegIndex" must be defined with syntax that includes a range > W: f(AGENTX-MIB.my), (452,19) Item "agentxRegContext" should have SIZE specified As agentxRegContext is an OCTET-STRING and OCTET-STRING has an implied range of OCTET STRING (SIZE (0..65535)). This is is specified in rfc1902. > E: f(AGENTX-MIB.my), (558,10) Item "agentxConnIndex" in object-group "agentxMIBGroup" has access of "not-accessible" agentxConnIndex "not-accessible" needs to be "read-only". > W: f(AGENTX-MIB.my), (9,27) "DisplayString" imported but not used DisplayString needs to be removed. agentxConnIndex, agentxSessionIndex, agentxRegIndex have SYNTAX of Unsigned32. Unsigned32 as per rfc1902 and the range is specified as 0..4294967295. Any comments or suggestions on limiting ranges or sizes of of the above objects?. smitha > > *** 5 errors and 4 warnings in parsing > > ---------------- > This e-mail message was sent to all subscribers to the > agentx mailing list. > > To unsubscribe from this mailing list, please send mail to: > agentx-request@proto.fv.com > with > Subject: unsubscribe your.address@your.domain > > (NOTE: Please do not reply to this message to unsubscribe. You must send > your request to agentx-request@proto.fv.com Thank you.) > From dfrancis@santa.cisco.com Thu Oct 30 12:49:11 1997 Received: from cashew.bmc.com by dorothy.peer.com with ESMTP (1.39.111.2/16.2) id AA158714550 for ; Thu, 30 Oct 1997 12:49:10 -0800 Return-Path: Received: (from uucp@localhost) by cashew.bmc.com (8.8.6/8.8.6) id OAA22665; Thu, 30 Oct 1997 14:49:08 -0600 (CST) Received: from farley.cisco.com(204.179.2.54) by cashew.bmc.com via smap (V2.0) id xma022650; Thu, 30 Oct 97 14:48:43 -0600 Received: from santa.cisco.com (santa [171.69.187.12]) by farley.cisco.com (8.8.5-Cisco.1/8.6.5) with SMTP id MAA23335; Thu, 30 Oct 1997 12:48:16 -0800 (PST) Received: from marvell.cisco.com by santa.cisco.com (4.1/SMI-4.1) id AA09063; Thu, 30 Oct 97 12:48:41 PST Received: by marvell.cisco.com (SMI-8.6/SMI-SVR4) id MAA22895; Thu, 30 Oct 1997 12:48:41 -0800 Date: Thu, 30 Oct 1997 12:48:41 -0800 From: dfrancis@santa.cisco.com (Dale Francisco) Message-Id: <199710302048.MAA22895@marvell.cisco.com> To: rpresuhn@peer.com, sgudur@peer.com Subject: Re: New version of agentx Mib draft (02) Cc: agentx@peer.com X-Sun-Charset: US-ASCII Randy, I reproduced the command line arguments and the entire error output from SMIC for the sake of completeness. Sometimes a compiler message that's mystifying to me will be plain as day to someone else, or, in the case of spurious error messages, it will lead indirectly to a real error. I agree there's nothing to be done about BITS, and as to the "must be defined with a syntax that includes a range" error, I assume (but do not know) that this stems from the v2 SMI's injunction to avoid 0-valued index objects. So, I bet a range of 1..maxUint32 would make SMIC contented and happy. Regards, Dale --- /// Dale Francisco Editor, AgentX WG \\\ Cisco Systems dfrancis@cisco.com /// 210 W Tasman Dr Bldg F voice: (408) 527-9787 \\\ San Jose CA 95134-1714 fax: (408) 527-2477 > From rpresuhn@peer.com Thu Oct 30 12:17:40 1997 > > Hi - > > (trying out the new exploder....) > > > Date: Wed, 29 Oct 1997 22:26:18 -0800 > > From: dfrancis@santa.cisco.com (Dale Francisco) > > Message-Id: <199710300626.WAA22532@marvell.cisco.com> > > To: sgudur@peer.com > > Subject: Re: New version of agentx Mib draft (02) > > Cc: agentx@fv.com > ... > > (2) Error output from SMIC > > -------------------------- > > % smicng -CC -CW -CB -M 0 AGENTX-MIB.inc > > > > E: f(AGENTX-MIB.my), (1,4) SMI item "BITS" used in AGENTX-MIB, but not defined or imported > > This is a peculiarity of SMIC. There is no BITS production to import. > BITS is part of the macro notation defined in RFC 1902 and 1903. > Importing it would be rather like importing "DESCRIPTION". > > > E: f(AGENTX-MIB.my), (157,16) Index item "agentxConnIndex" must be defined with syntax that includes a range > ... > > E: f(AGENTX-MIB.my), (264,21) Index item "agentxSessionIndex" must be defined with syntax that includes a range > ... > > E: f(AGENTX-MIB.my), (428,21) Index item "agentxRegIndex" must be defined with syntax that includes a range > ... > > Why on earth would ranges required for these indexes? The type definition > of Unsigned32 (the type of these indexes) already is defined with both > lower and upper bounds. Further constraints seem pointless. > > --------------------------------------------------------------------- > Randy Presuhn BMC Software, Inc. (Silicon Valley Division) > Voice: +1 408 556-0720 (Formerly PEER Networks) http://www.bmc.com > Fax: +1 408 556-0735 1190 Saratoga Avenue, Suite 130 > Email: rpresuhn@bmc.com San Jose, California 95129-3433 USA > --------------------------------------------------------------------- > In accordance with the BMC Communications Systems Use and Security > Policy memo dated December 10, 1996, page 2, item (g) (the first of > two), I explicitly state that although my affiliation with BMC may be > apparent, implied, or provided, my opinions are not necessarily those > of BMC Software and that all external representations on behalf of > BMC must first be cleared with a member of "the top management team." > --------------------------------------------------------------------- From dfrancis@santa.cisco.com Thu Oct 30 13:15:53 1997 Received: from almond.bmc.com by dorothy.peer.com with ESMTP (1.39.111.2/16.2) id AA165216152 for ; Thu, 30 Oct 1997 13:15:52 -0800 Return-Path: Received: (from uucp@localhost) by almond.bmc.com (8.8.6/8.8.6) id PAA12757 for ; Thu, 30 Oct 1997 15:15:51 -0600 (CST) Received: from gauntlet.fv.com(207.67.199.118) by almond.bmc.com via smap (V2.0) id xma012743; Thu, 30 Oct 97 15:15:38 -0600 Received: (from uucp@localhost) by gauntlet.fv.com (8.8.7/8.8.7) id NAA15354 for ; Thu, 30 Oct 1997 13:11:06 -0800 (PST) Received: from shekel.fv.com(207.67.199.130) by gauntlet.fv.com via smap (3.2) id xma015306; Thu, 30 Oct 97 13:10:36 -0800 Received: from gauntlet.fv.com (gauntlet-in.fv.com [10.0.0.2]) by shekel.fv.com (8.8.8/8.8.8) with ESMTP id NAA00521 for ; Thu, 30 Oct 1997 13:15:04 -0800 (PST) Received: (from uucp@localhost) by gauntlet.fv.com (8.8.7/8.8.7) id NAA15280 for ; Thu, 30 Oct 1997 13:10:35 -0800 (PST) Received: from farley.cisco.com(204.179.2.54) by gauntlet.fv.com via smap (3.2) id xma015246; Thu, 30 Oct 97 13:10:13 -0800 Received: from santa.cisco.com (santa [171.69.187.12]) by farley.cisco.com (8.8.5-Cisco.1/8.6.5) with SMTP id NAA26819; Thu, 30 Oct 1997 13:14:11 -0800 (PST) Received: from marvell.cisco.com by santa.cisco.com (4.1/SMI-4.1) id AA09551; Thu, 30 Oct 97 13:14:35 PST Received: by marvell.cisco.com (SMI-8.6/SMI-SVR4) id NAA22923; Thu, 30 Oct 1997 13:14:35 -0800 Date: Thu, 30 Oct 1997 13:14:35 -0800 From: dfrancis@santa.cisco.com (Dale Francisco) Message-Id: <199710302114.NAA22923@marvell.cisco.com> To: sgudur@peer.com Subject: Re: New version of agentx Mib draft (02) Cc: agentx@fv.com X-Sun-Charset: US-ASCII Smitha, I mentioned in an earlier post what I think the warning is about with regards the Unsigned32 indices. The warning about no SIZE for OCTET STRING is just that: a warning. There are very few applications that could handle an allocation of the max-size OCTET STRING, so I think the idea behind the warning is simply this: If you _can_ assign a reasonable upper bound, please do--it then becomes a plausible "contract" between MIB designer and agent implementor. If it's just "OCTET STRING", each implementor will pick what he or she thinks is a reasonable upper bound, almost certainly something less than 65,535 bytes. Thanks, Dale --- /// Dale Francisco Editor, AgentX WG \\\ Cisco Systems dfrancis@cisco.com /// 210 W Tasman Dr Bldg F voice: (408) 527-9787 \\\ San Jose CA 95134-1714 fax: (408) 527-2477 > From sgudur@peer.com Thu Oct 30 12:48:08 1997 > From: Smitha Gudur > Subject: Re: New version of agentx Mib draft (02) > To: dfrancis@santa.cisco.com > Date: Thu, 30 Oct 1997 12:33:55 PST > Cc: agentx@fv.com, sgudur@peer.com > > > > > (2) Error output from SMIC > > -------------------------- > > % smicng -CC -CW -CB -M 0 AGENTX-MIB.inc > > > > E: f(AGENTX-MIB.my), (1,4) SMI item "BITS" used in AGENTX-MIB, but not defined or imported > BITS needs to be imported. > > E: f(AGENTX-MIB.my), (157,16) Index item "agentxConnIndex" must be defined with syntax that includes a range > > W: f(AGENTX-MIB.my), (198,21) Item "agentxConnTransportAddr" should have SIZE specified > > W: f(AGENTX-MIB.my), (257,4) Sequence "AgentxSubagentEntry" and Row "agentxSessionEntry" should have related names > > E: f(AGENTX-MIB.my), (264,21) Index item "agentxSessionIndex" must be defined with syntax that includes a range > > E: f(AGENTX-MIB.my), (428,21) Index item "agentxRegIndex" must be defined with syntax that includes a range > > W: f(AGENTX-MIB.my), (452,19) Item "agentxRegContext" should have SIZE specified > > As agentxRegContext is an OCTET-STRING and OCTET-STRING has an implied > range of OCTET STRING (SIZE (0..65535)). > This is is specified in rfc1902. > > > E: f(AGENTX-MIB.my), (558,10) Item "agentxConnIndex" in object-group "agentxMIBGroup" has access of "not-accessible" > > agentxConnIndex "not-accessible" needs to be "read-only". > > > W: f(AGENTX-MIB.my), (9,27) "DisplayString" imported but not used > DisplayString needs to be removed. > > agentxConnIndex, agentxSessionIndex, agentxRegIndex have SYNTAX of Unsigned32. > Unsigned32 as per rfc1902 and the range is specified as 0..4294967295. > > Any comments or suggestions on limiting ranges or sizes > of of the above objects?. > > smitha > > > > > > > > *** 5 errors and 4 warnings in parsing > > > > ---------------- > > This e-mail message was sent to all subscribers to the > > agentx mailing list. > > > > To unsubscribe from this mailing list, please send mail to: > > agentx-request@proto.fv.com > > with > > Subject: unsubscribe your.address@your.domain > > > > (NOTE: Please do not reply to this message to unsubscribe. You must send > > your request to agentx-request@proto.fv.com Thank you.) > > > From rpresuhn@peer.com Thu Oct 30 13:46:10 1997 Received: by dorothy.peer.com (1.39.111.2/16.2) id AA168867970 for ; Thu, 30 Oct 1997 13:46:10 -0800 Date: Thu, 30 Oct 1997 13:46:10 -0800 From: Randy Presuhn Return-Path: Message-Id: <199710302146.AA168867970@dorothy.peer.com> To: agentx@peer.com Subject: Re: New version of agentx Mib draft (02) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi - > From: Smitha Gudur > Message-Id: <199710302033.AA154663635@dorothy.peer.com> > Subject: Re: New version of agentx Mib draft (02) > To: dfrancis@santa.cisco.com > Date: Thu, 30 Oct 1997 12:33:55 PST > Cc: agentx@fv.com, sgudur@peer.com .... > > W: f(AGENTX-MIB.my), (452,19) Item "agentxRegContext" should have SIZE specified > > As agentxRegContext is an OCTET-STRING and OCTET-STRING has an implied > range of OCTET STRING (SIZE (0..65535)). > This is is specified in rfc1902. ... The agentx protocol leaves the length of agentxRegContext unconstrained. Would it make sense to tighten up the MIB representation to align with VACM's notion of context? PRO: would probably be more consistent CON: the protocol would permit contest names that the MIB could not represent --------------------------------------------------------------------- Randy Presuhn BMC Software, Inc. (Silicon Valley Division) Voice: +1 408 556-0720 (Formerly PEER Networks) http://www.bmc.com Fax: +1 408 556-0735 1190 Saratoga Avenue, Suite 130 Email: rpresuhn@bmc.com San Jose, California 95129-3433 USA --------------------------------------------------------------------- In accordance with the BMC Communications Systems Use and Security Policy memo dated December 10, 1996, page 2, item (g) (the first of two), I explicitly state that although my affiliation with BMC may be apparent, implied, or provided, my opinions are not necessarily those of BMC Software and that all external representations on behalf of BMC must first be cleared with a member of "the top management team." --------------------------------------------------------------------- From rpresuhn@peer.com Thu Oct 30 14:06:27 1997 Received: by dorothy.peer.com (1.39.111.2/16.2) id AA173459187 for ; Thu, 30 Oct 1997 14:06:27 -0800 Date: Thu, 30 Oct 1997 14:06:27 -0800 From: Randy Presuhn Return-Path: Message-Id: <199710302206.AA173459187@dorothy.peer.com> To: agentx@peer.com Subject: Re: New version of agentx Mib draft (02) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi - > Date: Thu, 30 Oct 1997 12:48:41 -0800 > From: dfrancis@santa.cisco.com (Dale Francisco) > Message-Id: <199710302048.MAA22895@marvell.cisco.com> > To: rpresuhn@peer.com, sgudur@peer.com > Subject: Re: New version of agentx Mib draft (02) > Cc: agentx@peer.com ... > I agree there's nothing to be done about BITS, and as > to the "must be defined with a syntax that includes a > range" error, I assume (but do not know) that this > stems from the v2 SMI's injunction to avoid 0-valued > index objects. So, I bet a range of 1..maxUint32 would > make SMIC contented and happy. ... You're probably right. Although RFC 1902 clause 7.7 is advisory rather than normative, using "should" rather than "must", who knows what the MIB checker has in mind. :-) | Instances identified by use of integer-valued objects should be | numbered starting from one (i.e., not from zero). The use of zero as | a value for an integer-valued index object should be avoided, except | in special cases. Sounds like something thrown in to make FORTRAN IV programmers happy. :-) I don't see any particular value to prohibiting or distinguishing zero as an index value in this case, since there appears to be a strong logical dependency between connections, sessions, and registrations. (In other MIBs, zero proved useful as a sentinel value for unsatisfied relationships.) Your suggstion to subtype to (1 .. 4294967295) sounds like an easy way forward. --------------------------------------------------------------------- Randy Presuhn BMC Software, Inc. (Silicon Valley Division) Voice: +1 408 556-0720 (Formerly PEER Networks) http://www.bmc.com Fax: +1 408 556-0735 1190 Saratoga Avenue, Suite 130 Email: rpresuhn@bmc.com San Jose, California 95129-3433 USA --------------------------------------------------------------------- In accordance with the BMC Communications Systems Use and Security Policy memo dated December 10, 1996, page 2, item (g) (the first of two), I explicitly state that although my affiliation with BMC may be apparent, implied, or provided, my opinions are not necessarily those of BMC Software and that all external representations on behalf of BMC must first be cleared with a member of "the top management team." --------------------------------------------------------------------- From acec.com!natale@aceccomm.com Thu Oct 30 14:42:26 1997 Received: from cashew.bmc.com by dorothy.peer.com with ESMTP (1.39.111.2/16.2) id AA186971345 for ; Thu, 30 Oct 1997 14:42:25 -0800 Return-Path: Received: (from uucp@localhost) by cashew.bmc.com (8.8.6/8.8.6) id QAA28167; Thu, 30 Oct 1997 16:42:23 -0600 (CST) Received: from relay1.smtp.psi.net(38.8.14.2) by cashew.bmc.com via smap (V2.0) id xma028157; Thu, 30 Oct 97 16:42:04 -0600 Received: from nips.acec.com by relay1.smtp.psi.net (8.8.5/SMI-5.4-PSI) id RAA10848; Thu, 30 Oct 1997 17:41:54 -0500 (EST) Received: from bnatale by nips.acec.com (5.65/3.2.083191-ACE*COMM) id AA17015; Thu, 30 Oct 1997 17:43:16 -0500 Message-Id: <3.0.1.32.19971030174357.009713e0@nips.acecomm.com> X-Sender: natale@nips.acecomm.com X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Thu, 30 Oct 1997 17:43:57 -0500 To: Randy Presuhn From: Bob Natale Subject: Re: New version of agentx Mib draft (02) Cc: agentx@peer.com In-Reply-To: <199710302146.AA168867970@dorothy.peer.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" >At 01:46 PM 10/30/97 -0800, Randy Presuhn wrote: Hi Randy, <...> >The agentx protocol leaves the length of agentxRegContext unconstrained. >Would it make sense to tighten up the MIB representation to align with >VACM's notion of context? > > PRO: would probably be more consistent > > CON: the protocol would permit contest names > that the MIB could not represent I'd vote the PRO option here...for consistency, for synergy with an eventual SNMPv3, and for enhanced guidance to implementors. The CON (if I understand your point correctly) is something we encounter in general anyway...the MIB, in this case, should take precedence. Cordially, BobN ----- ISO 9001 Registered Hardware and Software Divsions ---- Bob Natale | ACE*COMM | 301-721-3000 [v] Dir, Net Mgmt Prod | 704 Quince Orchard Rd | 301-721-3001 [f] bnatale@acecomm.com| Gaithersburg MD 20878 | www.acecomm.com ---- WinSNMP DLL, SDK, Apps & Agents for Win16/32 & UNIX ---- ------ NetPlus (r) "FCAPS" Telemanagement Applications ------ From acec.com!natale@aceccomm.com Thu Oct 30 15:28:38 1997 Received: from almond.bmc.com by dorothy.peer.com with ESMTP (1.39.111.2/16.2) id AA217114116 for ; Thu, 30 Oct 1997 15:28:36 -0800 Return-Path: Received: (from uucp@localhost) by almond.bmc.com (8.8.6/8.8.6) id RAA23376 for ; Thu, 30 Oct 1997 17:28:34 -0600 (CST) Received: from relay1.smtp.psi.net(38.8.14.2) by almond.bmc.com via smap (V2.0) id xma023359; Thu, 30 Oct 97 17:28:09 -0600 Received: from nips.acec.com by relay1.smtp.psi.net (8.8.5/SMI-5.4-PSI) id SAA28715; Thu, 30 Oct 1997 18:28:05 -0500 (EST) Received: from bnatale by nips.acec.com (5.65/3.2.083191-ACE*COMM) id AA17671; Thu, 30 Oct 1997 18:29:26 -0500 Message-Id: <3.0.1.32.19971030183007.00955c10@nips.acecomm.com> X-Sender: natale@nips.acecomm.com X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Thu, 30 Oct 1997 18:30:07 -0500 To: agentx@peer.com From: Bob Natale Subject: New e-mail and archive instructions Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Hi, The AgentX e-mail list is now officially: agentx@peer.com Admin requests (subscribe/unsubscribe) must be addressed to: agentx-request@peer.com I recommend putting the requested action in both the "Subject:" header and the body text. An AgentX FTP repository has been established: ftp://ftp.peer.com/pub/agentx And the archives are in: ftp://ftp.peer.com/pub/agentx/archives The files in this directory are archives of the traffic that has flowed over the agentx mailing list. They are named by year and month, in the format YYYY-MM. The current month's traffic is accumulated in the file "current", which may actually lag behind the list's traffic by a few days. (this is a temporary situation) The files from 1995-11 to 1997-10 are from the distribution list. More recent files are from the distribution list. Peer/BMC personnel may issue additional instructions and/or information about use of these resources from time to time. I will get the IETF AgentX WG web page info updated asap. Thanks again to Peer/BMC for providing these resources, to First Virtual for having done so hitherto, and to the University at Buffalo, Cisco, and Center Technology for volunteering to do so. Cordially, BobN ----- ISO 9001 Registered Hardware and Software Divsions ---- Bob Natale | ACE*COMM | 301-721-3000 [v] Dir, Net Mgmt Prod | 704 Quince Orchard Rd | 301-721-3001 [f] bnatale@acecomm.com| Gaithersburg MD 20878 | www.acecomm.com ---- WinSNMP DLL, SDK, Apps & Agents for Win16/32 & UNIX ---- ------ NetPlus (r) "FCAPS" Telemanagement Applications ------