Hannu, > So HIT is routable IPv6 address to enable legacy to legacy > communication? Is that good?
I'm not sure this is the case for HIP. However, in RANGI, the host ID is an IPv6 PI address in CGA alike format ( the first part of this ID is Administrative Domain (AD) ID, the latter part is the hash of the AD ID and its public key ). This specific PI address could be routable in site where legacy hosts exist (just as map&encaps approach). This is just my rough thought of the proxy mechanism for RANGI, and I think this is also workable for HIP. > How about having a two faced DNS for upgraded nodes? HIT > returned if source is from EID space, AAAA if not? This is a very interesting idea. BTW, if the DNS server is upgraded, we can also define another field for the HIT/host ID value in DNS request/reply msgs which can be used between upgraded hosts and upgraded DNS servers. Xiaohu > >-----Original Message----- > >From: [email protected] [mailto:[email protected]] On > Behalf Of > >ext Xu Xiaohu > >Sent: Thursday, January 08, 2009 07:30 > >To: 'Scott Brim' > >Cc: 'RRG'; 'Robin Whittle' > >Subject: Re: [rrg] Rejecting all but Strategy A > > > > > >> > When a legecy host A initiates a communication with a > >> HIP-enabled host > >> > B, A could send a packet to a nearby proxy (like ITR's > >> role) by using > >> > B's HIT as locator. > >> > >> Would you replace host B's A record with a HIT? Or would > >this require > >> a modification to host A? If you're going to modify A, > why not just > >> implement HIP? > > > >Replacing host B's AAAA record with a HIT is my thought. If a legacy > >host got B's AAAA record from DNS, it will look that record > as a IPv6 > >address And the mapping between HIT and locator (IP address) can be > >maintained in a seperate mapping system, e.g. a hierarchical DHT > >system. > > > >Xiaohu > > > > > >_______________________________________________ > >rrg mailing list > >[email protected] > >https://www.irtf.org/mailman/listinfo/rrg > > > _______________________________________________ > rrg mailing list > [email protected] > http://www.irtf.org/mailman/listinfo/rrg _______________________________________________ rrg mailing list [email protected] http://www.irtf.org/mailman/listinfo/rrg
