Re: [ietf-dkim] [Technical Errata Reported] RFC6376 (4926)

Dave Crocker <dcrocker@bbiw.net> Tue, 07 February 2017 18:56 UTC

Return-Path: <ietf-dkim-bounces@mipassoc.org>
X-Original-To: ietfarch-ietf-dkim-archive@ietfa.amsl.com
Delivered-To: ietfarch-ietf-dkim-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82C2F129404 for <ietfarch-ietf-dkim-archive@ietfa.amsl.com>; Tue, 7 Feb 2017 10:56:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bbiw.net header.b=FbIvv9iH; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=bbiw.net header.b=dtKbp4HV
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 Qab90p_0dP8k for <ietfarch-ietf-dkim-archive@ietfa.amsl.com>; Tue, 7 Feb 2017 10:56:21 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3BDE41293D8 for <ietf-dkim-archive@ietf.org>; Tue, 7 Feb 2017 10:56:21 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com [127.0.0.1]) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v17Iv8Uo013719; Tue, 7 Feb 2017 10:57:09 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=bbiw.net; s=default; t=1486493829; bh=0jv1PXWEE0fvN1DJw/zaR3E71+B5YI5NFwY8hLP/ylc=; h=To:References:From:Date:In-Reply-To:Cc:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=FbIvv9iH4mJb1FLn3k0gBHEPNZjS7ixWlDVqLJnwos6cvOmhKwWCUbGTL5KnkKaPP 1wpknOjbpvUKm/zbIiuL1nlxcmkTAkBAGR85ZAKZe1T+HH9HFXPhxIP1lPzKtM6mmt 3a+4PohiiEpkMCoVHDd9PSGUaGSszz9cbD7wrXYU=
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v17Iv5DJ013705 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 7 Feb 2017 10:57:05 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=bbiw.net; s=default; t=1486493826; bh=rJVgojIh+J2DkXx35m3ux6MpilXPwgbEAvUu5+zpvvY=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=dtKbp4HV/r61EsnySmhDmXrGRN1DU6XLQchBRTgU7i3XB7zhvFebg35bv3rUD7FV1 WJgJTk7i+QPrAetyxezs2mWxNhB9j6n2vh7lezvMWN2pQ8vKTrgnYvZijrZ4TB6m0G iJGab36AiTs/6D6OHpEmnnvcUHVztjZ8guwbxq9c=
To: Barry Leiba <barryleiba@computer.org>
References: <CALaySJJ8QvWp=QChL9Pvt5ytySpeRnU1y4xaXAiRD9vi4M+oZg@mail.gmail.com> <20170207181909.9946.qmail@ary.lan> <CALaySJKWvg+92jSk25OvMR1J9vBqtsSgp+VUTw+KuYDY+zJS=g@mail.gmail.com> <84e6e9cd-738d-c642-5533-331113adb604@dcrocker.net> <CALaySJ+4R8MUndC2n7GzMPqNQHb_OCbVPJi07FY2za2rWN-DTw@mail.gmail.com>
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
Message-ID: <d24d889c-ecb9-8163-f3f0-58431ee9ec68@bbiw.net>
Date: Tue, 07 Feb 2017 10:55:17 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <CALaySJ+4R8MUndC2n7GzMPqNQHb_OCbVPJi07FY2za2rWN-DTw@mail.gmail.com>
Cc: John Levine <johnl@taugh.com>, DKIM Mailing List <ietf-dkim@mipassoc.org>
Subject: Re: [ietf-dkim] [Technical Errata Reported] RFC6376 (4926)
X-BeenThere: ietf-dkim@mipassoc.org
X-Mailman-Version: 2.1.16
Precedence: list
List-Id: IETF DKIM Discussion List <ietf-dkim.mipassoc.org>
List-Unsubscribe: <http://mipassoc.org/mailman/options/ietf-dkim>, <mailto:ietf-dkim-request@mipassoc.org?subject=unsubscribe>
List-Archive: <http://mipassoc.org/pipermail/ietf-dkim/>
List-Post: <mailto:ietf-dkim@mipassoc.org>
List-Help: <mailto:ietf-dkim-request@mipassoc.org?subject=help>
List-Subscribe: <http://mipassoc.org/mailman/listinfo/ietf-dkim>, <mailto:ietf-dkim-request@mipassoc.org?subject=subscribe>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: ietf-dkim-bounces@mipassoc.org
Sender: ietf-dkim <ietf-dkim-bounces@mipassoc.org>

On 2/7/2017 10:52 AM, Barry Leiba wrote:
>> I suspect that "says something technically wrong" is meant to constrain
>> things to the specification content, but that's not what the RFC-Editor
>> definition says, nor is it clear to me that it should be that constrained.
>
> I agree.  I think it mostly should, but that there should be judgment involved.
>
>> The current error has technical import, since we are talking about a broken
>> validation.
>>
>> So, I'm not at all clear that this qualifies as only an 'Editorial' error.
>
> I don't see it that way.
> I think there's a difference between an example that includes

So, I think I understand that view, which is why I said "ambiguous".

And the only reason I'm pursuing it, here, is that I think the 
determination of an erratum should not be so subjective.  I think the 
RFC Editor language defining categories should have criteria that are 
considerably more crisp.


d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html