[Anima-bootstrap] alternate to domain-certificate-identifier missing from voucher yang

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 24 March 2017 18:55 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: anima-bootstrap@ietfa.amsl.com
Delivered-To: anima-bootstrap@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id E828F1294BE for <anima-bootstrap@ietfa.amsl.com>; Fri, 24 Mar 2017 11:55:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id IC9S_9fYE5d4 for <anima-bootstrap@ietfa.amsl.com>; Fri, 24 Mar 2017 11:55:51 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00::f03c:91ff:feae:de77]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 42D58129458 for <anima-bootstrap@ietf.org>; Fri, 24 Mar 2017 11:55:51 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown []) by relay.sandelman.ca (Postfix) with ESMTPS id 746E91F8FB for <anima-bootstrap@ietf.org>; Fri, 24 Mar 2017 18:55:49 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 448953412; Fri, 24 Mar 2017 12:09:00 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: anima-bootstrap@ietf.org
X-Attribution: mcr
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Fri, 24 Mar 2017 11:09:00 -0500
Message-ID: <32445.1490371740@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima-bootstrap/dgK3y7liVGE_AMbHoP6OwpTZlMA>
Subject: [Anima-bootstrap] alternate to domain-certificate-identifier missing from voucher yang
X-BeenThere: anima-bootstrap@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mailing list for the bootstrap design team of the ANIMA WG <anima-bootstrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima-bootstrap>, <mailto:anima-bootstrap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima-bootstrap/>
List-Post: <mailto:anima-bootstrap@ietf.org>
List-Help: <mailto:anima-bootstrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima-bootstrap>, <mailto:anima-bootstrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Mar 2017 18:55:53 -0000

The MASA can use the combination of:
    trusted-ca-certificate plus
      (domain-certificate-identifier.subject xor cn-id xor dns-id)

to indirectly point at the JRC's certificate. There could be a series of
certificates in the chain between the trusted-ca-certificate and the
thing the voucher staples down, clearly.

In the yang, we write about trusted-ca-certificate:

            This field is optional because it may not be needed by all
            bootstrapping protocols.

So I was looking for the other way, where one points right at the
JRC's public key.  I didn't find it.  So I thought: OH, of course,
one could specify a certificate chain of zero length, by putting
the JRC's subjectKeyInfo into trusted-ca-certificate!

Or can I?  I don't think we got the reference in trusted-ca-certificate
correct (and I don't have 5280 on the plane with me. Bad me, disk space is
cheap) to check.  I think that:
       An X.509 v3 certificate structure as specified by RFC 5280,
       Section 4

is too much, I think we just wanted the subjectKeyInfo as suggested
by Sean Turner.

(Okay, I will follow up to my email and check)

Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-