summaryrefslogtreecommitdiff
path: root/doc/rfc/rfc582.txt
diff options
context:
space:
mode:
Diffstat (limited to 'doc/rfc/rfc582.txt')
-rw-r--r--doc/rfc/rfc582.txt59
1 files changed, 59 insertions, 0 deletions
diff --git a/doc/rfc/rfc582.txt b/doc/rfc/rfc582.txt
new file mode 100644
index 0000000..a773593
--- /dev/null
+++ b/doc/rfc/rfc582.txt
@@ -0,0 +1,59 @@
+
+
+
+
+
+
+Network Working Group R. Clements
+Request for Comments: 582 BBN-TENEX
+NIC: 19962 5 November 1973
+
+
+ Comments on RFC 580 -
+ Machine Readable Protocols
+
+ I fully support the requirement for machine-readable protocol
+ documents. In my situation, the line-printer is a much more reliable
+ device than the copying machine.
+
+ However, I object to the phrase "preferably as nls files" in RFC 580.
+ My objection is based on the lack of conversion mechanisms INTO NLS,
+ not to the retrieval process or NLS itself.
+
+ Most sites have their own text editors and RUNOFF's (or their
+ equivalents). Most large protocol documents are prepared at least
+ partially by secretarial help. Those persons should be able to
+ prepare the documents in the home machine (or wherever) in languages
+ with which they are familiar. There should be a general program
+ (preferably clever, but at least generally available and predictable)
+ for converting nicely formatted text to NLS files.
+
+ Perhaps the program which receives mail for the journal will do the
+ trick; if so it needs further documentation beyond the mail-oriented
+ RFC 543, and its existence and usage need to be publicised.
+
+ RECEIVED AT NIC NOVEMBER 14, 1973.
+
+
+ [ This RFC was put into machine readable form for entry ]
+ [ into the online RFC archives by Lorrie Shiota 1/02 ]
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Clements [Page 1]
+