IETF Logo Mail Archive

Re: [dmarc-ietf] DMARCbis WGLC Issue 136 - DMARC Records Can Be CNAMEs

Tero Kivinen <kivinen@iki.fi> Sat, 16 March 2024 08:53 UTC

Return-Path: <kivinen@iki.fi>
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 9F375C14F605 for <dmarc@ietfa.amsl.com>; Sat, 16 Mar 2024 01:53:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.199
X-Spam-Level:
X-Spam-Status: No, score=-2.199 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, NICE_REPLY_A=-0.091, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=iki.fi
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 PNWloMnn6zWE for <dmarc@ietfa.amsl.com>; Sat, 16 Mar 2024 01:53:01 -0700 (PDT)
Received: from meesny.iki.fi (meesny.iki.fi [195.140.195.201]) (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 7C2F3C14F5F8 for <dmarc@ietf.org>; Sat, 16 Mar 2024 01:52:59 -0700 (PDT)
Received: from fireball.acr.fi (fireball.acr.fi [83.145.195.1]) (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) (Authenticated sender: kivinen@iki.fi) by meesny.iki.fi (Postfix) with ESMTPSA id 4TxZdM1z0CzyVX; Sat, 16 Mar 2024 10:52:55 +0200 (EET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iki.fi; s=meesny; t=1710579176; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=l1HFKLH892d0vNVSyG4/JmVgRRdlt5OOIQTD07aX8DY=; b=SJJkJvtwH8BGSUa8iofiL5XsNtuLqDrUG2SH/yz++gjyC7Gzw8xwuiP3VcPq7dRtTuYEbJ SxpMkMCK8IOvIZdqW/VejJZEt87Mu69+c9sJ5nofh7W+6lABw2gS0qoSUbLGL1j3hdZdpW AMbWcWxgQwWoVDQ2qTOOq7r+Rs3YcUQ=
ARC-Seal: i=1; s=meesny; d=iki.fi; t=1710579176; a=rsa-sha256; cv=none; b=NvoADtizBOuAh5mQwvdKK7wZ/VtuOrlwFm0OKa41zaozXfM498R30PXXo8oYmkrEIaXPic jJerIPTiI8ZGsHS8r2LQupjNyn3wH3+7yCnql15MfyepfP9iPhhGCObMTnJ7W/C8OT0rSC egepUwXltAewucJ2L2x2lzjchwLZhU0=
ARC-Authentication-Results: i=1; ORIGINATING; auth=pass smtp.auth=kivinen@iki.fi smtp.mailfrom=kivinen@iki.fi
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=iki.fi; s=meesny; t=1710579176; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=l1HFKLH892d0vNVSyG4/JmVgRRdlt5OOIQTD07aX8DY=; b=v1XZq2I3xTEC95fJN9dRakns5dDZ6iD1lY2F/9bPgXTdcZFbXdxtoTuy4fg96Q0ZreVXfJ ro26CD8S0h4T3H2UY8NA2WlQjjICPfWVW7m62yE2l9f9mVOOqpegdpciKicd9NhuIqXqjl QokxLookT8DUecOVGXAjfibqJ93Enco=
Received: by fireball.acr.fi (Postfix, from userid 15204) id 59B6125C1310; Sat, 16 Mar 2024 10:52:54 +0200 (EET)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <26101.24038.278402.590044@fireball.acr.fi>
Date: Sat, 16 Mar 2024 10:52:54 +0200
From: Tero Kivinen <kivinen@iki.fi>
To: John Levine <johnl@taugh.com>
Cc: dmarc@ietf.org, todd.herr@valimail.com
In-Reply-To: <20240314231133.373738563BAE@ary.qy>
References: <CAHej_8my0_2y5NqsqawiH3x1S5Xn14eGXGYDNfHmPOWu585TKw@mail.gmail.com> <20240314231133.373738563BAE@ary.qy>
X-Mailer: VM 8.2.0b under 26.3 (x86_64--netbsd)
X-Edit-Time: 3 min
X-Total-Time: 4 min
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/NCjLEUqaR3nThsdOGfzC82-mGVY>
Subject: Re: [dmarc-ietf] DMARCbis WGLC Issue 136 - DMARC Records Can Be CNAMEs
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: Sat, 16 Mar 2024 08:53:02 -0000

John Levine writes:
> It appears that Todd Herr  <todd.herr@valimail.com> said:
> >I agree that clarifying it can't hurt, obviously, ...
> 
> I disagree, it does hurt.
> 
> If we say you're allowed to use CNAMEs to point to DMARC records,
> people are to say uh oh, is there something special here? What about
> DKIM records? what about SPF records? how about SPF includes? or SPF
> redirects?
> 
> Really, there is nothing to say here, so let's not say it.

We could add an example Appendix B that uses CNAME, so that would give
indication, yes of course you can use CNAMEs, without explicitly
adding text that might cause confusion.
-- 
kivinen@iki.fi

v2.23.0 | Report a Bug | By Email