From owner-agentx@dorothy.bmc.com Tue Dec 4 12:30:19 2001 Received: from babbler.bmc.com (firebird.bmc.com [198.207.223.228]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02872 for ; Tue, 4 Dec 2001 12:30:19 -0500 (EST) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id fB4HQPl09787; Tue, 4 Dec 2001 11:26:25 -0600 (CST) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id JAA15958 for agentx-list; Tue, 4 Dec 2001 09:18:51 -0800 (PST) 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 JAA15953 for ; Tue, 4 Dec 2001 09:18:47 -0800 (PST) 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 fB4HHpm17440 for ; Tue, 4 Dec 2001 11:17:51 -0600 (CST) Received: from ietf.org (unknown [132.151.1.176]) by mx-us-hou-1-int.bmc.com (Postfix) with SMTP id 7663F20EFD7 for ; Tue, 4 Dec 2001 17:12:50 -0600 (CST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02402; Tue, 4 Dec 2001 12:19:57 -0500 (EST) Message-Id: <200112041719.MAA02402@ietf.org> To: IETF-Announce: ; Cc: RFC Editor , Internet Architecture Board , agentx@dorothy.bmc.com From: The IESG Subject: Protocol Action: Agent Extensibility (AgentX) Protocol to Draft Standard Date: Tue, 04 Dec 2001 12:19:57 -0500 Sender: owner-agentx@dorothy.bmc.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list The IESG has elevated the Agent Extensibility (AgentX) Protocol (RFC2741) and Definitions of Managed Objects for Extensible SNMP Agents (RFC 2742) to Draft Standard. These documents were the product of the SNMP Agent Extensibility Working Group. The contact persons are Bert Wijnen and Randy Bush. Technical Summary RFC2741 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. RFC2742 defines a 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. Working Group Summary The working group collected 13 implementation and interoperability reports. The WG implementation report from the WG chair is at: http://www.ietf.org/IESG/Implementations/AGENTX-IMPLEMENTATION These reports demonstrated that all AgentX features have been implemented by two or more independent implementations and that sub-agents from one implementation are able to interoperate with master agents from an independent implementation. A number of the implementations are found in well-known commercial SNMP products; several are found in widely distributed academic and/or "open source" projects; implementations beyond those with filed reports are known to exist. Neither the referenced implementation reports nor the WG Last Call identified any changes to the these RFCs that are required for implementation or interoperability. The working group consensus is that these documents are ready for advancement to Draft Standard. Protocol Quality The documents have been reviewed for the IESG by Randy Bush and Bert Wijnen From owner-agentx@dorothy.bmc.com Tue Dec 4 15:05:01 2001 Received: from babbler.bmc.com (camaro.bmc.com [198.207.223.231]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09812 for ; Tue, 4 Dec 2001 15:05:01 -0500 (EST) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id fB4Jvej13033; Tue, 4 Dec 2001 13:57:40 -0600 (CST) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id LAA17216 for agentx-list; Tue, 4 Dec 2001 11:52:44 -0800 (PST) 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 LAA17211 for ; Tue, 4 Dec 2001 11:52:40 -0800 (PST) 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 fB4Jpjt06252 for ; Tue, 4 Dec 2001 13:51:45 -0600 (CST) Received: from riverstonenet.com (mail.riverstonenet.com [63.113.148.10]) by mx-us-hou-2-int.bmc.com (Postfix) with SMTP id 081BD1FF099 for ; Tue, 4 Dec 2001 19:46:38 -0600 (CST) Received: from dperkins-nb2.dsperkins.com by riverstonenet.com (8.9.3+Sun/SMI-SVR4-Yago) id LAA17342; Tue, 4 Dec 2001 11:53:09 -0800 (PST) Message-Id: <5.0.2.1.2.20011204113411.02a9a480@mail4.bayarea.net> X-Sender: dperkins@mail4.bayarea.net X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Tue, 04 Dec 2001 11:53:12 -0800 To: The IESG From: "David T. Perkins" Subject: Re: Protocol Action: Agent Extensibility (AgentX) Protocol to Draft Standard Cc: RFC Editor , Internet Architecture Board , agentx@dorothy.bmc.com In-Reply-To: <200112041719.MAA02402@ietf.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-agentx@dorothy.bmc.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list HI, While I do not want to derail the agent-X work, I certainly find troubling the implementation report specified in the URL below. It (by itself) does not provide to me the sufficient detail to determine if the IETF requirements for advancement to draft were achieved. I do know the WG chair and many of the WG members and trust their good judgement. However, a page or two of additional documentation would go a long way in helping the historians determine that interoperability of all aspects was truely achieved and that the technology was deployed and found to be useful. Regards, /david t. perkins At 12:19 PM 12/4/2001 -0500, The IESG wrote: >The IESG has elevated the Agent Extensibility (AgentX) Protocol >(RFC2741) and Definitions of Managed Objects for Extensible SNMP Agents >(RFC 2742) to Draft Standard. These documents were the product of the >SNMP Agent Extensibility Working Group. > >The contact persons are Bert Wijnen and Randy Bush. > >Technical Summary > > RFC2741 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. > > RFC2742 defines a 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. > >Working Group Summary > > The working group collected 13 implementation and interoperability > reports. The WG implementation report from the WG chair is at: > > http://www.ietf.org/IESG/Implementations/AGENTX-IMPLEMENTATION > > These reports demonstrated that all AgentX features have been > implemented by two or more independent implementations and that > sub-agents from one implementation are able to interoperate > with master agents from an independent implementation. A number > of the implementations are found in well-known commercial SNMP > products; several are found in widely distributed academic and/or > "open source" projects; implementations beyond those with filed > reports are known to exist. > > Neither the referenced implementation reports nor the WG Last Call > identified any changes to the these RFCs that are required for > implementation or interoperability. > > The working group consensus is that these documents are ready for > advancement to Draft Standard. > >Protocol Quality > > The documents have been reviewed for the IESG by Randy Bush and > Bert Wijnen From owner-agentx@dorothy.bmc.com Tue Dec 4 15:35:09 2001 Received: from babbler.bmc.com (firebird.bmc.com [198.207.223.228]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11180 for ; Tue, 4 Dec 2001 15:35:09 -0500 (EST) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id fB4KWBm23656; Tue, 4 Dec 2001 14:32:11 -0600 (CST) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id MAA17333 for agentx-list; Tue, 4 Dec 2001 12:28:02 -0800 (PST) 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 MAA17326 for ; Tue, 4 Dec 2001 12:27:58 -0800 (PST) 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 fB4KR1H17673 for ; Tue, 4 Dec 2001 14:27:01 -0600 (CST) Received: from auemail1.firewall.lucent.com (unknown [192.11.223.161]) by mx-us-hou-1-int.bmc.com (Postfix) with SMTP id BFB3920F094 for ; Tue, 4 Dec 2001 20:21:59 -0600 (CST) Received: from md6370exch001p.wins.lucent.com (h135-114-206-50.lucent.com [135.114.206.50]) by auemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id fB4KTDe20834 for ; Tue, 4 Dec 2001 15:29:13 -0500 (EST) Received: by md6370exch001p.nse.lucent.com with Internet Mail Service (5.5.2650.21) id ; Tue, 4 Dec 2001 15:28:57 -0500 Message-ID: From: "Natale, Robert C (Bob)" To: "David T. Perkins" Cc: RFC Editor , The IESG , Internet Architecture Board , agentx@dorothy.bmc.com Subject: RE: Protocol Action: Agent Extensibility (AgentX) Protocol to Dra ft Standard Date: Tue, 4 Dec 2001 15:28:56 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain Sender: owner-agentx@dorothy.bmc.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list Dave, Of the 13 implementation reports submitted, 10 were public and 3 were private. The full text of the 10 public reports was posted to the AgentX list at the time of submission. I have not checked lately, but I believe that info is still in the archives. None of the 3 private reports raised any significant issues with implementation or interoperability. (The requests for privacy -- while not requiring any explanation -- were made for what can generally be summed up as "business reasons" of varying (but extremely benign) nature in each case.) Cordially, BobN AgentX Chair > -----Original Message----- > From: David T. Perkins [mailto:dperkins@dsperkins.com] > Sent: Tuesday, December 04, 2001 2:53 PM > To: The IESG > Cc: RFC Editor; Internet Architecture Board; agentx@dorothy.bmc.com > Subject: Re: Protocol Action: Agent Extensibility (AgentX) Protocol to > Draft Standard > > > HI, > > While I do not want to derail the agent-X work, I certainly find > troubling the implementation report specified in the URL below. > It (by itself) does not provide to me the sufficient detail > to determine if the IETF requirements for advancement to draft > were achieved. I do know the WG chair and many of the WG members > and trust their good judgement. However, a page or two of additional > documentation would go a long way in helping the historians > determine that interoperability of all aspects was truely achieved > and that the technology was deployed and found to be useful. > > Regards, > /david t. perkins > > At 12:19 PM 12/4/2001 -0500, The IESG wrote: > > > >The IESG has elevated the Agent Extensibility (AgentX) Protocol > >(RFC2741) and Definitions of Managed Objects for Extensible > SNMP Agents > >(RFC 2742) to Draft Standard. These documents were the > product of the > >SNMP Agent Extensibility Working Group. > > > >The contact persons are Bert Wijnen and Randy Bush. > > > >Technical Summary > > > > RFC2741 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. > > > > RFC2742 defines a 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. > > > >Working Group Summary > > > > The working group collected 13 implementation and interoperability > > reports. The WG implementation report from the WG chair is at: > > > > http://www.ietf.org/IESG/Implementations/AGENTX-IMPLEMENTATION > > > > These reports demonstrated that all AgentX features have been > > implemented by two or more independent implementations and that > > sub-agents from one implementation are able to interoperate > > with master agents from an independent implementation. A number > > of the implementations are found in well-known commercial SNMP > > products; several are found in widely distributed academic and/or > > "open source" projects; implementations beyond those with filed > > reports are known to exist. > > > > Neither the referenced implementation reports nor the WG Last Call > > identified any changes to the these RFCs that are required for > > implementation or interoperability. > > > > The working group consensus is that these documents are ready for > > advancement to Draft Standard. > > > >Protocol Quality > > > > The documents have been reviewed for the IESG by Randy Bush and > > Bert Wijnen > From owner-agentx@dorothy.bmc.com Tue Dec 4 16:21:23 2001 Received: from babbler.bmc.com (camaro.bmc.com [198.207.223.231]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12842 for ; Tue, 4 Dec 2001 16:21:19 -0500 (EST) Received: from dorothy.bmc.com (localhost [127.0.0.1]) by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id fB4LIfj23869; Tue, 4 Dec 2001 15:18:41 -0600 (CST) Received: (from root@localhost) by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id NAA17824 for agentx-list; Tue, 4 Dec 2001 13:13:45 -0800 (PST) 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 NAA17819 for ; Tue, 4 Dec 2001 13:13:40 -0800 (PST) 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 fB4LCh803204 for ; Tue, 4 Dec 2001 15:12:43 -0600 (CST) Received: from riverstonenet.com (unknown [63.113.148.10]) by mx-us-hou-1-int.bmc.com (Postfix) with SMTP id D3B5620F091 for ; Tue, 4 Dec 2001 21:07:40 -0600 (CST) Received: from dperkins-nb2.dsperkins.com by riverstonenet.com (8.9.3+Sun/SMI-SVR4-Yago) id NAA23772; Tue, 4 Dec 2001 13:14:19 -0800 (PST) Message-Id: <5.0.2.1.2.20011204131158.02a9c710@mail4.bayarea.net> X-Sender: dperkins@mail4.bayarea.net X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Tue, 04 Dec 2001 13:14:22 -0800 To: "Natale, Robert C (Bob)" From: "David T. Perkins" Subject: RE: Protocol Action: Agent Extensibility (AgentX) Protocol to Dra ft Standard Cc: RFC Editor , The IESG , Internet Architecture Board , agentx@dorothy.bmc.com In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-agentx@dorothy.bmc.com Precedence: bulk List-Id: IETF Agentx Working Group mailing list HI, Thanks Bob! It looks like I was overreacting to seeing just the summary without hearing that there were documentation in the WG email archives. Sorry, /david t. perkins At 03:28 PM 12/4/2001 -0500, Natale, Robert C (Bob) wrote: >Dave, > >Of the 13 implementation reports submitted, >10 were public and 3 were private. The full >text of the 10 public reports was posted to >the AgentX list at the time of submission. >I have not checked lately, but I believe that >info is still in the archives. > >None of the 3 private reports raised any >significant issues with implementation or >interoperability. (The requests for privacy >-- while not requiring any explanation -- >were made for what can generally be summed >up as "business reasons" of varying (but >extremely benign) nature in each case.) > >Cordially, > >BobN >AgentX Chair > >> -----Original Message----- >> From: David T. Perkins [mailto:dperkins@dsperkins.com] >> Sent: Tuesday, December 04, 2001 2:53 PM >> To: The IESG >> Cc: RFC Editor; Internet Architecture Board; agentx@dorothy.bmc.com >> Subject: Re: Protocol Action: Agent Extensibility (AgentX) Protocol to >> Draft Standard >> >> >> HI, >> >> While I do not want to derail the agent-X work, I certainly find >> troubling the implementation report specified in the URL below. >> It (by itself) does not provide to me the sufficient detail >> to determine if the IETF requirements for advancement to draft >> were achieved. I do know the WG chair and many of the WG members >> and trust their good judgement. However, a page or two of additional >> documentation would go a long way in helping the historians >> determine that interoperability of all aspects was truely achieved >> and that the technology was deployed and found to be useful. >> >> Regards, >> /david t. perkins >> >> At 12:19 PM 12/4/2001 -0500, The IESG wrote: >> >> >> >The IESG has elevated the Agent Extensibility (AgentX) Protocol >> >(RFC2741) and Definitions of Managed Objects for Extensible >> SNMP Agents >> >(RFC 2742) to Draft Standard. These documents were the >> product of the >> >SNMP Agent Extensibility Working Group. >> > >> >The contact persons are Bert Wijnen and Randy Bush. >> > >> >Technical Summary >> > >> > RFC2741 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. >> > >> > RFC2742 defines a 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. >> > >> >Working Group Summary >> > >> > The working group collected 13 implementation and interoperability >> > reports. The WG implementation report from the WG chair is at: >> > >> > http://www.ietf.org/IESG/Implementations/AGENTX-IMPLEMENTATION >> > >> > These reports demonstrated that all AgentX features have been >> > implemented by two or more independent implementations and that >> > sub-agents from one implementation are able to interoperate >> > with master agents from an independent implementation. A number >> > of the implementations are found in well-known commercial SNMP >> > products; several are found in widely distributed academic and/or >> > "open source" projects; implementations beyond those with filed >> > reports are known to exist. >> > >> > Neither the referenced implementation reports nor the WG Last Call >> > identified any changes to the these RFCs that are required for >> > implementation or interoperability. >> > >> > The working group consensus is that these documents are ready for >> > advancement to Draft Standard. >> > >> >Protocol Quality >> > >> > The documents have been reviewed for the IESG by Randy Bush and >> > Bert Wijnen >>