Dear WG,

As mentioned during Session II today, we have developed a policy [0] for DNS 
DISPATCH. One of its provisions is that requests must be made using a template 
[1]. (Both files attached for convenience.)

The Chairs are soliciting feedback on

- the policy [0],
- the template [1],
- how it went today (optionally privately to dnsop-chairs).

If we do not hear much from the WG, we will assume that this approach is fine; 
otherwise, we may make adjustments.

Best,
Peter

[0] https://github.com/IETF-OPS-AD/Charters/blob/main/dnsdispatch.md
[1] https://github.com/IETF-OPS-AD/Charters/blob/main/dnsdispatch-template.md
# DNSDISPATCH

## Overall

DNS-related I-Ds that don't have an obvious WG which could adopt them can be submitted to the DNSOP WG for consideration. The DNSOP WG will advise whether to progress (or not) these I-Ds and will recommend a way to progress a proposal as appropriate. For instance, DNSOP may suggest the most suitable WG or recommend the chartering of a new WG.

The DNSDISPATCH dispatch decisions cannot result in automatic adoption.

DNSDISPATCH should decline to provide a recommendation for documents that are not within scope.

## Venue

DNSDISPATCH is traditionally held during plenary DNSOP sessions. However, the process can be run using dedicated virtual interims or via the mailing list. The actual mode used for a given proposal is left to the DNSOP WG Chairs.

## Prerequisites

- Presenters are required to use this [Template](dnsdispatch-template.md).
- Recommended: Presenters should generate useful discussion on the DNSOP mailing list before making a DNSDISPATCH request.
- The Chairs might use a pool of willing Shepherds to assist the Chairs and Authors with process related help for incoming documents.
- Documents to-be-dispatched should clearly articulate the problem space and proposed solution before consideration.

## Mode of Operation for Plenary DNSDISPATCH Sessions

- A DNSDISPATCH session may include up to 3 items.
- Chairs will rank received requests by relevance/priority.
- Chairs provide a reason when rejecting a request.
- Proponents of an item have 6 minutes to explain, then followed by 4 minutes of feedback.
- Chairs will summarize the main feedback and gauge consensus.
- If the consensus is "Go to WG X", "Consider a BoF", "Consider AD-Sponsorship", or "Discard because of reason Y", record the outcome.
   * If no consensus, proponents recommended to continue the discussion on the list.
   * Proponents may request a second DNSDISPATCH slot. In any case, a same item should not be considered for more than two DNSDISPATCH sessions.
- Chairs will summarize and send out an outcomes email to [email protected] (for each specific item).


## Coordination

Other IETF areas and IETF-maintained technologies (see below) may have their own process for considering new work. While DNSOP is the main DISPATCH home for new DNS-related proposals, some of these proposals may involve other technologies that falls under areas/groups. DNSOP Chairs will coordinate and liaise with these areas/groups when processing such proposals.

The DNS directorate is a resource available to the DNSDISPATCH working group, just as it is available to other working groups.

# Other IETF DISPATCH WGs

Dispatch functions for other IETF areas and technologies are handled by the following WGs:

* General area: [GENDISPATCH](https://datatracker.ietf.org/wg/gendispatch/) WG
* Internet of Things (ToT) topics: [IOTOPS](https://datatracker.ietf.org/wg/iotops/) WG
* Performance and Benchmarking related topics: [BPM](https://datatracker.ietf.org/wg/bpm/)
* Other Operations related topics: [OPSAWG](https://datatracker.ietf.org/wg/opsawg/)
* Routing area: [RTGWG](https://datatracker.ietf.org/wg/rtgwg/) WG
* Transport aspects of the WIT area: [TSVWG](https://datatracker.ietf.org/wg/tsvwg/).
* Applications and Real Time (ART), Security (SEC), and non-transport: [DISPATCH](https://datatracker.ietf.org/wg/dispatch/about/) WG 
# DNSDISPATCH Request Template

Proponents requesting DNSDISPATCH consideration should fill in this template and send it to the DNSOP WG Chairs ([email protected]). Please keep answers brief; links to the I-D and mailing list threads are preferred over lengthy text.

Incomplete requests may be deferred or declined.

## Basic Information

- **Title of the proposal:**

  > _[your answer]_

- **Internet-Draft(s):** (name and link to the latest revision)

  > _[your answer]_

- **Authors:**

  > _[your answer]_

- **Presenter(s):** (if different from the authors)

  > _[your answer]_

- **Contact email:**

  > _[your answer]_

## Problem Statement

- What problem does the proposal address? (2-3 sentences)

  > _[your answer]_

- Who is affected by the problem (e.g., resolver operators, authoritative operators, registries/registrars, stub/application developers, end users)?

  > _[your answer]_

- Why is the problem not solved by existing specifications or practices? (1-2 sentences)

  > _[your answer]_

## Proposed Solution

- Summary of the proposed solution. (2-3 sentences)

  > _[your answer]_

- Does the proposal change or extend the DNS protocol (e.g., new RR types, EDNS options, header flags, opcodes, RCODEs, or changes to resolution behavior)?

  > _[your answer]_

- Does the proposal require new IANA registries or registrations?

  > _[your answer]_

- Known alternative approaches, and why this one is preferred:

  > _[your answer]_

- Has this proposal been presented at DNSDISPATCH before? If so, when, and what has changed since then?

  > _[your answer]_

## Fit With Existing IETF Work

- Which WGs have been considered for this work, and why are they not an obvious home?

  > _[your answer]_

- Related RFCs, I-Ds, or ongoing work (in the IETF or elsewhere, e.g., DNS-OARC, RIPE, ICANN):

  > _[your answer]_

- Other IETF areas or groups that may need to be involved or consulted:

  > _[your answer]_

## Community Interest

- Links to prior discussion on [email protected] or other lists (required!):

  > _[your answer]_

- Implementation and deployment status (if any):

  > _[your answer]_

## Presentation

For DNSDISPATCH presentations, presenters have 6 minutes, followed by 4 minutes of feedback. Slides should focus on the problem statement and why the proposal needs dispatching, rather than on the details of the solution.

- **Slides:** (link, attachment or "will be provided by <date>")

  > _[your answer]_

Note: Your request will be deferred until slides are provided.
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to