It's mentioned in section 10. I mentioned this more explicitly in the old homenet naming architecture document. Here: https://tools.ietf.org/html/draft-lemon-homenet-naming-architecture-01#section-4.6
On Tue, Jul 3, 2018 at 2:21 PM, Michael Thomas <[email protected]> wrote: > On 07/02/2018 05:19 PM, Ted Lemon wrote: > > Hm, I think that’s mentioned explicitly in the document I agree that > that’s a possible solution. Let me know if you want to work on a draft. > > > Can you tell me where? I'm not seeing it? > > Mike > > > On Mon, Jul 2, 2018 at 8:10 PM Michael Thomas <[email protected]> wrote: > >> If every homenet has a local.arpa, then with mobility (eg, my phone) >> will possibly get >> confused by the currently attached homenet's naming, and my "home" >> homenet's naming. >> Say, for example, i try to reference (explicitly, implicitly) >> printer.local.arpa and i'm at, oh say, >> my neighbor's house. it seems that i could really easily accidentally >> chose my neighbor's printer >> which has the same name as my printer. That could possibly be a pretty >> bad thing. >> >> I don't think i've seen this addressed? If not, maybe each homenet >> naming domain should >> have some cryptographically random and unique prefix for .local.arpa? >> >> Mike >> >> On 07/02/2018 01:38 PM, [email protected] wrote: >> > A New Internet-Draft is available from the on-line Internet-Drafts >> directories. >> > This draft is a work item of the Home Networking WG of the IETF. >> > >> > Title : Simple Homenet Naming and Service Discovery >> Architecture >> > Authors : Ted Lemon >> > Daniel Migault >> > Stuart Cheshire >> > Filename : draft-ietf-homenet-simple-naming-02.txt >> > Pages : 15 >> > Date : 2018-07-02 >> > >> > Abstract: >> > This document describes how names are published and resolved on >> > homenets, and how hosts are configured to use these names to >> discover >> > services on homenets. It presents the complete architecture, and >> > describes a simple subset of that architecture that can be used in >> > low-cost homenet routers. >> > >> > >> > The IETF datatracker status page for this draft is: >> > https://datatracker.ietf.org/doc/draft-ietf-homenet-simple-naming/ >> > >> > There are also htmlized versions available at: >> > https://tools.ietf.org/html/draft-ietf-homenet-simple-naming-02 >> > https://datatracker.ietf.org/doc/html/draft-ietf-homenet- >> simple-naming-02 >> > >> > A diff from the previous version is available at: >> > https://www.ietf.org/rfcdiff?url2=draft-ietf-homenet-simple-naming-02 >> > >> > >> > Please note that it may take a couple of minutes from the time of >> submission >> > until the htmlized version and diff are available at tools.ietf.org. >> > >> > Internet-Drafts are also available by anonymous FTP at: >> > ftp://ftp.ietf.org/internet-drafts/ >> > >> > _______________________________________________ >> > homenet mailing list >> > [email protected] >> > https://www.ietf.org/mailman/listinfo/homenet >> >> >> _______________________________________________ >> homenet mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/homenet >> > > > _______________________________________________ > homenet mailing > [email protected]https://www.ietf.org/mailman/listinfo/homenet > > > > _______________________________________________ > homenet mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/homenet > >
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
