Re: Last Call: <draft-kucherawy-dkim-atps-11.txt> (DKIM Authorized Third-Party Signers) to Experimental RFC

Dave CROCKER <dhc@dcrocker.net> Mon, 05 December 2011 23:54 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F8A31F0C38 for <ietf@ietfa.amsl.com>; Mon, 5 Dec 2011 15:54:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 IVlq-WfTVC62 for <ietf@ietfa.amsl.com>; Mon, 5 Dec 2011 15:54:42 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 002151F0C35 for <ietf@ietf.org>; Mon, 5 Dec 2011 15:54:41 -0800 (PST)
Received: from [10.39.172.45] ([205.248.100.252]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id pB5NsWVv016620 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 5 Dec 2011 15:54:37 -0800
Message-ID: <4EDD59AB.9030305@dcrocker.net>
Date: Mon, 05 Dec 2011 15:54:19 -0800
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: John Levine <johnl@iecc.com>
Subject: Re: Last Call: <draft-kucherawy-dkim-atps-11.txt> (DKIM Authorized Third-Party Signers) to Experimental RFC
References: <20111204212736.64731.qmail@joyce.lan>
In-Reply-To: <20111204212736.64731.qmail@joyce.lan>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 05 Dec 2011 15:54:37 -0800 (PST)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Mon, 05 Dec 2011 23:54:42 -0000

On 12/4/2011 1:27 PM, John Levine wrote:
> ADSP already dictates use of the From: domain.

The the nature ADSP's use of the From: domain is fundamentally different from 
ATPS' use.

Broadly, we can distinguish:

    Name extraction:    determining what name is being claimed

    Name verification:  determining that the use of the name is authorized

    Name assessment:    determining whether the name is associated with good
                        or bad actor.

ADSP adds a constraint on name verification; it mandates that at least one DKIM 
d= name match the domain in the From: field.

ATPS essentially modifies name extraction, by making it a two-step process. The 
first step is the usual one, with d=, for use with validation, but the second 
one takes the domain in the From: field and makes it the output string to the 
assessment process.


 > ATPS is a modification
> to ADSP.  It doesn't change anything that DKIM reports, only the rule
> for deciding whether ADSP finds an Author Domain Signature.

While yes it has text pertaining to ADSP, I will claim that with ADSP, too, the 
modification is in name extraction rather than validation or assessment.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net