Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!VAX.FTP.COM!stev
From: stev@VAX.FTP.COM
Newsgroups: comp.protocols.tcp-ip
Subject: Re:  tcp port numbers
Message-ID: <9001171410.AA09018@vax.ftp.com>
Date: 17 Jan 90 14:10:27 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 27

>  Now I have beaucoup messages from
>  various blankity-blank Peesee's in a log on our network test machine.
>  Of course all the other systems on the net get to handle these
>  interrupts too.
>  
>  A way to stop this noise is to send the data back to them.  Yuck, yuck.
>  
>  We could call it "Well Known Socket Protection".
>  
>  Phil
>  

i understand you are kidding, phil, but before anyone decides to go give
this a try, you should consider that you are voilating the paradym as badly
as they are (hope the spelling is correct there, someone ran off with the
dictionary). while it *seems* like a good idea at the beginning, and one
could argue that is you are only replying to the hosts that generate traffic
to the discard socket with the broadcast address, it is still a bad idea to
lower ones self to their level.


personally, i liked the idea of charging back for the packets:)


stev knowles
ftp software
stev@ftp.com