[lamps] Double signatures

"Erik Andersen" <era@x500.eu> Mon, 10 September 2018 14:56 UTC

Return-Path: <era@x500.eu>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id E3791130E9F for <spasm@ietfa.amsl.com>; Mon, 10 Sep 2018 07:56:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.7
X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id YPdeQBKIKLDY for <spasm@ietfa.amsl.com>; Mon, 10 Sep 2018 07:56:49 -0700 (PDT)
Received: from smtpscan3.dandomain.dk (smtpscan3.dandomain.dk []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 958B5130DFD for <spasm@ietf.org>; Mon, 10 Sep 2018 07:56:49 -0700 (PDT)
Received: from localhost (localhost []) by smtpscan3.dandomain.dk (Postfix) with ESMTP id AF4D14F2D for <spasm@ietf.org>; Mon, 10 Sep 2018 16:56:46 +0200 (CEST)
Received: from smtpscan3.dandomain.dk ([]) by localhost (smtpscan3.dandomain.dk []) (amavisd-new, port 10024) with ESMTP id UAv1O9qEVR-H for <spasm@ietf.org>; Mon, 10 Sep 2018 16:56:45 +0200 (CEST)
Received: from mail03.dandomain.dk (mail03.dandomain.dk []) by smtpscan3.dandomain.dk (Postfix) with ESMTP id E45E1CE1FB for <spasm@ietf.org>; Mon, 10 Sep 2018 16:56:45 +0200 (CEST)
Received: from Morten ([]) by mail03.dandomain.dk (DanDomain Mailserver) with ASMTP id 3201809101656442409; Mon, 10 Sep 2018 16:56:44 +0200
From: "Erik Andersen" <era@x500.eu>
To: "Directory list" <x500standard@freelists.org>, "LAMPS" <spasm@ietf.org>
Date: Mon, 10 Sep 2018 16:56:42 +0200
Message-ID: <005a01d44916$7c9cb560$75d62020$@x500.eu>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_005B_01D44927.402621A0"
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AdRJE8Ft784CpTSnSY6kx9oi8PdHNw==
Content-Language: en-gb
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/Ir4PELWCWDwDonmTvLT1sytZTYE>
Subject: [lamps] Double signatures
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: Mon, 10 Sep 2018 14:56:52 -0000

Hi Folk,


In ITU-T we have plans to allow for double signatures using the SIGNED
parametrized data type defined in X.509 to cope with situation as described
in the internet draft: "Multiple Public-Key Algorithm X.509 Certificates


We suggest to enhance the SIGNED data type as shown below:





  altAlgorithmIdentifier  AlgorithmIdentifier{{SupportedAlgorithms}}

  altSignature            BIT STRING OPTIONAL  

  } (WITH COMPONENTS {..., altAlgorithmIdentifier PRESENT, altSignature

     WITH COMPONENTS {..., altAlgorithmIdentifier ABSENT,  altSignature


We are open to comments. We know that IETF is not a heavy user of this data


We have no intention to use this extended data type for certificates and


For your information, SIGNATURE is defined as:



  algorithmIdentifier  AlgorithmIdentifier{{SupportedAlgorithms}},

  signature            BIT STRING,

  ... }