Organization: China Interactive Publishing Network (
RFC Document Chinese Translation Program (http://www.china-pub.com/compters/emook/aboutemook.htm
E-mail: Ouyang@china-pub.com
Translator: Dong Guard (CNCHRIS DUKE913@163.com)
Translation time: 2001-10-1
Copyright: This Chinese translation copyright belongs to China Interactive Publishing Network. Can be used for non-commercial use free reprint, but the translation and copyright information of this document must be retained.
Network Working Group Robert D. BRESSLER
Request for Comments # 72 m.i.t./project Mac
September 28, 1970
Advise to network protocol changes
(Proposed Moratorium On Changes to Network Protocol)
Bill Crowther RFC67 proposes a more basic problem than the printing issue. Any changes to existing protocols will affect the results of hardware and software development - some have lasteded six months. In Multics Regardless of the completed or in the later debugging phase will be affected by him. This is undoubtedly a fact in other places.
Now talking about this problem is not to say that the existing agreement is perfect, but it has already admitted that he is available and began to implement him. Therefore, we recommend that most of the next six months will ban this agreement. Change, or, no matter how long, we let him run and learn more of him more.
This special referral, if some changes are just to affect the efficiency and convenience of implementation. If the main error in the design is discovered, it should be proposed and considered for the symbolic extension of the existing system. However, ,
The details of existing systems cannot be changed.
There is a point to this argument.
[First page]
Network Working Group RFC 72 Robert D. BRESSLER
The first point, it may be the most important thing is: To make the system work as soon as possible. The main benefits will be played in using his place, and the network is only available in use. We feel that in the future The work of re-writing some NCP will not be questioned, but it will be slightly negligible than the role of network use and high-rise network compared to another road.
Another problem that appears immediately is: What issues can constitute a formal change? The history of current agreement development shows that whenever a suggestion is proposed, it will be modified multiple times, and finally it can be recognized. So each of the relevant changes It is possible to prevent the development of the plan for several months.
The final factor is that some ideas may be discovered in the final implementation. It has agreed that people currently start discussing, and comprehensive testing will also be launched.
We believe that these factors have been important enough to freeze the network protocol unless the problem is serious to some functions. Some modifications will be kept to the real network operation.
[Page 2]
Network Working Group RFC 72 Robert D. BRESSLER
This is not to say that new ideas and opinions cannot be proposed, but it should be understood when it is proposed. They are discussed just in the future, but they are not right. This idea may be reflected by such a literature. "After prohibiting the change Suggestions on ...
[This RFC WAS PUT INTO MACHINE READABLE FORM for Entry]
[INTO THE Online RFC Archives BY Bob Hinden 6/97] [Page 3]
Copyright statement
Copyright (c) The Internet Society (2001). All Rights Reserved.
THIS Document And Translations of It May Be Copied and Furnished To
Others, And DeriVative Works That Comment On or OtherWise Explain IT
OR Assist in ITS Implementation May Be Prepared, Copied, Published
And Distributed, in Whole or in Part, WITHOUT RESTRICTION OF ANY
Kind, Provided That The Above Copyright Notice and this Paragraph Are
Included on All Such Copies and DeriVative Works. However, this
Document Itself May Not Be Modified in Any Way, Such as by Removing
The Copyright Notice Or References To The Internet Society or Other
Internet Organizations, Except As Needed for the purpose of
Developing Internet Standards in Which Case the Procedures for
Copyrights Defined in The Internet Standards Process Must Be
Followed, or as required to translate it inTo languages Other Than
ENGLISH.
THE LIMITED Permissions Grand Above Are Perpetual and Will Not Be
REVOKED by the Internet society or its surcessors or associgns.
This Document and the information contained here0 is provided on an
"As IS" Basis and the Internet Society and the Internet Engineering
Task Force Disclaims All Warranties, Express or Implied, Including
But not limited to any warranty That The Use of the information
Herein Will Not Infringe Any Rights or Any Implied Warranties of
Merchantability or fitness for a particular purpose.
Thank you
Funding for the RFC Editor Function Is Currently Provided by The Internet Society.
