IETF Logo Mail Archive

Re: [Anima] Alexey Melnikov's Discuss on draft-ietf-anima-bootstrapping-keyinfra-22: (with DISCUSS and COMMENT)

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 18 July 2019 23:30 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 DFCBB120115; Thu, 18 Jul 2019 16:30:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 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, URIBL_BLOCKED=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 PG40f7V1qbtT; Thu, 18 Jul 2019 16:30:13 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7EBA3120106; Thu, 18 Jul 2019 16:30:13 -0700 (PDT)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:56b2:3ff:fe0b:d84]) by tuna.sandelman.ca (Postfix) with ESMTP id 8E8A83808A; Thu, 18 Jul 2019 19:30:04 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id B4F0D71B; Thu, 18 Jul 2019 19:30:10 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Alexey Melnikov <aamelnikov@fastmail.fm>
cc: draft-ietf-anima-bootstrapping-keyinfra@ietf.org, tte+ietf@cs.fau.de, anima-chairs@ietf.org, The IESG <iesg@ietf.org>, anima@ietf.org
In-Reply-To: <b194301a-59f0-4edb-a387-d6cda1b3b599@www.fastmail.com>
References: <156285123896.32459.15810474411321920381.idtracker@ietfa.amsl.com> <27800.1563297174@localhost> <b194301a-59f0-4edb-a387-d6cda1b3b599@www.fastmail.com>
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: Thu, 18 Jul 2019 19:30:10 -0400
Message-ID: <9325.1563492610@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/hhaz-xq86F2A7aiBdV-VlkGhprw>
Subject: Re: [Anima] Alexey Melnikov'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: Thu, 18 Jul 2019 23:30:16 -0000

Alexey Melnikov <aamelnikov@fastmail.fm> wrote:
    >> > o In the language of [RFC6125] this provides for a SERIALNUM-ID >
    >> category of identifier that can be included in a certificate and >
    >> therefore that can also be used for matching purposes.  The >
    >> SERIALNUM-ID whitelist is collated according to manufacturer trust >
    >> anchor since serial numbers are not globally unique.

    > This is actually not helping. I was looking for something like:

    >   DNS-ID = a subjectAltName entry of type dNSName

    > Basically I was asking for a definition of SERIALNUM-ID somewhere.

It's a (subject)DN of serial number=123456, not a subjectAltName.
(not the CertificateSerialNumber)

It's X.520.. via 802.1AR and RFC5280 section 4.1.2.4.
https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-X.520-201610-I!!PDF-E&type=items
section 6.2.9.

    o  Client authentication is automated using Initial Device Identity
       (IDevID) as per the EST certificate based client authentication.
       The subject field's DN encoding MUST include the "serialNumber"
-      attribute with the device's unique serial number.
+      attribute with the device's unique serial number as explained in
+      Section 2.3.1
 
-   o  This extends the informal set of "identifer type" values defined
-      in [RFC6125] to include a SERIALNUM-ID category of identifier that
-      can be included in a certificate and therefore that can also be
-      used for matching purposes.  As noted in that document this is not


-- 
]               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    [

v2.23.0 | Report a Bug | By Email