[dmarc-ietf] Announcement - DMARC bis Design Team

Seth Blank <seth@valimail.com> Mon, 22 February 2021 17:59 UTC

Return-Path: <seth@valimail.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id BFDDD3A1E8E for <dmarc@ietfa.amsl.com>; Mon, 22 Feb 2021 09:59:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.088
X-Spam-Status: No, score=-2.088 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=valimail.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id SQUkbsA3pblN for <dmarc@ietfa.amsl.com>; Mon, 22 Feb 2021 09:59:06 -0800 (PST)
Received: from mail-vk1-xa32.google.com (mail-vk1-xa32.google.com [IPv6:2607:f8b0:4864:20::a32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D65C3A1E86 for <dmarc@ietf.org>; Mon, 22 Feb 2021 09:59:06 -0800 (PST)
Received: by mail-vk1-xa32.google.com with SMTP id f145so3033172vka.8 for <dmarc@ietf.org>; Mon, 22 Feb 2021 09:59:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:from:date:message-id:subject:to:cc; bh=cgWepUZaH0Dmlunk5H5QIgGFSJ0lLd89i0l0tktFdUQ=; b=gHADIp0pIguHJPLCavJIFlVNm+HOmOI6YWURrUmZPm5UlY5g3o8qvS2QurOi2XOkGX fBYRsq0mA2sWnvP9lxvcYtxsJxcG5eac5Oc1WguMkohxfhDZwlPWeZZwnTpA3a8KtEn1 VqQmRUyVgBHDJvgrXN+qmDUhhkVP+ctqUXgX/EXE3AJfsl+n9A8IWgYwscUWbPD409ac IzfyTLvdIk9fZLw3hsMH9DG4eDuhULydZKioRPoFWdE0LVdHd8ds8aYbscceNp1Dzk0g oWlNTk6+zrg8dGzj05fn/MZVeovvN2G9SjMusEL4aCoTs4ZsuJar9CR2y9yyFXdL3OqM LHTA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=cgWepUZaH0Dmlunk5H5QIgGFSJ0lLd89i0l0tktFdUQ=; b=RHNgcke6kZ2PfnbPaPWhfLaz08jM7Kv/pA4pIhsHjxN9CeOZ7i5W7wk+ocnk6kJhyC lbptVD+ZYMW3Bipl1QG5tcp35kNw8RUY6ZcCzpyuhBCOI087t9j+Z7uFzQAmmmjKrnvo Ywv481/aO72rvb2yMrHwkVDiw2zZhjmbEFuovUFTQyOVIlh+xIqDFST+tIG1TWzo6ygV 1FTvJIK50APsejAEZZL6xQ9GODjyRYQrop2vl92RE1G/Bhu9n3DOM8kdIvzgDE9vUrdt oZjpiztyaV76KE0JKdJMApvob0fD4qAY+F0e3te0iDfRtIozVMIbn9N+9i2y438r9+Sr EB+Q==
X-Gm-Message-State: AOAM532bN8gHI37DraP/0yiKfOPJ14CbK+vfGTS+XjbnyAR8RpOpXOYg N7XkGwzYTDTuuW6lYpsLkrW2iEk/CUg7MmXjM0zlqVw2sDq3LA==
X-Google-Smtp-Source: ABdhPJyVmodk4Zjs2+LvSy42WYULE9QkxDBn8+JzfMhWWy7QXVCqXsKGCG79+1xmNU06pbWdYtFPA09S72/PoB2d8Ok=
X-Received: by 2002:a1f:4c45:: with SMTP id z66mr13718654vka.4.1614016744885; Mon, 22 Feb 2021 09:59:04 -0800 (PST)
MIME-Version: 1.0
From: Seth Blank <seth@valimail.com>
Date: Mon, 22 Feb 2021 09:58:53 -0800
Message-ID: <CAOZAAfPbzfJvn5XQ=4d_jHcv8cSLR-R3pxCREKzT4U3pUzzNCg@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Cc: dmarc-chairs@ietf.org, ART ADs <art-ads@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000bda70105bbf08e0e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/K9j4TxYEg3D7oSlsbltYEnEEd3A>
Subject: [dmarc-ietf] Announcement - DMARC bis Design Team
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Feb 2021 17:59:09 -0000

On 27 October 2020, in post
the chairs announced a split of RFC7489 into three documents, to be scoped
as follows:

   - The DMARC Base Spec (editors - Emil Gustafsson, Todd Herr, and John
   - Aggregate Reporting (editor - Alex Brotman)
   - Forensic Reporting (editors - Steve Jones and Alessandro Vesely)

The chairs are of the opinion that discussion of topics related to the
DMARC bis documents on the mailing list has reached a point where it would
be unreasonable to expect any timely progress toward completion of the
refinement of the DMARC bis at this point.

Our charter (https://datatracker.ietf.org/wg/dmarc/about/) is clear on what
this working group’s priority should be when reviewing and improving the
DMARC specification: “Issues based on operational experience and/or data
aggregated from multiple sources will be given priority.”

We are spending too much time on items that are at best incidental to
DMARC, and rarely are informed by operational practice or data from
multiple sources. Efforts by the chairs to weigh in and declare discussions
unproductive work for that particular thread, but the involved parties just
move on to another thread, and consensus remains well over the horizon.

We have therefore decided that the best approach to achieve progress for
the DMARC bis documents is to form a design team, per RFC 2418, Section
6.5. The team will be composed of the editors, focused on their designated
documents, as defined above. The team will be charged with working through
all existing tickets and producing an updated version of each DMARC bis
document to present to the working group, at which point discussion would
resume on-list with respect to the updated documents.

The design team will operate as follows:


   A moratorium is hereby imposed on creating tickets for this working
   group, effective at 5pm PT, Friday, February 26th.

   The design team will have until 5pm PT, Friday, April 23rd, to work
   through all applicable tickets, and come to agreement on each to either
   modify DMARC bis documents (and make such modification) or reject the
   ticket, with the reason for rejection added to the ticket's comments. No
   tickets will be closed during this process, everything will be transparent
   for working group review after the design period.

   Changes made to the DMARC bis documents will be tracked in the following

      By comments added to the ticket driving the change

      By comments in the markdown (.md) and/or XML version of the documents

      Through an Appendix section added temporarily to the documents, so
      that changes can be easily summarized for the next step in the process.

      All changes throughout the process will be publicly visible within
      GitHub (https://github.com/ietf-wg-dmarc).

   At the end of the time period, in roughly sixty days (or earlier if
   their work is finished before then), the design team will deliver updated
   versions of the DMARC bis documents to the working group, and the working
   group will have a chance to review that version and make
   comments/recommending edits, etc., using
   https://trac.ietf.org/trac/dmarc/report/1 to create tickets as needed.
   Initial discussion will be limited to what’s in the documents.

   The design team will consult with each other and the chairs during their
   work as needed.

The chairs spent a great deal of time discussing this, and we don’t take
this action lightly or without hesitation, but in the end we feel it’s the
best way to not only make progress on the working group's efforts, but also
to allow for working group participants to reset and perhaps gain a fresh
perspective on this important work.

After the updated documents have been presented to the working group, we
will hold an interim to discuss them and hear all feedback.

Seth, Tim, and Alexey, as Co-Chairs


*Seth Blank* | VP, Standards and New Technologies
*e:* seth@valimail.com
*p:* 415.273.8818


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.