IETF Logo Mail Archive

Re: [ietf-dkim] Where is the formal definition of DKIM-Signature?

"Murray S. Kucherawy" <superuser@gmail.com> Thu, 08 February 2018 15:09 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 D143212D955 for <ietfarch-ietf-dkim-archive@ietfa.amsl.com>; Thu, 8 Feb 2018 07:09:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.587
X-Spam-Level:
X-Spam-Status: No, score=-1.587 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 EXuD0wanqwOL for <ietfarch-ietf-dkim-archive@ietfa.amsl.com>; Thu, 8 Feb 2018 07:09:35 -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 66D33129C6C for <ietf-dkim-archive@ietf.org>; Thu, 8 Feb 2018 07:09:35 -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 w18F7t8W028659; Thu, 8 Feb 2018 07:07:56 -0800
Authentication-Results: simon.songbird.com; dkim=fail reason="verification failed; unprotected key" header.d=gmail.com header.i=@gmail.com header.b=IFN7u+9Z; dkim-adsp=none (unprotected policy); dkim-atps=neutral
Received: from mail-lf0-f52.google.com (mail-lf0-f52.google.com [209.85.215.52]) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id w18F7q8q028650 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT) for <ietf-dkim@mipassoc.org>; Thu, 8 Feb 2018 07:07:54 -0800
Received: by mail-lf0-f52.google.com with SMTP id q194so6822122lfe.13 for <ietf-dkim@mipassoc.org>; Thu, 08 Feb 2018 07:06:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=u32Gmfxu+p0INnLK5DaOCEEqlvUcxyGh0humNu+pmfM=; b=IFN7u+9ZTmSzrKJlw4tt1kvWsl/NFtv6HsqYET4v60d5RAyiSCsOXgM+ZeAJgyuOml GDbq7yo9hFuahkDMs3C1YChIxpygM6eUe/F5PkfQtGBgFT2mUEZEcd39lpnQi/GTQBLY FN5m6Fz8FM81BqbnXuD5sgpUSrpZAYJjtVF+IYv30/kMUXrDEX4jwGuY+uXs0Eeutnh0 zwR3pbnxo7lD+Od20WgLwHxMGUeyI9NaAOU0rUSkIfdLGjf/eVKu6Or4ejaRv0kvg+du 987RjqZOarBiq5u54ZeAg3+4fZ9pkhkr6l78E4W8RQfe5JdvPcLrInMzRS8hvOGZHCSy 5tOw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=u32Gmfxu+p0INnLK5DaOCEEqlvUcxyGh0humNu+pmfM=; b=XmjIxWS662hzpSSIe9sZfNOZl50rQcGx/XdjCcowY7CIggaefpmAtuFN8D6xNXnqjv TCki1VCNRRdh/GDKiaahixGgTUahAEcuOlMSZUjIAUQSwBmErjobY7/CwFN7+mR/h4QS Ilmz981ldMm+ArACeNuqwvTaWDtA+8hBMU4WMtAOF/hTdfwrOXFGJPJswQEsnl5AkKM9 cIpkJ7gahVkBYnDlUbgvjrPfMIeGiUbCERaocrKrTWOCZDVYUVIkRIjKDUiIBd/AOtwo gbV9BsOAI8CuRO0SyptU/7rZB8/WwgnJ9Ki3fQ3NK6Zv3/VIL+1SViYGim59DTfumt/D 4hgQ==
X-Gm-Message-State: APf1xPDkBjNMHw3HIZkcO/zXAo6uJkyLp37aAtOmAHQ4wWBqn7yn8BaH WadTe97QsW95tDyONtvEzeakcsUs7tTxVLbNhCM=
X-Google-Smtp-Source: AH8x224wR7L+65Fp1LeAquIsL/kDbkpcqhaDsQduusonoSwIpc2boVdLDokU9nPuh/ykAwcqU9xac3aVc+6WMhfiXRU=
X-Received: by 10.25.74.87 with SMTP id x84mr795178lfa.109.1518102408394; Thu, 08 Feb 2018 07:06:48 -0800 (PST)
MIME-Version: 1.0
Received: by 10.46.66.79 with HTTP; Thu, 8 Feb 2018 07:06:47 -0800 (PST)
In-Reply-To: <alpine.OSX.2.21.1802080808160.51311@ary.qy>
References: <9e7d6a29-cbef-e032-4af9-eb5395071b4d@tana.it> <alpine.OSX.2.21.1802080808160.51311@ary.qy>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Thu, 08 Feb 2018 07:06:47 -0800
Message-ID: <CAL0qLwYZPRdrg-J5KMreS==SUcnAU1pZXwgFURs5T3=XaX4HOg@mail.gmail.com>
To: "John R. Levine" <johnl@iecc.com>
Cc: DKIM List <ietf-dkim@mipassoc.org>, Alessandro Vesely <vesely@tana.it>
Subject: Re: [ietf-dkim] Where is the formal definition of DKIM-Signature?
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: multipart/mixed; boundary="===============3350104503518046182=="
Errors-To: ietf-dkim-bounces@mipassoc.org
Sender: ietf-dkim <ietf-dkim-bounces@mipassoc.org>

On Thu, Feb 8, 2018 at 5:22 AM, John R. Levine <johnl@iecc.com> wrote:

> someone asked me about case sensitiveness of the header field name.  I
>> looked
>> for an ABNF in RFC6376, but only found examples and informative notes.
>>
>
> I was going to say that can't possibly be true, but it's true, there's no
> ABNF for the header.  So, for example, I don't know whether the v= field
> has to come first.  Send an erratum, we'll probably accept it as hold for
> update.
>

"v=1" doesn't have to come first.  It just usually does.  I think there was
a version of RFC4871 that did that, but then when challenged we couldn't
come up with a good reason to keep it that way.

-MSK

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

v2.23.0 | Report a Bug | By Email