From: Bob.Natale@AppliedSNMP.com Date: Wed, 25 Apr 2001 02:34:54 -0400 To: agentx@dorothy.bmc.com Subject: AgentX implementation reports requested List-Id: IETF Agentx Working Group mailing list AgentX Implementation Report Solicitation date: April 25, 2001 Desired due date: May 11, 2001 Required due date: May 18, 2001 Draft summary report posted to list by WG Chair: May 21, 2001 Final summary report submitted to IESG by WG Chair: May 31, 2001 Please complete a separate report for each distinct implementation. Please return all reports to the WG Chair, Bob.Natale@AppliedSNMP.com. We would appreciate having the reports copied to the AgentX list as well (agentx@dorothy.bmc.com). If you do not copy the list (or otherwise submit a report to the list), the report will be used only for the purpose of producing the overall summary report. Please use any of the "Comments:" areas to note areas of the specifications that were particularly difficult to implement due to complexity, ambiguity, inconsistency, incompleteness, etc. It is very important for us to identify any implementation hurdles here. You may also use these areas for any other notes that you consider helpful or otherwise worthy of WG attention. Use as much space as necessary. In the end, we need to show that IESG that we have at least two independent and interoperable implementations of all AgentX features for advancement to Draft Standard status. I will solicit interoperability reports with an analogous format next week (interoperability reports may come from end-users of the implementations as well as from implementors themselves). Report date: __________________________________________________ Submitted by: __________________________________________________ Organization: __________________________________________________ E-mail address: __________________________________________________ Implementation name: __________________________________________________ Implementation type: ___ Master and/or ___ Sub-Agent and/or ___ Toolkit Runtime platform(s): __________________________________________________ Reported version id: __________________________________________________ If Master Agent, did you implement: SNMPv1 support in master agent: ___ Yes ___ No Comments: SNMPv2c support in master agent: ___ Yes ___ No Comments: SNMPv3 support in master agent: ___ Yes ___ No Comments: If Sub-Agent, what MIB(s) did you implement: Comments: (Please identify each specific MIB.) If Toolkit, please identify: Development languages supported: Comments: Development platforms supported: Comments: Runtime platforms supported: Comments: For all implementations: Did you implement the following PDU types: agentx-Open-PDU: ___ Yes ___ No, but plan to within ___ months Comments: agentx-Close-PDU: ___ Yes ___ No, but plan to within ___ months Comments: agentx-Register-PDU: ___ Yes ___ No, but plan to within ___ months Comments: agentx-Unregister-PDU: ___ Yes ___ No, but plan to within ___ months Comments: agentx-Get-PDU: ___ Yes ___ No, but plan to within ___ months Comments: agentx-GetNext-PDU: ___ Yes ___ No, but plan to within ___ months Comments: agentx-GetBulk-PDU: ___ Yes ___ No, but plan to within ___ months Comments: agentx-TestSet-PDU: ___ Yes ___ No, but plan to within ___ months Comments: agentx-Commit-PDU: ___ Yes ___ No, but plan to within ___ months Comments: agentx-Set-PDU: ___ Yes ___ No, but plan to within ___ months Comments: agentx-UndoSet-PDU: ___ Yes ___ No, but plan to within ___ months Comments: agentx-CleanupSet-PDU: ___ Yes ___ No, but plan to within ___ months Comments: agentx-Notify-PDU: ___ Yes ___ No, but plan to within ___ months Comments: agentx-Ping-PDU: ___ Yes ___ No, but plan to within ___ months Comments: agentx-IndexAllocate-PDU: ___ Yes ___ No, but plan to within ___ months Comments: agentx-IndexDeallocate-PDU: ___ Yes ___ No, but plan to within ___ months Comments: agentx-AddAgentCaps-PDU: ___ Yes ___ No, but plan to within ___ months Comments: agentx-RemoveAgentCaps-PDU: ___ Yes ___ No, but plan to within ___ months Comments: agentx-Response-PDU: ___ Yes ___ No, but plan to within ___ months Comments: Does this implementation have interoperability experience with at least one other independent implementation with respect to: Registration operations: ___ Yes ___ No, but plan to within ___ months Comments: Registration priorities: ___ Yes ___ No, but plan to within ___ months Comments: Index allocation operations: ___ Yes ___ No, but plan to within ___ months Comments: Index deallocation operations: ___ Yes ___ No, but plan to within ___ months Comments: Multiple sub-agent connections: ___ Yes ___ No, but plan to within ___ months Comments: Connecting sub-agent(s) to multiple master agents: ___ Yes ___ No, but plan to within ___ months Comments: Detecting loss of connection of sub-agent(s): ___ Yes ___ No, but plan to within ___ months Comments: Detecting loss of connection with master agent(s): ___ Yes ___ No, but plan to within ___ months Comments: What transport mappings did you implement: TCP/IP on port 705: ___ Yes ___ No, but plan to within ___ months Comments: UNIX Domain Sockets on "/var/agentx/master": ___ Yes ___ No, but plan to within ___ months Comments: UNIX Domain Sockets on other endpoints: ___ Yes ___ No, but plan to within ___ months Comments: Other(s): ___ Yes ___ No, but plan to within ___ months Comments: (Please indicate at least type(s) and connection specifics.) Did you implement the AgentX MIB (RFC2742): ___ Yes ___ No, but plan to within ___ months Comments: Did you satisfy the agentxMIBCompliance MODULE-COMPLIANCE requirements:: ___ Yes ___ No, but plan to within ___ months Comments: Did you implement the MIB as an integral part of the master agent: ___ Yes ___ No Comments: Did you implement the MIB in an AgentX sub-agent: ___ Yes ___ No Comments: Please record any other comments or notes you deem useful for the record: Comments: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Bob Natale AgentX WG Chair