Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site mit-vax.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!mit-vax!romkey
From: romkey@mit-vax.UUCP (John Romkey)
Newsgroups: net.micro,net.lan
Subject: Re: License violation detection
Message-ID: <117@mit-vax.UUCP>
Date: Mon, 7-Apr-86 23:44:55 EST
Article-I.D.: mit-vax.117
Posted: Mon Apr  7 23:44:55 1986
Date-Received: Thu, 10-Apr-86 00:47:56 EST
References: <141@suneast.uucp> <20520@styx.UUCP> <136@brl-sem.ARPA> <612@nrcvax.UUCP>
Reply-To: romkey@mit-vax.UUCP (John Romkey)
Organization: MIT, Cambridge, MA
Lines: 26
Xref: watmath net.micro:14282 net.lan:1410

In article <612@nrcvax.UUCP> andre@nrcvax.UUCP (Andre Hut) writes:
>In article <136@brl-sem.ARPA> ron@brl-sem.ARPA (Ron Natalie <ron>) writes:
>>In article <20520@styx.UUCP>, fair@styx.UUCP (Erik E. Fair) writes:
>>> Fundamental question to ask:
>>> 	what happens to a UDP packet recieved on a port for which there is
>>> 	no process listening?
>>> Answer: packet gets thrown away.
>>
>>Guess again, chucko.  You may get an ICMP Destination Port Unreachable
>>message in return (you do on the VAX).
>
>"Chucko" ????
>
>You are BOTH right.  The packet is thrown away, and an ICMP message should
>be sent back.

Hang on there a minute. Normally an ICMP port or protocol unreachable
would be generated, HOWEVER, this conversation originated from a message
about *broadcasting* a packet to the UDP Discard port. Good IP
implementations should NEVER send ICMP errors in response to broadcast
packets.

John Romkey			FTP Software, Inc.
(617) 868-4878			PO Box 150
UUCP: romkey@mit-vax.UUCP	Kendall Square Branch
ARPA: romkey@borax.lcs.mit.edu	Boston, MA, 02142