[mod.protocols.tcp-ip] Getting info to non-arpanauts

geof@MIT-BORAX.ARPA (Geoffrey H. Cooper) (01/16/86)

Noel Chiappa expressed a concern about getting information to non-arpanet
subscribers about current ideas from the mainstream tcp world.  I think
that his idea of using usenet is a great one.  The TCP-IP list is
carried on usenet as mod.protocols.tcp-ip.  I don't know exactly how
this forwarding is set up (since mod.... means that it is supposed to be 
a moderated list, and I didn't think that the arpanet one was moderated),
but it would be a great boon to those of us who mostly (or entirely) rely
on UUCP links if RFC's were automatically fed down the pipe.  We might
avoid sending very long ones (>60 pages or so) for evfficiency reasons.

[Please respond to the list, since incoming mail is flakey for me
theseedays]

- Geof Cooper
  Imagen

tcp-ip@ucbvax.UUCP (01/17/86)

A year or two ago I posted copies of the IP, ICMP, TCP, UDP, TELNET, and
FTP RFCs, as well as a few other ones like RFC822, to the USENET
net.sources group (which is where big things like that get posted).

It may be time to do that again.  I'll confer with the moderator of the
USENET mod.sources group to see what he thinks, and if he approves, this
will be a reasonable way to spread the gospel.

Wouldn't be too bad an idea if Berkeley would include some of these with
their distribution tape either.  They already send RFC822 (I think) with
it so people will understand the 'sendmail' program better.

	Brian Kantor	UCSD Office of Academic Computing
			Academic Network Operations Group  
			UCSD B-028, La Jolla, CA 92093 (619) 452-6865

	decvax\ 	brian@sdcsvax.ucsd.edu
	ihnp4  >---  sdcsvax  --- brian
	ucbvax/		Kantor@Nosc