IETF Logo Mail Archive

Re: [homenet] New version draft-mglt-homenet-naming-architecture-dhc-options-02.txt

Michael Thomas <mike@mtcc.com> Tue, 15 July 2014 14:29 UTC

Return-Path: <mike@mtcc.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B0DD1B2886 for <homenet@ietfa.amsl.com>; Tue, 15 Jul 2014 07:29:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.353
X-Spam-Level:
X-Spam-Status: No, score=-0.353 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_ADSP_ALL=0.8, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 jy2WrhJ0lUAU for <homenet@ietfa.amsl.com>; Tue, 15 Jul 2014 07:29:26 -0700 (PDT)
Received: from mtcc.com (mtcc.com [50.0.18.224]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2BE0C1B2883 for <homenet@ietf.org>; Tue, 15 Jul 2014 07:29:26 -0700 (PDT)
Received: from takifugu.mtcc.com (takifugu.mtcc.com [50.0.18.224]) (authenticated bits=0) by mtcc.com (8.14.7/8.14.7) with ESMTP id s6FETOHa005486 for <homenet@ietf.org>; Tue, 15 Jul 2014 07:29:24 -0700
Message-ID: <53C53AC4.3080807@mtcc.com>
Date: Tue, 15 Jul 2014 07:29:24 -0700
From: Michael Thomas <mike@mtcc.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: homenet@ietf.org
References: <CADZyTkk6rUuFJ5Wds2hioBBQa9-kXDJxyg_gBGQ1R6u5CHF2Ww@mail.gmail.com> <87fvij5wdw.wl.jch@pps.univ-paris-diderot.fr> <CADZyTkk2bv7T-Bs_ckG4i2MpXVDRqLA2R1dQgrMVrPSckOy-GQ@mail.gmail.com> <87k37uy703.wl.jch@pps.univ-paris-diderot.fr> <CADZyTk=YgD=JtyDpEz8TXOQmHxKzBoiEZbbW0LhZQy2GaKLqZQ@mail.gmail.com> <87vbrcydr9.wl.jch@pps.univ-paris-diderot.fr> <CADZyTk=kST4zPaPzz4DsAcCOtmYbQo-s2du+nEvJv0MSrneEMg@mail.gmail.com> <CADZyTkmZ+rC99qeC7gFEwc4JBoX9sHBUpo7p89+VC6zY7Z8drQ@mail.gmail.com> <87d2dfb98w.wl-jch@pps.univ-paris-diderot.fr> <CADZyTk=U25=Yck8BL5nrzGAR7mPk5HWp0r0h2wYy5ruSOf6rsQ@mail.gmail.com> <87vbr6mv8t.wl-jch@pps.univ-paris-diderot.fr> <7EEF5CD0-C3B8-4559-A75D-E55931F94F61@iki.fi>
In-Reply-To: <7EEF5CD0-C3B8-4559-A75D-E55931F94F61@iki.fi>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/kX6shD1K2BUkpDm08kbGNCUcl_c
Subject: Re: [homenet] New version draft-mglt-homenet-naming-architecture-dhc-options-02.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 15 Jul 2014 14:29:28 -0000

On 07/14/2014 11:47 PM, Markus Stenberg wrote:
> On 9.7.2014, at 18.01, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr> wrote:
>> There's still something I don't understand.  If I'm understanding Steve's
>> and Markus' work correctly, HNCP performs prefix delegation to internal
>> routers over HNCP, and the internal routers don't proxy stateful DHCPv6 to
>> the CPE.  How does your protocol work in the presence of multiple links?
>> Or are you assuming that only nodes directly connected to the IHAS/CPE can
>> be advertised over your protocol?
> Or even more weirdly, what if you don’t want stateful DHCPv6? SLAAC + temporary addresses?
>
>> Finally, what happens when there are multiple CPEs, which HNCP explicitly
>> supports?  Are you assuming that only one acts as IHAS?
> .. and how do the zones map to multiple uplinks ..
>
> Personally, I don’t believe in auto-exported ~full DNS information from home because current service discovery schemes (mdns, dns-sd, upnp) or even host-name discovery schemes (dhcp*) do not really lend themselves to the external visibility being _opt in_. I don’t really want to publish my home zone, and if I even did, anything that’s firewalled (= everything except few ports on few addresses) is not useful outside the home in any case.
>
>

Yet, I really, really, triple-super really want to be able to access my 
home network devices when i'm not
at home. Any part of the naming architecture better take that as a very 
basic requirement.

Mike

v2.23.0 | Report a Bug | By Email