Re: [dmarc-ietf] Doing a tree walk rather than PSL lookup

Joseph Brennan <brennan@columbia.edu> Tue, 24 November 2020 15:00 UTC

Return-Path: <jb51@columbia.edu>
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 E55513A10A4 for <dmarc@ietfa.amsl.com>; Tue, 24 Nov 2020 07:00:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.421
X-Spam-Level: *
X-Spam-Status: No, score=1.421 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_12=1.629, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=columbia.edu
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 OByKUU1fvS_n for <dmarc@ietfa.amsl.com>; Tue, 24 Nov 2020 07:00:30 -0800 (PST)
Received: from mx0a-00364e01.pphosted.com (mx0a-00364e01.pphosted.com [148.163.135.74]) (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 A3CF53A109F for <dmarc@ietf.org>; Tue, 24 Nov 2020 07:00:30 -0800 (PST)
Received: from pps.filterd (m0167071.ppops.net [127.0.0.1]) by mx0a-00364e01.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id 0AOEgZ7X024791 for <dmarc@ietf.org>; Tue, 24 Nov 2020 10:00:30 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=columbia.edu; h=mime-version : references : in-reply-to : from : date : message-id : subject : to : content-type; s=pps01; bh=ZJrnhvvYDWS6vx0idnPgr5Jk9JJFyELpTvYuA3LuPpI=; b=LccpUTKTNBuzwmm2MdQGuwAAzfiVUrnjL3JoYIBZekNBtpmoF/nJMO4Xjw2UZuFLo8sM NZOrmfX3Z3JrF1+WFR46lQYpD0SOOaqQeKCCfzwUsymBGKxVRqmNGLvyZ/I/1hmwWOBP 3vL5xPRmGFOxHwzfWXWD0IwLoffVJK8PXTrA0lftWpcRya3hXPwbmG/yiXKCeW192qV0 bkkgOUkQ9HBYWmW61L/Ah/C9o2nHZa5trb9zQ7vs/ku9ZC6bu/koEQVXaIqGWMWEkRSX mh++3Za4h585l8wB5NQVI+Vjxd9ci3ffH+Gh5EAEmfy1WtdkSMNWl+MibsNpnzaAir9b PQ==
Received: from sendprodmail10.cc.columbia.edu (sendprodmail10.cc.columbia.edu [128.59.72.18]) by mx0a-00364e01.pphosted.com with ESMTP id 34y0qu9av3-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <dmarc@ietf.org>; Tue, 24 Nov 2020 10:00:30 -0500
Received: from mail-io1-f70.google.com (mail-io1-f70.google.com [209.85.166.70]) by sendprodmail10.cc.columbia.edu (8.14.4/8.14.4) with ESMTP id 0AOF0SRH016315 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT) for <dmarc@ietf.org>; Tue, 24 Nov 2020 10:00:28 -0500
Received: by mail-io1-f70.google.com with SMTP id b4so15799311ioa.4 for <dmarc@ietf.org>; Tue, 24 Nov 2020 07:00:28 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=ZJrnhvvYDWS6vx0idnPgr5Jk9JJFyELpTvYuA3LuPpI=; b=WDhy4jPxbtcLUXiJbvz7hPvqOZYf9O9h0Mpxp4aZV59tWt1rCzk6OAowZEuTrgHAbM tCmRL2cC4Eyj16iVCPiVwBg1kQvX/G+ImjrmkgrPB2r6sLQCYcOIZakF9H8DXkPv6fa5 JUvSLEuFvZiK9wErFgoOtQPbHuOfRYod+/F7KZYF0zYt/lYbB9YVBA/uGdhnajbLEBpo L9F/Z5iBdTCjQORSD7sDSv7JIkkrjLLwft8ENR+m8onlNJbOaj+xHLNRPj8lTYwrVL+N uO5T/AkBBsf6DP+Dr/mYYybA2PPuF3IT4dgUmKw3d3UQTT+bUDJ4CyxFJcTw5LbGgJet FnWQ==
X-Gm-Message-State: AOAM531BmvnFmtvm++UEpHvJJRC80ZpN/32xNvrvqkbtF8YbOarm0CEM vhnjPsoxHYRFTJAaSrjp9BiIHqEDUnEeWNe96yLoPswVvU8NESooOUHdsbN1V2uOXbVGh/G0xcv 6HlVQ4oK9VPp+4dHmYl+S7iFnVO5KNg==
X-Received: by 2002:a92:d03:: with SMTP id 3mr4754736iln.197.1606230027855; Tue, 24 Nov 2020 07:00:27 -0800 (PST)
X-Google-Smtp-Source: ABdhPJz8C234tLryo8GbPsOjzVfFku1+l/fVkCN5yQC500DunDGF0/WVqp9ACn5AigG+S1nBej3IMozI3PNbLlqC+/8=
X-Received: by 2002:a92:d03:: with SMTP id 3mr4754704iln.197.1606230027483; Tue, 24 Nov 2020 07:00:27 -0800 (PST)
MIME-Version: 1.0
References: <20201123213846.EB14127C8160@ary.qy> <efa0117e-5b17-800d-820d-b5d2413c6075@tana.it>
In-Reply-To: <efa0117e-5b17-800d-820d-b5d2413c6075@tana.it>
From: Joseph Brennan <brennan@columbia.edu>
Date: Tue, 24 Nov 2020 10:00:16 -0500
Message-ID: <CAMSGcLBimU5NSBnxDEfSLnBkjhosrxd8_7BaTfA-A5bQyrTe1g@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003758dc05b4db9218"
X-CU-OB: Yes
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.312, 18.0.737 definitions=2020-11-24_04:2020-11-24, 2020-11-24 signatures=0
X-Proofpoint-Spam-Details: rule=inbound_notspam policy=inbound score=0 malwarescore=0 priorityscore=1501 spamscore=0 mlxscore=0 phishscore=0 clxscore=1015 lowpriorityscore=10 suspectscore=2 mlxlogscore=661 impostorscore=10 bulkscore=10 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2011240091
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/CYFznscHJ6is8tGUBh_YFgK5VIM>
Subject: Re: [dmarc-ietf] Doing a tree walk rather than PSL lookup
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: Tue, 24 Nov 2020 15:00:32 -0000

I will ask why the recipient system should look up anything but the dmarc
record for the specific domain in the Header From.

In some cases looking up related domains is useful, and in some cases it
can lead to disruption. We don't look up SPF records for related domains,
because they are deliberately different in many cases, e.g. one domain for
mail from end users, another for mail sent by a vendor, yet another for
another vendor. Why is dmarc different?


-- 
Joseph Brennan
Lead, Email and Systems Applications
Columbia University Information Technology