Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!decvax!decwrl!pyramid!pesnta!hplabs!ucbvax!XEROX.COM!Murray.pa
From: Murray.pa@XEROX.COM.UUCP
Newsgroups: mod.protocols.tcp-ip
Subject: Re: Port Collisions
Message-ID: <860514-023737-4874@Xerox>
Date: Wed, 14-May-86 05:37:25 EDT
Article-I.D.: Xerox.860514-023737-4874
Posted: Wed May 14 05:37:25 1986
Date-Received: Thu, 15-May-86 23:47:59 EDT
References: <860513093608.7.MARGULIES@REDWING.SCRC.Symbolics.COM>
Sender: usenet@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 14
Approved: tcp-ip@sri-nic.arpa

One word of caution.... Xerox managed to get off on the wrong foot in
the Ethernet packet type assignment business.

If you administer a group of ports, I suggest that the ground rules
include publishing a who-to-contact as well as a simple (one line?)
description of its function. Otherwise people will flame at you when you
won't answer questions.

The proprietary aspect might complicate that attitude. I don't think
that objection really holds water. It's too easy to look at the bits on
an ethernet.

I like your second suggestion, but somebody is bound to ignore it
because it takes an extra packet to get started.