summaryrefslogtreecommitdiff
path: root/doc/rfc/rfc548.txt
diff options
context:
space:
mode:
Diffstat (limited to 'doc/rfc/rfc548.txt')
-rw-r--r--doc/rfc/rfc548.txt59
1 files changed, 59 insertions, 0 deletions
diff --git a/doc/rfc/rfc548.txt b/doc/rfc/rfc548.txt
new file mode 100644
index 0000000..3508281
--- /dev/null
+++ b/doc/rfc/rfc548.txt
@@ -0,0 +1,59 @@
+
+
+
+
+
+
+Network Working Group D. Walden
+RFC # 548 BBN-NET
+NIC # 17794 August 16, 1973
+
+
+ Hosts Using the IMP Going Down Message
+
+
+ As given in BBN Report 1822 (Specifications for the Interconnection
+of a Host and an IMP), IMP to Host message type 2 specifies that the IMP
+local to the Host is going down; the message further says when the IMP
+is going down, for how long, and why.
+
+ When the IMP goes down after sending the IMP Going Down message to
+the Host, the Host's network users and local users of the network will
+not, in general, be forewarned unless the Host sends a message to these
+users. We therefore urge all Hosts to warn their network users and
+users of the network of impending IMP downs; just logging the received
+IMP Going Down message on a logging teletype, as many Hosts currently
+do, seems insufficient.
+
+ Incidentally, please remember that Tuesday mornings from 7 a.m. to 9
+a.m. (Eastern Time) are reserved for Network Software Maintenance, as
+announced in RFC #440.
+
+
+
+
+
+
+
+
+
+
+ [ This RFC was put into machine readable form for entry ]
+ [ into the online RFC archives by Alex McKenzie with ]
+ [ support from GTE, formerly BBN Corp. 10/99 ]
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Walden [Page 1]
+