Re: [homenet] Ted's security talk at IETF99: DNCP Security

Michael Richardson <> Mon, 31 July 2017 17:41 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C47B7131C3C for <>; Mon, 31 Jul 2017 10:41:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
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, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id mNBfPOtOaWzK for <>; Mon, 31 Jul 2017 10:41:56 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 77A36131C7A for <>; Mon, 31 Jul 2017 10:41:55 -0700 (PDT)
Received: from ( [IPv6:2607:f0b0:f:2::247]) by (Postfix) with ESMTP id 7B48AE1DC; Mon, 31 Jul 2017 13:43:39 -0400 (EDT)
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 349B3806BA; Mon, 31 Jul 2017 13:41:54 -0400 (EDT)
From: Michael Richardson <>
To: Ted Lemon <>
In-Reply-To: <>
References: <> <>
X-Mailer: MH-E 8.6; nmh 1.6+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: Mon, 31 Jul 2017 13:41:54 -0400
Message-ID: <>
Archived-At: <>
Subject: Re: [homenet] Ted's security talk at IETF99: DNCP Security
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF Homenet WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 31 Jul 2017 17:41:58 -0000

Ted Lemon <>; wrote:
    mcr> Is there a document for this Ted? I will offer to help.

    > Your help would be much appreciated, but I don't know why there would
    > be an election, so there's at a minimum some thinking to do
    > there. There is no document yet.

I think that we need to have a Registrar that issues certificates.
ANIMA's BRSKI document automates much of this.

That partly gets rid of the security exception on each access to the
web interface: provided the web browser loads the new trust anchor.

    > Also, bear in mind that a vendor-centric approach to this probably isn't
    > going to work, because right now all the Homenet work I'm aware of is
    > happening on OpenWRT and LEDE. I'm sure that will change if we come up

This is where all the other pairing mechanisms come into play.
You mentioned having a laundry list of them.

Michael Richardson <>;, Sandelman Software Works
 -= IPv6 IoT consulting =-