> To recognize your own addresses, you should be doing a full 128-bit
> compare, not examining individual fields. Just put all of your
> own addresses in your routing table, with a prefix length of 128
> bits and a "self" indicator, and let normal longest-match lookup
> do its thing.
That is obviously doable, when an interface has single id.
However, the issue came up when I started to explore the possibilities
of implementing the "privacy option", which could be interpreted (?)
in such way that an interface can have N different id's.
And if, you see a router avertising M new prefixes, you will have to
add N x M addresses to your routing list. And when an id or a prefix
expires, you have to rip off the matching addressess.
I was just looking, what would happen if I kept two lists: one for
prefixes and one for id's, and allowed any combination to be used
and recognized as own address. [For new id's I would do the DAD using
the link local address combined with the generated id].
--
Markku Savela <[EMAIL PROTECTED]>
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
