From owner-freebsd-net@FreeBSD.ORG Fri Mar 2 12:59:44 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D115616A5A5 for ; Fri, 2 Mar 2007 12:59:44 +0000 (UTC) (envelope-from rrs@cisco.com) Received: from sj-iport-1.cisco.com (sj-iport-1-in.cisco.com [171.71.176.70]) by mx1.freebsd.org (Postfix) with ESMTP id AA27313C4A7 for ; Fri, 2 Mar 2007 12:59:44 +0000 (UTC) (envelope-from rrs@cisco.com) Received: from sj-dkim-6.cisco.com ([171.68.10.81]) by sj-iport-1.cisco.com with ESMTP; 02 Mar 2007 04:59:44 -0800 X-IronPort-AV: i="4.14,241,1170662400"; d="scan'208"; a="765209744:sNHT47377676" Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137]) by sj-dkim-6.cisco.com (8.12.11/8.12.11) with ESMTP id l22Cxi9A017122; Fri, 2 Mar 2007 04:59:44 -0800 Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id l22Cxbho024863; Fri, 2 Mar 2007 04:59:41 -0800 (PST) Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 2 Mar 2007 04:59:37 -0800 Received: from [127.0.0.1] ([171.68.225.134]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 2 Mar 2007 04:59:35 -0800 Message-ID: <45E81F98.8040205@cisco.com> Date: Fri, 02 Mar 2007 07:59:04 -0500 From: Randall Stewart User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.8) Gecko/20061029 FreeBSD/i386 SeaMonkey/1.0.6 MIME-Version: 1.0 To: Tsuyoshi MOMOSE References: <45E541A2.4020005@cisco.com> <200702281233.50145.max@love2party.net> <0D7E7D0C-80DA-4F8E-8008-A39F3A4C9EBD@kame.net> In-Reply-To: <0D7E7D0C-80DA-4F8E-8008-A39F3A4C9EBD@kame.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 02 Mar 2007 12:59:35.0987 (UTC) FILETIME=[A1223030:01C75CCA] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2782; t=1172840384; x=1173704384; c=relaxed/simple; s=sjdkim6002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rrs@cisco.com; z=From:=20Randall=20Stewart=20 |Subject:=20Re=3A=20Thinking=20about=20IPv6=20and=20DEPRECATED=20addresse s |Sender:=20; bh=1yEQLPT59vFS5uUA5SX/xbN5Vp8/Lnjwmn1q4r1jrA0=; b=FiVOsqKjlZUo9QvCZ7Dj3uF+VDyvjHkrNjyOEHYGb6ahImxan2L0Byy5AXaufLOKGqt1wZUk oSXm1jvNyTycsDXn4S/a4nSvEzO3MP++YbLvwegLaQGDihs3fhcl2elC; Authentication-Results: sj-dkim-6; header.From=rrs@cisco.com; dkim=pass (sig from cisco.com/sjdkim6002 verified; ); Cc: Max Laier , freebsd-net@freebsd.org Subject: Re: Thinking about IPv6 and DEPRECATED addresses X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Mar 2007 12:59:44 -0000 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 803-317-4952 (cell)