Tech-invite3GPPspaceIETFspace
96959493929190898887868584838281807978777675747372717069686766656463626160595857565554535251504948474645444342414039383736353433323130292827262524232221201918171615141312111009080706050403020100
in Index   Prev   Next

RFC 0073

Response to NWG/RFC 67

Pages: 1
Unclassified

ToP   noToC   RFC0073 - Page 1
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 ]