IETF Logo Mail Archive

Re: [dmarc-ietf] DMARCbis issue: what is DMARC ?

"John R Levine" <johnl@taugh.com> Fri, 24 May 2019 18:42 UTC

Return-Path: <johnl@taugh.com>
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 167091202EA for <dmarc@ietfa.amsl.com>; Fri, 24 May 2019 11:42:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=t+SZq0ZR; dkim=pass (1536-bit key) header.d=taugh.com header.b=vQWp/kKW
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 ltL1xsIO4yTA for <dmarc@ietfa.amsl.com>; Fri, 24 May 2019 11:42:19 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 236B512004B for <dmarc@ietf.org>; Fri, 24 May 2019 11:42:19 -0700 (PDT)
Received: (qmail 7236 invoked from network); 24 May 2019 18:42:15 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=1c41.5ce83b07.k1905; i=johnl-iecc.com@submit.iecc.com; bh=wTBJUeSoT80IFRNfJDw8XCEktlgu2HYfft1gn5UJRbA=; b=t+SZq0ZRo4Hv+VVPF74mUHhW7pEB9ncorfqu6X71qVMj+rr/9cSZYjM0cW76hovrAfcv+hDZx8reL4xt+810owevyf0U7k7y2FGFAyzfAyWaFLjMUGWC1JhjEQb3peHbj1l6y8T1HoGW/qs1MedMIJgYsH8rm7iXOX3e8tHTGY7XftLZiPBqPNJLWBl2e2/atpAAhOmdO3fjv90OrepPd+sMoYg5tEglppHWH0+jFp5mz4bwEWwzwr/If8G3OiV/
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=1c41.5ce83b07.k1905; olt=johnl-iecc.com@submit.iecc.com; bh=wTBJUeSoT80IFRNfJDw8XCEktlgu2HYfft1gn5UJRbA=; b=vQWp/kKWmZzKtpqzAHXJFRgsr66Q56UBe2Z0vncLFJyE+XR2kTasrOp1IYN3Nmg5DSEmmlqyP7glYP4CKSeENrkiZXwHpcGeaY5HayICNKmJFpL7+kqxv5OJPRptcPwIQtV8e3ZZyqmGzJ8ok0FY4mJk/KHxdYJVm2EcxOH1rJtfupUASIwhHNZV92AMSGn6QPm3yYH8PahJHqyIAF3nyqjP2NS06yzJqhL3xAJc3TNK+F/WGk7zptNmfUwQFxNs
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.2 ECDHE-RSA AES-256-GCM AEAD, johnl@iecc.com) via TCP6; 24 May 2019 18:42:14 -0000
Date: Fri, 24 May 2019 14:42:14 -0400
Message-ID: <alpine.OSX.2.21.9999.1905241441200.51329@ary.qy>
From: John R Levine <johnl@taugh.com>
To: Jim Fenton <fenton@bluepopcorn.net>
Cc: dmarc@ietf.org
In-Reply-To: <4e4a59d7-e652-48f1-feb1-09d948c3eb04@bluepopcorn.net>
References: <20190523225213.C214620147B780@ary.qy> <ab587c42-dd2f-2403-999a-c7d559764726@bluepopcorn.net> <alpine.OSX.2.21.9999.1905241036450.50141@ary.qy> <280824a0-536b-91f1-8072-f7d1cf3051aa@bluepopcorn.net> <alpine.OSX.2.21.9999.1905241416240.51329@ary.qy> <4e4a59d7-e652-48f1-feb1-09d948c3eb04@bluepopcorn.net>
User-Agent: Alpine 2.21.9999 (OSX 337 2019-05-05)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/FRg_MpitvKUlTS94nKcL9lf_1hg>
Subject: Re: [dmarc-ietf] DMARCbis issue: what is DMARC ?
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: Fri, 24 May 2019 18:42:21 -0000

>> I'm getting the impression that what we need is a non-normative
>> deployment guide, not as part of the spec.
>
> Although Section 8 of the spec currently has normative requirements for
> implementations. Yes, that's different from deployment but having those
> requirements to implement something that isn't deployed much (4a
> specifically) seems unnecessarily burdensome.

Taking out stuff that people don't actually do or marking it as optional 
seems like a reasonable change to the next version of the spec.  But I 
still think a non-normative deployment guide would help people.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly

v2.23.0 | Report a Bug | By Email