Re: [Secdispatch] Problem statement for post-quantum multi-algorithm PKI

Ira McDonald <blueroofmusic@gmail.com> Tue, 17 September 2019 17:56 UTC

Return-Path: <blueroofmusic@gmail.com>
X-Original-To: secdispatch@ietfa.amsl.com
Delivered-To: secdispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A5E312013F for <secdispatch@ietfa.amsl.com>; Tue, 17 Sep 2019 10:56:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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_NONE=-0.0001, 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=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 aUpcMYE6jcrS for <secdispatch@ietfa.amsl.com>; Tue, 17 Sep 2019 10:55:59 -0700 (PDT)
Received: from mail-vs1-xe29.google.com (mail-vs1-xe29.google.com [IPv6:2607:f8b0:4864:20::e29]) (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 EDC1D120127 for <secdispatch@ietf.org>; Tue, 17 Sep 2019 10:55:58 -0700 (PDT)
Received: by mail-vs1-xe29.google.com with SMTP id d204so2633852vsc.12 for <secdispatch@ietf.org>; Tue, 17 Sep 2019 10:55:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=jHJHyZoohImOqpdU4EYol6R0Qn1XCxmccumUrEGv+Bw=; b=ZdP2yo17/BQ6MwC6KcJjCM1PpvHsO/f4ugWBerjxqeXuh5nzyUo2hQddEr7/0teKq+ 4ejJrW+7PDAH2bbQ5LsVr1cEvDAZZcTpHzwvXfSHW1KmcP4LvNyaq6pAJ70EkThJEhYU xWtELlM7cS6Z4LrC176xlhJ5oIgTJeSYMDlyrHHeGuDkmytU2dMWSQkMxwMbukorYkpS 3HMHZvnf3li3rWsnE7laHWBWGhAz14o2j7LZEWzXOEBcTUJq6HM2KXLR6ADyZTEFQUoC 1YzcPdpJsQ82QS4bp9ECsp1rpCnpWZae0YWwDrMS9YtmHnD/h/8aKqa2l8OCCYGvJaHd LV4g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=jHJHyZoohImOqpdU4EYol6R0Qn1XCxmccumUrEGv+Bw=; b=Q8JFpARRPcIDLR8zNuCWDYVQz4kmJ4vGCfSg+6dVr7xjJEL8QGbSntqTFo/XZWkNjd SWlsbX7MS21dEmNl+W8XNbhmaYd0IqpWK1QLea1MVlVnUy5LFEDwJt+vAiB1KkOIZQfa jP5nT2ozBp61/agH+hbOCfketLyNGSjqnjblRO+wK2MJail56xarcLu43uWpLijK9Op7 9eagf9qRyUbwgzQx6wdzYa7uhoJSg8ydOz0hAH81gkPfDiZDR4c3PlOTYXOFlvacCHF0 TedsoDvziv1tieohCT6Xbue0MAHREpFKkopR5oZ4cyqZQ+r9wvQ10jSWDZpTchHMRsUk wqXQ==
X-Gm-Message-State: APjAAAUTMVWayKob3vYIM83q/pCZ0ePBAJWg15X9I6iv3p0V/iULaltI PdU+sBPfCjw/jp6XbYpM53auJeLeRP0nvnyDpI8=
X-Google-Smtp-Source: APXvYqzI63bh2kYdl0n0IzG2mNd0dXCIrc/jca0c8OK7b/Qo3Zv9snlJKnC3f68uv7+HSPdf1DoMja2lBr+Sn4QrhjE=
X-Received: by 2002:a67:e8ca:: with SMTP id y10mr1799220vsn.136.1568742958097; Tue, 17 Sep 2019 10:55:58 -0700 (PDT)
MIME-Version: 1.0
References: <a2e32c33-8589-f3fb-97e5-c5977dfc64b4@openca.org> <BL0PR11MB317285DF599EC58CCF26FD5EC1B00@BL0PR11MB3172.namprd11.prod.outlook.com> <28224.1568427573@dooku.sandelman.ca> <cf1a301c-47d6-7565-ddc7-69048e3c08f3@cs.tcd.ie> <5F8D32EB-CE27-4ECD-997F-D0AAE4B798B5@akamai.com> <2b87f695-314c-5aed-14a4-9877fe254161@ericsson.com> <CAN40gStdbJ0TNoeL0VFU4Tx1F5ubtAdJnz+QJXYFFAP7W2OV7w@mail.gmail.com> <3cfa21d8-efe2-1a69-5268-0a39e9171fe1@cs.tcd.ie> <CAN40gSseUfKyJo8SZzLVQGnoSOKPHQJysx7zz_w=n_SGuckfSw@mail.gmail.com> <45237418-7C96-4823-A7C6-39E92586756E@akamai.com> <CAN40gSuzC2hQsFmB2SFd8CnicLWfyiqgePf0pTYsHXZ=s5FV-g@mail.gmail.com> <E55FFB18-ABB5-442A-B41A-CC7678076C26@akamai.com> <CAN40gSvy4kcR1RwdJxoD+HSWc6eskTGHkrQ1=7iro2cieB-_rQ@mail.gmail.com> <6013.1568740878@localhost>
In-Reply-To: <6013.1568740878@localhost>
From: Ira McDonald <blueroofmusic@gmail.com>
Date: Tue, 17 Sep 2019 13:55:45 -0400
Message-ID: <CAN40gSvcVVFz3Nzfutc5OPcXnsutVr6wGxmCNB08ekbi2fZ5YA@mail.gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, Ira McDonald <blueroofmusic@gmail.com>
Cc: "secdispatch@ietf.org" <secdispatch@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c2eb0c0592c36e23"
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/Vshc4Y4cVodZZn9UVAq39IBM2Ms>
Subject: Re: [Secdispatch] Problem statement for post-quantum multi-algorithm PKI
X-BeenThere: secdispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Dispatch <secdispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdispatch/>
List-Post: <mailto:secdispatch@ietf.org>
List-Help: <mailto:secdispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Sep 2019 17:56:02 -0000

Hi Michael,

There's already work-in-progress in IETF WGs on CBOR wrapping
and/or encoding of X.509 certificates, including:

https://datatracker.ietf.org/doc/draft-ietf-cose-x509/

https://datatracker.ietf.org/doc/draft-raza-ace-cbor-certificates/

Cheers,
- Ira


Ira McDonald (Musician / Software Architect)
Co-Chair - TCG Trusted Mobility Solutions WG
Co-Chair - TCG Metadata Access Protocol SG
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music / High North Inc
http://sites.google.com/site/blueroofmusic
http://sites.google.com/site/highnorthinc
mailto: blueroofmusic@gmail.com
PO Box 221  Grand Marais, MI 49839  906-494-2434



On Tue, Sep 17, 2019 at 1:21 PM Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> The argument is about the timing.
> Whether we need to panic now or not.  Some suggest "we have time"
>
> My comment was that automobiles are being designed around ECUs today that
> will
> be built in 2025, which will be on the road until 2040.  So, no, we don't
> have the luxury of a lot of time.
>
> I'm personally unaware of a profile of X.509 certificates that permits a
> CA to sign multiple public keys with multiple algorithms.  RFC5280 says:
>
>    Certificate  ::=  SEQUENCE  {
>         tbsCertificate       TBSCertificate,
>         signatureAlgorithm   AlgorithmIdentifier,
>         signatureValue       BIT STRING  }
>
> I don't see a SET here, just a sequence.
>
> We (the IETF) can't solve the problem of ECUs having multiple hardware
> assists ourselves.  If I were working in that area, I'd already be looking
> through all the NIST submissions from last fall and figuring out what I
> need
> to accelerate them, and what operations are in common, and figuring out if
> I
> can accelerate the common operations, can I win regardless of which one is
> picked?
> Or at least, be closer to market to pick one or three variations.
>
> Rotiling RFC5280 so that we can support multiple signature algorithms on
> certificates means that we can get new CAs and related things deployed.
> I'm with Stephen in asking if the DER encoding is worth keeping at this
> point.
>
> Encode ASN.1 in CBOR (CBOR encoding rules for ASN.1) if we think the ASN.1
> is
> worth keeping, switch to CDDL if not.  We probably need to keep the
> semantics.
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>
> _______________________________________________
> Secdispatch mailing list
> Secdispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/secdispatch
>