diff options
author | Thomas Voss <mail@thomasvoss.com> | 2024-11-27 20:54:24 +0100 |
---|---|---|
committer | Thomas Voss <mail@thomasvoss.com> | 2024-11-27 20:54:24 +0100 |
commit | 4bfd864f10b68b71482b35c818559068ef8d5797 (patch) | |
tree | e3989f47a7994642eb325063d46e8f08ffa681dc /doc/rfc/rfc73.txt | |
parent | ea76e11061bda059ae9f9ad130a9895cc85607db (diff) |
doc: Add RFC documents
Diffstat (limited to 'doc/rfc/rfc73.txt')
-rw-r--r-- | doc/rfc/rfc73.txt | 59 |
1 files changed, 59 insertions, 0 deletions
diff --git a/doc/rfc/rfc73.txt b/doc/rfc/rfc73.txt new file mode 100644 index 0000000..7ee3c8d --- /dev/null +++ b/doc/rfc/rfc73.txt @@ -0,0 +1,59 @@ + + + + + + +Network Working Group S. Crocker +Request for Comments #73 UCLA + 25 Sept. 70 + + Response to NWM/RFC #67 + +Bill's suggestion is a good one; however, my current policy is to +encourage the most rapid implementation of the protocol in document +#1, and his suggested modification should be delayed. It seems to me +most important to gain experience using the network before making +changes to the protocol which are not dictated by necessity. (I +polled several sites regarding Bill's suggestion. Sites with NCP +implementations under way tended to agree with this policy, while +sites further behind tended to desire Bill's suggested change.) + +With respect to changes, in general, I believe that changes are +necessary to improve the efficiency, provide greater flexibility, and +guarantee reliability. Many of us can suggest changes now, but I +suspect that clearer ideas will emerge from usage. + + [ This RFC was put into machine readable form for entry ] + [ into the online RFC archives by Josh Elliott 1/98 ] + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + [Page 1] + |