IETF Logo Mail Archive

Re: [Anima] What does PKIX refer to: Re: Benjamin Kaduk's Discuss on draft-ietf-anima-bootstrapping-keyinfra-22: (with DISCUSS and COMMENT)

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 09 August 2019 18:24 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B08A41200F1; Fri, 9 Aug 2019 11:24:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 mCd08T14CzSX; Fri, 9 Aug 2019 11:24:53 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 95EB51200E6; Fri, 9 Aug 2019 11:24:53 -0700 (PDT)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:56b2:3ff:fe0b:d84]) by tuna.sandelman.ca (Postfix) with ESMTP id A5D6B3818F; Fri, 9 Aug 2019 14:24:11 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 9D2671027; Fri, 9 Aug 2019 14:24:51 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
to: Benjamin Kaduk <kaduk@mit.edu>, The IESG <iesg@ietf.org>, draft-ietf-anima-bootstrapping-keyinfra@ietf.org, tte+ietf@cs.fau.de, anima@ietf.org, anima-chairs@ietf.org
In-Reply-To: <27223.1565374549@localhost>
References: <156282301326.15131.7510532622479656237.idtracker@ietfa.amsl.com> <27223.1565374549@localhost>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Fri, 09 Aug 2019 14:24:51 -0400
Message-ID: <29229.1565375091@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/dGT8IiBtRf2Uq7Ux4JwjTdJCr5U>
Subject: Re: [Anima] What does PKIX refer to: Re: Benjamin Kaduk's Discuss on draft-ietf-anima-bootstrapping-keyinfra-22: (with DISCUSS and COMMENT)
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Aug 2019 18:24:56 -0000

Michael Richardson <mcr+ietf@sandelman.ca> wrote:
    > I hoping for some discussion about this comment that I previously
    > responded to, but it probably got buried.

Actually, you did respond on July 20, in an email that I thought to re-read
after pushing send.

In it you said:

mcr> I would never call the Internet PKI "PKIX".
mcr> I'd call it WebPKI, or CAB.
mcr> PKIX is the set of IETF specifications that made X509v3 useful.
mcr> (And why I try never to use "X509"...)
mcr>
mcr> I couldn't find a reference to private PKI, so maybe I mis-understand.

   doc> This document details protocols and messages to answer the above
   doc> questions.  It uses a TLS connection and an PKIX (X.509v3)
   doc> certificate (an IEEE 802.1AR [IDevID] LDevID) of the pledge to answer
   doc> points 1 and 2.  It uses a new artifact called a "voucher" that the
   doc> [...]
   doc> Pledge authentication and pledge voucher-request signing is via a
   doc> PKIX certificate installed during the manufacturing process.  This is

bk> The comment about private PKI was me making an assumption; I could be
bk> wrong.  But I don't really expect all manufacturers that do this to have
bk> their IDevID signing CA be part of the Internet PKI; I expect them to be
bk> standalone CAs with the root baked into hardware and nothing else that
bk> uses that root.  Does that help clarify?

It helps to clarify where you think I'm referring to the Internet PKI.

I don't think of "PKIX" as referring to the Internet PKI/WebPKI as managed by
the CAB-Forum.  Yes, it will be a private CA 96% of the time.
A 1988 era X509v3 certificate isn't good enough; it has to be the IETF PKIX
WG profile of X509v3.  801.1AR mostly says that.

If you feel that my use of PKIX here is too confusing, I will change it.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [






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

v2.23.0 | Report a Bug | By Email