> GIRO already does the separation of locator/identifier. In Fig. 3, > which describes the address format, you can view the "external > component" as the "locator", and the "internal component" is the > "identifier". The locator is announced in BGP, while the identifier > is used to route inside the dest network.
Ricardo, What you said is just the first approach I mentioned in the previous mail as follows: The first approach is to split the GIRO address into two parts: id and locator. In this approach, IPv4 address part in GIRO address is used as id, which means there is no need to change the hosts however it doesn't address the IPv4 address depletion issue and it introduces a new locator space compared to LISP/eFIT. What's the benefit of introducing a new locator namespace compared with LISP/eFIT which reuses IP address as locator? Once the id/loc split idea is introduced, the locator can be allocated in a hierarchical way even though we still use IPv4/v6 as locator. Best wishes, Xiaohu XU -- to unsubscribe send a message to [EMAIL PROTECTED] with the word 'unsubscribe' in a single line as the message text body. archive: <http://psg.com/lists/rrg/> & ftp://psg.com/pub/lists/rrg
