Re: [homenet] I-D Action: draft-ietf-homenet-simple-naming-02.txt

Michael Thomas <mike@mtcc.com> Tue, 03 July 2018 18:16 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 9EA5E130DC7 for <homenet@ietfa.amsl.com>; Tue, 3 Jul 2018 11:16:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.1
X-Spam-Level:
X-Spam-Status: No, score=-1.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, HTML_MESSAGE=0.001, 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 igp83prVIiqU for <homenet@ietfa.amsl.com>; Tue, 3 Jul 2018 11:16:23 -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 42BE112E039 for <homenet@ietf.org>; Tue, 3 Jul 2018 11:16:23 -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 w63IGKlG023704 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <homenet@ietf.org>; Tue, 3 Jul 2018 11:16:21 -0700
To: homenet@ietf.org
References: <153056390914.16161.485217145353190124@ietfa.amsl.com> <da5722d2-a21c-4790-402c-4f40e9be903e@mtcc.com> <CAPt1N1=_uc8Z5jOFOft4NaPPf7beV1P4HhrViUDMJE8J2k=dog@mail.gmail.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <96ce0e8c-d4ad-761a-7784-f374043e7f6c@mtcc.com>
Date: Tue, 03 Jul 2018 11:16:20 -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: <CAPt1N1=_uc8Z5jOFOft4NaPPf7beV1P4HhrViUDMJE8J2k=dog@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------8B10284126495B1664B94BF6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/hnicTPVTky5I9WtpG6XneP8D0Sc>
Subject: Re: [homenet] I-D Action: draft-ietf-homenet-simple-naming-02.txt
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: Tue, 03 Jul 2018 18:16:25 -0000

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 <mike@mtcc.com 
> <mailto:mike@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-drafts@ietf.org
>     <mailto:internet-drafts@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