IETF Logo Mail Archive

Re: [homenet] Host naming in Homenet

Michael Thomas <mike@mtcc.com> Mon, 31 August 2015 16:51 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 225451B5815 for <homenet@ietfa.amsl.com>; Mon, 31 Aug 2015 09:51:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.111
X-Spam-Level:
X-Spam-Status: No, score=-1.111 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 gc_03WA-iH28 for <homenet@ietfa.amsl.com>; Mon, 31 Aug 2015 09:51:58 -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 2C6D51B5816 for <homenet@ietf.org>; Mon, 31 Aug 2015 09:51:58 -0700 (PDT)
Received: from [192.168.1.3] ([170.75.133.46]) (authenticated bits=0) by mtcc.com (8.14.7/8.14.7) with ESMTP id t7VGpv6N025991 for <homenet@ietf.org>; Mon, 31 Aug 2015 09:51:57 -0700
To: homenet@ietf.org
References: <87a8te70er.wl-jch@pps.univ-paris-diderot.fr> <55DDA73B.2070205@openwrt.org> <8737z66x9s.wl-jch@pps.univ-paris-diderot.fr> <66521869-2188-4FA0-9940-C383BD50836C@openwrt.org> <87vbc25guj.wl-jch@pps.univ-paris-diderot.fr> <98EE78C8-0F37-469E-BA7A-4554646B1D61@iki.fi> <CAAedzxoSURQB-CbmfdFHsj_yREJozRp7mvUDh2U1CPg8T8LYxg@mail.gmail.com> <87oahty8or.wl-jch@pps.univ-paris-diderot.fr> <CAAedzxq4K6STs8e7zpR9=SNq1SyU8RbbRJX+sFsyFbhMtZTigQ@mail.gmail.com> <55E43DC1.2090106@globis.net>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <55E4862B.60804@mtcc.com>
Date: Mon, 31 Aug 2015 09:51:55 -0700
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <55E43DC1.2090106@globis.net>
Content-Type: multipart/alternative; boundary="------------000400060907090108020003"
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/rWz_amiicis4YB1Su-BOYLLg2gQ>
Subject: Re: [homenet] Host naming in Homenet
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 31 Aug 2015 16:51:59 -0000


On 08/31/2015 04:42 AM, Ray Hunter (v6ops) wrote:
>
> Juliusz (and others) have objected to 
> https://tools.ietf.org/html/draft-ietf-homenet-naming-architecture-dhc-options 
> because it appears to be tied to the ISP. Yet for reverse resolution, 
> the ISP is an essential party, because they have been delegated the 
> DNS zone for their entire allocated address space. And Homenet uses 
> delegated prefixes from within this overall allocation.

What that tells me, on the other hand, is that these are two separate 
problems that
just need to get solved. And, in fact, the forward and reverse maps may 
not same auth/authz
requirements for their respective CRUD operations.

Mike

v2.23.0 | Report a Bug | By Email