Re: [spfbis] [Technical Errata Reported] RFC7208 (4082)

Barry Leiba <barryleiba@computer.org> Thu, 14 August 2014 13:30 UTC

Return-Path: <barryleiba@gmail.com>
X-Original-To: spfbis@ietfa.amsl.com
Delivered-To: spfbis@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C5771A0408 for <spfbis@ietfa.amsl.com>; Thu, 14 Aug 2014 06:30:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 XQ_BxLHja5th for <spfbis@ietfa.amsl.com>; Thu, 14 Aug 2014 06:30:09 -0700 (PDT)
Received: from mail-la0-x231.google.com (mail-la0-x231.google.com [IPv6:2a00:1450:4010:c03::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 24A6F1A061D for <spfbis@ietf.org>; Thu, 14 Aug 2014 06:30:08 -0700 (PDT)
Received: by mail-la0-f49.google.com with SMTP id hz20so1025999lab.22 for <spfbis@ietf.org>; Thu, 14 Aug 2014 06:30:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=j6D3WUU7XI3VIClaCPIGJGoOZE+bivqu7WavbrY1X6I=; b=BZK84DLOual2VSTJTRPBaiqF0X0p81TR4FoxaehPbtqd3VItgVffYng91EpC2uSqWX sMevjnAZwmuVV+GWlQFbZu/vKyXUES0Ouavb7nc6u681s+j2cSf+0GRcy1deOjPNIsth 4lfCVDM35nXWugMi9thDBNq9Xk/ERDlUgKpGCabZFvIra3apgWVZKrHIIXT49NFdyomJ fIyKv/zHLOFMwDQYNAz0vaZyxJUnU0p+4rpDEfYV1QtjsxHN06R4f7aBvi7AUcUDdTBQ J0Jb337a7d8X7QFbUktUtfmfJbsYY0Cb1ZFwU+aWp+kO+5EkcejXsScM2GjHJhHQG/Tz ZEGQ==
MIME-Version: 1.0
X-Received: by 10.112.8.99 with SMTP id q3mr4982902lba.85.1408023007050; Thu, 14 Aug 2014 06:30:07 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.152.8.46 with HTTP; Thu, 14 Aug 2014 06:30:06 -0700 (PDT)
In-Reply-To: <bf1f1586-c2a1-4e87-8365-c8cf7be0bfe1@email.android.com>
References: <20140813231306.9680818000E@rfc-editor.org> <bf1f1586-c2a1-4e87-8365-c8cf7be0bfe1@email.android.com>
Date: Thu, 14 Aug 2014 09:30:06 -0400
X-Google-Sender-Auth: JLxSfSRZnoT1VpGhakiL0Dc2z7Y
Message-ID: <CALaySJK4U1fJUwMs93Sq=F8zgVehRetYP0+A2wNP9V0ydk3AcQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Scott Kitterman <scott@kitterman.com>
Content-Type: multipart/alternative; boundary="001a1134d1142bc62a050096e7b8"
Archived-At: http://mailarchive.ietf.org/arch/msg/spfbis/ZRdd8Jk0WOQLTx8kCkK2O_c1NEo
Cc: "presnick@qti.qualcomm.com" <presnick@qti.qualcomm.com>, "sm+ietf@elandsys.com" <sm+ietf@elandsys.com>, "ajs@anvilwalrusden.com" <ajs@anvilwalrusden.com>, "spfbis@ietf.org" <spfbis@ietf.org>, "d.stussy@yahoo.com" <d.stussy@yahoo.com>, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [spfbis] [Technical Errata Reported] RFC7208 (4082)
X-BeenThere: spfbis@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SPFbis discussion list <spfbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spfbis>, <mailto:spfbis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spfbis/>
List-Post: <mailto:spfbis@ietf.org>
List-Help: <mailto:spfbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spfbis>, <mailto:spfbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Aug 2014 13:30:11 -0000

Personally, I think 5.7.1 is the right code, until the email-auth-codes
draft (which is in the RFC Editor queue) pops out.  5.5.2 seems wrong to
me, as well.

That said, it's quite clear that what's in the document is what the working
group intended, and it's not a valid errata report.  I will mark it
Rejected.

Barry

On Wednesday, August 13, 2014, Scott Kitterman <scott@kitterman.com> wrote:

> 5.7.8 talks about things like incorrect password issues. That's not the
> kind of authentication at work for SPF. SPF is more strictly about
> authorization, not authentication.
>
> This should be rejected.
>
> Scott K
>
> On August 13, 2014 7:13:06 PM EDT, RFC Errata System <
> rfc-editor@rfc-editor.org
> <javascript:_e(%7B%7D,'cvml','rfc-editor@rfc-editor.org');>> wrote:
>>
>> The following errata report has been submitted for RFC7208,
>> "Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1".
>>
>> ------------------------------
>>
>> You may review the report below and at:
>> http://www.rfc-editor.org/errata_search.php?rfc=7208&eid=4082
>>
>> ------------------------------
>>
>> Type: Technical
>> Reported by: D. Stussy <d.stussy@yahoo.com <javascript:_e(%7B%7D,'cvml','d.stussy@yahoo.com');>>
>>
>> Section: 8.7
>>
>> Original Text
>> -------------
>> ...  If the message is rejected during the SMTP transaction for
>> this reason, the software SHOULD use an SMTP reply code of 550
>> and, if supported, the 5.5.2 enhanced status code ...
>>
>> Corrected Text
>> --------------
>> ...  If the message is rejected during the SMTP transaction for
>> this reason, the software SHOULD use an SMTP reply code of 550
>> and, if supported, the 5.7.8 enhanced status code ...
>> Notes
>> -----
>> 5.5.2 refers to responses where there's an SMTP COMMAND syntax error.
>> 5.7.8 refers to messages where authentication credentials are invalid.
>>
>> 5.7.8 is a better description for rejecting an unauthorized message due to the
>> application of invalid authentication credentials such as bad syntax in an SPF DNS record.
>>
>> The author of this errata notes that the IANA is showing a pending addition to
>> the enhanced codes to add SPF-specific error code 5.7.24 (in lieu of 5.5.2 or
>> 5.7.8), but currently sees no valid RFC proposing it.  The draft is located at:
>> http://tools.ietf.org/html/draft-ietf-appsawg-email-auth-codes-07
>>
>> The use of 5.5.2 here is misleading since the source of the error is not the
>> SMTP command stream.
>>
>> Instructions:
>> -------------
>> This erratum is currently posted as "Reported". If necessary,
>> please
>> use "Reply All" to discuss whether it should be verified or
>> rejected. When a decision is reached, the verifying party (IESG)
>> can log in to change the status and edit the report, if necessary.
>>
>> ------------------------------
>>
>> RFC7208 (draft-ietf-spfbis-4408bis-21)
>> ------------------------------
>>
>> Title               : Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1
>> Publication Date    : April 2014
>> Author(s)           : S. Kitterman
>> Category            : PROPOSED STANDARD
>> Source              : SPF Update
>> Area                : Applications
>> Stream              : IETF
>> Verifying Party     : IESG
>>
>>
>>