IETF Logo Mail Archive

Re: [Curdle] IETF time slot / next step for CURDLE

"Salz, Rich" <rsalz@akamai.com> Tue, 27 June 2017 16:20 UTC

Return-Path: <rsalz@akamai.com>
X-Original-To: curdle@ietfa.amsl.com
Delivered-To: curdle@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E39D129601 for <curdle@ietfa.amsl.com>; Tue, 27 Jun 2017 09:20:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.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 pHlgodRND_KA for <curdle@ietfa.amsl.com>; Tue, 27 Jun 2017 09:20:46 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::1]) (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 47DB4129B95 for <curdle@ietf.org>; Tue, 27 Jun 2017 09:20:44 -0700 (PDT)
Received: from pps.filterd (m0050102.ppops.net [127.0.0.1]) by m0050102.ppops.net-00190b01. (8.16.0.21/8.16.0.21) with SMTP id v5RGH92j004239; Tue, 27 Jun 2017 17:20:41 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-transfer-encoding : mime-version; s=jan2016.eng; bh=l06zPbGkWlv8HUlfF/nfFtMWiSIH8LKxuwutnWjdzUE=; b=j287qhcaKeP91XTxRsFTWv9nskY5tvIcHhvqzzKkZaLeKtSGmxaNIB976u1nIvhu+f93 UnvQdzhOhiP/QhOiz/UCD60679dbsXIq0DFd2ybDfJijr034WYb6SA5zxJe3BG46Z41n t202WAjWjdDbiSqYLKz/3vDcR4QrX1eeWMhOeUxOU6nDmt10jQtqkrGjKJuHK7Ojqx2g kNzlYHCtwVJEUvo+BNAEuLrKUXmxR4cXtTEsHFHy3NDOlYxRsL5hLno8j2t4zFqnFsJ8 w0uK+Tyc+doY1HFWtU7zebGIcIJtOyz3WbwhP6MzzK8yY4FgITBU0T3g4ASEezm2SxRq xg==
Received: from prod-mail-ppoint2 (a184-51-33-19.deploy.static.akamaitechnologies.com [184.51.33.19] (may be forged)) by m0050102.ppops.net-00190b01. with ESMTP id 2bbt3w883n-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 27 Jun 2017 17:20:41 +0100
Received: from pps.filterd (prod-mail-ppoint2.akamai.com [127.0.0.1]) by prod-mail-ppoint2.akamai.com (8.16.0.17/8.16.0.17) with SMTP id v5RGHKbk031062; Tue, 27 Jun 2017 12:20:40 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.31]) by prod-mail-ppoint2.akamai.com with ESMTP id 2b9kdv22g3-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 27 Jun 2017 12:20:40 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb2.msg.corp.akamai.com (172.27.123.102) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Tue, 27 Jun 2017 12:20:39 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([172.27.123.101]) by usma1ex-dag1mb1.msg.corp.akamai.com ([172.27.123.101]) with mapi id 15.00.1263.000; Tue, 27 Jun 2017 12:20:39 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: "Mark D. Baushke" <mdb@juniper.net>, Daniel Migault <daniel.migault@ericsson.com>
CC: "curdle@ietf.org" <curdle@ietf.org>
Thread-Topic: [Curdle] IETF time slot / next step for CURDLE
Thread-Index: AdLvQ0gS6mGD0VDZSnmHX/N5hNLS8wAFn41iAAHIdqA=
Date: Tue, 27 Jun 2017 16:20:39 +0000
Message-ID: <f28732ee6ded463aaee3f45d4943ed9a@usma1ex-dag1mb1.msg.corp.akamai.com>
References: <2DD56D786E600F45AC6BDE7DA4E8A8C118C878F5@eusaamb107.ericsson.se> <99335.1498577163@eng-mail01.juniper.net>
In-Reply-To: <99335.1498577163@eng-mail01.juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.32.114]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-06-27_09:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1706270262
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-06-27_09:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1706270262
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/EIPl_IvAgZ97Qalt-o59wP7D1pg>
Subject: Re: [Curdle] IETF time slot / next step for CURDLE
X-BeenThere: curdle@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "List for discussion of potential new security area wg." <curdle.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/curdle>, <mailto:curdle-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/curdle/>
List-Post: <mailto:curdle@ietf.org>
List-Help: <mailto:curdle-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/curdle>, <mailto:curdle-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jun 2017 16:20:50 -0000

> There are a number of expired and dead drafts that should probbly be
> finished (ssh-ed25519, dnskey-ed25519, pkix-eddsa, pkix-newcurves).

Yes, probably.


> I think some work on a better way to create Diffie-Hellman primes may also
> be good to consider.

This might be a good thing to do, but I'd really prefer we create a new WG for it.  This one definitely has the history of "don't create, just update algorithms to use what was already specified."  I think that's a big change in mindset, and perhaps the participants, so I think a new group is better.

> To be fair, this group may also want to start looking at Post-Qutanum-
> Cryptographic

Same answer, same reason :)

v2.23.0 | Report a Bug | By Email