Re: [dmarc-ietf] Announcement - DMARC bis Design Team
Dotzero <dotzero@gmail.com> Mon, 22 February 2021 21:59 UTC
Return-Path: <dotzero@gmail.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 465F03A20CA; Mon, 22 Feb 2021 13:59:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Level:
X-Spam-Status: No, score=-2.087 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, FREEMAIL_FROM=0.001, 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=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Yi88APEcU7m; Mon, 22 Feb 2021 13:59:25 -0800 (PST)
Received: from mail-qk1-x730.google.com (mail-qk1-x730.google.com [IPv6:2607:f8b0:4864:20::730]) (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 75FD13A20CB; Mon, 22 Feb 2021 13:59:24 -0800 (PST)
Received: by mail-qk1-x730.google.com with SMTP id m144so14255967qke.10; Mon, 22 Feb 2021 13:59:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=FZFdbjSGx9rFXRlfL1lbA1LcCnmBZFioJSlsQiDqm/8=; b=qGf0CCo4mjlCt4p6OsVASsim+YibAPSxX0NM7azZmiNiWfs7llmWaOt6Wy0wQSJDZz DSfzCFkHxJH7Bw+sfnw6kNiRKWurwNGP2mLwHnCbnYeds42QhVCujFbjWwjryzzqhG8c J05TJOs1trhSyWTLHp9GvIc3kgEsvqsvvN9lDf9SeDSReGqVJzhJpN/0zI65ueB4mPkh 4rZsXHKjD1w74gQ4c72NN26lWovoqP20T25qlWfP83NF455DtHZ9wvb1q9bWBQrLwCnI eDG3qAaaT/04sT2LkONUWlqCsA1Al38kT59y/ynzRirhTNC8h6mG6vdDBYFh9OAXfNu/ yrbA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=FZFdbjSGx9rFXRlfL1lbA1LcCnmBZFioJSlsQiDqm/8=; b=mYqYnBwEG9jm+9rTIOpKK7ZvR4B5UvSJybMp9354okUpjHMclO30N/shKKOLx4MVT1 C4WfWlZ33xXHApmbYfBUigWWVVj3HZrScqmh9hsqSa3ckjSm/HYGiZSp8b+YhU+cwPAX lHs5YsiKf15GQwzT2q+OWD5zuTy0F7fIPfGvQ41RKiqMP8vDx4aGQYW5h5Is06+dtGv/ PkTADBI0xHW3j8QcAQScGy5x/oKCBAR2JTAI/0Bt6jY5Lr1dnoupuMpZFvnm61KKKnIt xdkYVa84kDXyiBohSVXfMlzKfB4TR8dGGZQoOesVLkgRAIkcW+si5Gl8EAu4DgP5i37y bRkQ==
X-Gm-Message-State: AOAM532V3uCx6maRgZepxGUzaTXvRF5IDsh4ontC9CPaB+ImJX439Z/W /B47zFDONOiKkQcdn0Qjmi3vlKeFMN5JKKcWMw1sT5Ie
X-Google-Smtp-Source: ABdhPJyOppWJqvlu2QKGqSdlLozWEAEIeg3XBWQXn3BjpB5G3H+QRgIklCr0zfljjQxUkm+I2AdIEdm6DXDQv4GjxIk=
X-Received: by 2002:a37:27c8:: with SMTP id n191mr22796690qkn.146.1614031163407; Mon, 22 Feb 2021 13:59:23 -0800 (PST)
MIME-Version: 1.0
References: <CAOZAAfPbzfJvn5XQ=4d_jHcv8cSLR-R3pxCREKzT4U3pUzzNCg@mail.gmail.com>
In-Reply-To: <CAOZAAfPbzfJvn5XQ=4d_jHcv8cSLR-R3pxCREKzT4U3pUzzNCg@mail.gmail.com>
From: Dotzero <dotzero@gmail.com>
Date: Mon, 22 Feb 2021 16:59:11 -0500
Message-ID: <CAJ4XoYfNYHb0psvRhF1H0avNx-dauGPQuaSmPUk50Tf=0_vfFQ@mail.gmail.com>
To: Seth Blank <seth=40valimail.com@dmarc.ietf.org>
Cc: IETF DMARC WG <dmarc@ietf.org>, ART ADs <art-ads@ietf.org>, dmarc-chairs@ietf.org
Content-Type: multipart/alternative; boundary="00000000000026c34a05bbf3ea2a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/JORMbeoxHLQqMFZR5_k5EGaImUw>
Subject: Re: [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 21:59:27 -0000
So I'm assuming there won't be anything to talk about at the next IETF meeting. Michael Hammer On Mon, Feb 22, 2021 at 12:59 PM Seth Blank <seth= 40valimail.com@dmarc.ietf.org> wrote: > On 27 October 2020, in post > https://mailarchive.ietf.org/arch/msg/dmarc/qtCDyGbeDHz96G8FaCxJvhJKrvo/ > 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 > Levine) > - 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: > > > 1. > > A moratorium is hereby imposed on creating tickets for this working > group, effective at 5pm PT, Friday, February 26th. > 2. > > 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. > 3. > > Changes made to the DMARC bis documents will be tracked in the > following manner: > 1. > > By comments added to the ticket driving the change > 2. > > By comments in the markdown (.md) and/or XML version of the > documents > 3. > > Through an Appendix section added temporarily to the documents, so > that changes can be easily summarized for the next step in the process. > 4. > > All changes throughout the process will be publicly visible within > GitHub (https://github.com/ietf-wg-dmarc). > 4. > > 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. > 5. > > 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. > _______________________________________________ > dmarc mailing list > dmarc@ietf.org > https://www.ietf.org/mailman/listinfo/dmarc >
- [dmarc-ietf] Announcement - DMARC bis Design Team Seth Blank
- Re: [dmarc-ietf] Announcement - DMARC bis Design … Tim Wicinski
- Re: [dmarc-ietf] Announcement - DMARC bis Design … Dotzero
- Re: [dmarc-ietf] Announcement - DMARC bis Design … tjw ietf
- Re: [dmarc-ietf] Announcement - DMARC bis Design … Seth Blank
- Re: [dmarc-ietf] Announcement - DMARC bis Design … Seth Blank
- Re: [dmarc-ietf] Announcement - DMARC bis Design … Seth Blank