IETF Logo Mail Archive

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

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 31 July 2017 15:21 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA6A1132515 for <homenet@ietfa.amsl.com>; Mon, 31 Jul 2017 08:21:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QDm86Dd8GJpd for <homenet@ietfa.amsl.com>; Mon, 31 Jul 2017 08:21:04 -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 2C9041324EA for <homenet@ietf.org>; Mon, 31 Jul 2017 08:21:03 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 20EBBE1DB for <homenet@ietf.org>; Mon, 31 Jul 2017 11:22:47 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 2B16880243 for <homenet@ietf.org>; Mon, 31 Jul 2017 11:21:02 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: homenet@ietf.org
X-Attribution: mcr
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 11:21:02 -0400
Message-ID: <3725.1501514462@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/QIqMVwK3HNljxptqn1rNpyE0gIo>
Subject: [homenet] Ted's security talk at IETF99: DNCP Security
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jul 2017 15:21:07 -0000

So I'm watching via meetecho the meeting.  Some minor comment that it seems
like many things have happened in homenet that haven't really been on the
list.  {Or maybe it was just DMARC vs ietf.org forwarding "helping" me. I've
had to whitelist the ietf.org mail servers}

The things that Ted wants, such "this the ID of the router", and the like,
and this really the topic of the ANIMA BRSKI protocol.  It can be profiled
to work in Homenet, provided that HNCP can elect a registrar.
I think that is entirely workable, btw.
I don't think that Homenet has to invent any protocols here.

Is there a document for this Ted?  I will offer to help.

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

v2.23.0 | Report a Bug | By Email