Oleg Ponomarev wrote:
Hi! On Thu, 23 Apr 2009, Robert Moskowitz wrote:Of course, anyone posessing the private part of the Host Identity.And how do you 'prove' this? Been a long time since I looked at DYNDNS....We require successful HIP Base Exchange before the update.We have some operational experience in HIIT for local nameservers.So you become the new ISI? Neat! Actually, this makes a lot of sense to give it, at least at first, to a group like HIIT.It is just an experiment: aeris.infrahip.net accepts updates to hit-to-ip.net and 1.0.0.1.0.0.2.ip6.arpa over HIP. Then our local nameservers are configured to retrieve 1.0.0.1.0.0.2.ip6.arpa from aeris.
I run my own DNS for my testbed. Is there a way I can point my nameserver to specifically go to your server for 1.0.0.1.0.0.2.ip6.arpa? Something like the HINTS file for the root servers?
I would have to allow recursion for it, I think?
So it works fine inside the network: $ host 2001:1e:574e:2505:264a:b360:d8cc:1d755.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 domain name pointer stargazer.pc.infrahip.net.Yes, we will need a ORCHID reverse lookup ID (if we stay with ORCHIDs, given the need to change even ORCHID to support other hashes), and point to a HIT-to-IP ID for one mechanism used by the owner of the domain.ip6.arpa part could be split from draft-ponomarev-hip-hit2ip-03, if there is demand for it. A couple of servers would be enough to keep this zone at the current deployment state.There was some discussion in hiprg mailing list last December.I will try and dig it out.I checked, actually it was in January with subject "reverse DNS lookups of HITs".