From owner-freebsd-arch Tue Aug 1 12:21:24 2000 Delivered-To: freebsd-arch@freebsd.org Received: from hunkular.glarp.com (hunkular.glarp.com [199.117.25.251]) by hub.freebsd.org (Postfix) with ESMTP id BA8A737BA22 for ; Tue, 1 Aug 2000 12:21:21 -0700 (PDT) (envelope-from huntting@hunkular.glarp.com) Received: from hunkular.glarp.com (localhost [127.0.0.1]) by hunkular.glarp.com (8.9.3/8.9.3) with ESMTP id NAA18418 for ; Tue, 1 Aug 2000 13:21:20 -0600 (MDT) (envelope-from huntting@hunkular.glarp.com) Message-Id: <200008011921.NAA18418@hunkular.glarp.com> To: freebsd-arch@freebsd.org Subject: IPv6 Default Address Selection Reply-To: huntting@glarp.com Date: Tue, 01 Aug 2000 13:21:20 -0600 From: Brad Huntting Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone given any thought on how one could implement Default Addr Selection (draft-ietf-ipngwg-default-addr-select-01.txt) in FreeBSD? Not only does this algorithm seem rather time consuming, it needs to be used by the kernel (for local address select on unbound() sockets), as well as by the resolver (for sorting the results of an address query). One obvious approach is to put the "Source(D)" part of the algorithm which picks the optimal local address for a destination D in the kernel and give user space access to it through a some system call. Unfortunately, the algorithm for choosing destination addresses requires several calls to this function in order to sort a list of destination addresses. So perhaps the best thing would be to put Destination address sorting in the kernel as well, and allow userland programs (usually the resolver) to make a single system call to sort them. brad To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message