From owner-agentx@dorothy.bmc.com Sun Jan 2 00:38:06 2000 Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA02764 for ; Sun, 2 Jan 2000 00:38:05 -0500 (EST) Received: from dorothy.peer.com (dorothy.bmc.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id XAA18140; Sat, 1 Jan 2000 23:37:36 -0600 (CST) Received: (from root@localhost) by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id VAA20124 for agentx-list; Sat, 1 Jan 2000 21:28:52 -0800 (PST) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id VAA20118; Sat, 1 Jan 2000 21:28:48 -0800 (PST) Date: Sat, 1 Jan 2000 21:28:48 -0800 (PST) From: Randy Presuhn Message-Id: <200001020528.VAA20118@dorothy.bmc.com> To: agentx@dorothy.peer.com, disman@dorothy.peer.com Subject: agentx/disman y2k test - please ignore Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-agentx@dorothy.bmc.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list Content-Transfer-Encoding: 7bit Hi - This is merely a test of the mailing lists. Please ignore. ------------------------------------------------------------------------ Randy Presuhn randy_presuhn@bmc.com http://www.bmc.com/ Voice: +1 408 546-1006 BMC Software, Inc. 1-3141 2141 N. First Street Fax: +1 408 965-0359 San Jose, California 95131 USA ------------------------------------------------------------------------ Any relationship between my opinions and BMC's should be coincidental. ------------------------------------------------------------------------ From owner-agentx@dorothy.bmc.com Sat Jan 15 05:54:53 2000 Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11015 for ; Sat, 15 Jan 2000 05:54:53 -0500 (EST) Received: from dorothy.peer.com (dorothy.bmc.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id EAA17177; Sat, 15 Jan 2000 04:51:09 -0600 (CST) Received: (from root@localhost) by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id CAA21391 for agentx-list; Sat, 15 Jan 2000 02:41:34 -0800 (PST) Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id CAA21386 for ; Sat, 15 Jan 2000 02:41:26 -0800 (PST) Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250]) by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with SMTP id EAA15751 for ; Sat, 15 Jan 2000 04:41:50 -0600 (CST) Message-ID: <20000115104145.27160.qmail@web3107.mail.yahoo.com> Received: from [136.182.2.221] by web3107.mail.yahoo.com; Sat, 15 Jan 2000 02:41:45 PST Date: Sat, 15 Jan 2000 02:41:45 -0800 (PST) From: gopal krishna Subject: Master Agent mib instrumentation To: agentx@dorothy.peer.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-agentx@dorothy.bmc.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list hello, i am planning to build a multilingual(v1,v2c,v3) snmp master agent and subagent library with agentx as the protocol between master and subagents. A) I would like to know which are mibs that have to be instrumented in the master agent alone.(for example agentx-mib,rfc 1907,SNMP-FRAMEWORK-mib ). *********************************************** section 4.1 of draft-ietf-agentx-rfc-update-03.txt says master agent Provides instrumentation for the MIB objects defined in RFC 1907 , and for any MIB objects relevant to any administrative framework it supports. ************************************************* if this is a implementation specific issue, what would be the typical implementation if my master agent should support snmp v1, v2c & v3. B)also,is there any guidelines on how the master agent should dispatch when it recieves varbind list in which some of the snmp OIDs have instrumentation provided by master agent itself & for other OIDs subagents provide instrumentation. regards gopal __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com From owner-agentx@dorothy.bmc.com Mon Jan 17 09:51:28 2000 Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01979 for ; Mon, 17 Jan 2000 09:51:28 -0500 (EST) Received: from dorothy.peer.com (dorothy.bmc.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id IAA14487; Mon, 17 Jan 2000 08:48:12 -0600 (CST) Received: (from root@localhost) by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id GAA29355 for agentx-list; Mon, 17 Jan 2000 06:38:31 -0800 (PST) Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id GAA29350 for ; Mon, 17 Jan 2000 06:38:22 -0800 (PST) Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250]) by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with SMTP id IAA11741 for ; Mon, 17 Jan 2000 08:38:46 -0600 (CST) Received: by mailext04.compaq.com (Postfix, from userid 12345) id 7B540104CC1; Mon, 17 Jan 2000 08:38:42 -0600 (CST) Received: from mailint02.im.hou.compaq.com (mailint02.compaq.com [207.18.199.35]) by mailext04.compaq.com (Postfix) with ESMTP id 71050FB101; Mon, 17 Jan 2000 08:38:42 -0600 (CST) Received: by mailint02.im.hou.compaq.com (Postfix, from userid 12345) id D9A52BC4D0; Mon, 17 Jan 2000 08:38:34 -0600 (CST) Received: from sigma.zk3.dec.com (brysigma.zk3.dec.com [16.141.40.6]) by mailint02.im.hou.compaq.com (Postfix) with ESMTP id 4B3D6B2A4C; Mon, 17 Jan 2000 08:38:34 -0600 (CST) Received: from zk3.dec.com by sigma.zk3.dec.com (8.8.8/1.1.20.3/24Apr98-0811AM) id JAA0000017932; Mon, 17 Jan 2000 09:38:36 -0500 (EST) Message-ID: <388328B7.DAF3904E@zk3.dec.com> Date: Mon, 17 Jan 2000 09:35:35 -0500 From: Mike Daniele Organization: Compaq 64-bit UNIX networking X-Mailer: Mozilla 4.7 [en] (X11; I; OSF1 V5.0 alpha) X-Accept-Language: en MIME-Version: 1.0 To: gopal krishna Cc: agentx@dorothy.peer.com Subject: Re: Master Agent mib instrumentation References: <20000115104145.27160.qmail@web3107.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-agentx@dorothy.bmc.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list Content-Transfer-Encoding: 7bit Hello, gopal krishna wrote: > hello, > > i am planning to build a multilingual(v1,v2c,v3) snmp > master agent > and subagent library with agentx as the protocol > between master and subagents. > > A) I would like to know which are mibs that have to be > instrumented in the master agent alone.(for > example > agentx-mib,rfc 1907,SNMP-FRAMEWORK-mib ). > > *********************************************** > section 4.1 of draft-ietf-agentx-rfc-update-03.txt > says master agent Provides instrumentation for the > MIB objects defined in RFC 1907 , and for any > MIB objects relevant to any administrative > framework it supports. > ************************************************* > if this is a implementation specific issue, what > would be the typical implementation if my master > agent should support snmp v1, v2c & v3. > I think that for SNMPv1/2c, 1907 and the AgentX MIB would be expected. I'll let implementors of SNMPv3 comment on that. > > B)also,is there any guidelines on how the master agent > should dispatch when it recieves varbind list in which > some of the snmp OIDs have instrumentation provided > by master agent itself & for other OIDs subagents > provide instrumentation. That's really a question on how you want to design your implementation, not something that should be covered in the RFC. For our implementation on Tru64 UNIX, there is no special handling within master agent dispatching. All sessions/registered regions are handled identically. Hope this helps, Mike > > regards > gopal > __________________________________________________ > Do You Yahoo!? > Talk to your friends online with Yahoo! Messenger. > http://im.yahoo.com From owner-agentx@dorothy.bmc.com Mon Jan 17 14:03:36 2000 Received: from tangelo.bmc.com (fw-us-hou-1.bmc.com [198.207.223.250]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05886 for ; Mon, 17 Jan 2000 14:03:32 -0500 (EST) Received: from dorothy.peer.com (dorothy.bmc.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id NAA01399; Mon, 17 Jan 2000 13:01:18 -0600 (CST) Received: (from root@localhost) by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id KAA04615 for agentx-list; Mon, 17 Jan 2000 10:58:35 -0800 (PST) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA04590 for agentx@dorothy.bmc.com; Mon, 17 Jan 2000 10:58:30 -0800 (PST) Date: Mon, 17 Jan 2000 10:58:30 -0800 (PST) From: Randy Presuhn Message-Id: <200001171858.KAA04590@dorothy.bmc.com> To: agentx@dorothy.peer.com Subject: Re: Master Agent mib instrumentation Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-agentx@dorothy.bmc.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list Content-Transfer-Encoding: 7bit Hi - > Message-ID: <388328B7.DAF3904E@zk3.dec.com> > Date: Mon, 17 Jan 2000 09:35:35 -0500 > From: Mike Daniele > To: gopal krishna > Cc: agentx@dorothy.peer.com > Subject: Re: Master Agent mib instrumentation > References: <20000115104145.27160.qmail@web3107.mail.yahoo.com> > List-Id: IETF Agentx Working Group mailing list ... > > B)also,is there any guidelines on how the master agent > > should dispatch when it recieves varbind list in which > > some of the snmp OIDs have instrumentation provided > > by master agent itself & for other OIDs subagents > > provide instrumentation. > > That's really a question on how you want to design your implementation, > not something that should be covered in the RFC. > > For our implementation on Tru64 UNIX, there is no special handling > within master agent dispatching. All sessions/registered regions are handled identically. ... We've taken a similar approach in our implementation as well. This works well for other subagent protocols, since their service definitions are remarkably similar. However, there are a couple of annoying objects in RFC 2574 whose semantics require information not carried by an AgentX service: usmUserOwnAuthKeyChange and usmUserOwnPrivKeyChange. Specifically, |usmUserOwnPrivKeyChange OBJECT-TYPE | SYNTAX KeyChange -- typically (SIZE (0 | 32)) for DES | MAX-ACCESS read-create | STATUS current | DESCRIPTION "Behaves exactly as usmUserPrivKeyChange, with one | notable difference: in order for the Set operation | to succeed, the usmUserName of the operation | requester must match the usmUserName that indexes | the row which is targeted by this operation. | In addition, the USM security model must be | used for this operation. So, although the operation dispatch can procede just as it would for any other subagent, one needs to take care to pass the user name and security model through some non-agentx mechanism. Another area where there are subtle "gotchas" is in the sending of responses to key changes; whether the key change is successful or not, the old keying material is used for the response. ------------------------------------------------------------------------ Randy Presuhn randy_presuhn@bmc.com http://www.bmc.com/ Voice: +1 408 546-1006 BMC Software, Inc. 1-3141 2141 N. First Street Fax: +1 408 965-0359 San Jose, California 95131 USA ------------------------------------------------------------------------ Any relationship between my opinions and BMC's should be coincidental. ------------------------------------------------------------------------ From owner-agentx@dorothy.peer.com Mon Jan 24 05:09:46 2000 Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00631 for ; Mon, 24 Jan 2000 05:09:46 -0500 (EST) Received: from dorothy.peer.com (dorothy.bmc.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id VAA18896; Sun, 23 Jan 2000 21:55:11 -0600 (CST) Received: (from root@localhost) by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id KAA07758 for agentx-list; Sun, 23 Jan 2000 10:24:56 -0800 (PST) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA07752; Sun, 23 Jan 2000 10:24:52 -0800 (PST) Date: Sun, 23 Jan 2000 10:24:52 -0800 (PST) From: Randy Presuhn Message-Id: <200001231824.KAA07752@dorothy.bmc.com> To: disman@dorothy.peer.com Subject: You may be dropped if... Cc: agentx@dorothy.peer.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-agentx@dorothy.peer.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list Content-Transfer-Encoding: 7bit Hi - Some sites have apparently decided to block traffic from the disman and agentx WG mailing lists. I find this surprising, since I think our spam record has been quite good. When list administrators get bounces like these, there is no choice but to drop the offending addresses from the mailing list. Note that the nature of these blocks can prevent list administrators from notifying such subscribers that they have been dropped. ------------------------------------------------------------------------ Randy Presuhn randy_presuhn@bmc.com http://www.bmc.com/ Voice: +1 408 546-1006 BMC Software, Inc. 1-3141 2141 N. First Street Fax: +1 408 965-0359 San Jose, California 95131 USA ------------------------------------------------------------------------ Any relationship between my opinions and BMC's should be coincidental. ------------------------------------------------------------------------ > From MAILER-DAEMON Fri Jan 21 19:23:39 PST 2000 > Date: Fri, 21 Jan 2000 21:24:02 -0600 (CST) > From: Mail Delivery Subsystem > Message-Id: <200001220324.VAA08672@tangelo.bmc.com> > To: > Subject: Returned mail: Service unavailable > Auto-Submitted: auto-generated (failure) > > This is a MIME-encapsulated message > > --VAA08672.948511442/tangelo.bmc.com > > The original message was received at Fri, 21 Jan 2000 21:08:10 -0600 (CST) > from dorothy.bmc.com [192.146.153.65] > > ----- The following addresses had permanent fatal errors ----- > > > ----- Transcript of session follows ----- > 451 ... reply: read error from ecarsddd.nortelnetworks.com. > ... while talking to fobos.ulpgc.es.: > >>> MAIL From: > <<< 550 198.207.223.251 is an open relay - see http://www.orbs.org > 554 ... Service unavailable > > --VAA08672.948511442/tangelo.bmc.com > Content-Type: message/delivery-status > > Reporting-MTA: dns; tangelo.bmc.com > Received-From-MTA: DNS; dorothy.bmc.com > Arrival-Date: Fri, 21 Jan 2000 21:08:10 -0600 (CST) > > Final-Recipient: RFC822; mario@cicei.ulpgc.es > Action: failed > Status: 5.0.0 > Remote-MTA: DNS; fobos.ulpgc.es > Diagnostic-Code: SMTP; 550 198.207.223.251 is an open relay - see http://www.orbs.org > Last-Attempt-Date: Fri, 21 Jan 2000 21:20:53 -0600 (CST) > > --VAA08672.948511442/tangelo.bmc.com > Content-Type: text/rfc822-headers > > Return-Path: > Received: from dorothy.peer.com (dorothy.bmc.com [192.146.153.65]) > by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id VAA08621; > Fri, 21 Jan 2000 21:08:10 -0600 (CST) > Received: (from root@localhost) > by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id TAA26967 > for disman-list; Fri, 21 Jan 2000 19:03:26 -0800 (PST) > Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166]) > by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id TAA26962 > for ; Fri, 21 Jan 2000 19:03:10 -0800 (PST) > Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250]) > by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with SMTP id VAA08098 > for ; Fri, 21 Jan 2000 21:03:34 -0600 (CST) > Received: (ramk@localhost) by itech-view2.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) id TAA26314; Fri, 21 Jan 2000 19:02:21 -0800 (PST) > From: Ram Kavasseri > Message-Id: <200001220302.TAA26314@itech-view2.cisco.com> > Subject: draft-ietf-disman-notif-log-mib-13.txt > To: internet-drafts@ietf.org > Date: Fri, 21 Jan 2000 19:02:21 -0800 (PST) > Cc: rpresuhn@dorothy.peer.com, dharrington@mediaone.net, > disman@dorothy.peer.com > X-Mailer: ELM [version 2.5 PL1] > MIME-Version: 1.0 > Content-Type: text/plain; charset=us-ascii > Content-Transfer-Encoding: 7bit > Sender: owner-disman@dorothy.bmc.com > Precedence: bulk > List-Id: IETF disman Working Group mailing list > > --VAA08672.948511442/tangelo.bmc.com-- > > From owner-agentx@dorothy.peer.com Wed Jan 26 00:52:49 2000 Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17021 for ; Wed, 26 Jan 2000 00:52:48 -0500 (EST) Received: from dorothy.bmc.com (dorothy.bmc.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id XAA26414; Tue, 25 Jan 2000 23:52:36 -0600 (CST) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id VAA27700 for agentx-list; Tue, 25 Jan 2000 21:39:27 -0800 (PST) Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166]) by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id VAA27695 for ; Tue, 25 Jan 2000 21:39:22 -0800 (PST) Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250]) by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with SMTP id XAA25039 for ; Tue, 25 Jan 2000 23:39:48 -0600 (CST) Received: from bnatale (dhcppm17.acec.com [38.249.211.239]) by relay1.acec.com (8.9.3/8.9.3) with ESMTP id AAA02765; Wed, 26 Jan 2000 00:38:49 -0500 (EST) Message-Id: <4.2.2.20000126003007.00b4b810@plymouth.acec.com> X-Sender: bnatale@plymouth.acec.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Wed, 26 Jan 2000 00:42:32 -0500 To: agentx@dorothy.peer.com From: Bob Natale Subject: AgentX RFCs published! Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-agentx@dorothy.peer.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list Hi AgentX-ers, In case you did not catch the announcement via one of the RFC annoucements lists, the two AgentX RFCs have finally been published: RFC 2741 is the AgentX Protocol URL: ftp://ftp.isi.edu/in-notes/rfc2741.txt RFC 2742 is the AgentX MIB URL: ftp://ftp.isi.edu/in-notes/rfc2742.txt Once again, my thanks to the contributors, authors, editors, reviewers, advisors, ADs, and the RFC editor for bring these standards track documents to fruition. It is very fitting that these specs were published in the first month of the new millennium...lets hope that signals the start of several new implementations, the completion of others, and wide-spread use of AgentX technology to extend the reach of interoperable SNMP management among the user community. Cordially, BobN ------------ ISO 9001 Registered Quality Supplier ----------- 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 ------------- Free downloads at www.winsnmp.com ------------- From owner-agentx@dorothy.peer.com Mon Jan 31 16:32:29 2000 Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16275 for ; Mon, 31 Jan 2000 16:32:28 -0500 (EST) Received: from dorothy.bmc.com (dorothy.bmc.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id PAA15787; Mon, 31 Jan 2000 15:30:57 -0600 (CST) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id NAA07849 for agentx-list; Mon, 31 Jan 2000 13:04:48 -0800 (PST) Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id NAA07842 for ; Mon, 31 Jan 2000 13:04:45 -0800 (PST) Received: from ec01-hou.bmc.com (ec01-hou.bmc.com [172.17.0.150]) by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id PAA07026 for ; Mon, 31 Jan 2000 15:05:14 -0600 (CST) Received: by ec01-hou.bmc.com with Internet Mail Service (5.5.2650.21) id ; Mon, 31 Jan 2000 15:05:12 -0600 Message-ID: From: "Appelbaum, Muriel" To: "'agentx@dorothy.bmc.com'" Subject: FW: Non-member submission from [Jian.Song@nokia.com] Date: Mon, 31 Jan 2000 15:05:30 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="ISO-8859-1" Sender: owner-agentx@dorothy.peer.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list -----Original Message----- From: owner-agentx@dorothy.peer.com [mailto:owner-agentx@dorothy.peer.com] Sent: Monday, January 31, 2000 12:55 PM To: owner-agentx@dorothy.peer.com Subject: BOUNCE agentx@dorothy.bmc.com: Non-member submission from [Jian.Song@nokia.com] From owner-agentx Mon Jan 31 12:54:38 2000 Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id MAA07311 for ; Mon, 31 Jan 2000 12:54:37 -0800 (PST) From: Jian.Song@nokia.com Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250]) by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with SMTP id OAA04098 for ; Mon, 31 Jan 2000 14:54:43 -0600 (CST) Received: from mgw-i2.ntc.nokia.com (mgw-i2.ntc.nokia.com [131.228.118.61]) by mgw-x2.nokia.com (8.9.3/8.9.3/o) with ESMTP id WAA25199 for ; Mon, 31 Jan 2000 22:54:30 +0200 (EET) Received: from daebh02nok.americas.nokia.com (daebh02nok.americas.nokia.com [172.18.242.183]) by mgw-i2.ntc.nokia.com (8.9.3/8.9.3) with ESMTP id WAA20115 for ; Mon, 31 Jan 2000 22:54:29 +0200 (EET) Received: by daebh02nok with Internet Mail Service (5.5.2448.0) id <1B3WD15L>; Mon, 31 Jan 2000 14:54:27 -0600 Message-ID: To: agentx@dorothy.peer.com Subject: agentxConnIndex missing Date: Mon, 31 Jan 2000 14:53:49 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Hi, In RFC2742, agentxSessionTable is indexed by {agentxConnIndex, agentxSessionIndex}. However, agentxConnIndex is missing from AgentxSessionEntry ::= SEQUENCE { agentxSessionIndex Unsigned32, agentxSessionObjectID OBJECT IDENTIFIER, agentxSessionDescr SnmpAdminString, agentxSessionAdminStatus INTEGER, agentxSessionOpenTime TimeStamp, agentxSessionAgentXVer INTEGER, agentxSessionTimeout INTEGER } I would appreciate that you let me know whether this is an error or it is intentional. Regards, Jian Song Software Designer Nokia 555 Legget Dr. Kanata, Ontario, Canada