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

Michael Thomas <mike@mtcc.com> Fri, 25 May 2018 19:21 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 1B4FD127444 for <homenet@ietfa.amsl.com>; Fri, 25 May 2018 12:21:21 -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 JfHyO859Xsha for <homenet@ietfa.amsl.com>; Fri, 25 May 2018 12:21:20 -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 4225512E8D6 for <homenet@ietf.org>; Fri, 25 May 2018 12:21:20 -0700 (PDT)
Received: from Michaels-MacBook.local (170-75-130-17.volcanocom.com [170.75.130.17] (may be forged)) (authenticated bits=0) by mtcc.com (8.15.2/8.14.7) with ESMTPSA id w4PJLHoZ026244 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <homenet@ietf.org>; Fri, 25 May 2018 12:21:18 -0700
To: homenet@ietf.org
References: <CAPt1N1kcuDBxK1=RN=_Q4YM7L_-YDNaEt4WS-sh2YDeJgvMgRw@mail.gmail.com> <29946.1527267593@localhost> <1D99A968-513F-47D4-A208-9D401E58415A@fugue.com>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <3201c232-c6fd-3430-ee3a-f9e7ee0532e3@mtcc.com>
Date: Fri, 25 May 2018 12:21:10 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <1D99A968-513F-47D4-A208-9D401E58415A@fugue.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/nJY_OZzdlgHhFi1Ov0tmxidrJ84>
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: Fri, 25 May 2018 19:21:36 -0000


On 5/25/18 10:34 AM, Ted Lemon wrote:
> the ability to publish services on the Internet" seems like a 
> reasonable first attempt at specifying that, but I agree that it's 
> insufficient.   Do you have a theory to offer?   What I think I meant 
> by this was:
>
> - Has a globally-scoped delegation for publishing names (a forward tree)
> - Optionally with DNSSEC
> - Has one or more globally-scoped delegations for publishing records 
> referring to globally-scoped IP addresses on the network (a reverse tree)
> - Optionally with DNSSEC
> - Ability to specify which services are visible from outside, either 
> manually or automatically (e.g. with mud).
> - Ability to acquire ACME certs?   This is probably out of scope-ish, 
> but ACME does interact with the naming system.   This is one of my 
> primary motivations for caring about the advanced naming architecture, 
> TBH—it makes it possible to secure the gateway web UI.
>
>

Optional to implement or optional to deploy?

Mike