* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Welcome to the IETF Tools Pages

These pages are maintained by the IETF Tools Team.

The aim of these web-pages is to help the IETF community as follows:

  • Make it easy to find existing tools
  • Provide means of feedback on existing and new tools (wiki and mailing list)
  • Provide information on new and updated tools

If you have comments on these pages, or ideas for new tools or for refinement of current tools, please send them to tools-discuss@ietf.org.

For current tools, there is a list of available tools at the tools summary page (in addition to the tools page you can reach through the menu to the left). Comments and proposed additions should go to tools-discuss@ietf.org.

Current Tools Team Members
(As of 02 Nov 2007)

  • Henrik Levkowetz
  • Bill Fenner
  • Tero Kivinen
  • Tony Hansen
  • Pasi Eronen

TOOLS Team Charter

Date: 15 Jul 2005


Henrik Levkowetz < henrik@levkowetz.com>


  • Alex Rousskov
  • Bill Fenner
  • Stanislav Shalunov
  • Tero Kivinen
  • Donald Eastlake III
  • Larry Masinter


The purpose of the TOOLS team is to provide IETF feedback and guidance during the development of software tools to support various parts of IETF activities.


The first tool the team has considered is an ID submission tool. With this in place, other tools will follow, as listed in the milestones below.

IASA (IETF Administrative Support Activity) tools will be developed by subcontractor developers for the IASA, in line with BCP 101. The key point about these developers is that they have not worked as part of the IETF community, so they need direction and structure at the starting points, and as changes/fixes are needed. The team will be the voice for this.

Other tools may be adaptations of existing open source tools, ideally in cooperation with the original developers/maintainers of the tools. Again, the TOOLS team will be responsible for communicating IETF specific needs to the developers.

Guidance may be done by specification, but other methods like storyboarding or prototyping may be just as appropriate. This would be up to the team, in cooperation with the tool developers.

It is not the team's task to do the actual development, but being able to understand the tool development process and issues are part of the task, as well as the ability to formulate and communicate the IETF's needs with respect to the individual tools. It is also not prohibited for team members to actively develop tool implementations.

The team may also develop prototypes of tools on servers separate from the Secretariat servers. The team will however not be responsible for management and maintenance of such servers.

Prototype code will be licensed in a way that makes it available to the IASA if needed.

The team will coordinate with the IETF Administrative Director as needed.

The Chair will report to the IETF community regularly.


Milestone -
Requirements for:
Date Comments
ID submission tool Dec 2004 Published as RFC 4228
Draft status pages (revs, diffs, comments) Mar 2005 Running since Mar 2005
Notification services (RSS, mail notification) Aug 2005 Beta in July 2006
Meta-information publication Aug 2005 Available in xml format for individual drafts at http://tools.ietf.org/draft//status.xml
Guidelines for improving useability of the IETF web site Q3 2005 Small prototype available
Html-ized WG agendas Q3 2005 Running since Mar 2005
WG Status update web interface Q4 2005  
Publication request tool Q4 2005  
WG Pages with WG tools, provided to all WGs Q4 2005 Beta running, roll-out July 2006
A tool in support of 3rd party reviews and Last Call comments (extension to I-D tracker?) Q4 2005 Work in progress
I-D tracker extended for use by Chairs Q1 2006 Work in progress
Web interface to set up 'WG Pages' for BOFs Q1 2006  
Review progress to determine whether team needs to have a major re-charter, and/or change composition, or conclude Aug 2007 
Latest update: 2007-11-02 13:41 PDT - webmaster@tools.ietf.org