On 07/02/2018 05:21 PM, Ted Lemon wrote:
I didn’t get all the updates I wanted to into this version. A lot of the issues you mention here were discussed in my presentation in London. Will you be in Montreal?
No. Mike
On Mon, Jul 2, 2018 at 7:43 PM Michael Thomas <m...@mtcc.com <mailto:m...@mtcc.com>> wrote:One thing that confuses me reading this is where (if any) is the "caching resolver" expected to reside. in section 2.2, last bullet it makes mention of an ISP resolver, but it's not clear whether that resolver is the same as the homenet resolver. if it's not that resolver, maybe it would be better to defer that discussion somehow? that is, say that it can happen, but defer how it might happen until later. nit: you should move the terminology section up at least one section. I think this draft says that each homenet router can implement the naming functionality. how do they negotiate who is authoritative? If it's in another document, it might be nice to call that out. I'm not groking why this requires the use of ULA's for v6. It doesn't seem to require that ipv4 use rfc 1918 addresses? why does the naming function care which address space an address is in? what if i don't want to use ULA's? In section 6, it says that request are sent to the local resolver which is either a caching resolver or a proxy. Does that imply that the caching resolver cannot be authoritative too? I don't think that's what you mean, but it's sort of confusing. Some ascii art might be helpful to show the topology possibilities thanks, Mike On 07/02/2018 01:38 PM, internet-dra...@ietf.org <mailto:internet-dra...@ietf.org> 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 <http://tools.ietf.org>. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > homenet mailing list > homenet@ietf.org <mailto:homenet@ietf.org> > https://www.ietf.org/mailman/listinfo/homenet _______________________________________________ homenet mailing list homenet@ietf.org <mailto:homenet@ietf.org> https://www.ietf.org/mailman/listinfo/homenet _______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
_______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
