zweig@casca.cs.uiuc.edu (Johnny Zweig) (03/15/90)
[ IMPORTANT NOTE: Due to a stupid mistake on my part, the list as it
stood on 14 MAR 90 was lost. I apologize profusely (you can send
flowers to the sysadmin who doesn't do daily incrementals any more).
Everyone who asked to be added please ask again -- I'll be more
careful from now on. ]
This is the second announcement of the creation of a mailing list (a
reflector, to be precise) for the discussion of issues relating to
using ISDN as a transport mechanism for TCP/IP traffic. The list is a
means for people implementing systems to communicate with one another,
as well as to discuss issues peculiar to using moderately-fast
point-to-point reconfigurable serial links for internetworking.
Since different configurations allow different techniques for sending
the data (for example, a single workstation that dials up a server
directly would be able to elide IP-headers and most of the information
in each TCP-header as communication progresses).
As a favor to anyone who has trouble with mail aliases longer than 8
characters (or who just hates to type long names), the group is called
"tcp-isdn" rather than "tcp-ip-isdn" (*). Requests to be added to the
list should be sent to:
tcp-isdn-request@brutus.cs.uiuc.edu
Articles to be distributed to everyone on the list should be sent to
tcp-isdn@brutus.cs.uiuc.edu
(Notice, for those who usually send to user@cs.uiuc.edu, that the word
"brutus" is _not_ optional!)
Johnny List
(*) I opted against IP-ISDN since I think that using ISDN as a transport
mechanism for IP-datagrams ("ISDN as Ethernet") is only one of a number
of interesting ways of doing things, and didn't want to express a bias.