IETF Logo Mail Archive

Re: (DMARC) We've been here before, was Why mailing lists

Pete Resnick <presnick@qti.qualcomm.com> Thu, 17 April 2014 04:54 UTC

Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EC4B1A0458 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 21:54:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.573
X-Spam-Level:
X-Spam-Status: No, score=-4.573 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 V-C8rYsl_8QF for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 21:54:07 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 839E61A0454 for <ietf@ietf.org>; Wed, 16 Apr 2014 21:54:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1397710444; x=1429246444; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=rk+ooJq3WVRrTDb06jYRWAREyOArtu4n3eumoSEGlrE=; b=o9rOHz8Pu+DMRjVMlDGiwud2zp1yArQsKguZGMK7BC6rYAcu31Y6zRJH cmf73Ik6wC5wenUJWI0l6n2JP4arC4VyANhZq88TaaTug8/72nQhQEt28 qHRZQNUdx4xWD+sl47eH/em6ZVyoxwIPb6WvuU6XCp4ZLNt4bYCqc0TVj A=;
X-IronPort-AV: E=McAfee;i="5400,1158,7410"; a="120400675"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by wolverine02.qualcomm.com with ESMTP; 16 Apr 2014 21:54:03 -0700
X-IronPort-AV: E=Sophos;i="4.97,876,1389772800"; d="scan'208";a="650347367"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 16 Apr 2014 21:54:03 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 16 Apr 2014 21:54:03 -0700
Message-ID: <534F5E67.1010307@qti.qualcomm.com>
Date: Wed, 16 Apr 2014 23:53:59 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: John R Levine <johnl@taugh.com>
Subject: Re: (DMARC) We've been here before, was Why mailing lists
References: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com> <20140414214949.32126.qmail@joyce.lan> <CE39F90A45FF0C49A1EA229FC9899B0507D460CB@USCLES544.agna.amgreetings.com> <alpine.BSF.2.00.1404142150430.32657@joyce.lan> <CAL0qLwbPMm_i0fqNSGQPv=xZaiNASy=icsRNudaNJ_3PNtX3Og@mail.gmail.com> <alpine.BSF.2.00.1404151832460.38826@joyce.lan> <CAL0qLwZUptJVw85T2FjB2HRGoOvcOUHKiQXeadM0QE9BsFVM9w@mail.gmail.com> <CAKHUCzxpwS+nR9wRGOzU_83f7XabMr0pwB5x-MHrqM-28r80kw@mail.gmail.com> <CAKHUCzzw9mufrTCOBQOkRrZU6wOM21X8Y=FUEKf=qnzS9VESjA@mail.gmail.com> <alpine.BSF.2.00.1404161654430.2065@joyce.lan> <534F1183.6060702@qti.qualcomm.com> <alpine.BSF.2.00.1404162346400.2194@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1404162346400.2194@joyce.lan>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/lE_UlZ9-PrIhNoMTC_bqXH91tho
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 04:54:10 -0000

On 4/16/14 11:03 PM, John R Levine wrote:
>> The originator (well, more to the point, the originator's mail 
>> server) doesn't need a signal that it's a mailing list; it's simply 
>> that the destination makes an "if I forward the mail, I'll be 
>> including this" piece of data available, and the originator's server 
>> can then include that in the signature of the message. I was thinking 
>> this could be in some special kind of DMARC (or whatever) record that 
>> lived in the mailing list's domain and could be queried by the 
>> originator's server.
>
> The magic token has to be cryptographically tied to the contents of 
> the original message

No it doesn't. It has to be cryptographically tied to the mailing list's 
re-sending of the message. How to do that with asymmetric keys should be 
discussed somewhere other than on this list.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478

v2.23.0 | Report a Bug | By Email