Date of last change: 1/24/84 by Jerry Saltzer

Disclaimer:
This file is intended to document possible areas of changes in future
releases of the MIT IBM PC TCP/IP network programs. It is not necessarily
complete, but is intended to soften the impact of some changes and to give
users an idea of what to expect in the future. Also, the fact that a
possible change is mentioned in here does not mean that the change WILL
happen; it only means that it is something which we have thought of doing.
For areas of other possible changes, consult the bug list.

It is likely that the custom structure will change between releases. This
affects the files include/custom.h and net/net/netcrt.a86. Also, the
customizer will change and no new programs will be customizable with the old
customizer. Of course, pieces of code which use the changed parts of the
custom structure will change (or be added).

There is a (very slight) chance that internet/icmp will be modified to
upcall the client on receipt of an icmp destination unreachable. This would
change the in_open() call and require each higher layer (tcp, udp, rvd) to
have a handler for the upcall. Plus, tcp or udp should propagate this
information to their clients (telnet, tftp, etc).

Some changes might happen to tcp. The most important one, and hardest one,
is making it handle multiple connections. This would change the interface
specifications to the entire tcp layer, but at least they'd probably change
in a consistent way. It would also cause lots of internal changes to tcp.
We might also add a tiny whois server to tcp which would allow people to say
"whois @random-pc" and get a reply.

