Re: [dmarc-ietf] Kicking off DMARCbis -- tracker and process updates

Alexey Melnikov <aamelnikov@fastmail.fm> Sat, 09 May 2020 14:45 UTC

Return-Path: <aamelnikov@fastmail.fm>
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 1E9EB3A0B0F for <dmarc@ietfa.amsl.com>; Sat, 9 May 2020 07:45:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmail.fm header.b=hmzVWeas; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=pI2vV2US
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 q-U7jJyMku1b for <dmarc@ietfa.amsl.com>; Sat, 9 May 2020 07:45:00 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F054C3A0B08 for <dmarc@ietf.org>; Sat, 9 May 2020 07:44:59 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 377F35C00A8 for <dmarc@ietf.org>; Sat, 9 May 2020 10:44:59 -0400 (EDT)
Received: from imap21 ([10.202.2.71]) by compute3.internal (MEProxy); Sat, 09 May 2020 10:44:59 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm3; bh=QYKK5P5Q8ji2Fv4T32GnstWbkGdgPlM JUsla5pTY4WU=; b=hmzVWeasW1lzphmB/bYMKM6ihkiwHbaC8r+DnlYw4ROB5j9 U2kxSvtj3Fech6zEUBKh+mAbjE1mmNJWiYwxkceS9DG/U0t6TV9SDXavQ1w8EyhU I6pcuwac7F9zDWelXvURJ/MsEJJGsJEX51kcAxkCQT6Bqn93o5G8wODTycFvd0Hw DPhlbTuzM06MI+6twuetcawzuSJtIeUr8q1QdqVyL4IddG8893iu2uUZeAMjH9nm GyJGT+ydeFIU0afYptzr27D5Qy8vuQmGj2O78xSH0JhqabpTpV5reQHc+7RkdY10 COYT0InZf4U5+pWjDXVda1FxSiTt6mczXFoWccw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=QYKK5P 5Q8ji2Fv4T32GnstWbkGdgPlMJUsla5pTY4WU=; b=pI2vV2USJ7KMoezY/u+JuP xhLjXwde5EznOw4ann+H9QDQvGHEv/mRgwDy6uKH6lpjFySBhKiK+tdzZEy4pbek VXSf5Ob5WKGo8pZBZHpsCwDRISQdliBQfupriTAvXi0cMSPjMwbSD6B2rB/Ya47r Cnn5/SdHWFQzqKYlA5zk8Nn61iVObblLxDTxgNBbyybJPoKatnMQJNUJuGrGIf1X vMJ/7+YPpV8OY9iAg445TqrgNVGUWAPk4wAUnXt2ZqVfZ/AmQO7VEep1myCMSUrA SKD7TtsUeb1211wPy3FblgjAKL0K4a5BmmLrlKyhPWU3TQjEJgrPUH7Rl04narAA ==
X-ME-Sender: <xms:68G2XpVr0e4qzXe9fwTUZSXQUY4aA-_OB4TLuGpesXJfDgyhWtL0eA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrkeehgdektdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenog fuuhhsphgvtghtkfhmghffohhmrghinhculdeftddmnecujfgurhepofgfggfkjghffffh vffutgesrgdtreerreertdenucfhrhhomhepfdetlhgvgigvhicuofgvlhhnihhkohhvfd cuoegrrghmvghlnhhikhhovhesfhgrshhtmhgrihhlrdhfmheqnecuggftrfgrthhtvghr nhepgfellefgteduteegieeifffgueduteefveetvdekhefgjeevveelhfejieegffefne cuffhomhgrihhnpehivghtfhdrohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgr rhgrmhepmhgrihhlfhhrohhmpegrrghmvghlnhhikhhovhesfhgrshhtmhgrihhlrdhfmh
X-ME-Proxy: <xmx:68G2XiSwuWtdwN08O6MIEXeCd5Lhn_9nH0l5qOtf6Ue4WBOqhWXguA> <xmx:68G2XgrJ4xb1Bhvt0_OMBOpc5hDD6zO8gRtoEE-A4XUymERrKRkLYw> <xmx:68G2XuxFICNCBBNMe3pC9D07rK3PNnP3QFuNwAORhaRzbB0_QmeM9g> <xmx:68G2XqM1_96Isx55bPNVO_aldv0PBWAE_0p2A0pOzX5Z7_sfTRq-CA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id EF537660069; Sat, 9 May 2020 10:44:58 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-dev0-413-g750b809-fmstable-20200507v1
Mime-Version: 1.0
Message-Id: <76be3b2c-fe09-46f1-adc4-8804c86ca7c3@www.fastmail.com>
In-Reply-To: <CAOZAAfPrvrj+vfDNvGfvhAmUtUAoJM7yGYskpDHOrHppiaEzig@mail.gmail.com>
References: <CAOZAAfPrvrj+vfDNvGfvhAmUtUAoJM7yGYskpDHOrHppiaEzig@mail.gmail.com>
Date: Sat, 09 May 2020 15:43:42 +0100
From: Alexey Melnikov <aamelnikov@fastmail.fm>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="77b629220a054cf2956763ff7f932608"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/rBWzfzDa_tOhaVdxFzUBYVi46QI>
Subject: Re: [dmarc-ietf] Kicking off DMARCbis -- tracker and process updates
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: Sat, 09 May 2020 14:45:04 -0000

Hi all, 

This is the followup email that Seth was talking about in the message below. Here is the process that chairs will use for managing tickets in trac (and just to clarify, when Seth wrote "datatracker" he really meant "trac" on tools.ietf.org)

1) Opening tickets: anyone can open a new ticket. But please check existing tickets (including the closed ones) if the issue was already discussed. Chairs would require higher bar for reopening closed tickets. If you want to reopen a ticket, please email WG chairs directly at dmarc-chairs@ietf.org.

2) Closing tickets:

Document editors can close tickets about editorial issues. These will have the summary line starting with "Editorial: ".
(If in doubt, please ask WG chairs whether you think it is editorial or not)

Only Chairs can close larger issues.


All issues must be closed with a reference to the mailing list discussion (typically an URL of a message in the DMARC mailing list archive).

When we get closer to being done with DMARCbis, chairs might switch to stricter rules about closing tickets. If we do, we will send a separate email about that at that time.

Best Regards,
Alexey, on behalf of chairs.

On Mon, May 4, 2020, at 6:34 AM, Seth Blank wrote:
> Hi all,
> 
> For us to present a standards track document to the IESG, there are many items, some contentious and potentially time consuming, that we must discuss and resolve. While Tim has set up a GitHub repository for work on the I-D, we will be using the datatracker to manage that work.
> 
> The intention of the Chairs is to have an orderly discussion of all the items, ensure all concerns are raised, tracked, and resolved, and deliver a document that successfully makes the transition from ISE to IESG approval.
> 
> 
> Look for a separate email from Alexey on our process for managing items in the data tracker itself. Please refrain from adding any new items until Alexey's email is in hand.
> 
> The datatracker now reflects items raised on the list as well as other items brought to the Chairs directly: https://trac.ietf.org/trac/dmarc/report/1 Please do NOT edit, close, or comment on issues until a Chair explicitly opens discussion on the item on list, as discussed below.
> 
> As of this evening, there are 56 open items in the tracker, they all appear to roughly fall into the following buckets (with some examples from each):
> 
> 1) nits
>  - ABNF issues, preventing feedback loops, better statuses
> 
> 2) updates to tags (primarily calls for removal)
>  - remove sp, pct, ri, apsf, adkim, and reporting chunking
> 
> 3) reporting enhancements
>  - more extensible reporting, ARC reports, JSON reports, https POST reporting, stripped down failure reports
> 
> 4) clarifying prose
>  - implications of failure reports, define what it means to have "implemented" DMARC
> 
> 5) general improvements
>  - PSD, removing the PSL and Org Domain definition from DMARC
> 
> 
> None of these items are themselves requirements, some may overstate their claims, other under, and others still are mutually exclusive or depend on the resolution state of other items. The only requirement is that every item in the tracker must be brought to the group for discussion.
> 
> 
> To efficiently discuss as a WG and arrive at a rough consensus on each item, the Chairs will use the following process for DMARCbis to tear through open tracker items:
> 
> - We will have three tickets from the datatracker open for discussion on the list at any given time
> 
> - Each ticket will have a Chair responsible for shepherding discussion
> 
> - Once consensus is called on a ticket, that will be recorded in the tracker, and a new ticket will be opened for discussion
> 
> - This process is separate from editing the I-D (or I-Ds), which will occur in parallel, but will not block this process
> 
> We'll be bringing the first three items to the list later this week.
> 
> As MSK said in March, it will likely be a long road to get this work ready for Standards Track and address all the open issues. We're looking forward to everyone's collaboration and progressing this work together..
> 
> Seth, as Chair
> 
> -- 
> 

> *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
>