From owner-agentx@dorothy.bmc.com Tue May 21 10:53:03 2002 Received: from babbler.bmc.com (camaro.bmc.com [198.207.223.231]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13142 for ; Tue, 21 May 2002 10:53:03 -0400 (EDT) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g4LEpwq24984; Tue, 21 May 2002 09:51:58 -0500 (CDT) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id HAA20883 for agentx-list; Tue, 21 May 2002 07:44:02 -0700 (PDT) Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id HAA20878 for ; Tue, 21 May 2002 07:43:58 -0700 (PDT) Received: from mx-us-hou-2-int.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.10.2) with ESMTP id g4LEfTT29842 for ; Tue, 21 May 2002 09:41:29 -0500 (CDT) Received: from ihemail1.firewall.lucent.com (ihemail1.lucent.com [192.11.222.161]) by mx-us-hou-2-int.bmc.com (Postfix) with SMTP id 228DC1FF00A for ; Tue, 21 May 2002 09:45:34 -0500 (CDT) Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id g4LEjHj23075 for ; Tue, 21 May 2002 10:45:17 -0400 (EDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id ; Tue, 21 May 2002 16:45:16 +0200 Message-ID: From: "Wijnen, Bert (Bert)" To: agentx@dorothy.bmc.com Subject: Closing down AgentX WG Date: Tue, 21 May 2002 16:45:14 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-agentx@dorothy.bmc.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list AgentX WG, - I have not seen enourmous support/enthousiasm to the below email from Bob. - The WG finished all its workitems, and both the AgentX protocol and the MIB module are at Draft Status. Therefor, we'll shut down the WG now. Thank you all (especially WG chair, Editor(s) and all contributors). When it becomes time to consider advancement to full STD, we can then decide how to charter that work. Whenever anybody feels the documents are ready for advancement, pls inform the OPS ADs. I assume we can keep the mailing list open for any further discussion that we may need. Randy? Bert > -----Original Message----- > From: Natale, Robert C (Bob) [mailto:bnatale@lucent.com] > Sent: Thursday, April 04, 2002 7:56 AM > To: agentx@dorothy.bmc.com > Subject: AgentX WG: New work items or close? > Importance: High > > > Hi folks, > > With the advancement of the AgentX specs to > Draft Standard status some time ago, we now > need to decide whether we want to take on any > new work items as an WG or ask the IESG to > close the WG until the time comes to review > the specs' qualifications for Full Standard > status. > > The possible work items I know of that we > could incorporate into a revised charter > include: > > - Mechanisms for supporting the SNMPv3 > security features in AgentX...this has > been discussed on the list in the past > under the "security credentials" and > "isAccessAllowed()" threads. > > - Process mechanisms for ensuring that > IETF standard MIBs are written in such > a way as to avoid constructs that > prevent or seriously impede standard > AgentX support (e.g., avoiding the use > of scalar objects). This might take > the form of a new boilerplate section > for MIBs called "AgentX Considerations", > akin to the "Security Considerations" > section currently required. For vendor > MIBs, this process would encourage > AgentX supportability. > > - Any potential revisions to the specs > that have surfaced since the implementation > survey that we did prior to going to > Draft Standard status that we will need > to address for Full Standard status... > might as well air these at the earliest > possible point and come up with solutions. > > - Any other suggestions from the floor...? > > However, we should undertake these new work items > *only* if there is sufficient interest in actually > working on them (writing, editing, reviewing, > commenting, coding, testing, etc.) among a reasonable > subset of the group. Otherwise, we should ask the > IESG to close the WG. > > So, if you are interested in working on any of > the above items in this forum, please post your > comments to the list within the next several days. > I'll aim for summarizing the response by the end > of next week (Fri 4/12) and making a recommendation > to the ADs for their consideration. > > I have bcc:'d the "AgentPP" and "NET-SNMP" lists > on this notice since they have more AgentX traffic > than this list -- a good thing at this point! -- > but please post all responses back to this list > alias only. > > Thanks, > > BobN > Chair > From owner-agentx@dorothy.bmc.com Wed May 22 07:12:17 2002 Received: from babbler.bmc.com (firebird.bmc.com [198.207.223.228]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22342 for ; Wed, 22 May 2002 07:12:17 -0400 (EDT) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g4MBBQU29123; Wed, 22 May 2002 06:11:26 -0500 (CDT) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id EAA05347 for agentx-list; Wed, 22 May 2002 04:04:37 -0700 (PDT) Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117]) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id EAA05342 for ; Wed, 22 May 2002 04:04:33 -0700 (PDT) Received: from mx-us-hou-1-int.bmc.com (localhost [127.0.0.1]) by tattler.bmc.com (8.10.2/8.10.2) with ESMTP id g4MB23r11811 for ; Wed, 22 May 2002 06:02:03 -0500 (CDT) Received: from hotmail.com (unknown [64.4.20.141]) by mx-us-hou-1-int.bmc.com (Postfix) with SMTP id 17A9420F06E for ; Wed, 22 May 2002 06:06:09 -0500 (CDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 22 May 2002 04:06:03 -0700 Received: from 202.89.68.178 by lw14fd.law14.hotmail.msn.com with HTTP; Wed, 22 May 2002 11:06:03 GMT X-Originating-IP: [202.89.68.178] From: "vishnu varma chiluvuri" To: agentx@dorothy.bmc.com Subject: agentx and snmp Date: Wed, 22 May 2002 11:06:03 +0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 22 May 2002 11:06:03.0810 (UTC) FILETIME=[A9ECB820:01C20180] Sender: owner-agentx@dorothy.bmc.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list Hi all, This is vishnu from india and this is my first mail. we are working on optical ADM which works up to speed of sdh16. I have two questions. 1. for the telecom box which have multiple io cards and system controller card what are the advantages and disadvantages agentx can give when i compared with SNMP for communicaton between master agent and subagent. 2. some my friends proposing SNMP between the master agent and subagent by using snmp as explained below. A) set operation: when set request reaches master agent,master agent gets coresponding objects information from various subagents and stores in temparory memory. now master agent issues the set operation on subagent. if subagents sends any error in resonse messege of set request then master agetn again issue set request with old values.in this way they are doing set request automacity. B)dynamic registration: to register with master agent , subagent will issue a set request to master agent to create entry in the registry mib we have at master agent. this registration mib have the all parameters required for dynamic registration. using like this dynamic registration can be acheived. i am not much convence for this. just i want to put before you all. plese give me various points on the above methods. with regards. VISHNU _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx From owner-agentx@dorothy.bmc.com Wed May 22 13:34:36 2002 Received: from babbler.bmc.com (camaro.bmc.com [198.207.223.231]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20995 for ; Wed, 22 May 2002 13:34:35 -0400 (EDT) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g4MHXPu28965; Wed, 22 May 2002 12:33:25 -0500 (CDT) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA06501 for agentx-list; Wed, 22 May 2002 10:26:20 -0700 (PDT) Received: (from rpresuhn@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA06495 for agentx@dorothy.bmc.com; Wed, 22 May 2002 10:26:15 -0700 (PDT) Date: Wed, 22 May 2002 10:26:15 -0700 (PDT) From: Randy Presuhn Message-Id: <200205221726.KAA06495@dorothy.bmc.com> To: agentx@dorothy.bmc.com Subject: Re: agentx and snmp Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-agentx@dorothy.bmc.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list Content-Transfer-Encoding: 7bit Hi - > From: "vishnu varma chiluvuri" > To: agentx@dorothy.bmc.com > Subject: agentx and snmp > Date: Wed, 22 May 2002 11:06:03 +0000 > Message-ID: ... > 2. some my friends proposing SNMP between the master agent and subagent by > using snmp as explained below. > A) set operation: when set request reaches master agent,master agent gets > coresponding objects information from various subagents and stores in > temparory memory. now master agent issues the set operation on subagent. > if subagents sends any error in resonse messege of set request then master > agetn again issue set request with old values.in this way they are doing > set request automacity. Wrong. Consider the case where the SNMP request contains variable bindings requiring dispatch to different subagents. If one of the sub-requests fails, you're out of luck. > B)dynamic registration: to register with master agent , subagent will > issue a set request to master agent to create entry in the registry mib we > have at master agent. this registration mib have the all parameters > required for dynamic registration. using like this dynamic registration > can be acheived. ... Why re-invent the wheel? Furthermore, if you include subagents from other vendors in your product, how would they know how to interact with this MIB? ------------------------------------------------------ Randy Presuhn BMC Software, Inc. 1-3141 randy_presuhn@bmc.com 2141 North First Street Tel: +1 408 546-1006 San José, California 95131 USA ------------------------------------------------------ My opinions and BMC's are independent variables. ------------------------------------------------------