Re: [dmarc-ietf] Request for feedback: draft-ser-authentication-results-openpgp

Simon Ser <contact@emersion.fr> Thu, 22 October 2020 12:15 UTC

Return-Path: <contact@emersion.fr>
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 E760C3A0AD3 for <dmarc@ietfa.amsl.com>; Thu, 22 Oct 2020 05:15:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level:
X-Spam-Status: No, score=-2.101 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_MSPIKE_H2=-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=emersion.fr
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 K6ifdrDJm1b1 for <dmarc@ietfa.amsl.com>; Thu, 22 Oct 2020 05:15:13 -0700 (PDT)
Received: from mail-40133.protonmail.ch (mail-40133.protonmail.ch [185.70.40.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4FD173A0ADC for <dmarc@ietf.org>; Thu, 22 Oct 2020 05:15:13 -0700 (PDT)
Date: Thu, 22 Oct 2020 12:15:05 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=emersion.fr; s=protonmail2; t=1603368911; bh=YQDnT5pCjJbwyY5XFNAYCJlfOHXJrBdgkyC5UBUvpIU=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=dgdoQPcEy09m/e8YsvZeHuLGiNfvJNBI1y6u+vNnrCkc3aUeJCN3JiBXOhTKDJCno bfuJHrvYBG250zpFPbHf6Y+x4xm3vaf8Zu7Qxt9IOxjVJwFe3ZsA/2NPrhrafJHIU8 vm/kM+gXe2Xrng6U36OLa+O6lqeYRhiVHiAODzwBeabVCQjjpJkzEjKb+ReRBrzehc av+IWuS/RwjmX6bDA1fu9W1imIh4TKolcQmSd+Z/I+I9gsD/b2WruNvInOOfHCTnzP 0otZtugvmtXtvdZx7kyjqy1/tiuMwkmczuLfAe98s7v7gA5E9pfSHi44OtrUprZzBe w4s0Ed3nRZsWQ==
To: "Murray S. Kucherawy" <superuser@gmail.com>
From: Simon Ser <contact@emersion.fr>
Cc: "dmarc@ietf.org" <dmarc@ietf.org>
Reply-To: Simon Ser <contact@emersion.fr>
Message-ID: <W5w0E3cLJbS35FSkPd6yZENgdEGmKFOAOdiv1-4GJAz_FvD5LRpHY7-kct-7WSYgrQUtJKmWHxR3B1eR8TLcHEuTWJh1mZIRnVZUmeRAK08=@emersion.fr>
In-Reply-To: <CAL0qLwb77CeGNJ6AVk1NB6pk6Xf=74qEXjCxSzkhHc=V9sJ4wg@mail.gmail.com>
References: <ZxWD3Yo-oiRI8Rq8k9H-7vG3Rgogp5lhNRwW3JcDUpFjHlfxgubW8rC5g4jQKWnhFazItAexGXsB4xMb69mZg2jRtuXEC7l1GxfmqdBbCOU=@emersion.fr> <CAL0qLwb77CeGNJ6AVk1NB6pk6Xf=74qEXjCxSzkhHc=V9sJ4wg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/zLl2d4Zduqjsqmcu8oHHXUudNqM>
Subject: Re: [dmarc-ietf] Request for feedback: draft-ser-authentication-results-openpgp
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: Thu, 22 Oct 2020 12:15:16 -0000

On Thursday, October 22, 2020 9:51 AM, Murray S. Kucherawy <superuser@gmail.com> wrote:

> On Mon, Oct 19, 2020 at 2:49 PM Simon Ser <contact@emersion.fr> wrote:
>
> > I've submitted a draft for a new Authentication-Results method a while
> > back [1]. I'd like to get some feedback.
> >
> > My use-case is: on a mailing list system [2], I'd like to display PGP
> > signature status, if a PGP signature is present. I'd like the
> > verification to happen once in a mail filter. Having a standardized
> > Authentication-Results method that mail filters can generate and mail
> > user agents can display would be helpful. A very similar thing is
> > already implemented for DKIM.
> >
> > Does this sounds like something worth doing?
>
> Your references to RFC 7601 should change to RFC 8601.

Good catch!

> Are there any existing implementations of MTAs that generate this, and MUAs that consume it?

No, I wanted to try to standardize this before writing software that
depends on it. If you think software should come first, I could start
using an x- token or something.