BN> No problem. RFC1700 was written in 1994. Possibly the use
BN> of port 1235 by JNOS predates that (I don't have copies of
BN> the older ones which 1700 replaced to see if this was even
BN> covered earlier. I expect it was not.)
I never even realized that the callbook server port was formalized in an RFC.
In NOS, the "remote" service was assigned onto port 1234, which was chosen for
obvious reasons. However, the "remote" service (which allows kicking the TCP
timers, restarting the system, and so on) was entirely specific to NOS and no
one ever contemplated porting it to another system or submitting it for public
documentation and standardization. In fact, many people run the "remote"
service on an arbitrarily chosen port for added security, since it does allow
invasive operations such as remote rebooting.
Once "1234" was chosen for the proprietary "remote" service, other services
that got hacked into NOS informally were numbered sequentially by convention.
I think that the 1235 service was actually the "Buckmaster" callsign lookup
server, which was different than the telnet-like server under discussion, but
my memory grows dim on this point.
Heck, if anyone wants a nice port number for something related to amateur radio
and is planning to get it into an IANA RFC, I would suggest 7373.
-- Mike, N1BEE