Re: [apps-discuss] Pete Resnick's Discuss on draft-ietf-appsawg-email-auth-codes-05: (with DISCUSS)

Terry Zink <tzink@exchange.microsoft.com> Tue, 05 August 2014 16:35 UTC

Return-Path: <tzink@exchange.microsoft.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 824371A0030; Tue, 5 Aug 2014 09:35:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_PASS=-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 evBWsB94wbZd; Tue, 5 Aug 2014 09:35:45 -0700 (PDT)
Received: from na01-by1-obe.outbound.o365filtering.com (na01-by1-obe.ptr.o365filtering.com [64.4.22.91]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B7EB1A0364; Tue, 5 Aug 2014 09:35:45 -0700 (PDT)
Received: from BL2SR01MB605.namsdf01.sdf.exchangelabs.com (10.255.109.167) by BL2SR01MB604.namsdf01.sdf.exchangelabs.com (10.255.109.166) with Microsoft SMTP Server (TLS) id 15.0.1015.2; Tue, 5 Aug 2014 16:35:42 +0000
Received: from BL2SR01MB605.namsdf01.sdf.exchangelabs.com ([169.254.12.93]) by BL2SR01MB605.namsdf01.sdf.exchangelabs.com ([169.254.12.93]) with mapi id 15.00.1015.001; Tue, 5 Aug 2014 16:35:41 +0000
From: Terry Zink <tzink@exchange.microsoft.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Thread-Topic: [apps-discuss] Pete Resnick's Discuss on draft-ietf-appsawg-email-auth-codes-05: (with DISCUSS)
Thread-Index: AQHPsE2DCDw8SU69OUKUwt2HkK0ZPpvBUJeAgAAX5ACAAACUAIAAASuAgADKfJA=
Date: Tue, 05 Aug 2014 16:35:41 +0000
Message-ID: <456751dd3cce4deca23c50210f4eb72c@BL2SR01MB605.namsdf01.sdf.exchangelabs.com>
References: <20140805013510.3778.62099.idtracker@ietfa.amsl.com> <CAL0qLwby0q+VQOKYgJigXw4J1jheBgOqODY48m-VocuYKSfM5g@mail.gmail.com> <53E05B7A.5060308@qti.qualcomm.com> <CAL0qLwaTffcOiXMpCybuzX-j01VgxczS7PSmKbNtOGtSgVYdiQ@mail.gmail.com> <53E05CF1.9000102@qti.qualcomm.com>
In-Reply-To: <53E05CF1.9000102@qti.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [131.107.192.108]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;UriScan:;
x-forefront-prvs: 02945962BD
x-forefront-antispam-report: SFV:NSPM; SFS:(10009001)(377454003)(479174003)(199002)(189002)(52044002)(52604005)(50944004)(24454002)(76482001)(106116001)(1411001)(105586002)(50986999)(54356999)(76176999)(66066001)(46102001)(80022001)(106356001)(16236675004)(21056001)(93886004)(85306004)(74662001)(85852003)(74502001)(31966008)(83322001)(83072002)(19580405001)(19580395003)(92566001)(19625215002)(19300405004)(99396002)(77982001)(15202345003)(87936001)(79102001)(101416001)(15975445006)(2656002)(4396001)(33646002)(81542001)(107046002)(19617315012)(64706001)(110136001)(20776003)(81342001)(24736002)(108616003); DIR:OUT; SFP:1101; SCL:1; SRVR:BL2SR01MB604; H:BL2SR01MB605.namsdf01.sdf.exchangelabs.com; FPR:; PTR:InfoNoRecords; MX:1; LANG:en;
Content-Type: multipart/alternative; boundary="_000_456751dd3cce4deca23c50210f4eb72cBL2SR01MB605namsdf01sdf_"
MIME-Version: 1.0
X-OriginatorOrg: exchange.microsoft.com
Archived-At: http://mailarchive.ietf.org/arch/msg/apps-discuss/SnYsIMjYRDKKm-U38OVWmBWQXak
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>
Subject: Re: [apps-discuss] Pete Resnick's Discuss on draft-ietf-appsawg-email-auth-codes-05: (with DISCUSS)
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: Tue, 05 Aug 2014 16:35:49 -0000

This is a style nitpick and you can feel free to ignore. I have one complaint/suggestion regarding this text:

Description:       This status code is returned when a message
                          did not contain any acceptable DKIM
                          signatures.  (Note that this violates the
                          advice of Section 6.1 of RFC6376.)

Description:       This status code is returned when a message
                          did not contain any acceptable DKIM
                          signatures whose identifier(s) match the
                          author address(es) found in the From header
                          field.  (Note that this violates the advice
                          of Section 6.1 of RFC6376.)  This is a
                          special case of the X.7.20 status code.

The first two words of the phrases "Note that this violates the advice..." is redundant and superfluous [1]. In writing, if you have something to note, then note it; don't say "Note that..." In other words, I propose the shorter text "This violates the advice...".

-- Terry

[1] Note that the words "and superfluous" is redundant in that sentence.


From: apps-discuss [mailto:apps-discuss-bounces@ietf.org] On Behalf Of Pete Resnick
Sent: Monday, August 4, 2014 9:26 PM
To: Murray S. Kucherawy
Cc: appsawg-chairs@tools.ietf.org; draft-ietf-appsawg-email-auth-codes@tools.ietf.org; The IESG; IETF Apps Discuss
Subject: Re: [apps-discuss] Pete Resnick's Discuss on draft-ietf-appsawg-email-auth-codes-05: (with DISCUSS)

On 8/4/14 11:22 PM, Murray S. Kucherawy wrote:
On Mon, Aug 4, 2014 at 9:20 PM, Pete Resnick <presnick@qti.qualcomm.com<mailto:presnick@qti.qualcomm.com>> wrote:

Aha. That wasn't clear to me from the current text. I took "valid" to only be referring to passing the basic DKIM verification algorithms. I didn't realize that not passing local policies was a reason to send back X.7.20. Perhaps you could clarify the text?

How's this for a new Section 3.1?

Much clearer. I'll remove my DISCUSS in the morning, unless Barry wants me to leave it for housekeeping purposes; I'll assume that you all can decide on the specifics. Thanks for DISCUSSing it.

pr


3.1.  DKIM Failure Codes

   In the code point definitions below, the term "acceptable" means both
   of the following:

   a.  The signature passed the basic DKIM verification algorithm as
       defined in [RFC6376]; and

   b.  The signature satisfied any local policy requirements in addition
       to the basic algorithm (e.g., certain header fields included in
       the signed content, no partial signatures, etc.).

      Code:               X.7.20
      Sample Text:        No valid DKIM signature found
      Associated basic status code:  550
      Description:        This status code is returned when a message
                          did not contain any acceptable DKIM
                          signatures.  (Note that this violates the
                          advice of Section 6.1 of RFC6376.)
      Reference:          [this document]; RFC6376
      Submitter:          M. Kucherawy
      Change controller:  IESG


      Code:               X.7.21
      Sample Text:        No valid author-matched DKIM signature found
      Associated basic status code:  550
      Description:        This status code is returned when a message
                          did not contain any acceptable DKIM
                          signatures whose identifier(s) match the
                          author address(es) found in the From header
                          field.  (Note that this violates the advice
                          of Section 6.1 of RFC6376.)  This is a
                          special case of the X.7.20 status code.
      Reference:          [this document]; RFC6376
      Submitter:          M. Kucherawy
      Change controller:  IESG






_______________________________________________

apps-discuss mailing list

apps-discuss@ietf.org<mailto:apps-discuss@ietf.org>

https://www.ietf.org/mailman/listinfo/apps-discuss





--

Pete Resnick <http://www.qualcomm.com/~presnick/><http://www.qualcomm.com/~presnick/>

Qualcomm Technologies, Inc. - +1 (858)651-4478