From daemon Mon Nov 17 10:46:08 1997 Delivery-Date: Mon, 17 Nov 1997 10:54:10 -0500 Return-Path: daemon Received: (from daemon@localhost) by ietf.org (8.8.7/8.8.7a) id KAA15484 for ietf-123-outbound.10@ietf.org; Mon, 17 Nov 1997 10:45:57 -0500 (EST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.8.7/8.8.7a) with ESMTP id KAA15465; Mon, 17 Nov 1997 10:45:46 -0500 (EST) Message-Id: <199711171545.KAA15465@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce Cc: agentx@fv.com From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-agentx-mib-01.txt Date: Mon, 17 Nov 1997 10:45:46 -0500 Sender: cclark@cnri.reston.va.us --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the SNMP Agent Extensibility Working Group of the IETF. Title : Definitions of Managed Objects for Extensible SNMP Agents Author(s) : M. Greene, S. Gudur Filename : draft-ietf-agentx-mib-01.txt Pages : 18 Date : 14-Nov-97 This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes objects managing SNMP agents that use the Agent Extensibility (AgentX) Protocol. This memo specifies a MIB module in a manner that is both compliant to the SNMPv2 SMI, and semantically identical to the peer SNMPv1 definitions. This memo does not specify a standard for the Internet community. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-agentx-mib-01.txt". A URL for the Internet-Draft is: ftp://ds.internic.net/internet-drafts/draft-ietf-agentx-mib-01.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ds.internic.net US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ds.internic.net. In the body type: "FILE /internet-drafts/draft-ietf-agentx-mib-01.txt". NOTE: The mail server at ds.internic.net can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ds.internic.net" Content-Type: text/plain Content-ID: <19971114180355.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-agentx-mib-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-agentx-mib-01.txt"; site="ds.internic.net"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19971114180355.I-D@ietf.org> --OtherAccess-- --NextPart-- From adm Mon Dec 29 11:12:22 1997 Delivery-Date: Mon, 29 Dec 1997 11:22:08 -0500 Return-Path: adm Received: (from adm@localhost) by ns.ietf.org (8.8.7/8.8.7a) id LAA16247 for ietf-123-outbound.10@ietf.org; Mon, 29 Dec 1997 11:12:02 -0500 (EST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id LAA16131; Mon, 29 Dec 1997 11:07:17 -0500 (EST) Message-Id: <199712291607.LAA16131@ns.ietf.org> To: IETF-Announce: ; Cc: RFC Editor Cc: Internet Architecture Board Cc: agentx@fv.com From: The IESG Subject: Protocol Action: Agent Extensibility (AgentX) Protocol Version 1 to Proposed Standard Date: Mon, 29 Dec 1997 11:07:17 -0500 Sender: scoya@cnri.reston.va.us The IESG has approved the Internet-Draft 'Agent Extensibility (AgentX) Protocol Version 1' as a Proposed Standard. This document is the product of the SNMP Agent Extensibility Working Group. The IESG contact persons are John Curran and Michael O'Dell. Technical Summary This memo defines a standardized framework for extensible SNMP agents. It defines processing entities called master agents and subagents, a protocol (AgentX) used to communicate between them, and the elements of procedure by which the extensible agent processes SNMP protocol messages. Working Group Summary The Working Group spent significant time discussing the scope of the protocol and trying to balance the desire for a straightforward subagent communication model against the desire for a transparent subagent model which would work for any given MIB structure. This resulted in an approach which minimizes subagent communication messages while supporting the many common MIB object configurations. During Last Call, the issue was raised that the protocol was not suitable as a replacement for existing proprietary master/subagent protocols, as it could not address the full range of object types found in some MIBs. In review, it was determined that this tradeoff were made with the rough consensus of the working group, and that the resulting protocol is still sufficiently valuable for portable subagents development that it warrants standardization. Also raised during Last Call was an issue regarding inability of a master agent to administratively decline a subagent's registration request. While not a requirement, per se, it was felt that this concern was reasonable and would be best resolved by the creation of an additional return code or set of codes as determined by implementation experience. Protocol Quality This work has been reviewed by the Area Director responsible for the work as well as others knowledgable regarding master/subagent technology. There are at least two draft implementations at this time. From sw0l+hostmib-errors@andrew.cmu.edu Tue Mar 24 10:05:26 1998 Delivery-Date: Tue, 24 Mar 1998 10:05:31 -0500 Return-Path: sw0l+hostmib-errors@andrew.cmu.edu Received: from cnri.reston.va.us (cnri [132.151.1.1]) by ns.ietf.org (8.8.7/8.8.7a) with ESMTP id KAA29074 for ; Tue, 24 Mar 1998 10:05:05 -0500 (EST) Received: from andrew.cmu.edu (ANDREW.CMU.EDU [128.2.10.101]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id KAA07005 for ; Tue, 24 Mar 1998 10:07:36 -0500 (EST) Received: (from postman@localhost) by andrew.cmu.edu (8.8.5/8.8.2) id JAA07394; Tue, 24 Mar 1998 09:58:57 -0500 (EST) Received: via switchmail for hostmib+@andrew.cmu.edu; Tue, 24 Mar 1998 09:58:56 -0500 (EST) Received: from po5.andrew.cmu.edu via qmail ID ; Tue, 24 Mar 1998 09:55:41 -0500 (EST) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by po5.andrew.cmu.edu (8.8.5/8.8.2) with ESMTP id JAA12530 for ; Tue, 24 Mar 1998 09:55:34 -0500 (EST) Received: from unix.artemis.jussieu.fr (root@unix.artemis.jussieu.fr [134.157.55.10]) by shiva.jussieu.fr (8.8.8/jtpda-5.3) with ESMTP id PAA15293 ; Tue, 24 Mar 1998 15:53:55 +0100 (CET) Received: from pelsys.com (dione.artemis.jussieu.fr [134.157.55.57]) by unix.artemis.jussieu.fr (8.8.7/jtpda-5.2) with ESMTP id PAA03492 ; Tue, 24 Mar 1998 15:45:20 GMT Message-ID: <3517C8A0.42C40750@pelsys.com> Date: Tue, 24 Mar 1998 15:52:17 +0100 From: aecl X-Mailer: Mozilla 4.03 [fr] (Win95; I) MIME-Version: 1.0 To: agentx@fv.com, hostmib@andrew.cmu.edu, rdbms@us.oracle.com, rmonmib@cisco.com, applmib@emi-summit.com Subject: (pas d'objet) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit subscribe From adm Thu Apr 16 10:48:12 1998 Delivery-Date: Thu, 16 Apr 1998 11:01:27 -0400 Return-Path: adm Received: (from adm@localhost) by ns.ietf.org (8.8.5/8.8.7a) id KAA05012 for ietf-123-outbound.10@ietf.org; Thu, 16 Apr 1998 10:45:02 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ns.ietf.org (8.8.5/8.8.7a) with ESMTP id JAA03090; Thu, 16 Apr 1998 09:44:34 -0400 (EDT) Message-Id: <199804161344.JAA03090@ns.ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: agentx@peer.com From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-agentx-mib-02.txt Date: Thu, 16 Apr 1998 09:44:34 -0400 Sender: cclark@cnri.reston.va.us --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the SNMP Agent Extensibility Working Group of the IETF. Title : Definitions of Managed Objects for Extensible SNMP Agents Author(s) : M. Greene, S. Gudur Filename : draft-ietf-agentx-mib-02.txt Pages : 18 Date : 15-Apr-98 This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes objects managing SNMP agents that use the Agent Extensibility (AgentX) Protocol. This memo specifies a MIB module in a manner that is both compliant to the SNMPv2 SMI, and semantically identical to the peer SNMPv1 definitions. This memo does not specify a standard for the Internet community. Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-agentx-mib-02.txt". A URL for the Internet-Draft is: ftp://ftp.ietf.org/internet-drafts/draft-ietf-agentx-mib-02.txt Internet-Drafts directories are located at: Africa: ftp.is.co.za Europe: ftp.nordu.net ftp.nis.garr.it Pacific Rim: munnari.oz.au US East Coast: ftp.ietf.org US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-agentx-mib-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <19980415173543.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-agentx-mib-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-agentx-mib-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19980415173543.I-D@ietf.org> --OtherAccess-- --NextPart-- From ashishkh@wipinfo.soft.net Wed Jun 24 11:07:35 1998 Delivery-Date: Wed, 24 Jun 1998 11:07:35 -0400 Return-Path: ashishkh@wipinfo.soft.net Received: from cnri.reston.va.us (ns [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id BAA15261 for ; Wed, 24 Jun 1998 01:09:23 -0400 (EDT) Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id BAA13431 for ; Wed, 24 Jun 1998 01:11:39 -0400 (EDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id AAA25634 for ; Wed, 24 Jun 1998 00:09:15 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma025081; Wed, 24 Jun 98 00:08:01 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id AAA05077 for ; Wed, 24 Jun 1998 00:07:28 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma004469; Wed, 24 Jun 98 00:07:03 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id AAA08628; Wed, 24 Jun 1998 00:07:06 -0500 (CDT) Received: from almond.bmc.com (almond.bmc.com [172.17.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id WAA29666 for ; Tue, 23 Jun 1998 22:05:15 -0700 (PDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id AAA24667 for ; Wed, 24 Jun 1998 00:05:07 -0500 (CDT) Received: from agni.wipinfo.soft.net(164.164.6.20) by almond.bmc.com via smap (V2.0) id xma024635; Wed, 24 Jun 98 00:04:58 -0500 Received: from scan.wipinfo.soft.net by wipinfo.soft.net (SMI-8.6/SMI-SVR4) id KAA01078; Wed, 24 Jun 1998 10:29:54 -0500 Received: from 192.9.100.151 by scan.wipinfo.soft.net (InterScan E-Mail VirusWall NT) Received: from opel ([192.9.52.22]) by divya.wipinfo.soft.net (8.8.5/8.8.5) with SMTP id KAA16929 for ; Wed, 24 Jun 1998 10:36:09 +0530 Message-Id: <3.0.5.32.19980624103433.00946cb0@tagore> X-Sender: ashishkh@tagore X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 24 Jun 1998 10:34:33 To: agentx@peer.com From: Ashish Hanwadikar Subject: UNIX Domain Sockets Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Hi all, I want to know whether Microsoft NT/win95 supports UNIX Domain sockets or not. I searched for it msdn, but could not find it out. The Simple Times Article in March 1998 issue by Matt White on "An OverView of AgentX Protocol" says in "Security Issues" Subsection that "Fortunately, there are implementations of Unix domain sockets for all major platforms, including Microsoft Windows". If that is the case where can I get the implementation of UNIX domain sockets on NT/95? Thanks in advance, With Regds., Ashish Hanwadikar Technology Solutions, Wipro Limited Bangalore-27 http://www.geocities.com/SiliconValley/Bay/5393/ Email: ashishkh@writeme.com Ph: +91-80-2241730 Ext. 3315 From rpresuhn@dorothy.bmc.com Wed Jun 24 11:07:44 1998 Delivery-Date: Wed, 24 Jun 1998 11:07:44 -0400 Return-Path: rpresuhn@dorothy.bmc.com Received: from cnri.reston.va.us (ns [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id TAA07260 for ; Tue, 23 Jun 1998 19:55:44 -0400 (EDT) Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id TAA12667 for ; Tue, 23 Jun 1998 19:57:49 -0400 (EDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id SAA14426 for ; Tue, 23 Jun 1998 18:55:15 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma014111; Tue, 23 Jun 98 18:54:26 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id SAA28877 for ; Tue, 23 Jun 1998 18:53:47 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma027544; Tue, 23 Jun 98 18:52:35 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id SAA09812; Tue, 23 Jun 1998 18:52:50 -0500 (CDT) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id QAA27732 for agentx@peer.com; Tue, 23 Jun 1998 16:51:01 -0700 (PDT) Date: Tue, 23 Jun 1998 16:51:01 -0700 (PDT) From: Randy Presuhn Message-Id: <199806232351.QAA27732@dorothy.bmc.com> To: agentx@peer.com Subject: Re: Transport Mappings Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi - > Date: Tue, 23 Jun 1998 15:59:45 > To: agentx@peer.com > From: Ashish Hanwadikar > Subject: Transport Mappings ... > 1) The Transport Mappings TCP and UNIX Domain Socket are compulsory or > optional? > The AgentX RFC just mentions the two transport Domains. However, it does > not say whether the Master Agent or Sub Agents should always implement TCP > or UNIX Domain Sockets. > > My guess is that the Transport Mappings are purely optional. ... That'd be my reading of the current words. I'd prefer it if support for the TCP mapping were mandatory, but I can live with the current language. > If implementation of Transport Mapping are purely optional, then detection > of whether master agent is running or not is difficult to be detected by > the subagent library or subagent implementation. ... It's not THAT hard. One can use getservbyname() as well as the old "just try it" approach. One can even do this to support multiple subagent protocols over multiple transports. ... > e) One more alternative here is to include the master agent code as a > separate module alongwith subagent api or code. Thus, if no master agent is > available then subagent implementation can take over that responsibility. > This behavior can be tailored through some parameter in the config files or > whatever mechanism available. ... Deja vu. The access rights needed within a system for a master agent (for privacy/authentication keys and access control information) should not be within reach of a typical subagent. It's one thing to trigger the activation of a master agent if none is found; it's quite another to BECOME the master agent if no one else is doing the job. ----------------------------------------------------------------------- Randy Presuhn Email: rpresuhn@bmc.com http://www.bmc.com Voice: +1 408 616-3100 BMC Software, Inc. 965 Stewart Drive Fax: +1 408 616-3101 Sunnyvale, California 94086 USA ----------------------------------------------------------------------- In accordance with the BMC Communications Systems Use and Security Policy, 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 mwhite@andrew.cmu.edu Wed Jun 24 14:18:45 1998 Delivery-Date: Wed, 24 Jun 1998 14:18:46 -0400 Return-Path: mwhite@andrew.cmu.edu Received: from cnri.reston.va.us (ns [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id LAA21645 for ; Wed, 24 Jun 1998 11:44:43 -0400 (EDT) Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id LAA15386 for ; Wed, 24 Jun 1998 11:46:54 -0400 (EDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id KAA25522 for ; Wed, 24 Jun 1998 10:44:32 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma025168; Wed, 24 Jun 98 10:43:28 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id KAA09576 for ; Wed, 24 Jun 1998 10:42:54 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma008744; Wed, 24 Jun 98 10:42:15 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id KAA00286; Wed, 24 Jun 1998 10:41:54 -0500 (CDT) Received: from almond.bmc.com (almond.bmc.com [172.17.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id IAA02147 for ; Wed, 24 Jun 1998 08:37:12 -0700 (PDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id KAA24340 for ; Wed, 24 Jun 1998 10:37:09 -0500 (CDT) Received: from cmu1.acs.cmu.edu(128.2.35.186) by almond.bmc.com via smap (V2.0) id xma024323; Wed, 24 Jun 98 10:36:50 -0500 Received: from freehold.net.cmu.edu (FREEHOLD.NET.CMU.EDU [128.2.6.69]) by cmu1.acs.cmu.edu (8.8.5/8.8.5) with SMTP id LAA20936; Wed, 24 Jun 1998 11:33:04 -0400 (EDT) Date: Wed, 24 Jun 1998 11:33:03 -0400 (EDT) From: Matthew White X-Sender: mwhite@freehold.net.cmu.edu To: Ashish Hanwadikar cc: agentx@peer.com Subject: Re: UNIX Domain Sockets In-Reply-To: <3.0.5.32.19980624103433.00946cb0@tagore> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Ashish: The Cygnus GCC for windows supports unix domain sockets. You can get more information from http://www.cygnus.com/. -Matt On Wed, 24 Jun 1998, Ashish Hanwadikar wrote: > Hi all, > I want to know whether Microsoft NT/win95 supports UNIX Domain > sockets or not. I searched for it msdn, but could not find it out. The > Simple Times Article in March 1998 issue by Matt White on "An OverView of > AgentX Protocol" says in "Security Issues" Subsection that "Fortunately, > there are implementations of Unix domain sockets for all major platforms, > including Microsoft Windows". > If that is the case where can I get the implementation of UNIX domain > sockets on NT/95? > Thanks in advance, > > With Regds., > Ashish Hanwadikar > Technology Solutions, > Wipro Limited > Bangalore-27 > http://www.geocities.com/SiliconValley/Bay/5393/ > Email: ashishkh@writeme.com > Ph: +91-80-2241730 Ext. 3315 > > ---------- Matt White Network Systems Designer Carnegie Mellon Computing Services From daniele@zk3.dec.com Thu Jun 25 13:39:13 1998 Delivery-Date: Thu, 25 Jun 1998 13:39:13 -0400 Return-Path: daniele@zk3.dec.com Received: from cnri.reston.va.us (ns [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id NAA10217 for ; Thu, 25 Jun 1998 13:39:12 -0400 (EDT) Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id NAA20853 for ; Thu, 25 Jun 1998 13:41:33 -0400 (EDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id MAA09830 for ; Thu, 25 Jun 1998 12:39:12 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma009682; Thu, 25 Jun 98 12:38:43 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id MAA24670 for ; Thu, 25 Jun 1998 12:38:11 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma024119; Thu, 25 Jun 98 12:37:31 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id MAA01688; Thu, 25 Jun 1998 12:36:39 -0500 (CDT) Received: from cashew.bmc.com (cashew.bmc.com [172.19.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id KAA16172 for ; Thu, 25 Jun 1998 10:25:23 -0700 (PDT) Received: (from uucp@localhost) by cashew.bmc.com (8.8.8/8.8.8) id MAA08198 for ; Thu, 25 Jun 1998 12:25:23 -0500 (CDT) Received: from mail11.digital.com(192.208.46.10) by cashew.bmc.com via smap (V2.0) id xma008191; Thu, 25 Jun 98 12:25:03 -0500 Received: from quarry.zk3.dec.com (fquarry.zk3.dec.com [16.140.160.9]) by mail11.digital.com (8.8.8/8.8.8/WV1.0f) with SMTP id NAA27472 for ; Thu, 25 Jun 1998 13:24:57 -0400 (EDT) Received: from bernie.zk3.dec.com by quarry.zk3.dec.com; (5.65v4.0/1.1.8.2/16Jan95-0946AM) id AA17978; Thu, 25 Jun 1998 13:24:56 -0400 Received: from localhost by bernie.zk3.dec.com; (5.65/1.1.8.2/22Aug96-1117AM) id AA04982; Thu, 25 Jun 1998 13:24:57 -0400 Message-Id: <9806251724.AA04982@bernie.zk3.dec.com> To: agentx@peer.com Subject: Testing: some early results and net availability Date: Thu, 25 Jun 98 13:24:57 -0400 From: Mike Daniele X-Mts: smtp Hi, We've done some testing of DEC's subagent library vis a vis Peer/BMC's master agent. In general, the news is good. We've been able to open a session, register multiple regions, and have some SNMP Get and GetNext requests handled correctly end to end. I wanted to note 2 things that might help avoid problems for others: 1) SearchRange ending OID Cannot be identical to the SearchRange starting OID. 7.2.2.2 states that for next/bulk, a subagent must return a variable such that > - If the ending OID is not null, the variable's name > lexicographically precedes the ending OID. If the SearchRange's ending oid == its starting oid, the subagent can't legally return anything. 2) Register PDU's optional range upper bound (r.upper_bound) This field is present only if r.range_subid is non-zero. If r.range_subid is 0, the PDU ends with r.region. It does NOT contain (a 0-valued) r.upper_bound in this case. Note to editors: We should discuss r.upper_bound in sections 6.2.3 and 6.2.4 in a separate paragraph, just like we do with all the other fields. We should also include an example that has no upper bound. We have master and subagents available for testing (via TCP over the internet) if other folks are interested in doing so before the bakeoff. Thanks Lauren @ BMC, the testing so far has been very valuable. Regards, Mike From bnatale@acecomm.com Tue Jun 30 12:01:54 1998 Delivery-Date: Tue, 30 Jun 1998 12:01:55 -0400 Return-Path: bnatale@acecomm.com Received: from cnri.reston.va.us (ns [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id MAA18093 for ; Tue, 30 Jun 1998 12:01:54 -0400 (EDT) Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id MAA10817 for ; Tue, 30 Jun 1998 12:04:11 -0400 (EDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id LAA13829 for ; Tue, 30 Jun 1998 11:01:49 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma013522; Tue, 30 Jun 98 11:00:37 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id LAA17973 for ; Tue, 30 Jun 1998 11:00:02 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma016958; Tue, 30 Jun 98 10:59:03 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id KAA13465; Tue, 30 Jun 1998 10:59:06 -0500 (CDT) Received: from almond.bmc.com (almond.bmc.com [172.17.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id IAA18530 for ; Tue, 30 Jun 1998 08:43:43 -0700 (PDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id KAA11264 for ; Tue, 30 Jun 1998 10:43:41 -0500 (CDT) Received: from relay2.smtp.psi.net(38.8.188.2) by almond.bmc.com via smap (V2.0) id xma011245; Tue, 30 Jun 98 10:43:11 -0500 Received: from [192.152.208.5] (helo=acecomm.com) by relay2.smtp.psi.net with smtp (Exim 1.90 #1) for agentx@peer.com id 0yr2YW-0000bN-00; Tue, 30 Jun 1998 11:42:58 -0400 Received: from bnatale by acecomm.com (5.65/3.2.083191-ACE*COMM) id AA06228; Tue, 30 Jun 1998 11:45:00 -0400 Message-Id: <9806301545.AA06228@acecomm.com> X-Sender: natale@nips.acec.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Tue, 30 Jun 1998 11:44:41 -0400 To: agentx@peer.com From: Bob Natale Subject: Updated goals and milestones Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA18093 Hi, The AgentX page at www.ietf.org has been updated with the following: Goals and Milestones: Done Publication of AgentX protocol specification Done Submit working draft version of AgentX MIB I-D. Jun 98 Collect and evaluate implementation reports (through bake-off). Jul 98 Conduct AgentX interoperability testing (July 23-24, Sunnyvale). Aug 98 Meet at 42nd IETF-Chicago (refine or revise RFC 2257). Sep 98 Petition IESG to advance RFC 2257 to Draft or recycle at Proposed Oct 98 Submit final version of AgentX MIB I-D to IESG for consideration as Proposed. Nov 98 Submit initial draft version of AgentX API I-D Dec 98 Submit interim draft version of AgentX API I-D. Jan 99 Submit final version of AgentX API I-D to IESG for consideration as an Informational RFC. Feb 99 Evaluate necessary revisions to RFC 2257. Feb 99 Evaluate necessary revisions to AgentX MIB RFC. Mar 99 Meet at 44th IETF to Assess status of AgentX deployment Determine need for AgentX v2 (Protocol, MIB, or API) Plan future work items accordingly. Apr 99 Submit new charter proposal to IESG or retire WG. I have submitted a request for a single 2hr meeting slot in Chicago...I have not yet received notification of the scheduled time and place. The basic agenda will include: - the usual preliminaries - review implementation status reports - review bake-off results, findings - review list of open issues - review status of AgentX MIB - review need/desire for a standard AgentX API - review status of SNMPv3 and DISMAN wrt AgentX - recommend working plan wrt any of the above items - the usual summaries Comments on any of the above are welcomed...as are proposed mods (additions/deletions/changes) to the agenda outline. 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 ashishkh@wipinfo.soft.net Wed Jul 1 05:08:46 1998 Delivery-Date: Wed, 01 Jul 1998 05:08:47 -0400 Return-Path: ashishkh@wipinfo.soft.net Received: from cnri.reston.va.us (ns [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id FAA06581 for ; Wed, 1 Jul 1998 05:08:43 -0400 (EDT) Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id FAA14628 for ; Wed, 1 Jul 1998 05:10:54 -0400 (EDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id EAA00633 for ; Wed, 1 Jul 1998 04:08:34 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma000192; Wed, 1 Jul 98 04:07:11 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id EAA03319 for ; Wed, 1 Jul 1998 04:06:36 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma002808; Wed, 1 Jul 98 04:06:00 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id EAA08592; Wed, 1 Jul 1998 04:06:13 -0500 (CDT) Received: from almond.bmc.com (almond.bmc.com [172.17.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id CAA17702 for ; Wed, 1 Jul 1998 02:02:39 -0700 (PDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id EAA29692 for ; Wed, 1 Jul 1998 04:02:27 -0500 (CDT) Received: from agni.wipinfo.soft.net(164.164.6.20) by almond.bmc.com via smap (V2.0) id xma029655; Wed, 1 Jul 98 04:02:10 -0500 Received: from scan.wipinfo.soft.net by wipinfo.soft.net (SMI-8.6/SMI-SVR4) id OAA00601; Wed, 1 Jul 1998 14:26:07 -0500 Received: from 192.9.100.151 by scan.wipinfo.soft.net (InterScan E-Mail VirusWall NT) Received: from opel ([192.9.52.22]) by divya.wipinfo.soft.net (8.8.5/8.8.5) with SMTP id OAA07687; Wed, 1 Jul 1998 14:32:22 +0530 Reply-To: From: "Ashish K Hanwadikar" To: "Bob Natale" Cc: "Agentx" Subject: RE: Updated goals and milestones Date: Wed, 1 Jul 1998 14:31:07 +0530 Keywords: Mailing Lists Message-ID: <000501bda4ce$c904dfc0$163409c0@opel.wipinfo.soft.net> MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Reply-By: Mon, 6 Jul 1998 18:00:00 +0530 In-Reply-To: <9806301545.AA06228@acecomm.com> X-Message-Flag: Follow up Content-Type: text/plain; charset="iso-8859-1" X-MIME-Autoconverted: from 8bit to quoted-printable by tangelo.bmc.com id EAA08592 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id FAA06581 Hi, Is the AgentX API I-D going to be an information RFC or a standard RFC? Where can I get more information about the efforts on AgentX API (mailing lists, working groups etc.)? Also, one more thing, the AgentX-Close-PDU when sent by Sub Agent to Master Agent does not require master agent to respond until there is an error in closing the session. This is unnecessarily making the implementation complicated. Why can't master agent send response to all agentx-close-PDUs irrespective of the outcome? Otherwise, the sub agent has to keep on waiting for the response to agentx-close-PDU, when he don't even know whether there will be any response or not. The same is true for agentx-notify-PDU. The implementation becomes very complicated when we have to design a generic sub agent API. What should be the semantics of the call agent-close-session(sessionID), blocking or non-blocking? If it is non-blocking what happens when there is error in closing the session and response is received from the master agent? If it is made blocking and there is no resonse because the session was closed successfuly then how long should the call block? This waiting on the sub agent side is a general problem. What should be the timeout values from the sub agent side, i.e. for how long should the sub agent wait for responses from the master agent for various PDU's like registration etc. Thanks in advance. > -----Original Message----- > From: Bob Natale [mailto:bnatale@acecomm.com] > Sent: Tuesday, June 30, 1998 9:15 PM > To: agentx@peer.com > Subject: Updated goals and milestones > > > Hi, > > The AgentX page at www.ietf.org has been > updated with the > following: > > Goals and Milestones: > > Done Publication of AgentX protocol specification > Done Submit working draft version of AgentX MIB I-D. > Jun 98 Collect and evaluate implementation reports > (through bake-off). > Jul 98 Conduct AgentX interoperability testing > (July 23-24, Sunnyvale). > Aug 98 Meet at 42nd IETF-Chicago (refine or revise > RFC 2257). > Sep 98 Petition IESG to advance RFC 2257 to Draft > or recycle at Proposed > Oct 98 Submit final version of AgentX MIB I-D to > IESG for consideration as Proposed. > Nov 98 Submit initial draft version of AgentX API I-D > Dec 98 Submit interim draft version of AgentX API I-D. > Jan 99 Submit final version of AgentX API I-D to IESG > for consideration as an Informational RFC. > Feb 99 Evaluate necessary revisions to RFC 2257. > Feb 99 Evaluate necessary revisions to AgentX MIB RFC. > Mar 99 Meet at 44th IETF to > Assess status of AgentX deployment > Determine need for AgentX v2 (Protocol, MIB, or API) > Plan future work items accordingly. > Apr 99 Submit new charter proposal to IESG or retire WG. > > I have submitted a request for a single 2hr meeting slot in > Chicago...I have not yet received notification of the scheduled > time and place. The basic agenda will include: > > - the usual preliminaries > - review implementation status reports > - review bake-off results, findings > - review list of open issues > - review status of AgentX MIB > - review need/desire for a standard AgentX API > - review status of SNMPv3 and DISMAN wrt AgentX > - recommend working plan wrt any of the above items > - the usual summaries > > Comments on any of the above are welcomed...as are proposed > mods (additions/deletions/changes) to the agenda outline. > > 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 bnatale@acecomm.com Mon Jul 6 11:28:18 1998 Delivery-Date: Mon, 06 Jul 1998 11:28:19 -0400 Return-Path: bnatale@acecomm.com Received: from cnri.reston.va.us (ns [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id LAA24913 for ; Mon, 6 Jul 1998 11:28:18 -0400 (EDT) Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id LAA03235 for ; Mon, 6 Jul 1998 11:30:38 -0400 (EDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id KAA23089 for ; Mon, 6 Jul 1998 10:28:11 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma022849; Mon, 6 Jul 98 10:27:04 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id KAA13780 for ; Mon, 6 Jul 1998 10:26:30 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma013317; Mon, 6 Jul 98 10:26:08 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id KAA14187; Mon, 6 Jul 1998 10:25:55 -0500 (CDT) Received: from almond.bmc.com (almond.bmc.com [172.17.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id IAA29874 for ; Mon, 6 Jul 1998 08:18:41 -0700 (PDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id KAA22297 for ; Mon, 6 Jul 1998 10:18:38 -0500 (CDT) Received: from relay2.smtp.psi.net(38.8.188.2) by almond.bmc.com via smap (V2.0) id xma022295; Mon, 6 Jul 98 10:18:27 -0500 Received: from [192.152.208.5] (helo=acecomm.com) by relay2.smtp.psi.net with smtp (Exim 1.90 #1) for agentx@peer.com id 0ytD24-0001tf-00; Mon, 6 Jul 1998 11:18:21 -0400 Received: from bnatale by acecomm.com (5.65/3.2.083191-ACE*COMM) id AA00601; Mon, 6 Jul 1998 11:20:39 -0400 Message-Id: <9807061520.AA00601@acecomm.com> X-Sender: natale@nips.acec.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Mon, 06 Jul 1998 11:20:25 -0400 To: agentx@peer.com From: Bob Natale Subject: Fwd: 42nd IETF-CHICAGO, IL: AGENTX Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" >Date: Mon, 06 Jul 1998 10:54:59 -0400 >From: Marcia Beaulieu >This is to confirm one session for AGENTX as follows: > > Wednesday, August 26 at 1530-1730 > > Other groups scheduled at that time: ip1394, > Routing Area Meeting, avt We must submit a formal agenda by Aug 19. I have already posted (on Jun 30) the outline candidate agenda included below. Please post any suggested changes to the list (or to me directly if you prefer). Thanks. The basic agenda will include: - the usual preliminaries - review implementation status reports - review bake-off results, findings - review list of open issues - review status of AgentX MIB - review need/desire for a standard AgentX API - review status of SNMPv3 and DISMAN wrt AgentX - recommend working plan wrt any of the above items - the usual summaries 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 uglyware@berkscountypa.com Thu Jul 16 02:50:38 1998 Delivery-Date: Thu, 16 Jul 1998 02:50:39 -0400 Return-Path: uglyware@berkscountypa.com Received: from cnri.reston.va.us (ns [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id CAA08466 for ; Thu, 16 Jul 1998 02:50:38 -0400 (EDT) From: uglyware@berkscountypa.com Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id CAA19048 for ; Thu, 16 Jul 1998 02:50:34 -0400 (EDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id BAA05076 for ; Thu, 16 Jul 1998 01:50:38 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma004777; Thu, 16 Jul 98 01:49:41 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id BAA25510 for ; Thu, 16 Jul 1998 01:49:05 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma025284; Thu, 16 Jul 98 01:48:34 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id BAA20526; Thu, 16 Jul 1998 01:48:45 -0500 (CDT) Received: from almond.bmc.com (almond.bmc.com [172.17.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id XAA07395 for ; Wed, 15 Jul 1998 23:41:12 -0700 (PDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id BAA04079 for ; Thu, 16 Jul 1998 01:41:11 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma004065; Thu, 16 Jul 98 01:40:45 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id BAA23228 for ; Thu, 16 Jul 1998 01:40:12 -0500 (CDT) Date: Thu, 16 Jul 1998 01:40:12 -0500 (CDT) Message-Id: <199807160640.BAA23228@dresden.bmc.com> Received: from unknown(205.148.246.213) by dresden.bmc.com via smap (3.2) id xma023215; Thu, 16 Jul 98 01:40:05 -0500 To: agentx@peer.com Subject: Public Service - S.M.A.R.T. Sensor As a public service, Higher Ground Diagnostics, Inc. is offering a free download of the Hard Drive Mechanics S.M.A.R.T. sensor. This program will check your PC for the presence of *Predictive* technology installed into most hard drives built after 1996. This technology is capable of determining when hard drive failures will occur. If your hard drive has the S.M.A.R.T. technology, then your PC already has the ability to detect hard drive crashes, weeks even months before they actually occur. To take advantage of the S.M.A.R.T. technology, you simply need to access it. As a free public service, the S.M.A.R.T. tester can be downloaded from http://www.uglyware.com/deluxe/ The S.M.A.R.T. tester has been checked for viruses and may be downloaded safely from that website. Zandy Carter International Marketing Manager From agentx-bugs@andrew.cmu.edu Fri Jul 17 13:46:49 1998 Delivery-Date: Fri, 17 Jul 1998 13:46:50 -0400 Return-Path: agentx-bugs@andrew.cmu.edu Received: from cnri.reston.va.us (ns [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id NAA12346 for ; Fri, 17 Jul 1998 13:46:49 -0400 (EDT) From: agentx-bugs@andrew.cmu.edu Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id NAA27198 for ; Fri, 17 Jul 1998 13:46:39 -0400 (EDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id MAA08130 for ; Fri, 17 Jul 1998 12:46:43 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma007598; Fri, 17 Jul 98 12:45:05 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id MAA26914 for ; Fri, 17 Jul 1998 12:44:31 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma025612; Fri, 17 Jul 98 12:43:35 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id MAA22575; Fri, 17 Jul 1998 12:43:50 -0500 (CDT) Received: from cashew.bmc.com (cashew.bmc.com [172.19.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id JAA26493 for ; Fri, 17 Jul 1998 09:27:31 -0700 (PDT) Received: (from uucp@localhost) by cashew.bmc.com (8.8.8/8.8.8) id LAA05633 for ; Fri, 17 Jul 1998 11:27:25 -0500 (CDT) Received: from gauntlet.fv.com(207.67.199.118) by cashew.bmc.com via smap (V2.0) id xma005619; Fri, 17 Jul 98 11:27:02 -0500 Received: from shekel.fv.com (shekel.fv.com [207.67.199.130]) by gauntlet.fv.com (8.9.1/8.9.0) with ESMTP id JAA26845 for ; Fri, 17 Jul 1998 09:25:53 -0700 (PDT) Received: from gauntlet.fv.com (gauntlet-in.fv.com [10.0.0.2]) by shekel.fv.com (8.9.1/8.9.1) with ESMTP id JAA04153 for ; Fri, 17 Jul 1998 09:26:45 -0700 (PDT) Received: from mail1.andrew.cmu.edu (MAIL1.ANDREW.CMU.EDU [128.2.10.131]) by gauntlet.fv.com (8.9.1/8.9.0) with ESMTP id JAA26831 for ; Fri, 17 Jul 1998 09:25:42 -0700 (PDT) Received: from po4.andrew.cmu.edu (PO4.ANDREW.CMU.EDU [128.2.10.104]) by mail1.andrew.cmu.edu (8.8.5/8.8.2) with ESMTP id MAA11804 for ; Fri, 17 Jul 1998 12:26:41 -0400 (EDT) Received: (from daemon@localhost) by po4.andrew.cmu.edu (8.8.5/8.8.2) id MAA23553 for post+internet.computing.agentx@MAIL1.ANDREW.CMU.EDU; Fri, 17 Jul 1998 12:26:38 -0400 (EDT) Received: via switchmail for post+internet.computing.agentx@andrew.cmu.edu; Fri, 17 Jul 1998 12:26:36 -0400 (EDT) Received: from cmu1.acs.cmu.edu (CMU1.ACS.CMU.EDU [128.2.35.186]) by po4.andrew.cmu.edu (8.8.5/8.8.2) with ESMTP id MAA23530; Fri, 17 Jul 1998 12:26:26 -0400 (EDT) Received: from FRAUGHT.NET.CMU.EDU (FRAUGHT.NET.CMU.EDU [128.2.6.66]) by cmu1.acs.cmu.edu (8.8.5/8.8.5) with SMTP id MAA24850; Fri, 17 Jul 1998 12:26:22 -0400 (EDT) Date: Fri, 17 Jul 1998 12:28:33 -0400 To: post+internet.computing.agentx@andrew.cmu.edu Subject: CMU AgentX v0.1.1 available Message-ID: <3030348966.900678513@FRAUGHT.NET.CMU.EDU> X-Mailer: Mulberry (Win32) [1.3.3, s/n S-100002] X-Authenticated: mwhite by cyrus.andrew.cmu.edu X-Licensed-To: site license MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I have made a second alpha quality release of our AgentX subagent library and snmpd available for FTP. While there are still several protocol features that need to be implemented, we have verified that we interoperate with Digital's implementation of the AgentX protocol. The web site for the CMU AgentX project is located at; http://www.net.cmu.edu/projects/agentx/ Commnets or questions should be addressed to: agentx-bug@andrew.cmu.edu Thanks to all who have shown interest in our work. Matt White ---------- Matt White Maintainer, AgentX Implementation Carnegie Mellon Computing Services From ashishkh@wipinfo.soft.net Fri Jul 31 11:28:58 1998 Delivery-Date: Fri, 31 Jul 1998 11:28:58 -0400 Return-Path: ashishkh@wipinfo.soft.net Received: from cnri.reston.va.us (ns [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id LAA21286 for ; Fri, 31 Jul 1998 11:28:56 -0400 (EDT) Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id LAA28480 for ; Fri, 31 Jul 1998 11:27:34 -0400 (EDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id KAA17698 for ; Fri, 31 Jul 1998 10:27:48 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma017391; Fri, 31 Jul 98 10:26:49 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id KAA18543 for ; Fri, 31 Jul 1998 10:26:10 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma017781; Fri, 31 Jul 98 10:25:34 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id KAA18474; Fri, 31 Jul 1998 10:25:49 -0500 (CDT) Received: from almond.bmc.com (almond.bmc.com [172.17.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id GAA11429 for ; Fri, 31 Jul 1998 06:59:40 -0700 (PDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id IAA11006 for ; Fri, 31 Jul 1998 08:59:38 -0500 (CDT) Received: from agni.wipinfo.soft.net(164.164.6.20) by almond.bmc.com via smap (V2.0) id xma010837; Fri, 31 Jul 98 08:59:03 -0500 Received: from tagore.wipinfo.soft.net by wipinfo.soft.net (SMI-8.6/SMI-SVR4) id TAA09690; Fri, 31 Jul 1998 19:23:51 -0500 From: "Ashish Hanwadikar" To: "Agentx" Cc: "RAMAKUMARA K" Subject: Sub Agent Processing of AgentX GetNext Response Date: Fri, 31 Jul 1998 19:29:15 +0530 Message-ID: <005301bdbc8b$67266f10$163409c0@opel.wipinfo.soft.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0054_01BDBCB9.80DEAB10" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 This is a multi-part message in MIME format. ------=_NextPart_000_0054_01BDBCB9.80DEAB10 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Hi all, While going through the AgentX RFC we noticed one ambiguity: "Section 7.2.2.2. Subagent Processing of the agentx-GetNext-PDU Upon the subagent's receipt of an agentx-GetNext-PDU, each SearchRange in the request is processed as follows: (1) The subagent searches for a variable within the lexicographically ordered list of variable names for all variables it instantiates (without regard to registration of regions) within the indicated context and session, for which the following are all true:" Suppose master agent sends AgentX GetNext request to a subagent (Sub Agent #1) with a SearchRange (falling under a target MIB Region #1). The sub agent responds with a oid and its value falling under a different MIB Region (lexicographically after MIB Region #1). Lets call these region as MIB Region #2. Now suppose another sub agent had registered an MIB Region #3. The lexicographical relationship is MIB Region #1 < #3 < #2 That means, if the SearchRange doesn't fall within MIB Region #1, then ideally target sub agent should return endOfMIBView. The Master Agent will find lexicographically next region, i.e. MIB Region #3 (by subagent #2) and resend the request to sub agent #2. If first sub agent returns the oid and value from MIB Region #2 (as he has to search through a list of lexicographically ordered list of instantiated variables without regard to registration of region), then the SNMP Response for SNMP GetNext will be wrong. Either this is a error or it is not clear what is meant by "without regard to registration of MIB region". Please clarify. Also, in the section "7.2.4.3. Processing of Responses to agentx-GetNext-PDU and agentx-GetBulk-PDU ", the Master Agent never checks whether for each oid in the VarBind the response returned by a sub agent is valid or not. I think the master agent should check whether, for the oid in the varbind, the response returned by the sub agent is falling within the target MIB Region (which he determined while preparing the AgentX GetNext PDU for that particular sub agent). Thanks. With regards, Ashish K Hanwadikar Senior Software Engineer, Wipro Infotech, Technology Solutions, Bangalore INDIA ------=_NextPart_000_0054_01BDBCB9.80DEAB10 Content-Type: text/x-vcard; name="Ashish K Hanwadikar.vcf" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="Ashish K Hanwadikar.vcf" BEGIN:VCARD VERSION:2.1 N:Hanwadikar;Ashish;K;; FN:Ashish K Hanwadikar ORG:Wipro Infotech, Technology Solutions;Technology Solutions TITLE:Senior Software Engineer TEL;WORK;VOICE:+91-80-2241730 Ext. 3315 TEL;HOME;VOICE:+91-80-2241730 Ext. 3315 ADR;WORK:;Mission Road LABEL;WORK:Mission Road ADR;HOME;ENCODING=3DQUOTED-PRINTABLE:;;Wipro Limited=3D0D=3D0A30 Mission = Road,=3D0D=3D0A1st Main,=3D0D=3D0AS.R. Nagar;Bangalo=3D re;Karnataka;560 027;INDIA LABEL;HOME;ENCODING=3DQUOTED-PRINTABLE:Wipro Limited=3D0D=3D0A30 Mission = Road,=3D0D=3D0A1st Main,=3D0D=3D0AS.R. Nagar=3D0D=3D0ABang=3D alore, Karnataka 560 027=3D0D=3D0AINDIA URL:http://www.geocities.com/SiliconValley/Bay/5393/ URL:http://www.geocities.com/SiliconValley/Bay/5393 EMAIL;PREF;INTERNET:ashishkh@wipinfo.soft.net REV:19980630T133122Z END:VCARD ------=_NextPart_000_0054_01BDBCB9.80DEAB10-- From daniele@zk3.dec.com Fri Jul 31 13:15:58 1998 Delivery-Date: Fri, 31 Jul 1998 13:16:00 -0400 Return-Path: daniele@zk3.dec.com Received: from cnri.reston.va.us (ns [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id NAA25631 for ; Fri, 31 Jul 1998 13:15:56 -0400 (EDT) Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id NAA29347 for ; Fri, 31 Jul 1998 13:15:25 -0400 (EDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id MAA27276 for ; Fri, 31 Jul 1998 12:15:41 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma026670; Fri, 31 Jul 98 12:13:53 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id MAA07608 for ; Fri, 31 Jul 1998 12:13:14 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma006461; Fri, 31 Jul 98 12:12:24 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id MAA21709; Fri, 31 Jul 1998 12:12:37 -0500 (CDT) Received: from almond.bmc.com (almond.bmc.com [172.17.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id JAA12460 for ; Fri, 31 Jul 1998 09:58:58 -0700 (PDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id LAA25297 for ; Fri, 31 Jul 1998 11:58:56 -0500 (CDT) Received: from mail11.digital.com(192.208.46.10) by almond.bmc.com via smap (V2.0) id xma025290; Fri, 31 Jul 98 11:58:49 -0500 Received: from quarry.zk3.dec.com (fquarry.zk3.dec.com [16.140.160.9]) by mail11.digital.com (8.8.8/8.8.8/WV1.0f) with SMTP id MAA15672; Fri, 31 Jul 1998 12:57:52 -0400 (EDT) Received: from bernie.zk3.dec.com by quarry.zk3.dec.com; (5.65v4.0/1.1.8.2/16Jan95-0946AM) id AA06644; Fri, 31 Jul 1998 12:57:51 -0400 Received: from localhost by bernie.zk3.dec.com; (5.65/1.1.8.2/22Aug96-1117AM) id AA20179; Fri, 31 Jul 1998 12:58:03 -0400 Message-Id: <9807311658.AA20179@bernie.zk3.dec.com> To: "Ashish Hanwadikar" Cc: agentx@peer.com Subject: Re: Sub Agent Processing of AgentX GetNext Response In-Reply-To: Your message of "Fri, 31 Jul 98 19:29:15 +0530." <005301bdbc8b$67266f10$163409c0@opel.wipinfo.soft.net> Date: Fri, 31 Jul 98 12:58:03 -0400 From: Mike Daniele X-Mts: smtp Hi Ashish, > If first sub agent returns the oid and value from MIB Region #2 (as he has >to search through a list of lexicographically ordered list of instantiated >variables without regard to registration of region), then the SNMP Response >for SNMP GetNext will be wrong. > Either this is a error or it is not clear what is meant by "without regard >to registration of MIB region". Please clarify. > Also, in the section "7.2.4.3. Processing of Responses to >agentx-GetNext-PDU and agentx-GetBulk-PDU ", the Master Agent never checks >whether for each oid in the VarBind the response returned by a sub agent is >valid or not. I think the master agent should check whether, for the oid in >the varbind, the response returned by the sub agent is falling within the >target MIB Region (which he determined while preparing the AgentX GetNext >PDU for that particular sub agent). 7.2.1 states 1) Honoring the registry Because AgentX supports overlapping registrations, it is possible for the master agent to obtain a value for a requested varbind from within multiple registered MIB regions. The master agent must ensure that the value (or exception) actually returned in the SNMP response PDU is taken from the authoritative region (as defined in section 7.1.5.1). I think this "blanket rule" covers your concerns. Note that the master agent may use the ending oid of the searchrange to "scope" the instances the subagent may return, as described in 2) of section 7.2.1, and 7.2.2.2. Does this make it clear? Regards, Mike From sgudur@hotmail.com Fri Jul 31 13:40:32 1998 Delivery-Date: Fri, 31 Jul 1998 13:40:32 -0400 Return-Path: sgudur@hotmail.com Received: from cnri.reston.va.us (ns [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id NAA26257 for ; Fri, 31 Jul 1998 13:40:31 -0400 (EDT) Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id NAA29464 for ; Fri, 31 Jul 1998 13:40:14 -0400 (EDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id MAA29816 for ; Fri, 31 Jul 1998 12:40:13 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma029406; Fri, 31 Jul 98 12:39:14 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id MAA01953 for ; Fri, 31 Jul 1998 12:38:34 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma001305; Fri, 31 Jul 98 12:38:01 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id MAA28932; Fri, 31 Jul 1998 12:38:19 -0500 (CDT) Received: from cashew.bmc.com (cashew.bmc.com [172.19.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id KAA12551 for ; Fri, 31 Jul 1998 10:33:03 -0700 (PDT) Received: (from uucp@localhost) by cashew.bmc.com (8.8.8/8.8.8) id MAA07662 for ; Fri, 31 Jul 1998 12:33:01 -0500 (CDT) Received: from f220.hotmail.com(207.82.251.111) by cashew.bmc.com via smap (V2.0) id xma007630; Fri, 31 Jul 98 12:32:35 -0500 Received: (qmail 29030 invoked by uid 0); 31 Jul 1998 17:32:29 -0000 Message-ID: <19980731173229.29029.qmail@hotmail.com> Received: from 152.67.249.57 by www.hotmail.com with HTTP; Fri, 31 Jul 1998 10:32:29 PDT X-Originating-IP: [152.67.249.57] From: "Smitha Gudur" To: agentx@peer.com Subject: open issues in agentX MIB Content-Type: text/plain Date: Fri, 31 Jul 1998 10:32:29 PDT Hi, Some of the open issues that needs to be addressed for agentx MIB include: 1. Relevance of agentxConnNumber, and agentxSessionNumber. This gives the number of entries in each respective table. Do we need these in the tables? 2. Add agentXLastChange to RegistrationTable to be consistent with the other tables. If there are any other open items that need to be addressed in the MIB, I urge everyone on the mailing list to send them as early as possible. These need to be resolved before the Chicago IETF meeting in August. Please send all email to agentx mailing list. thanks smitha ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com From fenner@parc.xerox.com Fri Jul 31 15:09:32 1998 Delivery-Date: Fri, 31 Jul 1998 15:09:33 -0400 Return-Path: fenner@parc.xerox.com Received: from cnri.reston.va.us (ns [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id PAA28204 for ; Fri, 31 Jul 1998 15:09:32 -0400 (EDT) Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id PAA00009 for ; Fri, 31 Jul 1998 15:09:17 -0400 (EDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id OAA07003 for ; Fri, 31 Jul 1998 14:09:19 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma006340; Fri, 31 Jul 98 14:07:23 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id OAA29431 for ; Fri, 31 Jul 1998 14:06:46 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma028224; Fri, 31 Jul 98 14:05:54 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id OAA26344; Fri, 31 Jul 1998 14:06:11 -0500 (CDT) Received: from almond.bmc.com (almond.bmc.com [172.17.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id LAA13234 for ; Fri, 31 Jul 1998 11:51:47 -0700 (PDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id NAA04931 for ; Fri, 31 Jul 1998 13:51:46 -0500 (CDT) Received: from omega.xerox.com(13.1.64.95) by almond.bmc.com via smap (V2.0) id xma004880; Fri, 31 Jul 98 13:51:16 -0500 Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <40677(2)>; Fri, 31 Jul 1998 11:51:05 PDT Received: by crevenia.parc.xerox.com id <177515>; Fri, 31 Jul 1998 11:50:55 -0700 From: Bill Fenner To: agentx@peer.com Subject: Can an AgnetX sub-agent send an AgentX-GET PDU to the AgentX master? Cc: fenner@parc.xerox.com Message-Id: <98Jul31.115055pdt.177515@crevenia.parc.xerox.com> Date: Fri, 31 Jul 1998 11:50:52 PDT Hi, Let's say I have a routing daemon which wants to present a MIB which happens to include ifindex values. However, the local interface to ifindex value mapping happens in a different subagent; the routing daemon doesn't know what this mapping is. It has to walk the iftable and try to match that up with its view of the interfaces. Can this routing daemon send AgentX-GET PDU's up to the master agent and expect it to dispatch them to the right sub-agent and dispatch the reply back to me all via AgentX, or do I have to use SNMP for this part? I ask because it seems like a shame that an application that only wants to be an AgentX sub-agent also has to be able to be an SNMP client. Thanks, Bill From fenner@parc.xerox.com Fri Jul 31 15:20:09 1998 Delivery-Date: Fri, 31 Jul 1998 15:20:09 -0400 Return-Path: fenner@parc.xerox.com Received: from cnri.reston.va.us (ns [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id PAA28399 for ; Fri, 31 Jul 1998 15:20:09 -0400 (EDT) Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id PAA00078 for ; Fri, 31 Jul 1998 15:19:52 -0400 (EDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id OAA08630 for ; Fri, 31 Jul 1998 14:20:06 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma008420; Fri, 31 Jul 98 14:19:31 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id OAA11186 for ; Fri, 31 Jul 1998 14:18:54 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma009923; Fri, 31 Jul 98 14:18:03 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id OAA00175; Fri, 31 Jul 1998 14:18:20 -0500 (CDT) Received: from cashew.bmc.com (cashew.bmc.com [172.19.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id MAA13406 for ; Fri, 31 Jul 1998 12:13:11 -0700 (PDT) Received: (from uucp@localhost) by cashew.bmc.com (8.8.8/8.8.8) id OAA14055 for ; Fri, 31 Jul 1998 14:13:09 -0500 (CDT) Received: from omega.xerox.com(13.1.64.95) by cashew.bmc.com via smap (V2.0) id xma013944; Fri, 31 Jul 98 14:12:46 -0500 Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <40652(2)>; Fri, 31 Jul 1998 12:11:20 PDT Received: by crevenia.parc.xerox.com id <177515>; Fri, 31 Jul 1998 12:11:13 -0700 From: Bill Fenner To: agentx@peer.com Subject: Misleading wording in section 8.1.2: AgentX over TCP operation Cc: fenner@parc.xerox.com Message-Id: <98Jul31.121113pdt.177515@crevenia.parc.xerox.com> Date: Fri, 31 Jul 1998 12:11:00 PDT Section 8.1.2 says: All AgentX PDUs are presented individually to the TCP, to be sent as the data portion of a TCP PDU. Applications can't control TCP PDU's; e.g. if you do 3 small TCP writes in a row, most TCP's will coalesce the 2nd and 3rd write into a single TCP PDU. And, of course, large writes will be fragmented into multiple TCP PDU's. I'd suggest removing this sentence in the next version of the document, since how you present data to TCP has very little to do with how TCP puts the data into PDU's. Bill From schoenw@ibr.cs.tu-bs.de Fri Jul 31 16:27:27 1998 Delivery-Date: Fri, 31 Jul 1998 16:27:28 -0400 Return-Path: schoenw@ibr.cs.tu-bs.de Received: from cnri.reston.va.us (ns [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id QAA29583 for ; Fri, 31 Jul 1998 16:27:27 -0400 (EDT) Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id QAA00550 for ; Fri, 31 Jul 1998 16:27:08 -0400 (EDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id PAA14905 for ; Fri, 31 Jul 1998 15:27:07 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma014390; Fri, 31 Jul 98 15:25:54 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id PAA15230 for ; Fri, 31 Jul 1998 15:25:18 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma014183; Fri, 31 Jul 98 15:24:26 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id PAA19354; Fri, 31 Jul 1998 15:24:32 -0500 (CDT) Received: from cashew.bmc.com (cashew.bmc.com [172.19.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id NAA13775 for ; Fri, 31 Jul 1998 13:12:35 -0700 (PDT) Received: (from uucp@localhost) by cashew.bmc.com (8.8.8/8.8.8) id PAA17695 for ; Fri, 31 Jul 1998 15:12:33 -0500 (CDT) Received: from mumm.ibr.cs.tu-bs.de(134.169.34.190) by cashew.bmc.com via smap (V2.0) id xma017637; Fri, 31 Jul 98 15:11:53 -0500 Received: from henkell.ibr.cs.tu-bs.de (schoenw@henkell [134.169.34.191]) by mumm.ibr.cs.tu-bs.de (8.9.1/8.9.0) with ESMTP id WAA17833; Fri, 31 Jul 1998 22:11:51 +0200 (MET DST) Received: from schoenw@localhost by henkell.ibr.cs.tu-bs.de (8.7.6/tubsibr) id WAA01760; Fri, 31 Jul 1998 22:11:50 +0200 Date: Fri, 31 Jul 1998 22:11:50 +0200 Message-Id: <199807312011.WAA01760@henkell.ibr.cs.tu-bs.de> From: Juergen Schoenwaelder To: agentx@peer.com Subject: Extensions for AgentX Version 1 Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII AgentX verion 1 does not allow a subagent to do the following: 1) check whether access is allowed to variables that exist in other subagents 2) read variables that exist in other subagents (with appropriate access control applied) 3) write variables that exist in other subagents (with appropriate access control applied) Some of the DISMAN MIBs that are currently on their way to proposed standard require to do the operations listed above. This means that it is impossible to implement and ship these DISMAN MIBs as separate products that you can plug into your native AgentX master agent. It might be possible to extend AgentX to provide this capability. The hardest part of the problem is how you maintain the required input for the access control function. Shipping this information to the subagent is probably not a good idea (it would make it pretty easy to mount guessing attacks from a subagent). However, it might be possible to find a solution where the master maintains a cache for security related information and passes only a handle to a subagent, probably only on a special request from the subagent while processing a read or write SNMP request. Anyway, I would like to know if there is interest in extending AgentX in this direction so that DISMAN MIBs can be implemented based on AgentX. (Bob, please consider this a request to discuss this during the AgentX meeting in Chicago. ;-) Juergen Juergen Schoenwaelder schoenw@ibr.cs.tu-bs.de http://www.cs.tu-bs.de/~schoenw Technical University Braunschweig, Dept. Operating Systems & Computer Networks Bueltenweg 74/75, 38106 Braunschweig, Germany. (Tel. +49 531 / 391 3289) From mithatch@cisco.com Fri Jul 31 16:33:47 1998 Delivery-Date: Fri, 31 Jul 1998 16:33:47 -0400 Return-Path: mithatch@cisco.com Received: from cnri.reston.va.us (ns [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id QAA29743 for ; Fri, 31 Jul 1998 16:33:46 -0400 (EDT) Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id QAA00586 for ; Fri, 31 Jul 1998 16:33:27 -0400 (EDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id PAA16677 for ; Fri, 31 Jul 1998 15:33:42 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma016117; Fri, 31 Jul 98 15:32:14 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id PAA22117 for ; Fri, 31 Jul 1998 15:31:36 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma020699; Fri, 31 Jul 98 15:30:28 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id PAA20945; Fri, 31 Jul 1998 15:30:28 -0500 (CDT) Received: from almond.bmc.com (almond.bmc.com [172.17.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id NAA13847 for ; Fri, 31 Jul 1998 13:27:05 -0700 (PDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id PAA14881 for ; Fri, 31 Jul 1998 15:27:02 -0500 (CDT) Received: from brownale.cisco.com(171.69.95.89) by almond.bmc.com via smap (V2.0) id xma014359; Fri, 31 Jul 98 15:25:50 -0500 Received: from mithatch-ultra.cisco.com (mithatch-ultra.cisco.com [171.69.50.33]) by brownale.cisco.com (8.8.4-Cisco.1/8.6.5) with ESMTP id NAA08617; Fri, 31 Jul 1998 13:24:36 -0700 (PDT) Received: from cisco.com (localhost [127.0.0.1]) by mithatch-ultra.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/CISCO.WS.1.2) with ESMTP id NAA12501; Fri, 31 Jul 1998 13:24:35 -0700 (PDT) Sender: mithatch@cisco.com Message-ID: <35C22803.C5940BEE@cisco.com> Date: Fri, 31 Jul 1998 13:24:35 -0700 From: Mike Thatcher X-Mailer: Mozilla 4.03C-CISCOENG [en] (X11; U; SunOS 5.5.1 sun4u) MIME-Version: 1.0 To: Smitha Gudur CC: agentx@peer.com Subject: Re: open issues in agentX MIB References: <19980731173229.29029.qmail@hotmail.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit If there is a relationship between sessionID as defined in RFC2257and agentxSessionIndex then the relationship needs to be clarified and the description of agentxSessionIndex made consistent with the definition in the RFC. (See sections 6.1, 6.2.16, 7.1.1(3)) MikeT From rpresuhn@dorothy.bmc.com Fri Jul 31 17:41:51 1998 Delivery-Date: Fri, 31 Jul 1998 17:41:51 -0400 Return-Path: rpresuhn@dorothy.bmc.com Received: from cnri.reston.va.us (ns [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id RAA01143 for ; Fri, 31 Jul 1998 17:41:50 -0400 (EDT) Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id RAA01147 for ; Fri, 31 Jul 1998 17:41:21 -0400 (EDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id QAA22259 for ; Fri, 31 Jul 1998 16:41:25 -0500 (CDT) Received: from dresden.bmc.com(198.64.253.250) by almond.bmc.com via smap (V2.0) id xma021531; Fri, 31 Jul 98 16:39:45 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id QAA19859 for ; Fri, 31 Jul 1998 16:39:08 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma018792; Fri, 31 Jul 98 16:38:23 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id QAA09606; Fri, 31 Jul 1998 16:38:36 -0500 (CDT) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id OAA14938 for agentx@peer.com; Fri, 31 Jul 1998 14:24:42 -0700 (PDT) Date: Fri, 31 Jul 1998 14:24:42 -0700 (PDT) From: Randy Presuhn Message-Id: <199807312124.OAA14938@dorothy.bmc.com> To: agentx@peer.com Subject: Re: Extensions for AgentX Version 1 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi - > Date: Fri, 31 Jul 1998 22:11:50 +0200 > From: Juergen Schoenwaelder > To: agentx@peer.com > Subject: Extensions for AgentX Version 1 ... > Anyway, I would like to know if there is interest in extending AgentX > in this direction so that DISMAN MIBs can be implemented based on > AgentX. (Bob, please consider this a request to discuss this during > the AgentX meeting in Chicago. ;-) ... Discussion of whatever the AgentX WG has to say on this topic is already on the proposed disman agenda. ----------------------------------------------------------------------- Randy Presuhn Email: rpresuhn@bmc.com http://www.bmc.com Voice: +1 408 616-3100 BMC Software, Inc. 965 Stewart Drive Fax: +1 408 616-3101 Sunnyvale, California 94086 USA ----------------------------------------------------------------------- In accordance with the BMC Communications Systems Use and Security Policy, 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@hotmail.com Fri Jul 31 17:50:49 1998 Delivery-Date: Fri, 31 Jul 1998 17:50:49 -0400 Return-Path: sgudur@hotmail.com Received: from cnri.reston.va.us (ns [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id RAA01283 for ; Fri, 31 Jul 1998 17:50:48 -0400 (EDT) Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id RAA01173 for ; Fri, 31 Jul 1998 17:50:33 -0400 (EDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id QAA24052 for ; Fri, 31 Jul 1998 16:50:50 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma023713; Fri, 31 Jul 98 16:50:05 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id QAA00709 for ; Fri, 31 Jul 1998 16:49:29 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma029506; Fri, 31 Jul 98 16:48:45 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id QAA12462; Fri, 31 Jul 1998 16:49:10 -0500 (CDT) Received: from almond.bmc.com (almond.bmc.com [172.17.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id OAA15711 for ; Fri, 31 Jul 1998 14:45:37 -0700 (PDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id QAA23291 for ; Fri, 31 Jul 1998 16:45:35 -0500 (CDT) Received: from f185.hotmail.com(207.82.251.74) by almond.bmc.com via smap (V2.0) id xma023283; Fri, 31 Jul 98 16:45:29 -0500 Received: (qmail 29356 invoked by uid 0); 31 Jul 1998 21:45:24 -0000 Message-ID: <19980731214524.29355.qmail@hotmail.com> Received: from 152.67.249.57 by www.hotmail.com with HTTP; Fri, 31 Jul 1998 14:45:24 PDT X-Originating-IP: [152.67.249.57] From: "Smitha Gudur" To: mithatch@cisco.com Cc: agentx@peer.com Subject: Re: open issues in agentX MIB Content-Type: text/plain Date: Fri, 31 Jul 1998 14:45:24 PDT Hi, Mike, There is relationship between sessionID defined in RFC2257 and the agentxSessionIndex. Current description for agentxSessionIndex includes: "Index values assigned for a given registration are constant for the lifetime of this table." is inappropriate and needs to be removed. The other part of the description is consistent with the RFC. "A unique index for the subagent session. Note that if a subagent's session with the master agent is closed for any reason its index should not be re-used, therefore, the values of agentxSessionIndex may not be contiguous and will generally not be the same for the same subagent across multiple sessions." thanks for the inputs. regards smitha >From mithatch@cisco.com Fri Jul 31 13:25:54 1998 >Received: from mithatch-ultra.cisco.com (mithatch-ultra.cisco.com [171.69.50.33]) by brownale.cisco.com (8.8.4-Cisco.1/8.6.5) with ESMTP id NAA08617; Fri, 31 Jul 1998 13:24:36 -0700 (PDT) >Received: from cisco.com (localhost [127.0.0.1]) by mithatch-ultra.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/CISCO.WS.1.2) with ESMTP id NAA12501; Fri, 31 Jul 1998 13:24:35 -0700 (PDT) >Sender: mithatch@cisco.com >Message-ID: <35C22803.C5940BEE@cisco.com> >Date: Fri, 31 Jul 1998 13:24:35 -0700 >From: Mike Thatcher >X-Mailer: Mozilla 4.03C-CISCOENG [en] (X11; U; SunOS 5.5.1 sun4u) >MIME-Version: 1.0 >To: Smitha Gudur >CC: agentx@peer.com >Subject: Re: open issues in agentX MIB >References: <19980731173229.29029.qmail@hotmail.com> >Content-Type: text/plain; charset=us-ascii >Content-Transfer-Encoding: 7bit > >If there is a relationship between sessionID as defined in RFC2257and >agentxSessionIndex then the relationship needs to be clarified and the >description of agentxSessionIndex made consistent with the definition in >the RFC. (See sections 6.1, 6.2.16, 7.1.1(3)) > >MikeT > > ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com From martin@exmandato.se Fri Jul 31 18:05:05 1998 Delivery-Date: Fri, 31 Jul 1998 18:05:05 -0400 Return-Path: martin@exmandato.se Received: from cnri.reston.va.us (ns [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id SAA01487 for ; Fri, 31 Jul 1998 18:05:04 -0400 (EDT) Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id SAA01257 for ; Fri, 31 Jul 1998 18:04:44 -0400 (EDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id RAA26363 for ; Fri, 31 Jul 1998 17:05:01 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma026066; Fri, 31 Jul 98 17:04:15 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id RAA13150 for ; Fri, 31 Jul 1998 17:03:30 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma010923; Fri, 31 Jul 98 17:01:47 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id RAA15629; Fri, 31 Jul 1998 17:01:57 -0500 (CDT) Received: from almond.bmc.com (almond.bmc.com [172.17.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id OAA16380 for ; Fri, 31 Jul 1998 14:57:17 -0700 (PDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id QAA25126 for ; Fri, 31 Jul 1998 16:57:14 -0500 (CDT) Received: from oden.exmandato.se(192.71.33.1) by almond.bmc.com via smap (V2.0) id xma025120; Fri, 31 Jul 98 16:56:53 -0500 Received: from localhost (martin@localhost) by oden.exmandato.se (8.8.8/8.8.5) with SMTP id XAA00477; Fri, 31 Jul 1998 23:56:59 +0200 (MET DST) Date: Fri, 31 Jul 1998 23:56:59 +0200 (CEST) From: Martin Jacobsson Reply-To: Martin Jacobsson To: Smitha Gudur cc: agentx@peer.com Subject: Re: open issues in agentX MIB In-Reply-To: <19980731173229.29029.qmail@hotmail.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 31 Jul 1998, Smitha Gudur wrote: > If there are any other open items that need to be addressed in the MIB, > I urge everyone on the mailing list to send them as early as possible. Section 2, goal 4 says: - Provide statistics about the protocol operation such as the number of packets to and from each subagent This information is not available through the mib as defined. One option is to add agentxSessionInPackets and agentxSessionOutPackets to the session table. And another is to add agentxConnInPackets, agentxConnOutPackets, agentxConnProtocolErrors and agentxConnParseErrors to the connection table. All as Counter32's. Then a port table would be nice, so that it is possible to see what ports the master agent accepts connections from and if it listens on any nondefault ports. A typical unix master agent will listen on both tcp port 705 and unix-domain socket "/var/agentx/master". /Martin Jacobsson --- .signature: No such file or directory From sgudur@hotmail.com Fri Jul 31 18:46:31 1998 Delivery-Date: Fri, 31 Jul 1998 18:46:32 -0400 Return-Path: sgudur@hotmail.com Received: from cnri.reston.va.us (ns [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id SAA02130 for ; Fri, 31 Jul 1998 18:46:31 -0400 (EDT) Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id SAA01472 for ; Fri, 31 Jul 1998 18:46:09 -0400 (EDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id RAA29685 for ; Fri, 31 Jul 1998 17:46:14 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma028834; Fri, 31 Jul 98 17:44:28 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id RAA10171 for ; Fri, 31 Jul 1998 17:43:50 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma008835; Fri, 31 Jul 98 17:42:59 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id RAA26717; Fri, 31 Jul 1998 17:43:21 -0500 (CDT) Received: from almond.bmc.com (almond.bmc.com [172.17.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id PAA25398 for ; Fri, 31 Jul 1998 15:30:07 -0700 (PDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id RAA27889 for ; Fri, 31 Jul 1998 17:30:06 -0500 (CDT) Received: from f139.hotmail.com(207.82.251.18) by almond.bmc.com via smap (V2.0) id xma027878; Fri, 31 Jul 98 17:29:43 -0500 Received: (qmail 1049 invoked by uid 0); 31 Jul 1998 22:29:42 -0000 Message-ID: <19980731222942.1048.qmail@hotmail.com> Received: from 152.67.249.57 by www.hotmail.com with HTTP; Fri, 31 Jul 1998 15:29:41 PDT X-Originating-IP: [152.67.249.57] From: "Smitha Gudur" To: mithatch@cisco.com Cc: agentx@peer.com Subject: Re: open issues in agentX MIB Content-Type: text/plain Date: Fri, 31 Jul 1998 15:29:41 PDT >From mithatch@cisco.com Fri Jul 31 15:03:58 1998 >Received: from mithatch-ultra.cisco.com (mithatch-ultra.cisco.com [171.69.50.33]) by pleco.cisco.com (8.8.4-Cisco.1/8.6.5) with ESMTP id PAA29758; Fri, 31 Jul 1998 15:02:54 -0700 (PDT) >Received: from cisco.com (localhost [127.0.0.1]) by mithatch-ultra.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/CISCO.WS.1.2) with ESMTP id PAA12637; Fri, 31 Jul 1998 15:02:54 -0700 (PDT) >Sender: mithatch@cisco.com >Message-ID: <35C23F0D.44E2CE36@cisco.com> >Date: Fri, 31 Jul 1998 15:02:53 -0700 >From: Mike Thatcher >X-Mailer: Mozilla 4.03C-CISCOENG [en] (X11; U; SunOS 5.5.1 sun4u) >MIME-Version: 1.0 >To: Smitha Gudur >Subject: Re: open issues in agentX MIB >References: <19980731214524.29355.qmail@hotmail.com> >Content-Type: text/plain; charset=us-ascii >Content-Transfer-Encoding: 7bit > >Smitha Gudur wrote: > >> Hi, Mike, >> >> There is relationship between sessionID defined in RFC2257 and >> the agentxSessionIndex. >> >> Current description for agentxSessionIndex includes: >> >> "Index values assigned for a given registration are constant for the >> lifetime of this table." >> >> is inappropriate and needs to be removed. >> >> The other part of the description is consistent with the RFC. >> >> "A unique index for the subagent session. Note that if a >> subagent's session with the master agent is closed for >> any reason its index should not be re-used, therefore, >> > >However the RFC does not restrict the reuse of sessionID. I agree, it does not restrict the usage but says that it should be globally unique over all its sessions if master agent supports multiple transports. The description has to be changed to make it unique across all the sessions that the master agent supports instead of saying it cannot be reused. smitha > >MikeT > > ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com From bnatale@acecomm.com Fri Jul 31 18:47:15 1998 Delivery-Date: Fri, 31 Jul 1998 18:47:16 -0400 Return-Path: bnatale@acecomm.com Received: from cnri.reston.va.us (ns [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id SAA02139 for ; Fri, 31 Jul 1998 18:47:15 -0400 (EDT) Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id SAA01475 for ; Fri, 31 Jul 1998 18:46:53 -0400 (EDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id RAA00057 for ; Fri, 31 Jul 1998 17:47:07 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma029437; Fri, 31 Jul 98 17:45:45 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id RAA11639 for ; Fri, 31 Jul 1998 17:45:06 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma008922; Fri, 31 Jul 98 17:43:03 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id RAA26713; Fri, 31 Jul 1998 17:43:20 -0500 (CDT) Received: from almond.bmc.com (almond.bmc.com [172.17.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id PAA25406 for ; Fri, 31 Jul 1998 15:30:08 -0700 (PDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id RAA27891 for ; Fri, 31 Jul 1998 17:30:06 -0500 (CDT) Received: from relay2.smtp.psi.net(38.8.188.2) by almond.bmc.com via smap (V2.0) id xma027887; Fri, 31 Jul 98 17:29:56 -0500 Received: from [192.152.208.5] (helo=acecomm.com) by relay2.smtp.psi.net with smtp (Exim 1.90 #1) id 0z2NgO-0005N2-00; Fri, 31 Jul 1998 18:29:53 -0400 Received: from bnatale by acecomm.com (5.65/3.2.083191-ACE*COMM) id AA17422; Fri, 31 Jul 1998 18:32:10 -0400 Message-Id: <9807312232.AA17422@acecomm.com> X-Sender: natale@nips.acec.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Fri, 31 Jul 1998 18:32:19 -0400 To: "Smitha Gudur" From: Bob Natale Subject: Re: open issues in agentX MIB Cc: mithatch@cisco.com, agentx@peer.com In-Reply-To: <19980731214524.29355.qmail@hotmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" >At 7/31/98 02:45 PM, Smitha Gudur wrote: Hi Smitha, >There is relationship between sessionID defined in RFC2257 and >the agentxSessionIndex. Logically, that's true. The value used for agentxSessionIndex to identify the session should be the same as that used for the SessionID as given by the master agent to the subagent. The problem Mike alludes to here derives from the "should not be re-used" semantics used for agentxSessionIndex in the MIB but which are missing from the RFC references to SessionID. I would argue that the RFC text should be tightened in this respect, to stipulate non-reuse; but it is clear that a reasonable argument can be made for not stipulating it and leaving it up to the implementation. In my view, however, management apps will be able to use the MIB better to monitor the overall AgentX system if the non-reuse semantics of agentxSessionIndex are carried over to SessionID. This value, via agentxSessionIndex, is critical to all three of the tables currently defined in the MIB [btw, we should all be reading from the -02.txt version of the MIB document, dated April 14, 1998, at this point]: agentxConnectionTable agentxSessionTable agentxRegistrationTable In thinking through the relationships, it seems that we need to add agentxConnIndex to the AgentxSessionEntry and agentxSessionIndex to the AgentxRegistrationEntry. In this way, each registration entry can point to the session in which it lives and each session can point to the connection in which it lives. [Note to Smitha and Lauren here in particular:] The rationale and the consequent OBJECT-TYPE macros should be obvious (I think), but if not let me know. >Current description for agentxSessionIndex includes: > >"Index values assigned for a given registration are constant >for the lifetime of this table." > >is inappropriate and needs to be removed. Right. >The other part of the description is consistent with the RFC. That's the debatable part. >thanks for the inputs. Likewise. 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 bnatale@acecomm.com Fri Jul 31 19:07:10 1998 Delivery-Date: Fri, 31 Jul 1998 19:07:10 -0400 Return-Path: bnatale@acecomm.com Received: from cnri.reston.va.us (ns [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id TAA02325 for ; Fri, 31 Jul 1998 19:07:09 -0400 (EDT) Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id TAA01547 for ; Fri, 31 Jul 1998 19:06:52 -0400 (EDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id SAA02632 for ; Fri, 31 Jul 1998 18:06:55 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma002095; Fri, 31 Jul 98 18:05:39 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id SAA20798 for ; Fri, 31 Jul 1998 18:05:03 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma020093; Fri, 31 Jul 98 18:04:26 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id SAA01875; Fri, 31 Jul 1998 18:04:51 -0500 (CDT) Received: from cashew.bmc.com (cashew.bmc.com [172.19.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id PAA10570 for ; Fri, 31 Jul 1998 15:56:45 -0700 (PDT) Received: (from uucp@localhost) by cashew.bmc.com (8.8.8/8.8.8) id RAA26038 for ; Fri, 31 Jul 1998 17:56:43 -0500 (CDT) Received: from relay2.smtp.psi.net(38.8.188.2) by cashew.bmc.com via smap (V2.0) id xma026033; Fri, 31 Jul 98 17:56:17 -0500 Received: from [192.152.208.5] (helo=acecomm.com) by relay2.smtp.psi.net with smtp (Exim 1.90 #1) id 0z2O5t-0000Op-00; Fri, 31 Jul 1998 18:56:14 -0400 Received: from bnatale by acecomm.com (5.65/3.2.083191-ACE*COMM) id AA17629; Fri, 31 Jul 1998 18:58:27 -0400 Message-Id: <9807312258.AA17629@acecomm.com> X-Sender: natale@nips.acec.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Fri, 31 Jul 1998 18:58:35 -0400 To: Martin Jacobsson From: Bob Natale Subject: Re: open issues in agentX MIB Cc: Smitha Gudur , agentx@peer.com In-Reply-To: References: <19980731173229.29029.qmail@hotmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" >At 7/31/98 11:56 PM, Martin Jacobsson wrote: Hi Martin, >Section 2, goal 4 says: > >- Provide statistics about the protocol operation such >as the number of packets to and from each subagent > >This information is not available through the mib as defined. >One option is to add agentxSessionInPackets and >agentxSessionOutPackets to the session table. And another is >to add agentxConnInPackets, agentxConnOutPackets, >agentxConnProtocolErrors and agentxConnParseErrors >to the connection table. All as Counter32's. First, let me note that there is considerable sentiment to keep this MIB relatively minimal. Second, you are right, if state such purposes (and the one you quote seems like a sound one to me). The approach that I would like to propose for this purpose is to add an agentxResponseTable. This would be indexed by agentxSessionID and consist of a set of objects (with syntax of GAUGE32, I suggest), one for each of the possible AgentX-Response-PDU res.error codes (including no_error). Such a table would handle overall (by simple summing), connection-specific (by mapping back to agentxConnectionTable via the agentxConnIndex in the corresponding agentxSessionTable row, and session-specific traffic and error counts for all active sessions. >Then a port table would be nice, so that it is possible to see >what ports the master agent accepts connections from I think this can be had now, via the agentxConnTransportDomain and agentxConnTransportAddress objects in the agentxConnectionTable. No...? >and if it listens on any nondefault ports. I'll pass on that one (I don't really see the need for it). >A typical unix master agent will listen on both tcp port >705 and unix-domain socket "/var/agentx/master". True...and the two objects mentioned above would, I think, tend to reveal that, given at least one active connection from each domain. 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 rpresuhn@dorothy.bmc.com Fri Jul 31 19:58:31 1998 Delivery-Date: Fri, 31 Jul 1998 19:58:32 -0400 Return-Path: rpresuhn@dorothy.bmc.com Received: from cnri.reston.va.us (ns [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id TAA02678 for ; Fri, 31 Jul 1998 19:58:31 -0400 (EDT) Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id TAA01720 for ; Fri, 31 Jul 1998 19:58:14 -0400 (EDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id SAA05749 for ; Fri, 31 Jul 1998 18:58:31 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma005145; Fri, 31 Jul 98 18:57:08 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id SAA06572 for ; Fri, 31 Jul 1998 18:56:32 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma005796; Fri, 31 Jul 98 18:55:55 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id SAA11662; Fri, 31 Jul 1998 18:56:20 -0500 (CDT) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id QAA24395 for agentx@peer.com; Fri, 31 Jul 1998 16:43:08 -0700 (PDT) Date: Fri, 31 Jul 1998 16:43:08 -0700 (PDT) From: Randy Presuhn Message-Id: <199807312343.QAA24395@dorothy.bmc.com> To: agentx@peer.com Subject: Re: open issues in agentX MIB Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi - > Date: Fri, 31 Jul 1998 18:58:35 -0400 > To: Martin Jacobsson > From: Bob Natale > Subject: Re: open issues in agentX MIB > Cc: Smitha Gudur , agentx@peer.com > References: <19980731173229.29029.qmail@hotmail.com> > > >At 7/31/98 11:56 PM, Martin Jacobsson wrote: > > Hi Martin, > > >Section 2, goal 4 says: > > > >- Provide statistics about the protocol operation such > >as the number of packets to and from each subagent ... > First, let me note that there is considerable sentiment to > keep this MIB relatively minimal. ... A counter-proposal to consider: delete goal 4 in section 2. ----------------------------------------------------------------------- Randy Presuhn Email: rpresuhn@bmc.com http://www.bmc.com Voice: +1 408 616-3100 BMC Software, Inc. 965 Stewart Drive Fax: +1 408 616-3101 Sunnyvale, California 94086 USA ----------------------------------------------------------------------- In accordance with the BMC Communications Systems Use and Security Policy, 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 ashishkh@wipinfo.soft.net Sun Aug 2 05:19:05 1998 Delivery-Date: Sun, 02 Aug 1998 05:19:06 -0400 Return-Path: ashishkh@wipinfo.soft.net Received: from cnri.reston.va.us (ns [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id FAA01169 for ; Sun, 2 Aug 1998 05:19:03 -0400 (EDT) Received: from almond.bmc.com (mail-gw1.bmc.com [198.64.253.22]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id FAA00502 for ; Sun, 2 Aug 1998 05:18:46 -0400 (EDT) Received: (from uucp@localhost) by almond.bmc.com (8.8.8/8.8.8) id EAA02813 for ; Sun, 2 Aug 1998 04:18:59 -0500 (CDT) Received: from firewall.bmc.com(192.245.162.250) by almond.bmc.com via smap (V2.0) id xma002353; Sun, 2 Aug 98 04:17:54 -0500 Received: (from uucp@localhost) by dresden.bmc.com (8.8.5/8.8.6) id EAA17869 for ; Sun, 2 Aug 1998 04:17:11 -0500 (CDT) Received: from tangelo.bmc.com(172.17.7.166) by dresden.bmc.com via smap (3.2) id xma017361; Sun, 2 Aug 98 04:16:44 -0500 Received: from dorothy.bmc.com (dorothy.peer.com [192.146.153.65]) by tangelo.bmc.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id EAA07409; Sun, 2 Aug 1998 04:17:10 -0500 (CDT) Received: from cashew.bmc.com (cashew.bmc.com [172.19.0.100]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id BAA04388 for ; Sun, 2 Aug 1998 01:02:27 -0700 (PDT) Received: (from uucp@localhost) by cashew.bmc.com (8.8.8/8.8.8) id DAA08809 for ; Sun, 2 Aug 1998 03:02:24 -0500 (CDT) Received: from agni.wipinfo.soft.net(164.164.6.20) by cashew.bmc.com via smap (V2.0) id xma008791; Sun, 2 Aug 98 03:02:08 -0500 Received: from scan.wipinfo.soft.net by wipinfo.soft.net (SMI-8.6/SMI-SVR4) id NAA18037; Sun, 2 Aug 1998 13:27:25 -0500 Received: from 192.9.100.151 by scan.wipinfo.soft.net (InterScan E-Mail VirusWall NT) Received: from opel ([192.9.52.22]) by divya.wipinfo.soft.net (8.8.5/8.8.5) with SMTP id NAA26354; Sun, 2 Aug 1998 13:34:01 +0530 From: "Ashish Hanwadikar" To: "Bob Natale" Cc: "Agentx" Subject: RE: open issues in agentX MIB Date: Sun, 2 Aug 1998 13:32:36 +0530 Message-ID: <008401bdbdeb$ea7e6c80$163409c0@opel.wipinfo.soft.net> MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal In-Reply-To: <9807312258.AA17629@acecomm.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0085_01BDBE1A.0436A880" This is a multi-part message in MIME format. ------=_NextPart_000_0085_01BDBE1A.0436A880 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Ashish K Hanwadikar Senior Software Engineer, Wipro Infotech, Technology Solutions, Bangalore INDIA -----Original Message----- From: Bob Natale [mailto:bnatale@acecomm.com] Sent: Saturday, August 01, 1998 4:29 AM To: Martin Jacobsson Cc: Smitha Gudur; agentx@peer.com Subject: Re: open issues in agentX MIB >At 7/31/98 11:56 PM, Martin Jacobsson wrote: Hi Martin, >Section 2, goal 4 says: > >- Provide statistics about the protocol operation such >as the number of packets to and from each subagent > >This information is not available through the mib as defined. >One option is to add agentxSessionInPackets and >agentxSessionOutPackets to the session table. And another is >to add agentxConnInPackets, agentxConnOutPackets, >agentxConnProtocolErrors and agentxConnParseErrors >to the connection table. All as Counter32's. First, let me note that there is considerable sentiment to keep this MIB relatively minimal. Second, you are right, if state such purposes (and the one you quote seems like a sound one to me). The approach that I would like to propose for this purpose is to add an agentxResponseTable. This would be indexed by agentxSessionID and consist of a set of objects (with syntax of GAUGE32, I suggest), one for each of the possible AgentX-Response-PDU res.error codes (including no_error). Such a table would handle overall (by simple summing), connection-specific (by mapping back to agentxConnectionTable via the agentxConnIndex in the corresponding agentxSessionTable row, and session-specific traffic and error counts for all active sessions. >Then a port table would be nice, so that it is possible to see >what ports the master agent accepts connections from I think this can be had now, via the agentxConnTransportDomain and agentxConnTransportAddress objects in the agentxConnectionTable. No...? >and if it listens on any nondefault ports. I'll pass on that one (I don't really see the need for it). >A typical unix master agent will listen on both tcp port >705 and unix-domain socket "/var/agentx/master". True...and the two objects mentioned above would, I think, tend to reveal that, given at least one active connection from each domain. given at least one active connection .. That is the hitch. Suppose, the sub agent wants to know which transport should he use to communicate with the Master Agent? If no connections are active, then it is very difficult to known on which transport domains the Master Agent is listening. I think it will be generally be useful from the Sub Agent and Sub Agent API developers point of view to add an agentxListenTable to the AgentX MIB. I guess such a table was there in the DPI from which AgentX derives its inspiration. Thanks 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 ------------- ------=_NextPart_000_0085_01BDBE1A.0436A880 Content-Type: text/x-vcard; name="Ashish K Hanwadikar.vcf" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="Ashish K Hanwadikar.vcf" BEGIN:VCARD VERSION:2.1 N:Hanwadikar;Ashish;K;; FN:Ashish K Hanwadikar ORG:Wipro Infotech, Technology Solutions;Technology Solutions TITLE:Senior Software Engineer TEL;WORK;VOICE:+91-80-2241730 Ext. 3315 TEL;HOME;VOICE:+91-80-2241730 Ext. 3315 ADR;WORK:;Mission Road LABEL;WORK:Mission Road ADR;HOME;ENCODING=3DQUOTED-PRINTABLE:;;Wipro Limited=3D0D=3D0A30 Mission = Road,=3D0D=3D0A1st Main,=3D0D=3D0AS.R. Nagar;Bangalo=3D re;Karnataka;560 027;INDIA LABEL;HOME;ENCODING=3DQUOTED-PRINTABLE:Wipro Limited=3D0D=3D0A30 Mission = Road,=3D0D=3D0A1st Main,=3D0D=3D0AS.R. Nagar=3D0D=3D0ABang=3D alore, Karnataka 560 027=3D0D=3D0AINDIA URL:http://www.geocities.com/SiliconValley/Bay/5393/ URL:http://www.geocities.com/SiliconValley/Bay/5393 EMAIL;PREF;INTERNET:ashishkh@wipinfo.soft.net REV:19980630T133122Z END:VCARD ------=_NextPart_000_0085_01BDBE1A.0436A880--