To help facilitate the introduction of proposed new work, SAWDISPATCH 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. SAWDISPATCH is inspired by the guidance and methodology
of [RFC7957](https://datatracker.ietf.org/doc/html/rfc7957) and the
experience of the DISPATCH and SECDISPATCH WGs.

With respect to the WIT area, SAWDISPATCH is not to be used for new work
relating to a transport protocol that is maintained by an existing working
group (such as NFS, QUIC, RTP, SCTP, TCP, etc). New work relating to the
way the IETF transport protocols interact with network elements should be
directed to TSVWG if a relevant working group cannot be found.

Participants requesting to present a topic at a SAWDISPATCH working group
meeting must have:

1. a clear problem statement, motivation and deliverables
2. Identified commonalities and overlap amongst published or ongoing protocol work.
3. people with interest and expertise to work on this problem
4. people interested in an interoperable solution and capable of implementing and deploying it
5. documentation in the form of one or more Internet-Drafts 
6. a slide presentation to be given at the SAWDISPATCH meeting

The SAWDISPATCH chairs may place other requirements on presentations and
may reject presentation requests if not appropriate for the scope of the
SAWDISPATCH working group.

Precedence will be given to documents which have evidence of interest in the
form of active 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 SAWDISPATCH working group may include, but is
not limited to, the following:

1. Directing new work to an existing WG.
2. Guidance to propose a BoF for the new work.
3. Guidance to create a charter for a new working group.
4. Recommend the new work is of sufficient scope to be AD-sponsored (this does not mean an AD is required to sponsor the work).
5. Create a mailing list for further discussion of the proposal. 
6. 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 SAWDISPATCH working group is not binding. Feedback
from SAWDISPATCH is not guaranteed if the SAWDISPATCH chairs cannot
determine consensus on the presented new work.

The SAWDISPATCH 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 SAWDISPATCH working group does not process documents.

Other areas may have their own process for considering new work. Support
for other IETF areas is out of scope for SAWDISPATCH.

The chairs are empowered to create operational procedures within the bounds
of established IETF processes to meet the goals of this working group,
including but not limited to, mandating presentation templates, instituting
mailing list workflows, etc…