From owner-freebsd-arch Tue Jul 11 5:31:29 2000 Delivered-To: freebsd-arch@freebsd.org Received: from hitpro.hitachi.co.jp (hitpro.hitachi.co.jp [133.145.224.7]) by hub.freebsd.org (Postfix) with ESMTP id 5241037B9D2; Tue, 11 Jul 2000 05:31:16 -0700 (PDT) (envelope-from ume@bisd.hitachi.co.jp) Received: from bisdgw.bisd.hitachi.co.jp by hitpro.hitachi.co.jp (8.9.3/3.7W-hitpro) id VAA29364; Tue, 11 Jul 2000 21:31:07 +0900 (JST) Received: from plum.ssr.bisd.hitachi.co.jp by bisdgw.bisd.hitachi.co.jp (8.9.3+3.2W/3.7W-bisdgw) with ESMTP id VAA15772; Tue, 11 Jul 2000 21:31:06 +0900 (JST) (envelope-from ume@bisd.hitachi.co.jp) Received: from localhost (IDENT:TnWloJykWU499Texbnpyz7+L7aXQQU/kh9ySh/cxpbi11sA6dAzw5ukJkKVt7Fug@localhost [::1]) by plum.ssr.bisd.hitachi.co.jp (8.10.1/3.7W-plum) with ESMTP id e6BCV6F67499; Tue, 11 Jul 2000 21:31:06 +0900 (JST) (envelope-from ume@bisd.hitachi.co.jp) Message-Id: <200007111231.e6BCV6F67499@plum.ssr.bisd.hitachi.co.jp> To: kris@FreeBSD.org Cc: arch@freebsd.org, net@freebsd.org, jkh@freebsd.org Subject: Re: Merge of KAME code From: Hajimu UMEMOTO In-Reply-To: References: X-Mailer: xcite1.20> Mew version 1.94.2 on XEmacs 21.1 (Bryce Canyon) X-PGP-Fingerprint: D3 3D D3 54 88 13 DE 22 3F 31 C4 4D A1 08 84 7B X-PGP-Public-Key: http://www.imasy.org/~ume/ume@bisd.hitachi.co.jp.asc X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 4.0-STABLE Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 11 Jul 2000 21:31:05 +0900 X-Dispatcher: imput version 20000414(IM141) Lines: 27 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> On Tue, 11 Jul 2000 03:56:15 -0700 (PDT) >>>>> kris@FreeBSD.org (Kris Kennaway) said: kris> I'm still nervous about merging back the libc changes because (as kris> demonstrated already) they have a larger chance to affect IPv4 operation. kris> Umemoto-san, do you have any opinions about the wisdom of this? The merges to res_init.c, res_send.c and getaddrinfo.c before merging latest KAME issue is aready MFCed. Though, the change to getaddrinfo.c is slightly big, it corrects the behavior of mapped address and saves IPv4 users. I believe the problem of DNS IPv6 transport support was gone and I've never heared the problem anymore. DNS IPv6 transport is desireble for IPv6 users to live under IPv6 only environment. I wrote IPv6 code for installer and intend to commit it for 4.1-RELEASE. It supports installation under IPv6 only environment. It requires DNS IPv6 transport. I think other parts are no problem for IPv4 users. There are some changes which are not merged into 5.0-CURRENT yet. I think such parts are rather experimental and shouldn't be merged in this time. -- Hajimu UMEMOTO @ Business Solution System Development Div., Hitachi Ltd. E-Mail: ume@bisd.hitachi.co.jp ume@mahoroba.org ume@FreeBSD.org URL: http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message