From owner-freebsd-net@FreeBSD.ORG Wed Oct 6 16:44:22 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6CB6C16A4CE for ; Wed, 6 Oct 2004 16:44:22 +0000 (GMT) Received: from pit.databus.com (p70-227.acedsl.com [66.114.70.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id BDB1443D39 for ; Wed, 6 Oct 2004 16:44:21 +0000 (GMT) (envelope-from barney@pit.databus.com) Received: from pit.databus.com (localhost [127.0.0.1]) by pit.databus.com (8.13.1/8.13.1) with ESMTP id i96GiK6h010824; Wed, 6 Oct 2004 12:44:21 -0400 (EDT) (envelope-from barney@pit.databus.com) Received: (from barney@localhost) by pit.databus.com (8.13.1/8.13.1/Submit) id i96GiKX4010823; Wed, 6 Oct 2004 12:44:20 -0400 (EDT) (envelope-from barney) Date: Wed, 6 Oct 2004 12:44:20 -0400 From: Barney Wolff To: Petri Helenius Message-ID: <20041006164420.GA10568@pit.databus.com> References: <41640CEE.9070900@web.de> <4164106A.70901@cronyx.ru> <416415DA.9030109@web.de> <200410061628.i96GS3eo046161@khavrinen.lcs.mit.edu> <41641DB3.2090303@he.iki.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41641DB3.2090303@he.iki.fi> User-Agent: Mutt/1.5.6i X-Scanned-By: MIMEDefang 2.44 cc: FreeBSD-net cc: Waldemar Kornewald cc: Garrett Wollman Subject: Re: modularization X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Oct 2004 16:44:22 -0000 On Wed, Oct 06, 2004 at 07:30:43PM +0300, Petri Helenius wrote: > Garrett Wollman wrote: > > >< > said: > > > >>Yes, something in that direction, plus: protocols: > >>IPv4, IPv6, TCP, UDP, ICMP, IPX, etc. > >>Just about everything as modules. > > > >It is not generally regarded as a good idea to make artificial > >boundaries between (e.g.) IP and TCP. > > > However from the success of the OSI/IP and related (CLNS, TP4, etc) > protocols it can said that it's a good way to fail. It's important to make a distinction between specification and implementation. Protocols should be designed and defined with clear boundaries between layers, but protocol handlers need not, and often should not, be implemented that way. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net.