Re: [dmarc-ietf] what's a list

"John Levine" <johnl@taugh.com> Sat, 20 April 2013 20:15 UTC

Return-Path: <johnl@iecc.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 EE06D21F8619 for <dmarc@ietfa.amsl.com>; Sat, 20 Apr 2013 13:15:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.199
X-Spam-Level:
X-Spam-Status: No, score=-111.199 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TAPRZ2eP3xUX for <dmarc@ietfa.amsl.com>; Sat, 20 Apr 2013 13:15:06 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 1F8C721F8C06 for <dmarc@ietf.org>; Sat, 20 Apr 2013 13:15:06 -0700 (PDT)
Received: (qmail 62392 invoked from network); 20 Apr 2013 20:16:39 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 20 Apr 2013 20:16:39 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=5172f749.xn--3zv.k1304; i=johnl@user.iecc.com; bh=RZBhtQqDU3ofBs9Srk80pVi/2Nj4BrI2mHfGCdjFdKE=; b=H2RzHi6K8EgbICfHYtxx5tVsKGmhoJ9vcOZ3FOLrcj7l6ZzGQYrRxnZAjkbNzdJhKD+mva45hXOB1FCvMWUDk9QQ2ZPuFT9bv8YOzGaXlNnWIXxciovgE429Nma3e229WCtE7eahr4hXQNp+jnKC03BCVzgTOXaFrgS3MLQ8wqI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=5172f749.xn--3zv.k1304; olt=johnl@user.iecc.com; bh=RZBhtQqDU3ofBs9Srk80pVi/2Nj4BrI2mHfGCdjFdKE=; b=XXr1chPEQOkJhSUrjGPLoFZhbsaTudGtWN5J8eWTzDtw9qF/OGcniAWQmqNroyhBcGnbDNbgkEFs8LHiysonC4SmPFPqwDa8l3V1lW/TrWgr5TVIp/BdwtcQb9Zc9PGlNEafY+YYSGiszm7Scc9xJkxaHrbzHu5s22XU4xITqB4=
Date: Sat, 20 Apr 2013 20:14:43 -0000
Message-ID: <20130420201443.46371.qmail@joyce.lan>
From: John Levine <johnl@taugh.com>
To: dmarc@ietf.org
In-Reply-To: <1581179.AB75fythCq@scott-latitude-e6320>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 7bit
Cc: sklist@kitterman.com
Subject: Re: [dmarc-ietf] what's a list
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 20 Apr 2013 20:15:07 -0000

>Most of the current deployment is at large providers that can do significant 
>data analysis to effectively identify lists.  As a small domain, there's no way 
>I can do the same.
>
>If there were a protocol method to share this information, either among 
>trusted receivers or via 'hints', it could be useful to smaller providers that 
>don't have the scale to mine the data themselves.

That's the kind of thing that VBR is intended for.  A trusted party
publishes a list of certified domains in the DNS.  When you get a
message, you look up the authenticated domain (DKIM valid d= or SPF
mail from pass) in the VBR list, and if it's there, it's certified.

The mechanism is trivial.  The hard parts are collecting the set of
trustworthy sending domains, and arranging for someone credible to
publish it.