The RFC Archive
 The RFC Archive   RFC 73   « Jump to any RFC number directly 
 RFC Home
Full RFC Index
Recent RFCs
RFC Standards
Best Current Practice
RFC Errata
1 April RFC



IETF RFC 73

Response to NWG/RFC 67

Last modified on Friday, January 16th, 1998

Permanent link to RFC 73
Search GitHub Wiki for RFC 73
Show other RFCs mentioning RFC 73







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 top


Response to NWG/RFC 67 RFC TOTAL SIZE: 1268 bytes PUBLICATION DATE: Friday, January 16th, 1998 LEGAL RIGHTS: The IETF Trust (see BCP 78)


RFC-ARCHIVE.ORG

© RFC 73: The IETF Trust, Friday, January 16th, 1998
© the RFC Archive, 2024, RFC-Archive.org
Maintainer: J. Tunnissen

Privacy Statement