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

Barry Leiba <barryleiba@computer.org> Tue, 07 February 2017 18:53 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 7E9821295B1 for <ietfarch-ietf-dkim-archive@ietfa.amsl.com>; Tue, 7 Feb 2017 10:53:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.29
X-Spam-Level:
X-Spam-Status: No, score=-1.29 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_SORBS_SPAM=0.5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=gmail.com
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 XS6-G5lW-nA2 for <ietfarch-ietf-dkim-archive@ietfa.amsl.com>; Tue, 7 Feb 2017 10:53:38 -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 5CF64129428 for <ietf-dkim-archive@ietf.org>; Tue, 7 Feb 2017 10:53:38 -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 v17IsWsw013662; Tue, 7 Feb 2017 10:54:33 -0800
Authentication-Results: simon.songbird.com; dkim=fail reason="verification failed; unprotected key" header.d=gmail.com header.i=@gmail.com header.b=r7/5w+MJ; dkim-adsp=none (unprotected policy); dkim-atps=neutral
Received: from mail-qk0-f182.google.com (mail-qk0-f182.google.com [209.85.220.182]) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v17IsSN1013651 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT) for <ietf-dkim@mipassoc.org>; Tue, 7 Feb 2017 10:54:30 -0800
Received: by mail-qk0-f182.google.com with SMTP id 11so98086807qkl.3 for <ietf-dkim@mipassoc.org>; Tue, 07 Feb 2017 10:52:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=69WBeh+7bAHVcnNrGle69D3OMGcYK0pXSTIKyytHGmo=; b=r7/5w+MJIWSHBePHhflCgX5C+E3F6Z7IDbhhlAQgxy6TunH47mjL2FWNYtJS/pPEAJ BhkA3aEcKiVcWbKCx4f05pNSv4uIWn1x/XvLhxWi9HK4IVyV0qdRo22z2wttqI9Iyw3h qulZ8KpPY9KK/MiZwdScnzmDdyEre1noaYoAEQsrNwQK7+xaqJWFSSyhLn+ehf/vAJIh sWPR0aMr4DDpY4bt9CaRG9VLcMSVS2AJqqCskFXwZ0PeCRzpTcv3KiUjl/rk0j+dHfzv aWyugkQ21r4eFfoHLJMaY77lYjuLMrSYl4LRCkAsQ5AFBaWY56ONbQVPCOLZ3Op0nS9F s1+Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=69WBeh+7bAHVcnNrGle69D3OMGcYK0pXSTIKyytHGmo=; b=X0oAQAmZhYajGUwgV+C/2w3YsX19KSDGhuXlpqNosnEmyLC6s3vzDu4jLR1qtxEeo3 C0iO8MvXHUz37YO4meXD5QsIEN7OTkR7g4qYHNVAKvnaISQCMuonTjDRtQA8mEeIxMue rSFNavxyhCtnQw4nUC2jjp+DqmZpAe3QtYddALHSdRQauSgmKuSnS6cJ96ok24SpFR6N DGcBQcwIT/Qu+/0ImAKe80mbcJ8LazH0B/+4BmwZaHzrTGaVjjTR/vCGFl9DE4Qez5OF aYndfKNPLdgfWQvbG9p+FodqDC7/jIpJ8pVmeU6Xmb9Tc5k4WH5Qzxy3vlAxWPNG3SW6 8R9A==
X-Gm-Message-State: AMke39n6SwU+aZg6CbWuf4Q61UTSJJDTb5/bLwf0Bb0W66JiHTb7IpBGsd3CEA3IjDe8NHB2ugRo60EJhvBnCA==
X-Received: by 10.55.44.195 with SMTP id s186mr15888909qkh.151.1486493564518; Tue, 07 Feb 2017 10:52:44 -0800 (PST)
MIME-Version: 1.0
Received: by 10.140.19.72 with HTTP; Tue, 7 Feb 2017 10:52:44 -0800 (PST)
In-Reply-To: <84e6e9cd-738d-c642-5533-331113adb604@dcrocker.net>
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>
From: Barry Leiba <barryleiba@computer.org>
Date: Tue, 07 Feb 2017 10:52:44 -0800
X-Google-Sender-Auth: oIlA3G0VdJspI5tk50mMeSmQUSQ
Message-ID: <CALaySJ+4R8MUndC2n7GzMPqNQHb_OCbVPJi07FY2za2rWN-DTw@mail.gmail.com>
To: Dave Crocker <dcrocker@bbiw.net>
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-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: ietf-dkim-bounces@mipassoc.org
Sender: ietf-dkim <ietf-dkim-bounces@mipassoc.org>

> 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
"Reply-To" when it should have included "Subject" (that'd be a
technical error) and an example that includes "Sujbect" when it should
have included "Subject" (that'd be an editorial error)... even though
both of those errors might cause the signature not to verify.

I think an incorrect number of space characters is in the latter category.

Barry
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html