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

Michael Thomas <mike@mtcc.com> Thu, 31 May 2018 22:06 UTC

Return-Path: <mike@mtcc.com>
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 0978D127873 for <homenet@ietfa.amsl.com>; Thu, 31 May 2018 15:06:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.101
X-Spam-Level:
X-Spam-Status: No, score=-1.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, SPF_PASS=-0.001] autolearn=no 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 ipGxY3-1MbOO for <homenet@ietfa.amsl.com>; Thu, 31 May 2018 15:05:59 -0700 (PDT)
Received: from mtcc.com (mtcc.com [50.0.18.224]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01183129C59 for <homenet@ietf.org>; Thu, 31 May 2018 15:05:58 -0700 (PDT)
Received: from takifugu.mtcc.com (takifugu.mtcc.com [50.0.18.224]) (authenticated bits=0) by mtcc.com (8.15.2/8.14.7) with ESMTPSA id w4VM5wRR028570 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <homenet@ietf.org>; Thu, 31 May 2018 15:05:58 -0700
To: homenet@ietf.org
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>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <69d6999b-af05-c38d-56e2-6f391f6bcf05@mtcc.com>
Date: Thu, 31 May 2018 15:05:58 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <CAPt1N1nHMS42F9Qke8wWHhTSF_Szr9AGao+ZxftwDavZAkztCQ@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/GSHA8PoBEJy-LiNBu-Ci1lmzJ3Q>
Subject: Re: [homenet] Introduction to draft-ietf-homenet-simple-naming
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: Thu, 31 May 2018 22:06:00 -0000

On 05/31/2018 02:32 PM, Ted Lemon wrote:
> In practice, you just change the device's name in its web ui. Then 
> it's starts advertising the new name, and the old name stops working. 
> If you have enough of a model of this to change the name, you also 
> know enough to select the printer under it's new name. Of course it 
> would be nice if we could have it publish some kind of announcement 
> about the name change.

On the subject of naming, it's not really necessary to change the name 
to give it a pretty display name in DNS... you can just give it a CNAME 
or something like that. That would at least give me one source of truth 
on naming without having to go to every grotty web interface on low end 
devices (assuming it exists at all).

Mike