From owner-freebsd-hackers  Thu Sep 12 14:15:53 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id OAA04139
          for hackers-outgoing; Thu, 12 Sep 1996 14:15:53 -0700 (PDT)
Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA04129
          for <freebsd-hackers@freebsd.org>; Thu, 12 Sep 1996 14:15:49 -0700 (PDT)
Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <15909(1)>; Thu, 12 Sep 1996 14:13:15 PDT
Received: by crevenia.parc.xerox.com id <177595>; Thu, 12 Sep 1996 14:12:52 -0700
From: Bill Fenner <fenner@parc.xerox.com>
To: karl@mcs.net, terry@lambert.org
Subject: Re: SYN Resisting (fwd)
Cc: avalon@coombs.anu.edu.au, freebsd-hackers@freebsd.org, koshy@india.hp.com
Message-Id: <96Sep12.141252pdt.177595@crevenia.parc.xerox.com>
Date: Thu, 12 Sep 1996 14:12:50 PDT
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>Like you are probably ignoring source quench.

Source quenches are deprecated by RFC1812.  RFC1122 is still the host
requirements RFC so technically hosts must still pay attention to them,
but routers are not supposed to send them.

4.3.3.3 Source Quench
   
   A router SHOULD NOT originate ICMP Source Quench messages.
...
   DISCUSSION 
      Research seems to suggest that Source Quench consumes network
      bandwidth but is an ineffective (and unfair) antidote to
      congestion.  See, for example, [INTERNET:9] and [INTERNET:10].
      Section [5.3.6] discusses the current thinking on how routers  
      ought to deal with overload and network congestion.

  Bill