Date: Thu, 14 Oct 93 04:30:01 PDT
From: Advanced Amateur Radio Networking Group <tcp-group@ucsd.edu>
Errors-To: TCP-Group-Errors@UCSD.Edu
Reply-To: TCP-Group@UCSD.Edu
Precedence: Bulk
Subject: TCP-Group Digest V93 #267
To: tcp-group-digest
TCP-Group Digest Thu, 14 Oct 93 Volume 93 : Issue 267
Today's Topics:
bootp on KA9Q
Packet Standards
Send Replies or notes for publication to: <TCP-Group@UCSD.Edu>.
Subscription requests to <TCP-Group-REQUEST@UCSD.Edu>.
Problems you can't solve otherwise to brian@ucsd.edu.
Archives of past issues of the TCP-Group Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives".
We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party. Your mileage may vary. So there.
----------------------------------------------------------------------
Date: Wed, 13 Oct 1993 10:43:37 +0000 (GMT)
From: Janos Mohacsi <mohacsi@bagira.fsz.bme.hu>
Subject: bootp on KA9Q
To: tcp-group@ucsd.edu
Hi everyone,
I would like to use bootp (the client) on KA9Q.
I started a bootp server on a SUN. And I tried the following
configuration (autoexec.net):
attach packet 0x60 ethernet 15 1500
route add 255.255.255.255 ethernet
arp add 255.255.255.255 ethernet ff:ff:ff:ff:ff:ff
bootp
When I start this config the KA9Q start requesting bootp answers but
as I see nothing happens on the Ethernet. What should I change?
How to configure KA9Q to use bootp?
Thanks a lot,
Janos Mohacsi
P.S.: Bootp server is working, because it serves other hosts also
(running NCSA telnet)
------------------------------
Date: Wed, 13 Oct 93 11:44:57 BST
From: eeyimkn@unicorn.ccc.nottingham.ac.uk (Mike Knell)
Subject: Packet Standards
To: tcp-group@ucsd.edu
(Copy to: tcp-group@ucsd.edu, rec.radio.amateur.digital.misc, AUTHOR@WW)
Hi people,
At the recent UK Sysop's meeting, it was decided that it was time to
start working towards a unified system for the publication of the
various standards used in packet. I, for my sins, have been given this
job :-)
At the moment, it can be difficult or impossible to find those
standards documents that do exist for packet radio, as they have
either never been written or are tucked away on obscure FTP archives..
When a new software author wants to find out how the forwarding
protocols work, and the real nitty-gritty such as "how many characters
may a BID have?" it can be impossible to find out. It's a shame, as
this will only breed lots of new mutually incompatible systems. We've
seen the beginning of this already with the FBB/NNA forwarding thing,
and the BID question provoked a huge flamewar recently on the UK
network.. :-(
What I'd like to start is an RFC-like system for making sure that
people publish their standards. The way it works is thus:
* Authors and other people developing new systems or protocols are
encouraged to document them fully and send them in for adding to the
standards library.
* New standards are numbered, a la RFC, and added to the archive for
public access by anyone interested.
* When a standard is superseded or updated, a new document is
published and the old one marked as superseded.
* Editorial control of documents remains with the authors.
Simple and hopefully effective. I know that there are standards
written already for things like AX25, MBL forwarding, and the such,
but for anything that there isn't one for, it would be kind of nice to
get one written - any volunteers? Anybody with anything they've been
hiding away which they've been meaning to release, also get in touch.. :-)
Note that virtually anything is acceptable, a few poems would go down
just fine.. *grin*
We aren't going to be able to call them RFCs, as the Internet has them
already, so a suitable acronym needs to be thought up. Let me know
your ideas! A few to get started..
RFF - Request for Flames
RFHM - Request for Hate Mail
and so on..
The archive would be available by anonymous FTP (anyone got any spare
space? Give me a shout.. :-) ), and from packet BBSs by CLIVE server
or REQFIL..
I think it's a great idea. A set of canonical documents for packet is
long overdue.. Comments, suggestions, flames, welcome, to any of the
addresses below...
73 Mike G7GPA
UK Packet Standards Coordinator
+--------------------------- O Mike Knell, University of Nottingham, UK -+
| Nevertheless.. -/ \- Internet: eeyimkn@unicorn.nott.ac.uk |
| the Turtle Moves! -\_/- AX25: g7gpa@gb7bad.#23.gbr.eu |
+--M.T.V. - GET OFF THE AIR!-- | AMPRnet: mpk@hobbes.g7gpa.ampr.org -------+
------------------------------
End of TCP-Group Digest V93 #267
******************************
******************************