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.
Xiaohu:
The main advantage of using the ASN+location+SID namespace is to
enable both topological and geographical aggregation, and help in
reducing route geographical stretch.
Note that GIRO is *not* a loc/id separation solution, but just a
different way of organizing the bits in the address and announcing in
BGP only the relevant bits for inter-domain routing. The 2nd half of
GIRO address is also a locator to route pkts inside the dest ASN.
This means that all mapping can be easily done trough DNS by querying
the dest host name to get the full GIRO address, in the same way
hosts are looked up in current Internet.
--Ricardo
--
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
