From owner-freebsd-ports Fri Jan 7 7: 3:10 2000 Delivered-To: freebsd-ports@freebsd.org Received: from prince.net.ebina.hitachi.co.jp (sagami148234.allnet.ne.jp [210.251.148.234]) by hub.freebsd.org (Postfix) with ESMTP id 2A5AB14FF1; Fri, 7 Jan 2000 07:03:01 -0800 (PST) (envelope-from sumikawa@ebina.hitachi.co.jp) Received: from ebina.hitachi.co.jp (localhost [127.0.0.1]) by prince.net.ebina.hitachi.co.jp (8.9.3/3.7W) with SMTP id AAA46153; Sat, 8 Jan 2000 00:02:51 +0900 (JST) From: sumikawa@ebina.hitachi.co.jp Message-Id: <200001071502.AAA46153@prince.net.ebina.hitachi.co.jp> Date: Sat, 8 Jan 2000 00:02:51 +0900 (JST) To: asami@FreeBSD.ORG Cc: freebsd-ports@FreeBSD.ORG, committers@FreeBSD.ORG Cc: sumikawa@ebina.hitachi.co.jp Subject: Re: IPv6-enable ports In-Reply-To: References: <200001061955.EAA34652@prince.net.ebina.hitachi.co.jp> X-Mailer: xcite1.31> Mew version 1.95b10 on Emacs 20.4 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org asami> That sounds fine, but what about packages? They will all be built asami> without IPv6 support, right? I think It should synchronize default kernel configuration. If kernel is enabled IPv6 in default, the packages should be build with IPv6 support. asami> Or is IPv6 support downwards compatible with IPv4? In that case I can asami> set USE_INET6 in the build environment and be done with it. Almost of applications work fine, but downwards compatibility is depends on each implementations in general. In IPv4/IPv6-mixed world, a typical host is assigned several IPv4/IPv6 addresses. In this case, applications must try to connect all of address of the host until it make a success as below. foreach an address from candidates { try to connect an address; if (failed) next; else break; } This is too general explanation. Getaddrinfo() loop is used concretely. See, http://www.kame.net/newsletter/19980604/. However, it is possible that some of applications give up in first trying. These programs quit right now, when a non-IPv6 kernel fails to connect to an IPv6 host. It will be inconvenience for IPv4 users. It's a kind of bug. But many programers have no experience of address family independent programming. Anyway, this releasing discussion is another issue, I believe. I'll go ahead. --- Munechika SUMIKAWA @ KAME Project / FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message