Dispatch
charter-ietf-dispatch-03-01
| Document | Proposed charter | Dispatch WG (dispatch) | |
|---|---|---|---|
| Title | Dispatch | ||
| Last updated | 2026-06-05 | ||
| State | External Review (Message to Community, Selected by Secretariat) Rechartering | ||
| WG | State | Active | |
| IESG | Responsible AD | Andy Newton | |
| Charter edit AD | Andy Newton | ||
| Telechat date | On agenda of 2026-06-18 IESG telechat | ||
| Send notices to | (None) |
To help facilitate the introduction of proposed new work, DISPATCH WG
provides a standing venue to provide feedback on, and define next steps
for topics in the ART, SEC and non-transport aspects of the WIT areas.
This facilitation is enabled through a discussion mailing list to
germinate new ideas before they might move to a dedicated mailing list.
Additionally, the WG enables a new work proponent to present their topic
at a WG meeting. DISPATCH is inspired by the guidance and methodology
of RFC7957 and the
experience of the previously chartered DISPATCH and SECDISPATCH WGs.
With respect to the WIT area, DISPATCH is not to be used for new work
relating to transport protocols within the scope of an existing working
group. A list of those working groups is to be maintained on the DISPATCH working
group's IETF Wiki page by the DISPATCH chairs in consultation with the WIT ADs.
Other IETF areas and IETF-maintained technologies may have their own process
for considering new work and are out-of-scope for DISPATCH. The WG chairs will maintain
a list on the DISPATCH WG Wiki of the other working groups with a dispatch function
covering other IETF areas and IETF-maintained technologies.
While DISPATCH has traditionally processed new work proposals during
sessions at IETF meetings, the working group may process new work
at interim meetings, and on the group's mailing list.
The chairs are empowered to create operational procedures to process new
work via all these forums.
The DISPATCH chairs will place requirements on presentations and
may reject presentation requests if not appropriate for the
DISPATCH working group. The chairs will maintain a list of presentation
requirements on the DISPATCH WG Wiki.
Precedence to present will be given to proposals which have evidence of interest in the
form of active Internet-Drafts and list discussion. An Internet-Draft shall not be
dispatched multiple times unless a substantially revised proposal is put
forth, including compelling new reasons for accepting the work.
The feedback given by the DISPATCH working group may include, but is
not limited to, the following:
- Directing new work to an existing WG.
- Guidance to propose a BoF for the new work.
- Guidance to create a charter for a new working group.
- Recommending that the new work is of sufficient scope to be AD-sponsored (this does not mean an AD is required to sponsor the work).
- Creating a mailing list for further discussion of the proposal.
- Suggesting the work be deferred or rejected. Some possible reasons for this include:
* the required expertise for the work does not reside in the IETF
* the work is in the subject area of another Standards Development Organization (SDO)
* there are not enough individuals willing to complete the work in the IETF
* there is no interoperability concern, or no people interested in an interoperable solution.
Guidance given by the DISPATCH working group is not binding. Feedback
from DISPATCH is not guaranteed if the DISPATCH chairs cannot
determine consensus on the presented new work.
The DISPATCH working group may, with the agreement of the relevant
ART, SEC, or WIT ADs, process and have as work items simple administrative
documents for media-type specifications and other IANA actions. Otherwise,
the DISPATCH working group does not process documents.
Proposed milestones
No milestones for charter found.