[Hipsec-rg] meeting minutes posted

thomas.r.henderson at boeing.com (Henderson, Thomas R) Mon, 12 January 2009 16:52 UTC

From: "thomas.r.henderson at boeing.com"
Date: Mon, 12 Jan 2009 08:52:38 -0800
Subject: [Hipsec-rg] meeting minutes posted
In-Reply-To: <alpine.LFD.2.00.0901121802320.17180@stargazer.pc.infrahip.net>
References: <77F357662F8BFA4CA7074B0410171B6D07B0BBE5@XCH-NW-5V1.nw.nos.boeing.com> <alpine.LFD.2.00.0901071641330.12787@stargazer.pc.infrahip.net> <77F357662F8BFA4CA7074B0410171B6D07B0BC6B@XCH-NW-5V1.nw.nos.boeing.com> <alpine.LFD.2.00.0901121802320.17180@stargazer.pc.infrahip.net>
Message-ID: <77F357662F8BFA4CA7074B0410171B6D07B0BC70@XCH-NW-5V1.nw.nos.boeing.com>

 

> 
> > But how do you view that delegation might work in this space, using 
> > HITs?
> 
> I implemented an access policy for BIND9 (small patch from 
> HIPL source 
> needed) that allows DNS updates to 1.0.0.1.0.0.2.ip6.arpa iff 
> they are 
> sent from HITs. So Host Identifiers itself are used as keys to 
> authenticate the updater.
> 
> For example, only 2001:1e:574e:2505:264a:b360:d8cc:1d75 is allowed to 
> modify 
> 5.7.d.1.c.c.8.d.0.6.3.b.a.4.6.2.5.0.5.2.e.4.7.5.e.1.0.0.1.0.0.
> 2.IP6.ARPA
> PTRs

Functionally, I see how that can work, but operationally, do you propose
that the five root servers of ip6.arpa implement and maintain this?  Or,
presuming that there is a HIP-specific allocation in the future, that
there is a global root nameserver or set of nameservers for this HIT
space?

Tom