Re: [lamps] Problems with the current ALGORITHM information object class
Erik Andersen <era@x500.eu> Tue, 12 May 2020 16:25 UTC
Return-Path: <era@x500.eu>
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 711233A00E0 for <spasm@ietfa.amsl.com>; Tue, 12 May 2020 09:25:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.696
X-Spam-Level:
X-Spam-Status: No, score=-1.696 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=x500.eu
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 5W5Br3MelRJM for <spasm@ietfa.amsl.com>; Tue, 12 May 2020 09:25:49 -0700 (PDT)
Received: from outscan1.mf.dandomain.dk (outscan1.mf.dandomain.dk [212.237.249.58]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2008B3A00D8 for <spasm@ietf.org>; Tue, 12 May 2020 09:25:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by outscan1.mf.dandomain.dk (Postfix) with ESMTP id 5EE414068C3A; Tue, 12 May 2020 18:25:47 +0200 (CEST)
Received: from outscan1.mf.dandomain.dk ([127.0.0.1]) by localhost (outscan1.mf.dandomain.dk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id To6szkAP1oAZ; Tue, 12 May 2020 18:25:46 +0200 (CEST)
Received: from mail-proxy.dandomain.dk (dilvs03.dandomain.net [194.150.112.64]) by outscan1.mf.dandomain.dk (Postfix) with ESMTPA id 4C6684068AA9; Tue, 12 May 2020 18:25:44 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=x500.eu; s=dandomain; t=1589300746; bh=SmkF/B7I7ZK6uqlAUQxNoopqWpcqysrtpQ7VgTU3UIM=; h=From:To:Cc:References:In-Reply-To:Subject:Date:From; b=lP2+nlmoI6XWI2tP8bsRCN6VL503bzMxPbBTzDzGSlEl0oDdbxY0uDOXDXWYSS00M DnRamNks6Zc6s82adFHYE2vSoWQFkeHmksnAGr2qh3ZEIuIJPgKu5Khvv+3OPgimzX 3RmbVYLaUs7MGKdzjQVYSPlpFs9LPp/IMkrxXKrbuaC5Ia2116ox9biea7To5eQoor n5G0Ikpcc7mIuXRsGKkpVZYYCfG8Rgl6JtRiNR5XWvYMGCMZl+UviSLTF7Ak/Fw0zi k5uqxFp1Ws7vyEVmwFBHp+ttVXuwEsoVdr0No5fdpGdynkpCVcjolSmoQitYy2U0xb sGNflfy7mtKGg==
From: Erik Andersen <era@x500.eu>
To: "'Salz, Rich'" <rsalz=40akamai.com@dmarc.ietf.org>, 'Russ Housley' <housley@vigilsec.com>
Cc: 'LAMPS' <spasm@ietf.org>
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> <63E46AF5-CA96-4406-9C42-129944383641@akamai.com>
In-Reply-To: <63E46AF5-CA96-4406-9C42-129944383641@akamai.com>
Date: Tue, 12 May 2020 18:25:43 +0200
Message-ID: <003a01d62879$fd9ae8f0$f8d0bad0$@x500.eu>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_003B_01D6288A.C1242E20"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQGsSWEsGbi5WzyRcw86Ep3rBlnkMwIwrpU6Ai4BHRYB4xM3wQG2KIYmAjRDVbICBSPYSAGOl1uYqIphsyA=
Content-Language: en-gb
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/AAEjGjHeKiaGLmjwHrm__Y98hT8>
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:25:52 -0000
Right, to avoid interworking problems Erik From: Spasm <spasm-bounces@ietf.org> On Behalf Of Salz, Rich Sent: 12 May 2020 18:20 To: Erik Andersen <era@x500.eu>; 'Russ Housley' <housley@vigilsec.com> Cc: 'LAMPS' <spasm@ietf.org> Subject: Re: [lamps] Problems with the current ALGORITHM information object class 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?
- [lamps] Problems with the current ALGORITHM infor… Erik Andersen
- Re: [lamps] Problems with the current ALGORITHM i… Russ Housley
- Re: [lamps] Problems with the current ALGORITHM i… Russ Housley
- Re: [lamps] Problems with the current ALGORITHM i… Erik Andersen
- Re: [lamps] Problems with the current ALGORITHM i… Salz, Rich
- Re: [lamps] Problems with the current ALGORITHM i… Russ Housley
- Re: [lamps] Problems with the current ALGORITHM i… Erik Andersen
- Re: [lamps] Problems with the current ALGORITHM i… Salz, Rich
- Re: [lamps] Problems with the current ALGORITHM i… Erik Andersen