IETF Logo Mail Archive

Re: [Dcrup] stronger crypto, I-D Action: draft-ietf-dcrup-dkim-usage-02.txt

Phillip Hallam-Baker <phill@hallambaker.com> Wed, 14 June 2017 02:41 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: dcrup@ietfa.amsl.com
Delivered-To: dcrup@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA625129AF6 for <dcrup@ietfa.amsl.com>; Tue, 13 Jun 2017 19:41:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level:
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) 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 nV4jVk0Om7yq for <dcrup@ietfa.amsl.com>; Tue, 13 Jun 2017 19:41:31 -0700 (PDT)
Received: from mail-qt0-x231.google.com (mail-qt0-x231.google.com [IPv6:2607:f8b0:400d:c0d::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85024129AE9 for <dcrup@ietf.org>; Tue, 13 Jun 2017 19:41:31 -0700 (PDT)
Received: by mail-qt0-x231.google.com with SMTP id c10so194706209qtd.1 for <dcrup@ietf.org>; Tue, 13 Jun 2017 19:41:31 -0700 (PDT)
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=93j7L85JEVIdEX9nrmngWfMeDil+ysoQQBu4i2RvfoY=; b=RhEIaoPt+GSvt/J/AZ9BuAJG/Vq8XWUOGprdcUmp8ipBkEi+hPIWemcXC3ML5ksBkB DoRZFxz/reTpBZQlf1jIZWY8EfG1fswmfP5DFg2kR091kI6PMzTYZr9JSzAg32US41g0 4dbUUGoOv8t/+IKZS9O11pJ5ib5HRDI2AGVqy/U5/vhb5xwGcQPXLXgqNiIIxkwr/JLP 3Qz6xEe2WgzoshamBMGCvhd4ubJ9jL2+tKioB0eJyG81zPJgtfIbWH/oC49jIEjS8Mdl 17DpN+eOPZ9/zHwjQ/nEwKjQSwvIMZZxA/J6ZT5UQi/r0b9u9SorpnV8MqKUVx/VnekE V/dQ==
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=93j7L85JEVIdEX9nrmngWfMeDil+ysoQQBu4i2RvfoY=; b=dvGD9Op2Wypxx+TqeTvZYnOdDSRAerKtW3Wr1H8k3P5WOUm+Flyc2uJ0+XpK1lLwUd Cd+WlJ+bIbqta0EboVQl4GesxMMkBdvs9co1uZIKFfNtcW+1yFFV5jv3dAH7U4tHd0tA qu2+6xyueBN99HTTcyf5eq+UaaxhDYlw7TvHHRuLxozvwyvCL9rEyTjyM1UqWCfIilzv cLoZDdbTCda/Wjti1xUcEDU8fUFH5EM1u3LClGgRccm6YPUkLjHbNXXXQffrbpqOAOMl raaLS28Iq3G/uWu1LaGU4rGjjN4fjI0IECJ+3mFwmN0SnxX15EP/K5QYxMAqAcnLOwHz NOqw==
X-Gm-Message-State: AKS2vOwACx1LeKKtr7I+PHPgh6PhjN1Kh6PMXUnOdeboDszY85VDJNfU t/Px9ZHd6rpadUkOHIUXcv3+fDKXTg==
X-Received: by 10.200.2.79 with SMTP id o15mr4286333qtg.26.1497408090776; Tue, 13 Jun 2017 19:41:30 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.140.19.200 with HTTP; Tue, 13 Jun 2017 19:41:29 -0700 (PDT)
In-Reply-To: <CABcZeBO_RanavMmMEmw3XjC5Kuj8cLFki3WbxcqkheDM45fozg@mail.gmail.com>
References: <CABkgnnXAVni8Xgms2snX9LrGRd+xKuyt8VTU_XmXgh4ksBqHEw@mail.gmail.com> <20170611231340.17586.qmail@ary.lan> <CABkgnnUxsWUwiKvee7ngFNv5jz8==c1mAJpJYD3eD5VMKZqntQ@mail.gmail.com> <alpine.OSX.2.21.1706121039140.19565@ary.local> <CABcZeBO_RanavMmMEmw3XjC5Kuj8cLFki3WbxcqkheDM45fozg@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Tue, 13 Jun 2017 22:41:29 -0400
X-Google-Sender-Auth: pFS6-TX0HDAVoQ8JYbJsuTV2TtM
Message-ID: <CAMm+LwiKmeJ75wFUDzaO114WUbvbZfBdGbPuD8zcefmfBzA8rA@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
Cc: John R Levine <johnl@taugh.com>, dcrup@ietf.org, Martin Thomson <martin.thomson@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/f7LR09aIDbShnFeDh7mFXWb-IdU>
Subject: Re: [Dcrup] stronger crypto, I-D Action: draft-ietf-dcrup-dkim-usage-02.txt
X-BeenThere: dcrup@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: DKIM Crypto Update <dcrup.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dcrup>, <mailto:dcrup-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dcrup/>
List-Post: <mailto:dcrup@ietf.org>
List-Help: <mailto:dcrup-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dcrup>, <mailto:dcrup-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Jun 2017 02:41:33 -0000

On Mon, Jun 12, 2017 at 5:49 AM, Eric Rescorla <ekr@rtfm.com> wrote:

> You can bikeshed on anything, but I don't see how this is actually a
> particular problem,
> given that you can pin the hash to the signature algorithm, as we do with
> elliptic curves.

As a process matter. Could we not use the term 'bikeshed' when
referring to contributions?

I am completely serious about this. I have seen the term used by
certain individuals to essentially trash someone's contribution and
then gaslight them. It really does get used as a form of harassment in
IETF.

Basically what I hear is, 'this is an unimportant issue so we are
going to do it my way and I can't be bothered to enter into
discussions on the topic because your work on the issue is utterly
insignificant'.


Choice of identifiers is an important consideration in any protocol.
In fact it is pretty much the only decision to make most of the time.

Wanting to do a job properly is not 'bikeshedding'.

v2.29.0 | Report a Bug | By Email | System Status