From owner-freebsd-current@FreeBSD.ORG  Tue Jun  3 01:33:57 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 8514637B401; Tue,  3 Jun 2003 01:33:57 -0700 (PDT)
Received: from v6.hitachi.co.jp (galilei.v6.hitachi.co.jp [133.145.167.4])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 493E043F75; Tue,  3 Jun 2003 01:33:56 -0700 (PDT)
	(envelope-from suz@crl.hitachi.co.jp)
Received: from s30.crl.hitachi.co.jp (galilei.v6.hitachi.co.jp
	[IPv6:2001:200:165::1])
	by v6.hitachi.co.jp (8.12.9/8.11.6) with ESMTP id h538jBah039158;
	Tue, 3 Jun 2003 17:45:11 +0900 (JST)
	(envelope-from suz@crl.hitachi.co.jp)
Date: Tue, 03 Jun 2003 17:32:35 +0900
Message-ID: <x7k7c31rz0.wl%suz@crl.hitachi.co.jp>
From: SUZUKI Shinsuke <suz@freebsd.org>
To: re@freebsd.org
X-cite: xcite 1.33
In-Reply-To: <200306011400.h51E0E2X053391@fledge.watson.org>
References: <200306011400.h51E0E2X053391@fledge.watson.org>
User-Agent: User-Agent: Wanderlust/2.11.3 (Wonderwall) Emacs/21.1 Mule/5.0
	(SAKAKI)
Organization: Network Systems Research Dept., Central Research Laboratory,
	Hitachi, Ltd, Japan
MIME-Version: 1.0 (generated by SEMI 1.14.4 - "Hosorogi")
Content-Type: text/plain; charset=US-ASCII
cc: current@freebsd.org
Subject: Re: 5.2-RELEASE TODO
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jun 2003 08:33:57 -0000

>>>>> On Sun, 1 Jun 2003 10:00:14 -0400 (EDT)
>>>>> rwatson@freebsd.org(Robert Watson)  said:

>    |                     |          |                 | The FreeBSD KAME    |
>    |                     |          |                 | IPv6 code is now    |
>    |                     |          |                 | substantially dated |
>    |                     |          |                 | with respect to the |
>    | KAME                |          |                 | KAME vendor source. |
>    | Synchronization     | --       | --              | The FreeBSD Project |
>    |                     |          |                 | needs to take       |
>    |                     |          |                 | initiative in       |
>    |                     |          |                 | driving the merge   |
>    |                     |          |                 | of new bug fixes,   |
>    |                     |          |                 | features, et al.    |

I discussed this issued within KAME.

Here's our rough plan about this synchronization.

If you have some opinion, please let me know.
When I've finished each merge, I'll ask you how to proceed.


- sync per feature; don't do a complete sync with the KAME-snap:
	Since some of the KAME-specific features are still under
	standardization or immature, it's dangerous to sync without
	much consideration.

- items to be merged
	Here's the candidate items to be merged.

	5.2-RELEASE
		- IPv6 Advanced API (RFC3542 = written as
		  'RFC2292bis' in source code)
			Binary compatibility to RFC2292 is
			provided.

		- Source Address Selection (RFC3484)
			It involves too many unessential changes.
			(e.g. NDP data structure change, use struct
			sockaddr_in6 instead of struct in6_addr).

			So if time does not permit, I'll shift it
			to the future release.

	5.x-RELEASE
		- IGMPv3 (RFC3478 and draft-ietf-magma-msf-api-04.txt)
			seems almost okay in terms of standardization,
			but has less priority.

			So if time permits, I'll shift it to
			5.2-RELEASE.

		- Mobile IPv6 Corresponding Node (draft-ietf-mobileip-ipv6-22.txt)
			waiting for becoming an RFC

- items not to be merged
	The following items are not merged for the time being, because
	of their immaturity, wating for standardization, etc.

		MLDv2
		mDNS 
		Scoped routing
		VRRPv6
		Mobile-IPv6 Home-Agent and Mobile-Node
		Router Selection
		ISATAP
		DNS server discovery
		DHCPv6
		SCTP