143:
bits, with support for other word sizes provided by higher-level protocols. The connection was identified by a combination of the 16-bit addresses of each host and a 16-bit "connection index" assigned by each host to maintain uniqueness. "Controlled" packets within a connection were identified by a 16-bit packet number, which was used to deliver controlled packets reliably and in order, with re-transmission and flow control. "Uncontrolled" packets were not retransmitted, and were used at a lower level to support the flow-control and re-transmission. Chaosnet also supported "BRD" broadcast packets to multiple subnets.
147:"FILE" was a contact name for the Lisp Machine network file service. Other contact names included "SUPDUP", "MAIL", "NAME" for the Arpanet Finger protocol, "TIME", "SEND" for interactive messaging, "ARPA" for a gateway service to Arpanet. "DOVER" was the contact name for sending print jobs to Chaosnet hosts with a
142:
The
Chaosnet protocol identifies hosts by 16-bit addresses, 8 bits of which identify the subnet, 8 bits of which identify the host within the subnet. The basic protocol was a full-duplex reliable packet transmission between two user processes. The packet contents could be treated as bytes of 8 or 16
146:
Initial establishment of the connection was made using "contact names." These names identified the network service and higher-level protocol. For example, "STATUS" was the contact name which requested basic network statistics from a host. "TELNET" was a contact name for the
Arpanet TELNET protocol.
87:
range, that included a pseudo-slotted feature intended to reduce collisions, which worked by passing a virtual token of permission from host to host; successful packet transmissions updated each host's knowledge of which host had the token at that time. Collisions caused a host to fall silent for a
162:
Simple transactions could be completed by a single "RFC" packet containing a contact name, answered by a single "ANS" packet with the relevant information. For example, an RFC to contact name "TIME" would result in a single ANS packet containing a 32-bit number indicating the time.
91:
Chaosnet's network topology was usually series of linear (not circular) cables, each up to a maximum of a kilometer and roughly 12 clients. The individual segments were interconnected by "bridges" (much in the ARPANET mold), generally older computers like
159:, a new server for that protocol could be installed by creating a link to the program in the location DSK:DEVICE;CHAOS <cname> where <cname> was up to six letters of the contact name.
88:
duration depending on the distance from the host it collided with. Collisions were never a real problem, and the pseudo-slotting fell into disuse.
322:
31:
442:
462:
406:(Technical report). MIT AI Memos (1959–2004). Massachusetts Institute of Technology Artificial Intelligence Laboratory. AIM-628.
291:
156:
451:
80:
483:
37:
in 1975 and thereafter. It refers to two separate, but closely related, technologies. The more widespread was a set of
134:
uses a built-in pseudo-top-level-domain in the "CHAOS class" for retrieving information about a running DNS server.
434:
99:
The protocols were also later implemented as a payload that could be carried over
Ethernet (usually the later
27:
123:
111:
456:
305:
42:
326:
127:
50:
23:
115:
104:
295:
281:
277:
155:). Developers could easily experiment with new protocols by inventing new contact names. In
411:
446:
439:
477:
397:
167:
152:
185:
177:
46:
308:
285:
148:
170:
mentioned that it aimed to, among other things, support the
Chaosnet protocol.
66:
45:
intended to connect the then-recently developed and very popular (within MIT)
34:
401:
173:
118:(IP), and was recognized as one of the other network classes (other than "
119:
72:
38:
76:
300:
93:
468:
103:
variety). Chaosnet was specifically for LANs; features to support
131:
83:(TCP). It was a contention-based system intended to work over a
62:
181:
61:
The
Chaosnet protocol originally used an implementation over
184:
Chaosnet hardware and software implementation from the
110:
Chaosnet can be regarded as a contemporary of both the
423:
Online documentation from the ITS SYSDOC; directory
457:A better scan of AI Memo 628 than the one below
8:
323:"BIND 9 version 9.3.2 Manual / User Guide"
107:were left out for the sake of simplicity.
299:
463:Another place to get AI Memos 500 to 999
197:
287:Domain Names - Concepts and Facilities
26:technology. It was first developed by
49:; the second was one of the earliest
7:
380:
369:
358:
346:
264:
252:
240:
228:
216:
204:
114:protocols invented by PARC, and the
65:coaxial cable modeled on the early
435:Cisco's Implementation of Chaosnet
294:. p. 12. sec. 3.6.
14:
452:Another reference to AI Memo 628
53:(LAN) hardware implementations.
16:Local area networking technology
469:Chaosnet (Linux source driver)
1:
96:with two network interfaces.
81:Transmission Control Protocol
151:printer attached (an early
41:communication packet-based
500:
412:"CHAOS ORDER (chaord.57)"
440:Chaosnet implementations
30:and Jack Holloway at
484:Local area networks
445:2021-10-09 at the
282:"Resource Records"
128:Domain Name System
51:local area network
24:local area network
188:computer design.
176:, a maker of the
138:Chaosnet protocol
116:Internet Protocol
101:10 megabit/second
491:
422:
420:
418:
407:
383:
378:
372:
367:
361:
356:
350:
344:
338:
337:
335:
334:
325:. Archived from
319:
313:
312:
303:
301:10.17487/RFC1034
274:
268:
262:
256:
250:
244:
238:
232:
226:
220:
214:
208:
202:
102:
86:
71:
70:3 megabit/second
499:
498:
494:
493:
492:
490:
489:
488:
474:
473:
447:Wayback Machine
431:
426:
416:
414:
410:
396:
392:
387:
386:
379:
375:
368:
364:
357:
353:
345:
341:
332:
330:
321:
320:
316:
276:
275:
271:
263:
259:
255:, p. 3, 14
251:
247:
239:
235:
227:
223:
215:
211:
203:
199:
194:
180:, licensed the
140:
100:
84:
69:
59:
17:
12:
11:
5:
497:
495:
487:
486:
476:
475:
472:
471:
466:
460:
454:
449:
437:
430:
429:External links
427:
425:
424:
408:
398:Moon, David A.
393:
391:
388:
385:
384:
373:
362:
351:
339:
314:
269:
257:
245:
243:, pp. 6–8
233:
221:
209:
196:
195:
193:
190:
139:
136:
58:
55:
15:
13:
10:
9:
6:
4:
3:
2:
496:
485:
482:
481:
479:
470:
467:
464:
461:
458:
455:
453:
450:
448:
444:
441:
438:
436:
433:
432:
428:
413:
409:
405:
404:
400:(June 1981).
399:
395:
394:
389:
382:
377:
374:
371:
366:
363:
360:
355:
352:
348:
343:
340:
329:on 2006-07-18
328:
324:
318:
315:
310:
307:
302:
297:
293:
289:
288:
283:
279:
273:
270:
266:
261:
258:
254:
249:
246:
242:
237:
234:
230:
225:
222:
218:
213:
210:
206:
201:
198:
191:
189:
187:
183:
179:
178:Lisp machines
175:
171:
169:
168:GNU Manifesto
166:The original
164:
160:
158:
154:
153:laser printer
150:
144:
137:
135:
133:
129:
125:
121:
117:
113:
108:
106:
97:
95:
89:
82:
78:
74:
68:
64:
56:
54:
52:
48:
47:Lisp machines
44:
40:
36:
33:
29:
28:Thomas Knight
25:
21:
415:. Retrieved
402:
376:
365:
354:
349:, p. 10
342:
331:. Retrieved
327:the original
317:
286:
280:(Dec 1987).
272:
260:
248:
236:
224:
212:
200:
172:
165:
161:
145:
141:
109:
98:
90:
85:0–1000 meter
75:, the early
60:
19:
18:
278:Mockapetris
267:, p. 1
231:, p. 3
219:, p. 2
207:, p. 2
149:Xerox Dover
390:References
333:2009-10-28
126:") in the
67:Xerox PARC
381:Moon 1981
370:Moon 1981
359:Moon 1981
347:Moon 1981
265:Moon 1981
253:Moon 1981
241:Moon 1981
229:Moon 1981
217:Moon 1981
205:Moon 1981
174:Symbolics
43:protocols
478:Category
443:Archived
417:June 12,
403:Chaosnet
73:Ethernet
39:computer
20:Chaosnet
122:" and "
94:PDP-11s
77:ARPANET
79:, and
57:Origin
35:AI Lab
465:(FTP)
459:(pdf)
192:Notes
32:MIT's
22:is a
419:2013
309:1034
292:IETF
186:CADR
132:BIND
105:WANs
63:CATV
306:RFC
296:doi
182:MIT
157:ITS
112:PUP
480::
304:.
290:.
284:.
130:.
124:HS
120:IN
421:.
336:.
311:.
298::
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.