RFC 1602:The Internet Standards Process -- Revisio...
RFC-Ref

Internet standard


Click on the red underlined text to get to the source

... This memo documents the process currently used by the Internet community for the standardization of protocols and procedures. The Internet Standards process is an activity of the Internet Society that is organized and managed on behalf of the Internet community ...
... Internet Standards ...
... host-to-host communication through voluntary adherence to open protocols and procedures defined by Internet Standards. There are also many isolated internets, i.e., sets of interconnected networks, which ...
... networks, which are not connected to the Internet but use the Internet Standards. Internet Standards ...
... Internet Standards. Internet Standards were once limited to those protocols composing what has been commonly known as the "TCP/IP protocol suite". ...
... multiple protocol suites, especially the Open Systems Interconnection (OSI) suite. The Internet Standards process described in this document is concerned with all protocols, procedures, and conventions that are used in or by the Internet ...
... case of protocols developed and/or standardized by non-Internet organizations, however, the Internet Standards process may apply only to the application of the protocol or procedure in the Internet ...
... context, not to the specification of the protocol itself. In general, an Internet Standard is a specification that is stable and well-understood, is technically competent, has multiple, ...
... o These procedures are intended to provide a fair, open, and objective basis for developing, evaluating, and adopting Internet Standards. They provide ample opportunity for participation and comment by all interested parties. At each stage of the standardization process, a specification is ...
... interoperability by multiple independent parties and utilized in increasingly demanding environments, before it can be adopted as an Internet Standard. o These procedures provide a great deal of flexibility to adapt ...
... fairness. In summary, the goals for the Internet standards process are: * technical excellence; ...
... timeliness. In outline, the process of creating an Internet Standard is straightforward: a specification undergoes a period of development and several iterations of review by the Internet community ...
... Internet standardization. Section 2 presents the nomenclature for different kinds and levels of Internet standard technical specifications and their applicability. Section 3 describes the process and rules for ...
... intellectual property rights and to assure unrestricted ability for all interested parties to practice Internet Standards. ...
... The following organizations are involved in the Internet standards process. * IETF ...
... principal body engaged in the development of new Internet Standard specifications, although it is not itself a part of the Internet Society ...
... for technical management of IETF activities and the Internet Standards process. As part of the Internet Society, it administers the Internet Standards process ...
... Internet Standards process. As part of the Internet Society, it administers the Internet Standards process according to the rules and procedures given in this document, which have been accepted and ratified by the Internet Society ...
... movement along the "standards track", as described in section 3 of this document, including final approval of specifications as Internet Standards. The IESG is composed of the IETF ...
... Internet and its protocols, and to serve in the context of the Internet Standards process as a body to which the decisions of the IESG may be appealed (as described ...
... archival series is the official publication channel for Internet standards documents and other publications of the IESG, IAB ...
... service specification. See Section 3.1.3 below. Some RFCs document Internet standards. These RFCs form the 'STD' subseries of the RFC series [4 ...
... STD' subseries of the RFC series [4]. When a specification has been adopted as an Internet Standard, it is given the additional label "STDxxxx", but it keeps its RFC number and its place in the RFC series. ...
... services for the Internet should or will become Internet Standards. Such non- standards track specifications are not subject to the rules for ...
... * are standards track documents, and that not all * * standards track documents reach the level of * * Internet Standard. * ******************************************************** ...
... Each category of assigned numbers typically arises from some protocol that is on the standards track or is an Internet Standard. For example, TCP port numbers are assigned because TCP ...


... The Internet Standards Track ...
... Specifications that are destined to become Internet Standards evolve through a set of maturity levels known as the "standards track". These maturity levels -- "Proposed Standard ...
... Section 3.2. Even after a specification has been adopted as an Internet Standard, further evolution often occurs based on experience and the recognition of new requirements. The nomenclature and ...
... procedures of Internet standardization provide for the replacement of old Internet Standards with new ones, and the assignment of descriptive labels to indicate the status of "retired" Internet Standards. A set of maturity levels is defined in Section 3.3 to ...
... of old Internet Standards with new ones, and the assignment of descriptive labels to indicate the status of "retired" Internet Standards. A set of maturity levels is defined in Section 3.3 to cover these and other "off-track" specifications. ...
... be completely self-contained, or it may incorporate material from other specifications by reference to other documents (which may or may not be Internet Standards). A TS ...
... Internet capability. An AS may specify uses for TSs that are not Internet Standards, as discussed in Section 4. An AS ...
... ASs and TSs go through stages of development, testing, and acceptance. Within the Internet standards process, these stages are formally labeled "maturity levels". ...
... Internet Standard ...
... A specification for which significant implementation and successful operational experience has been obtained may be elevated to the Internet Standard level. An Internet Standard (which may simply be referred to as a Standard) is ...
... successful operational experience has been obtained may be elevated to the Internet Standard level. An Internet Standard (which may simply be referred to as a Standard) is characterized by a high degree of technical maturity and by a ...
... AS is on the standards track. A TS may not be intended to be an Internet Standard, or it may be intended for eventual standardization but not yet ready to enter the standards track. A TS ...
... TS or AS may have been superseded by more recent Internet Standards, or have otherwise fallen into disuse or disfavor. ...
... "Informational", and "Historic". There are no time limits associated with these non-standard track labels, and the documents bearing these labels are not Internet standards in any sense. As the Internet grows, there is a growing amount of credible ...
... Internet community and are not incorporated into the Internet standards process by any of the provisions of Section 4 may be published as Informational RFCs, with the permission of the owner. ...


... THE INTERNET STANDARDS PROCESS ...
... shall appear in each issue of the Internet Society Newsletter. This shall constitute the "journal of record" for Internet standards actions. In addition, the IESG shall publish a monthly summary of standards actions completed and pending in ...
... A specification that is potentially an Internet Standard may originate from: ...
... When a standards-track specification has not reached the Internet Standard level but has remained at the same status level for twenty-four (24) months, and every twelve (12) months thereafter until the status is changed, the IESG ...
... A new version of an established Internet Standard must progress through the full Internet standardization process as if it were a ...
... which will move to Historic status. However, in some cases both versions may remain as Internet Standards to honor the requirements of an installed base. In this situation, the ...
... As the technology changes and matures, it is possible for a new Standard specification to be so clearly superior technically that one or more existing Internet Standards for the same function should be retired. In this case, the IESG ...


... desirable to reach common agreements on their usage -- i.e., to establish Internet Standards relating to these external specifications. ...
... (a) Incorporation of an Open Standard An Internet Standard TS or AS may incorporate an open external ...
... organization that is responsible for the specification. For example, many Internet Standards incorporate by reference the ANSI standard character set ...
... For a vendor-proprietary specification to be incorporated within the Internet standards process, the proprietor must meet the requirements of section 5 below, and in general the ...


... o "Standards track documents" are specifications and other documents that have been elevated to the Internet standards track in accordance with the Internet Standards Process. ...
... documents that have been elevated to the Internet standards track in accordance with the Internet Standards Process. o "Copyrights" are purportedly valid ...
... o "Standards work" is work involved in the creation, testing, development, revision, adoption, or maintenance of an Internet standard that is carried out under the auspices of ISOC. ...
... Internet, either directly or indirectly, and users of any other networks which implement and use Internet Standards. ...
... applications, or other rights in the contribution. The procedures set forth in this section apply to contributions submitted after 1 April 1994. For Internet standards documents published before this date (the RFC series has been published continuously since April 1969), information on rights and permissions must be sought ...
... ISOC will not propose, adopt, or continue to maintain any standards, including but not limited to standards labelled Proposed, Draft or Internet Standards, which can only be practiced using technology or works that are subject to ...
... technology or works in its standards work; 2. upon adoption and during maintenance of an Internet Standard, any party will be able to obtain the right to implement and use the technology or works under specified, reasonable, non-discriminatory terms; and ...
... any copyrights, patents, patent applications, or other rights pertaining to Internet Standards. For this purpose, each standards document will include the following invitation: ...
... Internet community and other persons that any standards, whether or not elevated to the Internet Standard level of maturity, or any standards-related documentation made available under the auspices of ISOC ...
... Internet and users of any other networks which implement and use Internet Standards (hereinafter together with ISOC called "Internet community ...
... The Rights Holder further agrees to review the Rights listed in Schedule A from time to time, and, in particular, immediately prior to the elevation of the Standards to the Internet Standard level of maturity in accordance with the Internet Standards Process, and to inform the Executive Director ...
... prior to the elevation of the Standards to the Internet Standard level of maturity in accordance with the Internet Standards Process, and to inform the Executive Director of the Internet Engineering Task Force Secretariat promptly upon learning of any ...


... o Policy Recommendations and Operational Guidelines Internet standards have generally been concerned with the technical specifications for hardware and software required for computer ...



Google
Web
RFC-Ref