[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GSE IDs [Re: IETF multihoming powder: just add IPv6 and stir]
Brian,
On Monday, May 5, 2003, at 12:05 AM, Brian E Carpenter wrote:
I thought we were talking about a M + S + 64 bits address space where
the M
bits can be guaranteed globally unique and the S bits are managed by
the site.
Or, more specifically, S+64.
For the purposes of global routing, this is unique enough to
guarantee no
collisions. The uniqueness of the 64 bits within the local segment
are managed
by existing mechanisms of address autoconfig.
Right.
That isn't the only requirement. If the M is mutable and the S has no
particular reason to be unique, then if you have a set of peers
intercommunicating, you've only got the 64 bit IDs available to act as
unique IDs for transport end-point and security end-point
identification.
Not unless M is globally unique.
So there is a strong requirement that the 64 bit IDs be unique within
any set of intercommunicating peers. (In the case of TCP, the set has
two members; in the case of FTP it's any number, by use of the PORT
command.)
No.
All the GSE-like solutions discussed to date that I am aware of have
assumed the first 48 bits (the locator) are globally unique. This is
sort of fundamental. If the first 48 bits are unique, then the last 80
bits may or may not be unique depending on what you want to do.
Rgds,
-drc