IETF Logo Mail Archive

Re: [dmarc-ietf] Standards Track? Yes or No.

Alessandro Vesely <vesely@tana.it> Tue, 02 April 2024 10:09 UTC

Return-Path: <vesely@tana.it>
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 505E5C14F61B for <dmarc@ietfa.amsl.com>; Tue, 2 Apr 2024 03:09:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.397
X-Spam-Level:
X-Spam-Status: No, score=-4.397 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1152-bit key) header.d=tana.it
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xyF8LL4dGr2L for <dmarc@ietfa.amsl.com>; Tue, 2 Apr 2024 03:09:26 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [94.198.96.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28BEDC14F616 for <dmarc@ietf.org>; Tue, 2 Apr 2024 03:09:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1712052558; bh=ueefp2AWtIyfWt/ZhkEwiXhE324UPEpe8YKWDn7nkq0=; h=Date:Subject:To:References:From:In-Reply-To; b=DkmnpbgtE/rJBz7Gu7cKq00SSRROHuKlQnuqI+utGOyXQ9Rvic5EGiN3j1r+aBZtz OScByGcODH5KHtUTZbuSR8pF0I5JQeDQCQrw5SyEl92J0dcPpiI7x8G5NHPvuXmBDq 61WmEX7WQ1tCqSLxQnnoyC2UeBR4csVLzCEaEZaH9N30Xe3fMzno9jJdxq9Qj
Original-Subject: Re: [dmarc-ietf] Standards Track? Yes or No.
Author: Alessandro Vesely <vesely@tana.it>
Received: from [172.25.197.120] (pcale.tana [::ffff:172.25.197.120]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLS1.3, 128bits, ECDHE_RSA_AES_128_GCM_SHA256) by wmail.tana.it with ESMTPSA id 00000000005DC05A.00000000660BD94D.000066F2; Tue, 02 Apr 2024 12:09:17 +0200
Message-ID: <87350d50-1522-485e-89de-7aa17bebb043@tana.it>
Date: Tue, 02 Apr 2024 12:09:17 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: dmarc@ietf.org
References: <CFEA2796-9213-4847-836B-81E8770973F5@bluepopcorn.net> <10f94e0e-7199-ee0d-ce36-62a2c6c78d95@iecc.com> <CAH48ZfznLaAsbsg8enqg5ZUvp6+sntNDNvX6yWOj5N_7y8m+4Q@mail.gmail.com>
Authentication-Results: tana.it; auth=pass (details omitted)
From: Alessandro Vesely <vesely@tana.it>
Content-Language: en-US, it-IT
In-Reply-To: <CAH48ZfznLaAsbsg8enqg5ZUvp6+sntNDNvX6yWOj5N_7y8m+4Q@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/5B50c-gmPvJTotiZFfsKoER0mXY>
Subject: Re: [dmarc-ietf] Standards Track? Yes or No.
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 02 Apr 2024 10:09:32 -0000

On Tue 02/Apr/2024 07:13:16 +0200 Douglas Foster wrote:
> Standards track?   Not until we fix the failure inherited from RFC 7489: the 
> untutored evaluator who does not know how to use DMARC results wisely.


Doing it all-at-once would expand the time scale unbearably.  In addition, we'd 
need to timely communicate the progress in some other unofficial way, lest the 
final outcome go unnoticed.


Best
Ale
--

v2.23.0 | Report a Bug | By Email