Date: Fri, 23 Jul 1999 10:39:42 +0200 From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> To: itojun@iijlab.net Cc: hackers@FreeBSD.ORG Subject: Re: Will FreeBSD ever see native IPv6 ?? Message-ID: <19990723103942.C9276@daemon.ninth-circle.org> In-Reply-To: <22056.932649289@coconut.itojun.org>; from itojun@iijlab.net on Thu, Jul 22, 1999 at 10:14:49PM %2B0900 References: <19990722142445.B814@daemon.ninth-circle.org> <22056.932649289@coconut.itojun.org>
next in thread | previous in thread | raw e-mail | index | archive | help
* itojun@iijlab.net (itojun@iijlab.net) [990722 16:17]: > > >> Are you just teasing or are you serious? > >Well, according to what was discussed earlier he is serious. But from > >prolonged exposure to the kame lists I (think I) know that the FreeBSD ipv6 > >stuff is only available for 3.x and below. > > We (KAME) are using 3.2-RELEASE and 2.2.8-RELEASE because we can't > base our IPv6 development on top of moving target. > FreeBSD 3.x-STABLE and 4.x are moving target (which moves very quickly) > and are unusable as base version for us - if we need to chase two > moving things (IPv6 and FreeBSD) we are doomed. Problem being is that the 2.2.x branch has been declared obsolete and dead by the Project. If serious development work is being done CURRENT has always been the targetted platform. But let's not nitpick about decissions make months earlier. However, 3.2-STABLE isn't that fast moving forward, and I doubt, based on earlier discussions about touching the 3.x branch, that Jordan will allow IPv6 to be entered into the 3.x branch (however TPTB may judge otherwise). So 4.x seems like the only alternative left... And I am still working on that =) > There has been NRL/INRIA/KAME integration work going on (basically > to avoid "4 BSDs and 3 IPv6 = 12 choices" nightmare by making one > IPv6 stack). There are, mainly, some (or too many) management > issues there. We will be resolving management issues issue very soon, > hopefully by next week. That's good new ITOJUN-san, but I hope you can understand that after seeing OpenBSD deploy IPv6 and NetBSD-CURRENT getting the IPv6 code merged by you, that FreeBSD (read the userbase/developers) is anxious to also incorporate this. > There's incomplete "unified" codebase there, which is not very > ready for public consumption. Anyway please hold till the managment > issue is resolved, I believe I can give you a good news. Let me ask one question: if a few of us got the 3.x kit of kame up to 4.x level and it got all commited would it make the `merged' stack easier to integrate into CURRENT or does the stack-project prefer to use a clean codebase? I myself think the first, which allows our driver writers time to adjust to IPv6 changes, get a lot of still-present bugs out and basically restabilize the system before the next IPv6 changes. Not to mention allow people to test/work with IPv6 already. I would love to hear your reactions to the above, kind regards, -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project <http://home.wxs.nl/~asmodai>; Network/Security Specialist BSD: Technical excellence at its best Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990723103942.C9276>