Re: [Ietf-dkim] DKIM issues (tag "v=DKIM1", tag "p=")

Dave Crocker <dcrocker@bbiw.net> Wed, 14 June 2023 16:24 UTC

Return-Path: <dcrocker@bbiw.net>
X-Original-To: ietf-dkim@ietfa.amsl.com
Delivered-To: ietf-dkim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4140FC15256E for <ietf-dkim@ietfa.amsl.com>; Wed, 14 Jun 2023 09:24:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.796
X-Spam-Level:
X-Spam-Status: No, score=-2.796 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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=bbiw.net header.b="lG+7FtaE"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="NKfFLSRO"
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 5nRs2-v8Ps_F for <ietf-dkim@ietfa.amsl.com>; Wed, 14 Jun 2023 09:24:39 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A705DC15257D for <ietf-dkim@ietfa.amsl.com>; Wed, 14 Jun 2023 09:24:33 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 57C1B5C0161; Wed, 14 Jun 2023 12:24:32 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Wed, 14 Jun 2023 12:24:32 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bbiw.net; h=cc :cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm3; t=1686759872; x=1686846272; bh=4A hO/3D8L/Wehp1iAbu1/oUQi7DVq6JOWDVMkKZktXk=; b=lG+7FtaEDGCl6Nfc6Q ypxtNEQeROY5YICY8YbX2eaNf/0HxXu9b73PJHARTJW2oqAeaC5JQr5GW6d+rCid nPBQY45T6nFiFnVs6bEH0a3I5VBJcdF7/A64+iyM2NsTHc/x/hArcmChn3/MHbGY Avanj65ruzn7v8+DsBCL0Qvmg/0UvQa8Iz3EGmZ5dnAyRpAkAumrLoUR0qOYWmb5 EtDqdwxyVfbCtC/Sw7jqavzC9QHfROizn4eCmcNfjLMqXRq32gk0JKfTZVI9MDJT RsJ305avTSr8g39pYbQl/TOEdqPb0+gxZSi4kxFMZ0Dc7AGfHuFES5bSQ6dJfRbl demQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; t=1686759872; x=1686846272; bh=4AhO/3D8L/Weh p1iAbu1/oUQi7DVq6JOWDVMkKZktXk=; b=NKfFLSROIp+4tBTyL/ctB+X9fltTm M0wdC0lpADRNZQEhaPN2i0oAURFEvFgqEHnpa68UURPfDSGEB3DG/aoDTpHys9TU 8T4O8/K395hneJihhZOrOde7o2G4w8BP5bL8oVAs0oDg0qQNOTTG2kzPA+qyuLr0 Kaam1+58pKt35P9/t6JUHBl1hlvuGdUvdip0YjNIcGsYQIiKEz0l+YYuh9o0Rlow U8BCyWcpL+5T6PvBkZjlnhgb8EwaDAhpdiheQLe3UBGXChDagBitSKnZc6wdXqL4 ajfvvEkqcujNRVgQTeIjlff/DsQZzzlBSYE0KG5a5J57nd+sdaZMnRG4Q==
X-ME-Sender: <xms:v-mJZKtzhe9CFo6ZaLA-bzTre9Nm0oijGckyieH0ZWLahnZxlfWXZw> <xme:v-mJZPf9VxXXAcpGp9pqqE75a-t-ZU6luWu2_bSgbhhNHu2DKdFf6tIuKYjXGYDVn KSvWgM_0xg9lUAQDA>
X-ME-Received: <xmr:v-mJZFxkt21lG47jB2QKsDGqZTgDwAaJu9wGYrWXfTMtmRxTfQK8Ko8yAgJbuzKbaz3oB8ddb5UtbOVfEphr3xTlPh0xygCXoz78RY4>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrgedvtddguddtvdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpegtkfffgggfuffvvehfhfhojgesrgdtreertdefjeenucfhrhhomhepffgr vhgvucevrhhotghkvghruceouggtrhhotghkvghrsegssghifidrnhgvtheqnecuggftrf grthhtvghrnhepjeehvdejjeeitdevkedvvdfgvdeftdehvedutdfggefhhfetvdehtdfh ffefudelnecuffhomhgrihhnpehrfhgtqdgvughithhorhdrohhrghdpsggsihifrdhnvg htnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepuggt rhhotghkvghrsegssghifidrnhgvth
X-ME-Proxy: <xmx:wOmJZFPP8wwp-ZkMYuJHNIC6aLmuP2wlhGusub4ywLZ43pPOvGGsow> <xmx:wOmJZK-c2-ZzAWfhPduaCTGrJGLd7oRlmdkfkYw0gYLN2FPJ8YWPAQ> <xmx:wOmJZNWMgU46ACmd17EGKNjnORIfE7E4tf8rC3zmVpyypTvWZdWmnA> <xmx:wOmJZMLwtTvQ51u-J5bEmdkK_a5doX1h_87e-X9ldmzUatQBXdf29g>
Feedback-ID: i16d9478d:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 14 Jun 2023 12:24:31 -0400 (EDT)
Content-Type: multipart/alternative; boundary="------------IPOZ1sYok2jLNBnfg5NPOLt0"
Message-ID: <aaef861f-317f-a975-82eb-172813ffd91f@bbiw.net>
Date: Wed, 14 Jun 2023 11:24:32 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.12.0
To: Jan Dušátko <jan=40dusatko.org@dmarc.ietf.org>
Cc: "Murray S. Kucherawy" <superuser@gmail.com>, ietf-dkim@ietfa.amsl.com, Barry Leiba <barryleiba@computer.org>
References: <e2afdc9b-3c71-a045-8fff-0cd9095a8464@dusatko.org> <CAL0qLwbDufOOKrVSj4zwKvAgpmUNU7c0sWGjS-V380q1E0X1tA@mail.gmail.com> <be0733a8-f2b6-a4af-c7de-dd494e773954@dcrocker.net> <5fad734b-0f8f-a0bc-9623-2b2106e93309@dusatko.org> <CALaySJLhndR331MLwz+VsUC48EuL6StNxW4_aF75=TUXuDQu1A@mail.gmail.com>
Content-Language: en-US
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
In-Reply-To: <CALaySJLhndR331MLwz+VsUC48EuL6StNxW4_aF75=TUXuDQu1A@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-dkim/Whxr4LF8RTMDiLHwmsuXYpGsbTs>
Subject: Re: [Ietf-dkim] DKIM issues (tag "v=DKIM1", tag "p=")
X-BeenThere: ietf-dkim@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF DKIM List <ietf-dkim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-dkim>, <mailto:ietf-dkim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-dkim/>
List-Post: <mailto:ietf-dkim@ietf.org>
List-Help: <mailto:ietf-dkim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-dkim>, <mailto:ietf-dkim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Jun 2023 16:24:45 -0000

On 6/12/2023 12:33 PM, Barry Leiba wrote:
> DomainKeys was already made Historic when RFC 4870 was published in
> 2007.  Look at the RFC status.

Indeed.  Upper right corner of the page: rfc4870 
<https://www.rfc-editor.org/rfc/rfc4870>

It is relatively common to have a working specification come from the 
community, as input to an IETF standards effort, and to publish the 
community specification as a companion document, usually as Informational.

Marking one as Historic is, I think, relatively unusual.  As I recall, 
in this case, it was an explicit decision, as an informal encouragement 
to have existing users of Domainkeys move to using the (then) 
newly-minted DKIM.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net
mast:@dcrocker@mastodon.social