IETF Logo Mail Archive

Re: [Iot-onboarding] How to locate the EST server on a network?

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 14 January 2020 21:20 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: iot-onboarding@ietfa.amsl.com
Delivered-To: iot-onboarding@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDE79120882 for <iot-onboarding@ietfa.amsl.com>; Tue, 14 Jan 2020 13:20:03 -0800 (PST)
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 jkELWGMxVhhJ for <iot-onboarding@ietfa.amsl.com>; Tue, 14 Jan 2020 13:20:02 -0800 (PST)
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 5D47E120110 for <iot-onboarding@ietf.org>; Tue, 14 Jan 2020 13:20:02 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 5A83B3897B; Tue, 14 Jan 2020 16:19:35 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 5D1B4108F; Tue, 14 Jan 2020 16:20:01 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "M. Ranganathan" <mranga@gmail.com>, iot-onboarding@ietf.org
In-Reply-To: <20200114173728.GO14549@faui48f.informatik.uni-erlangen.de>
References: <CAHiu4JOFMeENPRnAF49rU7u7KpTSfPS9Kj+We72VVkQ4jcHVpw@mail.gmail.com> <20200114173728.GO14549@faui48f.informatik.uni-erlangen.de>
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: Tue, 14 Jan 2020 16:20:01 -0500
Message-ID: <15846.1579036801@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/iot-onboarding/hh-RHRgnPO2NPaFQaZDRgBxzn4I>
Subject: Re: [Iot-onboarding] How to locate the EST server on a network?
X-BeenThere: iot-onboarding@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion of IoT onboarding mechanisms <iot-onboarding.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iot-onboarding>, <mailto:iot-onboarding-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iot-onboarding/>
List-Post: <mailto:iot-onboarding@ietf.org>
List-Help: <mailto:iot-onboarding-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iot-onboarding>, <mailto:iot-onboarding-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2020 21:20:04 -0000

Toerless Eckert <tte@cs.fau.de> wrote:
    > If you want to use BRSKI, you would use the DNS-SD service name
    > brski-registrar, see BRSKI draft section 8.6. If you just want to do
    > EST alone (again, that would only result in insecure "duckling" initial
    > enrolment but sufficient for renewal/rekeying), the service name in DNS
    > is "est". The ACP draft specifies the service names for discovery via
    > GRASP, which i guess might not be your fist choice outside of ANIMA
    > today ;-).

DNS-SD is an optional thing for BRSKI!
The MTI is a GRASP DULL message to find the join proxy.

If you don't have a device->network trust issue (because your wires carry
implicit trust), then you can use EST with IDevID to do enrollment of an LDevID.
DNS-SD is a very good way.

Owen and Rifaat's Cloud Registrar document provides a number of other
interesting options too.

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

v2.23.0 | Report a Bug | By Email