Date: Fri, 02 Mar 2007 07:59:04 -0500 From: Randall Stewart <rrs@cisco.com> To: Tsuyoshi MOMOSE <t-momose@kame.net> Cc: Max Laier <max@love2party.net>, freebsd-net@freebsd.org Subject: Re: Thinking about IPv6 and DEPRECATED addresses Message-ID: <45E81F98.8040205@cisco.com> In-Reply-To: <0D7E7D0C-80DA-4F8E-8008-A39F3A4C9EBD@kame.net> References: <45E541A2.4020005@cisco.com> <200702281233.50145.max@love2party.net> <0D7E7D0C-80DA-4F8E-8008-A39F3A4C9EBD@kame.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Tsuyoshi MOMOSE wrote: > > On 2007/02/28, at 20:33, Max Laier wrote: > >>> So, I am contemplating adding to rtsock.c the ability to >>> send these types of events up. I am thinking on adding >>> this there for two reasons.. >>> >>> a) SCTP already hooks into the routing socket to get >>> interface changes. >>> and >>> >>> b) It may well be a relevant fact that if an address becomes >>> DETACHED or non-DETACHED (etc) for a routing process >>> to want to know about.. >>> >>> >>> What do others think? If I am off in the weeds somewhere and >>> this does not concern the routing socket I could use other >>> methods .. including isolating the "look at the state" flags >>> into a special place so that proper locking could be added >>> when we actually do locking for the ifa's... of course I would >>> prefer just not to have to look at it :-D >>> >>> Opinions if this is a good idea or not?? >> >> Great idea. I'm also CC-ing Tsuyoshi MOMOSE who is working on importing >> MIP6 which will likely be interested in this information (in userland) as >> well. AFAIK, the mnd already listens on the rtsock to pick up new >> addresses as soon as possible, but not sooner (for which it has to go >> through great lengths). > > Thanks for CCed to me. > > As Max said, our Mobile IPv6 stack uses rtsock to detect changing > address address such as added, deleted. > (but actually, the program which listens the rtsock is not mnd but > mdd(babymdd). The aim of mdd is just detcting the movement of the node > and notifies to mnd its movement information) > > To do that, SHISA introduces a new routing socket message RTM_ADDRINFO > which is sent from kernel when a new address is attached, detached, and > DAD was done. So, you can get an address information soon as possible. > I guess the message meets Randall's requirement for the SCTP. > > I don't start the SHISA porting to the head yet, but I can begin the > port first from the RTM_ADDRINFO part if you hope. Well it might meet some of them.. I need to know when DAD is done, but also if a interface detaches.. aka stops hearing the RT adverts.. and then later starts hearing them again.. I was thinking of all the various states V6 addresses go through.. Now, I would love to look at your "patch" if you could send it to me.. and see if it can be the basis for what I want. Will you be at the WIDE meeting next week? Or maybe BSD Asia. If so maybe we could meet up to discuss this :-) R > > > > ---------------------------- > Tsuyoshi MOMOSE / ももせつよし > momose@momose.org > http://www.momose.org/ (Underconstruction) > -- Randall Stewart NSSTG - Cisco Systems Inc. 803-345-0369 <or> 803-317-4952 (cell)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45E81F98.8040205>