<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.6000.16441" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV>
<DIV><STRONG><FONT face=Arial size=2> In keeping with the tradition of this
list, with has historically</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=Arial size=2>dealt with development of Jnos and adding
protocol features</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=Arial size=2>to it to make it more "Network Realistic"
in both the Internet</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=Arial size=2>and Amprnet (RF) domains, I have a
request for a protocol</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=Arial size=2>that has long been
missing.</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=Arial size=2></FONT></STRONG> </DIV>
<DIV><STRONG><FONT face=Arial size=2> Although the current direction of
Jnos development by means</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=Arial size=2>of strictly porting to alternate (Yet
statistically irrelevent) operating</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=Arial size=2>systems, and adding more ATTACH features
such as various</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=Arial size=2>wideband HF modes to keep with the winlink
trend is interesting,</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=Arial size=2>what HAS </FONT></STRONG><STRONG><FONT
face=Arial size=2>been missing over the years is DHCP. Being a
NOS</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=Arial size=2>fundamentalist,
</FONT></STRONG><STRONG><FONT face=Arial size=2>gaining internet acces from DOS
by merely</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=Arial size=2>attaching a packet
</FONT></STRONG><STRONG><FONT face=Arial size=2>driver and issuing 3 or 4
autoexec commands,</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=Arial size=2>I find the </FONT></STRONG><STRONG><FONT
face=Arial size=2>need to boot windows to get my LAN assigned a
public</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=Arial size=2>IP address to be quite bothersome. Not to
mention if those</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=Arial size=2>addresses are not Re-Leased in a certain
amount of time they</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=Arial size=2>are lost and another is assigned from the
pool to replace it on the next</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=Arial size=2>DHCP query. Not only would this complete
the simplicty and elegance</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=Arial size=2>of an internet accessible DOS gateway, it
would also bring much more</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=Arial size=2>functionality to RF radio networks. No
longer would end users need</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=Arial size=2>to query a "IP designator" by E-mail and
wait day or weeks</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=Arial size=2>(Depending on the integration of this hobby
into the IP assignor)</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=Arial size=2>rather all they need do is send out the
same type of request on the RF</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=Arial size=2>network as my Windows IP stack does on my
LAN and the IP coordinator's</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=Arial size=2>DHCP server would handle the
rest.</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=Arial size=2></FONT></STRONG> </DIV>
<DIV><STRONG><FONT face=Arial size=2>Pretty Please with sugar on
top?</FONT></STRONG></DIV>
<DIV><STRONG><FONT face=Arial size=2></FONT></STRONG> </DIV>
<DIV><STRONG><FONT face=Arial size=2>Steven - N1OHX</FONT></STRONG></DIV>
<DIV> </DIV></DIV></BODY></HTML>