> > Regarding HIP + map/encaps, maybe it is obvious to everyone > else already but I think what that gives you is an endpoint > identity (the HIT), an inner routing locator (iRLOC), and an > outer RLOC (oRLOC). Up to now, LISP (and perhaps others) have > been using the term "EID" to refer to what I mean by "iRLOC", > and the term "RLOC" to refer to what I mean by "oRLOC".
Since a pure id/locator split solution (e.g. HIP) could use multiple PA address (locator) which are topologically aggregatable, there may be no need to use the two layers of locator(iRLOC and oRLOC) > In this sense, "oRLOC" is routable within the scope of an > interdomain region, while "iRLOC" is routable only within and > end site (or edge network, or whatever you want to call it). > The HIP HIT is not routable within any scope so it is purely > an identifier and not a locator. 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. Upon receiving the packet, the proxy will resolve B's HIT to B's locator, and send the packet to B, while using its locator as the packet's source locator and generating a temperay HIT for A. B will then send response packet to the above proxy. The proxy will do reverse mapping from the temporary HIT of A to the IP address of A, and then send the packet in legacy IP format to A. It's just my assumption. Xiaohu _______________________________________________ rrg mailing list [email protected] https://www.irtf.org/mailman/listinfo/rrg
