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.

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.