IETF Logo Mail Archive

Re: [Dtls-iot] IP Addresses in Certificates

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 07 August 2015 19:15 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: dtls-iot@ietfa.amsl.com
Delivered-To: dtls-iot@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0F9E1A1AE1 for <dtls-iot@ietfa.amsl.com>; Fri, 7 Aug 2015 12:15:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 LJvZk-Uq2kMm for <dtls-iot@ietfa.amsl.com>; Fri, 7 Aug 2015 12:15:25 -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 226CA1A03A1 for <dtls-iot@ietf.org>; Fri, 7 Aug 2015 12:15:25 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id AE381E472; Fri, 7 Aug 2015 14:04:48 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id BAAB563B10; Fri, 7 Aug 2015 13:47:07 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id A687063AD9; Fri, 7 Aug 2015 13:47:07 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
In-Reply-To: <55C4BFA1.1030600@gmx.net>
References: <55A63EEF.7010608@gmx.net> <55A641EC.4030203@cs.tcd.ie>, <D1D3F9D5.31B15%thomas.fossati@alcatel-lucent.com> <trinity-5e418e2e-726a-4c31-8498-634e598fb57e-1438786484782@3capp-gmx-bs46> <55C23E1B.5050300@cs.tcd.ie> <22776.1438803665@sandelman.ca> <55C4BFA1.1030600@gmx.net>
X-Mailer: MH-E 8.6; nmh 1.3-dev; GNU Emacs 24.4.2
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-sha1"; protocol="application/pgp-signature"
Date: Fri, 07 Aug 2015 13:47:07 -0400
Message-ID: <9160.1438969627@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/mRydcJIbkLD2HjK-LMMtwUvnFKc>
Cc: "dtls-iot@ietf.org" <dtls-iot@ietf.org>, "FOSSATI, Thomas (Thomas)" <thomas.fossati@alcatel-lucent.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [Dtls-iot] IP Addresses in Certificates
X-BeenThere: dtls-iot@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DTLS for IoT discussion list <dtls-iot.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dtls-iot>, <mailto:dtls-iot-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dtls-iot/>
List-Post: <mailto:dtls-iot@ietf.org>
List-Help: <mailto:dtls-iot-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dtls-iot>, <mailto:dtls-iot-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Aug 2015 19:15:26 -0000

Hannes Tschofenig <hannes.tschofenig@gmx.net> wrote:
    > could you explain the idea behind draft-richardson-6tisch-idevid-cert?

    > I don't see how it relates to Stephen's request to add a description on
    > how to use IP addresses in certificates for the DTLS/TLS IoT profiles
    > draft.

1) I rather agree that putting IP addresses in certificates is not useful.

2) I would prefer to see manufacturer installed certificates with something
   else in them, such as 802.1AR with a clear serial number that would
   be replaced by an LDevID certificate during a bootstrap process.

   The idevid-cert document goes a step further and suggests
   how the device with the installed certificate will validate the peer
   that it interacts with in much the same way that RPKI has been setup.
   I would claim that this is actually more important than what's in
   the device.

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

v2.23.0 | Report a Bug | By Email