Re: [apps-discuss] Stephen Farrell's No Objection on draft-ietf-appsawg-email-auth-codes-06: (with COMMENT)

"Murray S. Kucherawy" <superuser@gmail.com> Wed, 06 August 2014 23:55 UTC

Return-Path: <superuser@gmail.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D75F91A0358; Wed, 6 Aug 2014 16:55:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 fnt9hMeudhfs; Wed, 6 Aug 2014 16:55:11 -0700 (PDT)
Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B86BF1A0350; Wed, 6 Aug 2014 16:55:08 -0700 (PDT)
Received: by mail-wi0-f181.google.com with SMTP id bs8so4076327wib.2 for <multiple recipients>; Wed, 06 Aug 2014 16:55:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=r4jqdGcHt9oPvbns+yKT5+XRHNh0M840eBrI3pInat8=; b=i5Jw9IV5Qr8ZTFRzF78oJccL953GHU5kd848DMa8+Mj6Px6RfIbZSzeuLJp45xCMpt ElHyIwI28ix3QqT9XgITHO2YLU3Wo4mxd/ajGtHPK9Bzifczm29s0JDJmsW4IXQe7k67 J4q78YA10vcpeR/rVgFP8BK1By2RxOm2b+GBOCGZlINIhSDeukEEmt8QeiY4DzP95UND gdRjllc/MZMQf5WHcYea4TgzVlIkJGWLH8EKVg9eCIsc/LHRvO5HEKN2N+tdo4oYtb03 5lPOjRlTznDCd1Sq/j/f4Cdp5xfAFytx7wyFVJNWZxWs9U/SjDEGIDSGWTrn412Filjb zTvQ==
MIME-Version: 1.0
X-Received: by 10.180.81.234 with SMTP id d10mr20138034wiy.79.1407369306939; Wed, 06 Aug 2014 16:55:06 -0700 (PDT)
Received: by 10.180.10.99 with HTTP; Wed, 6 Aug 2014 16:55:06 -0700 (PDT)
In-Reply-To: <20140806215037.13299.94321.idtracker@ietfa.amsl.com>
References: <20140806215037.13299.94321.idtracker@ietfa.amsl.com>
Date: Wed, 06 Aug 2014 16:55:06 -0700
Message-ID: <CAL0qLwb-XexyOk4nQrP=a1JzXC8gh_+FyEcwTd3QkH4NreBDYQ@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: multipart/alternative; boundary="f46d044281349ba95004fffeb3e7"
Archived-At: http://mailarchive.ietf.org/arch/msg/apps-discuss/fGvEDMdbHkum0L-MVjV8OJvVS2E
Cc: "appsawg-chairs@tools.ietf.org" <appsawg-chairs@tools.ietf.org>, "draft-ietf-appsawg-email-auth-codes@tools.ietf.org" <draft-ietf-appsawg-email-auth-codes@tools.ietf.org>, The IESG <iesg@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>, SM <sm+ietf@elandsys.com>
Subject: Re: [apps-discuss] Stephen Farrell's No Objection on draft-ietf-appsawg-email-auth-codes-06: (with COMMENT)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss/>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Aug 2014 23:55:13 -0000

Hi Stephen,

On Wed, Aug 6, 2014 at 2:50 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie>
wrote:

> - Since only one code is returned and since the client has to
> assume that other failures may have happened in parallel, and
> since the X.7.20 code covers two different things (i.e. (a) and
> (b) from 3.1), did the wg consider splitting out 3.1's (a) and
> (b) into different codes?  That way the 3.1.a code would
> conform to 6376 and the 3.1.b code would be "failed my local
> DKIM specifics." Seems to me that splitting those out might be
> better but I'm fine if this was considered and rejected (i.e.
> no need to re-do the reason for rejecting, just tell me it
> happened and that'll be fine).
>

There haven't to my knowledge been any instances of wanting or needing to
report 3.1.a separately from 3.1.b, which is why they're rolled into the
same status code.  To date the only distinction of interest is between
what's covered by x.7.20 and x.7.21, namely the domain name alignment.  In
that sense all we're documenting here is a set of codes that match what the
industry has been doing since DKIM started achieving serious deployment.

-MSK