IETF Logo Mail Archive

Re: [homenet] Introduction to draft-ietf-homenet-simple-naming

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 18 June 2018 22:35 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 2F7F7130E36 for <homenet@ietfa.amsl.com>; Mon, 18 Jun 2018 15:35:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 fw5wuvMTN3kN for <homenet@ietfa.amsl.com>; Mon, 18 Jun 2018 15:35:27 -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 90D6E129385 for <homenet@ietf.org>; Mon, 18 Jun 2018 15:35:27 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 5139620090; Mon, 18 Jun 2018 18:49:34 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 5EBD91817; Mon, 18 Jun 2018 18:32:26 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 5C414E2E; Mon, 18 Jun 2018 18:32:26 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "STARK, BARBARA H" <bs7652@att.com>
cc: HOMENET <homenet@ietf.org>
In-Reply-To: <2D09D61DDFA73D4C884805CC7865E6114DE01573@GAALPA1MSGUSRBF.ITServices.sbc.com>
References: <CAPt1N1kcuDBxK1=RN=_Q4YM7L_-YDNaEt4WS-sh2YDeJgvMgRw@mail.gmail.com> <20180528180538.GF12038@mx4.yitter.info> <CADZyTkmAc+CUdFxaur=qfFagtrUx64vv7QGFocgdHM1rXqJB7Q@mail.gmail.com> <762d4d6d-38d3-05ac-7cd6-fc87b2f1b042@gmail.com> <10568.1527686230@localhost> <29be80e3-bd65-bcd3-5db2-c2ef0a084f12@gmail.com> <37902D77-2528-4D9E-815A-DFF83905EB83@fugue.com> <8736y8hnll.wl-jch@irif.fr> <355c2773-efb5-20ce-f813-2fcd48470543@gmail.com> <1F6977CE-A176-432C-85EC-92CDACA71C02@orandom.net> <35df1f70-c900-501e-7014-eae265d8ebdf@gmail.com> <CAPt1N1nHMS42F9Qke8wWHhTSF_Szr9AGao+ZxftwDavZAkztCQ@mail.gmail.com> <69d6999b-af05-c38d-56e2-6f391f6bcf05@mtcc.com> <CAPt1N1=s+x26pPk2-kP7vgHMs6R=0zG6ZoXevKymbf1EwbqTMw@mail.gmail.com> <a75e515f-0d67-10c4-326a-0c4f70d8b888@mtcc.com> <CB6C0B26-CF8C-4713-94F0-86F06819FF3C@fugue.com> <20694.1527865346@localhost> <2D09D61DDFA73D4C884805CC7865E6114DE01573@GAALPA1MSGUSRBF.ITServices.sbc.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-sha1"; protocol="application/pgp-signature"
Date: Mon, 18 Jun 2018 18:32:26 -0400
Message-ID: <20815.1529361146@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/KThn7dDeNQY8kqd2gA40qzko3S8>
Subject: Re: [homenet] Introduction to draft-ietf-homenet-simple-naming
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.26
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, 18 Jun 2018 22:35:31 -0000

STARK, BARBARA H <bs7652@att.com> wrote:
    > in which case we can and should re-discuss) is: Some users like to give
    > their devices pretty/friendly names. We need to make sure that's
    > possible, but not required.  Others will simply accept whatever name
    > the device comes with.  These names are visible to users and should not
    > be confused with credentials or a stable identity. But they do need to
    > be unique.  Stable identity is also needed.

This is essentially correct, but it feels a bit weak to me.

Given that devices wind up with pretty/friendly names, and that those name
can change for a variety of reasons, we REQUIRE stable identity as well as
pretty names.

Users need to be able to connect policies (including, but not just security
policies) to both pretty names ("the office printer"),  and to stable
identies.   Neither thing should have anything to do with IP addresses
(which get renumbered), nor to MAC addresses (which may be more frequently
randomized, even for things like printers).

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

v2.23.0 | Report a Bug | By Email