[Dcrup] Deprecating algorithms
"Murray S. Kucherawy" <superuser@gmail.com> Tue, 13 June 2017 13:45 UTC
Return-Path: <superuser@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 A533D13150D for <dcrup@ietfa.amsl.com>; Tue, 13 Jun 2017 06:45:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham 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 DeV-ec9gLAC5 for <dcrup@ietfa.amsl.com>; Tue, 13 Jun 2017 06:45:53 -0700 (PDT)
Received: from mail-vk0-x230.google.com (mail-vk0-x230.google.com [IPv6:2607:f8b0:400c:c05::230]) (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 B84031316D7 for <dcrup@ietf.org>; Tue, 13 Jun 2017 06:45:51 -0700 (PDT)
Received: by mail-vk0-x230.google.com with SMTP id p62so64384275vkp.0 for <dcrup@ietf.org>; Tue, 13 Jun 2017 06:45:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=xzktYTEybvr8ofBm5JiMEiE0H5G0Df6FW/vhODoU/Dc=; b=GBkNdAS+/MmrAWUVHJS2UwvtNLj0z14zSRLEkCZyCJNW0ilqjzmM9FVz/o+/g9WqBO llE2kNUQRvjHZCkV5ytniR5es4D235neX4I+AV+WtQNIqPGZWGZCFCfqgTvCPb4gA3XB hcRk7ojoQSo/9extE+Xk+DnU4FoKUA3GHsU3Ndp5frAbYd4lFzII4O+1piHP9DA0dxug wBbkeWGguIcReoGUknJX0UwxMRyAEqEFL6SREZw5LWBNhwTkhM3ZEm9hdtQl494ulycD HmPnaMV8S5iSNdybFD655MoVLXFUnOkR2LS3PCqdlgTQnoSGte37kMD2elyfZFOWv/Ad mB0A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=xzktYTEybvr8ofBm5JiMEiE0H5G0Df6FW/vhODoU/Dc=; b=dDlqRnUHUQYUjauGWwWSnWK+cBEAXJLTdmP7N8/8pUoc8LAtlta9zcRfdeFOQ574ZO SLPxlugY/8Q0f2YqTRWm7qOOjndh8Gjyf0V6vX2fkS9sKbrVfSUxT80cyox3CRRMcJm0 fuGJRWOWC9RYMt47EycRjodcPq8JFtQAnqL/4qsGPk4AZUGKlQXvoxNEcIToiKPs1Soj v3eDU3N7v6WITKRrLfpZ5E5LkW9sw5saEWbG4cXuxf11djXyBX2VZBZqeBMdjOjj7wf4 6YFW3ruZPrQxc9x8Uct1pLP2bG9afRBkV+7CM66f6vvMl8OPPTxmoKuEsJ6CMyCjpaPV 3aWg==
X-Gm-Message-State: AODbwcARwrPWsFG7q39MSqwxtLGEEKSa7+J6e5Sedafs32c2+zv+hJj+ LVcjqLMOfYCK+xi2vAebpyrfwJND54Kc
X-Received: by 10.31.3.100 with SMTP id 97mr27789577vkd.80.1497361550575; Tue, 13 Jun 2017 06:45:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.103.138.3 with HTTP; Tue, 13 Jun 2017 06:45:50 -0700 (PDT)
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Tue, 13 Jun 2017 06:45:50 -0700
Message-ID: <CAL0qLwZDpGeBgTGZfKLFKq8x7UQeExSUm0JeoHMx1EN-xUmswA@mail.gmail.com>
To: dcrup@ietf.org
Content-Type: multipart/alternative; boundary="001a11428ab2528c750551d7a744"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrup/GPP_SVp3x62aeR-N0l4sjahDU7Q>
Subject: [Dcrup] Deprecating algorithms
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: Tue, 13 Jun 2017 13:45:54 -0000
<chair> As a procedural matter, I looked at our charter and discovered that it doesn't explicitly allow us to deprecate "rsa-sha1". It only allows us to make new algorithms or ways to transport larger keys, and give revised advice about key sizes. For the sake of dotting and crossing everything I talked to Alexey and Eric and they don't imagine there would be a problem here, nor would it be a problem to adjust the charter accordingly. I'd prefer to have the charter tweaked so we're covered, and since doing so wouldn't interrupt our work flow, unless anyone objects I'm going to ask Alexey to start that process for us. </chair> -MSK
- [Dcrup] Deprecating algorithms Murray S. Kucherawy
- Re: [Dcrup] Deprecating algorithms Martin Thomson
- Re: [Dcrup] Deprecating algorithms Murray S. Kucherawy
- Re: [Dcrup] Deprecating algorithms Murray S. Kucherawy
- Re: [Dcrup] Deprecating algorithms Kurt Andersen