IETF Logo Mail Archive

Re: [lamps] Problems with the current ALGORITHM information object class

"Salz, Rich" <rsalz@akamai.com> Tue, 12 May 2020 16:22 UTC

Return-Path: <rsalz@akamai.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E4F33A00C1 for <spasm@ietfa.amsl.com>; Tue, 12 May 2020 09:22:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.271
X-Spam-Level:
X-Spam-Status: No, score=-2.271 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.173, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 GsdTEhtOq8Sj for <spasm@ietfa.amsl.com>; Tue, 12 May 2020 09:22:41 -0700 (PDT)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::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 CF4EA3A00C0 for <spasm@ietf.org>; Tue, 12 May 2020 09:22:41 -0700 (PDT)
Received: from pps.filterd (m0050095.ppops.net [127.0.0.1]) by m0050095.ppops.net-00190b01. (8.16.0.42/8.16.0.42) with SMTP id 04CGM27a032616; Tue, 12 May 2020 17:22:40 +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 : mime-version; s=jan2016.eng; bh=j9WTJsaXp8V8ZIQGgpgTHddPqTo0giTSP0hfAkCLA54=; b=IwBNP8vW6wYIjrKscub6eFWXKfNeuMYtkkQnj0kqvt2j3R3e27F2VkkTy7HAWTK/LcsY AtobKl87+y1ODwwF/+WUgRnGl0/AcRyuiMLIYDUwlPlxdz8CD7EuZ63g/+MzLpFN86VN 2YsAvDqFAdQWqAFvZ90ndzkCIOcdAMm4wQYgQfnQAhHlIvn6fOXMZMLxbJ2JQ07hUV9q bXAptgFePlikNT5z3rWVyFOH8yO82ULjq6P9A1dbznPlneAO9aosISqETpN2pH/9pbuh 5SMv6aScNwYdlT2a1PG+fZV4cDWrlD4XydbtwukELjM0a3eKWBVfGSr+JQAGa3MqX8W5 Eg==
Received: from prod-mail-ppoint5 (prod-mail-ppoint5.akamai.com [184.51.33.60] (may be forged)) by m0050095.ppops.net-00190b01. with ESMTP id 30y2dfu4ts-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 12 May 2020 17:22:40 +0100
Received: from pps.filterd (prod-mail-ppoint5.akamai.com [127.0.0.1]) by prod-mail-ppoint5.akamai.com (8.16.0.27/8.16.0.27) with SMTP id 04CGI9Kx001752; Tue, 12 May 2020 09:22:38 -0700
Received: from email.msg.corp.akamai.com ([172.27.165.117]) by prod-mail-ppoint5.akamai.com with ESMTP id 30wtg8ha2g-9 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 12 May 2020 09:22:36 -0700
Received: from USTX2EX-DAG1MB3.msg.corp.akamai.com (172.27.165.121) by ustx2ex-dag1mb2.msg.corp.akamai.com (172.27.165.120) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 12 May 2020 11:20:30 -0500
Received: from USTX2EX-DAG1MB3.msg.corp.akamai.com ([172.27.165.121]) by ustx2ex-dag1mb3.msg.corp.akamai.com ([172.27.165.121]) with mapi id 15.00.1497.006; Tue, 12 May 2020 11:20:29 -0500
From: "Salz, Rich" <rsalz@akamai.com>
To: Erik Andersen <era@x500.eu>, 'Russ Housley' <housley@vigilsec.com>
CC: 'LAMPS' <spasm@ietf.org>
Thread-Topic: [lamps] Problems with the current ALGORITHM information object class
Thread-Index: AdYmysgWP4xsKPedQly3iSGlHws7SQBETt4AACquuQAAAtrBAP//x3mAgABEGACAABBfAP//wwAA
Date: Tue, 12 May 2020 16:20:29 +0000
Message-ID: <63E46AF5-CA96-4406-9C42-129944383641@akamai.com>
References: <000001d62762$8385a360$8a90ea20$@x500.eu> <97737DBD-54DB-4336-A387-E22C59E78B11@vigilsec.com> <001f01d6285c$d614adb0$823e0910$@x500.eu> <15833649-2B4C-49ED-9ACD-6F9AF9B41FFD@vigilsec.com> <B9ABCF64-ABE3-423D-8CE2-2BE79A6D1DF8@akamai.com> <697D575A-B0BA-4BA5-B5F6-10ACF3E6C6B4@vigilsec.com> <002301d62876$3b1f5750$b15e05f0$@x500.eu>
In-Reply-To: <002301d62876$3b1f5750$b15e05f0$@x500.eu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.37.20051002
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.36.167]
Content-Type: multipart/alternative; boundary="_000_63E46AF5CA9644069C42129944383641akamaicom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.216, 18.0.676 definitions=2020-05-12_05:2020-05-11, 2020-05-12 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=893 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-2002250000 definitions=main-2005120124
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.216, 18.0.676 definitions=2020-05-12_05:2020-05-11, 2020-05-12 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 impostorscore=0 mlxscore=0 lowpriorityscore=0 clxscore=1015 spamscore=0 adultscore=0 malwarescore=0 priorityscore=1501 bulkscore=0 phishscore=0 mlxlogscore=879 suspectscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2003020000 definitions=main-2005120124
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/wvptoDpoX-bLRSsRYUz9kFjmS9Y>
Subject: Re: [lamps] Problems with the current ALGORITHM information object class
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 May 2020 16:22:43 -0000

Just to make it clear since I’m not sure I understood your last note:  you will not re-use OID’s already defined that use the older syntax, but will define new OID’s for algorithms that want to use the new parameter clarifications, even if the mechanism is the same?

v2.23.0 | Report a Bug | By Email