From owner-freebsd-current@FreeBSD.ORG  Wed Dec 29 16:19:54 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3A3F516A4CE
	for <current@FreeBSD.org>; Wed, 29 Dec 2004 16:19:54 +0000 (GMT)
Received: from avout3.midco.net (avout3.midco.net [24.220.0.102])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B23A843D1D
	for <current@FreeBSD.org>; Wed, 29 Dec 2004 16:19:53 +0000 (GMT)
	(envelope-from pmes@bis.midco.net)
Received: (qmail 26879 invoked by uid 1009); 29 Dec 2004 16:19:53 -0000
Received: from pmes@bis.midco.net by avout3 by uid 1003 with
	qmail-scanner-1.22 
	(f-prot: 4.4.2/3.14.11.  Clear:RC:1(24.220.217.79):. 
	Processed in 0.011793 secs); 29 Dec 2004 16:19:53 -0000
X-Qmail-Scanner-Mail-From: pmes@bis.midco.net via avout3
X-Qmail-Scanner: 1.22 (Clear:RC:1(24.220.217.79):. Processed in 0.011793 secs)
Received: from host-79-217-220-24.midco.net (HELO [10.0.0.3])
	([24.220.217.79])          (envelope-sender <pmes@bis.midco.net>)
	by avout3.midco.net (qmail-ldap-1.03) with SMTP
	for <skylar@cs.earlham.edu>; 29 Dec 2004 16:19:53 -0000
In-Reply-To: <m2u0q5c1f9.wl@minion.local.neville-neil.com>
References: <41D0FB74.2000901@ispworkshop.com>
	<41D1E3DA.4080704@cs.earlham.edu> <20041228225929.GA13275@odin.ac.hmc.edu>
	<m2u0q5c1f9.wl@minion.local.neville-neil.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <778E3F3E-59B5-11D9-AB97-000D936BE398@bis.midco.net>
Content-Transfer-Encoding: 7bit
From: Peter Schultz <pmes@bis.midco.net>
Date: Wed, 29 Dec 2004 10:19:51 -0600
To: "George V. Neville-Neil" <gnn@neville-neil.com>
X-Mailer: Apple Mail (2.619)
cc: Ong Beng Hui <ongbh@ispworkshop.com>
cc: Skylar Thompson <skylar@cs.earlham.edu>
cc: current@FreeBSD.org
Subject: Re: FreeBsd as internet router
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Dec 2004 16:19:54 -0000

On Dec 28, 2004, at 7:56 PM, George V. Neville-Neil wrote:
> At Tue, 28 Dec 2004 14:59:29 -0800,
> Brooks Davis wrote:
>>
>> [1  <text/plain; us-ascii (quoted-printable)>]
>> [cc'ing doc since I think this is really a doc issue.  Please trim 
>> your
>> reply list as needed]
>>
>
> Sorry to chime in late on this.  I suspect the assertion about FreeBSD
> and building a router does have to do with complete RFC compliance.
> As Brooks pointed out, no router ever built actually complied with all
> the RFCs.

I got into FreeBSD starting with release 3.2, and I remember reading 
and asking about this then.  The answer I got was not as explanatory, 
it was more like, "FreeBSD routing works great, get 'er done!"  How 
about changing it around to put FreeBSD in a more positive light:

     FreeBSD is a highly reliable solution for your routing needs.
     However, configured in this way, it does not completely comply
     with the Internet standard requirements for routers.  The fact is,
     these same standards are not implemented by dedicated routing
     hardware either, and not only that, but it would be unwise to
     implement some of them.

Or something like that, so that people don't jump to the conclusion 
that FreeBSD is behind the times or somehow inferior.

Cheers,
Pete...