Concluded WG SNMP Agent Extensibility (agentx)
Note: The data for concluded WGs is occasionally incorrect.
| WG | Name | SNMP Agent Extensibility | |
|---|---|---|---|
| Acronym | agentx | ||
| Area | Operations and Management Area (ops) | ||
| State | Concluded | ||
| Charter | charter-ietf-agentx-01 Approved | ||
| Document dependencies | |||
| Additional resources | More information on Agentx | ||
| Personnel | Chair | Bob Natale | |
| Editor | Mark Ellison | ||
| Mailing list | Address | agentx@ietf.org | |
| To subscribe | https://www.ietf.org/mailman/listinfo/agentx | ||
| Archive | https://mailarchive.ietf.org/arch/browse/agentx/ |
Final Charter for Working Group
The goal of this working group is to define standards-track technology
for SNMP Agent extensibility. The resulting technology specification
will allow independently developed sub-agents to communicate with a
master-agent running on an Internet device.
The technology specification will consist of:
o (mandatory) a platform-independent protocol which supports
intra-agent communication within a device or local area network;
o (optional) a MIB module, which, when implemented by a master-agent,
allows an SNMP-based management application to monitor and control
the intra-agent communication service; and,
o (optional) a programmatic interface to the services offered by
that protocol.
The working group is explicitly directed to develop a solution which is
adequate to achieve transparency with respect to whether a SNMP request
is processed by a master-agent and/or one or more sub-agents;
simultaneously, the working group is further directed to use good
engineering judgement is developing an approach with the smallest
reasonable "footprint" to achieve intra-agent communication. As a
consequence, if the working group may choose to avoid complete
transparency, if, at its discretion, this proves too costly. In this
case, the working group should document its decision for this
engineering trade-off.
Although the working group will solicit existing specifications and
experience in this area, it will produce a vendor-neutral technology
specification.
Milestones
| Date | Milestone | Associated documents |
|---|---|---|
| Jan 2002 | Shutdown WG or re-charter |
Done milestones
| Date | Milestone | Associated documents |
|---|---|---|
| Done | Request for advancement of RFC 2741 and 2742 made to IESG | |
| Done | Decision to advance or recycle made by WG and handed off to IESGfor action | |
| Done | Modifications (if any) to documents (RFC2741 and RFC2742) completed | |
| Done | All open issues resolved | |
| Done | Implementation and interoperability reports summarized (by WG Chair) and assessed via WG e-mail discussion | |
| Done | Interoperability reports formally solicited | |
| Done | Implementation reports formally solicited | |
| Done | Publication of AgentX protocol specification as Proposed | |
| Done | Publication of AgentX MIB specification as a Proposed Standard |