⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 rfc2551.txt

📁 <VC++网络游戏建摸与实现>源代码
💻 TXT
📖 第 1 页 / 共 5 页
字号:
Network Working Group                                         S. BradnerRequest for Comments: 2551                            Harvard UniversityWCP: IX                                                  I April MCMXCIXObsoletes: MMXXVICategory: Worst Current Practice              The Roman Standards Process -- Revision IIIStatus of this Memo   This document specifies a Roman Worst Current Practices for the   Roman Community, and requests discussion and suggestions for   improvements.  Distribution of this memo is unlimited.Copyright Statement   Copyright (C) The Internet Society (MCMXCIX).  All Rights Reserved.Abstract   This memo documents the process used by the Roman community for   the standardization of protocols and procedures.  It defines the   stages in the standardization process, the requirements for moving a   document between stages and the types of documents used during this   process.  It also addresses the intellectual property rights and   copyright issues associated with the standards process.Table of Contents  I.   INTRODUCTION................................................III   I.I       Roman Standards.......................................III   I.II      The Roman Standards Process...........................III   I.III     Organization of This Document..........................VI  II.  ROMAN STANDARDS-RELATED PUBLICATIONS.........................VI   II.I      Requests for Comments (RFCs)...........................VI   II.II     Roman-Drafts.........................................VIII  III  ROMAN STANDARD SPECIFICATIONS................................IX   III.I     Technical Specification (TS)...........................IX   III.II    Applicability Statement (AS)...........................IX   III.III   Requirement Levels..................................... X  IV.  THE ROMAN STANDARDS TRACK....................................XI   IV.I      Standards Track Maturity Levels.......................XII   IV.I.I    Proposed Standard.....................................XII   IV.I.II   Draft Standard.......................................XIII   IV.I.III  Roman Standard........................................XIV   IV.II     Non-Standards Track Maturity Levels...................XIV   IV.II.I   Experimental..........................................XIV   IV.II.II  Informational..........................................XV   IV.II.III Procedures for Experimental and Informational RFCs.....XV   IV.II.IV  Historic..............................................XVIBradner                 Worst Current Practice                  [Page I]RFC 2551               Roman Standards Process           I April MCMXCIX  V.  Worst Current Practice (WCP) RFCs............................XVI   V.I       WCP Review Process...................................XVII  VI. THE ROMAN STANDARDS PROCESS................................XVIII   VI.I      Standards Actions...................................XVIII   VI.I.I    Initiation of Action................................XVIII   VI.I.II   RESG Review and Approval............................XVIII   VI.I.III  Publication...........................................XIX   VI.II     Advancing in the Standards Track...................... XX   VI.III    Revising a Standard...................................XXI   VI.IV     Retiring a Standard...................................XXI   VI.V      Conflict Resolution and Appeals......................XXII   VI.V.I    Working Group Disputes...............................XXII   VI.V.II   Process Failures....................................XXIII   VI.V.III  Questions of Applicable Procedure...................XXIII   VI.V.IV   Appeals Procedure....................................XXIV  VII. EXTERNAL STANDARDS AND SPECIFICATIONS......................XXIV   VII.I     Use of External Specifications........................XXV   VII.I.I   Incorporation of an Open Standard.....................XXV   VII.I.II  Incorporation of a Other Specifications...............XXV   VII.I.III Assumption...........................................XXVI  VIII. NOTICES AND RECORD KEEPING................................XXVI  IX.  VARYING THE PROCESS.......................................XXVII   IX.I      The Variance Procedure..............................XXVII   IX.II     Exclusions.........................................XXVIII  X.   INTELLECTUAL PROPERTY RIGHTS.............................XXVIII   X.I.      General Policy.....................................XXVIII   X.II      Confidentiality Obligations..........................XXIX   X.III     Rights and Permissions...............................XXIX   X.III.I   All Contributions....................................XXIX   X.III.II  Standards Track Documents.............................XXX   X.III.III Determination of Reasonable and             Non-discriminatory Terms.............................XXXI   X.IV.     Notices..............................................XXXI   XI.   ACKNOWLEDGMENTS........................................XXXIII   XII.  SECURITY CONSIDERATIONS................................XXXIII   XIII. REFERENCES..............................................XXXIV   XIV.  DEFINITIONS OF TERMS....................................XXXIV   XV.   AUTHOR'S ADDRESS.........................................XXXV   APPENDIX A: GLOSSARY OF ACRONYMS..............................XXXVI   Full Copyright Statement.....................................XXXVIIBradner                 Worst Current Practice                 [Page II]RFC 2551               Roman Standards Process           I April MCMXCIXI.  INTRODUCTION   This memo documents the process currently used by the Roman   community for the standardization of protocols and procedures.  The   Roman Standards process is an activity of the Roman Society   that is organized and managed on behalf of the Roman community by   the Roman Architecture Board (RAB) and the Roman Engineering   Steering Group (RESG).I.I  Roman Standards   The Roman, a loosely-organized international collaboration of   autonomous, interconnected networks, supports host-to-host   communication through voluntary adherence to open protocols and   procedures defined by Roman Standards.  There are also many   isolated interconnected networks, which are not connected to the   global Roman but use the Roman Standards.   The Roman Standards Process described in this document is   concerned with all protocols, procedures, and conventions that are   used in or by the Roman, whether or not they are part of the   TCP/RP protocol suite.  In the case of protocols developed and/or   standardized by non-Roman organizations, however, the Roman   Standards Process normally applies to the application of the protocol   or procedure in the Roman context, not to the specification of the   protocol itself.   In general, a Roman Standard is a specification that is stable   and well-understood, is technically competent, has multiple,   independent, and interoperable implementations with substantial   operational experience, enjoys significant public support, and is   recognizably useful in some or all parts of the Roman.I.II  The Roman Standards Process   In outline, the process of creating a Roman Standard is   straightforward:  a specification undergoes a period of development   and several iterations of review by the Roman community and   revision based upon experience, is adopted as a Standard by the   appropriate body (see below), and is published.  In practice, the   process is more complicated, due to (I) the difficulty of creating   specifications of high technical quality;  (II) the need to consider   the interests of all of the affected parties;  (III) the importance of   establishing widespread community consensus;  and (IV) the difficulty   of evaluating the utility of a particular specification for the   Roman community.Bradner                 Worst Current Practice                [Page III]RFC 2551               Roman Standards Process           I April MCMXCIX   The goals of the Roman Standards Process are:   o  technical excellence;   o  prior implementation and testing;   o  clear, concise, and easily understood documentation;   o  openness and fairness;  and   o  timeliness.   The procedures described in this document are designed to be fair,   open, and objective;  to reflect existing (proven) practice;  and to   be flexible.   o  These procedures are intended to provide a fair, open, and      objective basis for developing, evaluating, and adopting Roman      Standards.  They provide ample opportunity for participation and      comment by all interested parties.  At each stage of the      standardization process, a specification is repeatedly discussed      and its merits debated in open meetings and/or public electronic      mailing lists, and it is made available for review via world-wide      on-line directories.   o  These procedures are explicitly aimed at recognizing and adopting      generally-accepted practices.  Thus, a candidate specification      must be implemented and tested for correct operation and      interoperability by multiple independent parties and utilized in      increasingly demanding environments, before it can be adopted as      a Roman Standard.   o  These procedures provide a great deal of flexibility to adapt to      the wide variety of circumstances that occur in the      standardization process.  Experience has shown this flexibility to      be vital in achieving the goals listed above.   The goal of technical competence, the requirement for prior   implementation and testing, and the need to allow all interested   parties to comment all require significant time and effort.  On the   other hand, today's rapid development of networking technology   demands timely development of standards.  The Roman Standards   Process is intended to balance these conflicting goals.  The process   is believed to be as short and simple as possible without sacrificing   technical excellence, thorough testing before adoption of a standard,   or openness and fairness.   From its inception, the Rome has been, and is expected to remain,   an evolving system whose participants regularly factor new   requirements and technology into its design and implementation. Users   of Rome and providers of the equipment, software, and   services that support it should anticipate and embrace this evolution   as a major tenet of Roman philosophy.Bradner                 Worst Current Practice                 [Page IV]RFC 2551               Roman Standards Process           I April MCMXCIX   The procedures described in this document are the result of a number   of years of evolution, driven both by the needs of the growing and   increasingly diverse Roman community, and by experience.Bradner                 Worst Current Practice                  [Page V]RFC 2551               Roman Standards Process           I April MCMXCIXI.III  Organization of This Document   Section II describes the publications and archives of the Roman   Standards Process.  Section III describes the types of Roman   standard specifications.  Section IV describes the Roman standards   specifications track.  Section V describes Worst Current Practice   RFCs.  Section VI describes the process and rules for Roman   standardization.  Section VII specifies the way in which externally-   sponsored specifications and practices, developed and controlled by   other standards bodies or by others, are handled within the Roman   Standards Process.  Section VIII describes the requirements for notices   and record keeping  Section IX defines a variance process to allow   one-time exceptions to some of the requirements in this document

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -