The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
* [TUHS] Research Datakit notes
@ 2022-07-03 17:54 Geoff Pool
  0 siblings, 0 replies; 2+ messages in thread
From: Geoff Pool @ 2022-07-03 17:54 UTC (permalink / raw)
  To: tuhs

[-- Attachment #1: Type: text/plain, Size: 263 bytes --]

I've enjoyed reading this thread as networking has always been a passion of
mine.  Lawrence Livermore had, at one time, their own networking system
they called Spider.  Is this the same Spider technology that Sandy Fraiser
references in his Datakit notes?


[-- Attachment #2: Type: text/html, Size: 319 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [TUHS] Research Datakit notes
@ 2022-06-25 23:01 Paul Ruizendaal
  0 siblings, 0 replies; 2+ messages in thread
From: Paul Ruizendaal @ 2022-06-25 23:01 UTC (permalink / raw)
  To: tuhs

Wanted to post my notes as plain text, but the bullets / sub-bullets get lost.

Here is a 2 page PDF with my notes on Research Datakit:

The main takeaway is that connection build-up and tear-down is considerably more expensive than with TCP. The first cost is in the network, which builds up a dedicated path for each connection. Bandwidth is not allocated/reserved, but a path is and routing information is set up at each hop. The other cost is in the relatively verbose switch-host communication in this phase. This compares to the 3 packets exchanged at the hosts’ driver level to set up a TCP connection, with no permanent resources consumed in the network.

In compensation, the cost to use a connection is considerably lower: the routing is known and the host-host link protocol (“URP") can be light-weight, as the network guarantees in-order delivery without duplicates but packets may be corrupted or lost (i.e. as if the connection is a phone line with a modem). No need to deal with packet fragmentation, stream reassembly and congestion storms as in the TCP of the early 80’s.

Doing UDP traffic to a fixed remote host is easily mapped to using URP with no error correction and no flow control. Doing UDP where the remote host is different all the time is not practical on a Datakit network (i.e. a virtual circuit would be set up anyway).

A secondary takeaway is that Research Datakit eventually settled on a three-level ascii namespace: “area/trunk/switch”. On each switch, the hosts would be known by name, and each connection request had a service name as parameter. In an alternate reality we would maybe have used “ca/stclara/mtnview!google!www” to do a search.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2022-07-03 17:55 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-07-03 17:54 [TUHS] Research Datakit notes Geoff Pool
  -- strict thread matches above, loose matches on Subject: below --
2022-06-25 23:01 Paul Ruizendaal

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).