From owner-freebsd-current Sun Sep 6 01:24:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA20668 for freebsd-current-outgoing; Sun, 6 Sep 1998 01:24:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA20649 for ; Sun, 6 Sep 1998 01:24:35 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id KAA15327; Sun, 6 Sep 1998 10:19:40 +0200 (CEST) To: sthaug@nethelp.no cc: tlambert@primenet.com, dg@root.com, tom@uniserve.com, freebsd-current@FreeBSD.ORG Subject: Re: Should FreeBSD-3.0 ship with RFC 1644 (T/TCP) turned off by In-reply-to: Your message of "Sun, 06 Sep 1998 09:57:00 +0200." <6915.905068620@verdi.nethelp.no> Date: Sun, 06 Sep 1998 10:19:40 +0200 Message-ID: <15325.905069980@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That settles it. I've disabled RFC1644 as default and removed it from tcp_extensions in /etc/rc.{conf,networking} Poul-Henning >RFC 1644 has the status "Experimental Protocol", which means: > > 4.1.4. Experimental Protocol > > A system should not implement an experimental protocol unless it > is participating in the experiment and has coordinated its use of > the protocol with the developer of the protocol. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message