From owner-freebsd-net Fri Nov 30 13:19:18 2001 Delivered-To: freebsd-net@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 287B737B417 for ; Fri, 30 Nov 2001 13:19:16 -0800 (PST) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id fAULIui91678; Fri, 30 Nov 2001 16:18:56 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Fri, 30 Nov 2001 16:18:55 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Bill Fumerola Cc: Alex Rousskov , freebsd-net@FreeBSD.ORG Subject: Re: funding TCP stack rewrite In-Reply-To: <20011130120008.G32521@elvis.mu.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, 30 Nov 2001, Bill Fumerola wrote: > core has nothing to do with preventing or allowing completed work to > enter the tree. the quality of the code does. presumably, the people > that the foundation (or NAI or whoever) contracts to do FreeBSD work are > of high calibur and that isn't a problem. For reference, the NAI Labs model has been to identify specific areas of the stack where we felt further work was needed in order to meet our, DARPA's, and general US .mil needs, and to contract out to an appropriately qualified developer to do implementation (in the case of the network stack, Jonathan Lemon). Right now, I don't think we have any interest in funding a complete rewrite of the network stack, as there is really not much motivation to. An evolutionary model means that you can address the specific needs at hand without investing rediculous amounts of money in a potential failure :-). The main reasons I might might be interested in a major rewrite or restructuring would be to see better support for threading, better support for extensibility, or better resistance to attack. However, it seems to me that at least in the short term, this work can be done in the context of the current stack without starting from scratch, which seems to be what is being proposed. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message