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

IETF


Click on the red underlined text to get to the source

... Some RFCs standardize the results of community deliberations about statements of principle or conclusions about what is the best way to perform some operations or IETF process function. These RFCs form the specification has been adopted as a BCP, it is given the ...
... draft versions of the document are made available for informal review and comment by placing them in the IETF's "Internet-Drafts" directory, which is replicated on a number of Internet ...


... research effort (e.g., a Research Group of the IRTF), an IETF Working Group, or it may be an individual contribution. ...
... Unless they are the result of IETF Working Group action, documents intended to be published with Experimental or Informational status ...
... Informational publication which, in the opinion of the RFC Editor, may be related to work being done, or expected to be done, within the IETF community. The IESG shall review such a referred document within a reasonable period of time, and recommend either that it be ...
... IESG shall review such a referred document within a reasonable period of time, and recommend either that it be published as originally submitted or referred to the IETF as a contribution to the Internet Standards Process. ...
... If (a) the IESG recommends that the document be brought within the IETF and progressed within the IETF context, but the author declines ...
... IESG recommends that the document be brought within the IETF and progressed within the IETF context, but the author declines to do so, or (b) the IESG ...
... IESG considers that the document proposes something that conflicts with, or is actually inimical to, an established IETF effort, the document may still be published as an Experimental or Informational RFC. In these cases, however, the IESG ...
... Documents proposed for Experimental and Informational RFCs by IETF Working Groups go through IESG review. The review is initiated using the process described in section 6.1.1. ...


... BCP document is subject to the same basic set of procedures as standards track documents and thus is a vehicle by which the IETF community can define and ratify the community's best current thinking on a statement of principle or on what is believed to be the best way to perform some operations or IETF ...
... IETF community can define and ratify the community's best current thinking on a statement of principle or on what is believed to be the best way to perform some operations or IETF process function. ...
... IESG are composed of individuals who may participate, as individuals, in the technical work of the IETF, it is also recognized that the entities themselves have an existence as leaders in the community. As leaders in the Internet ...
... structured way for these management entities to insert proposals into the consensus-building machinery of the IETF while gauging the community's view of that issue. ...
... Finally, the BCP series may be used to document the operation of the IETF itself. For example, this document defines the IETF Standards Process and is published as a BCP ...
... BCP series may be used to document the operation of the IETF itself. For example, this document defines the IETF Standards Process and is published as a BCP. ...
... is submitted to the IESG for review, (see section 6.1.1) and the existing review process applies, including a Last-Call on the IETF Announce mailing list. However, once the IESG ...
... document, the process ends and the document is published. The resulting document is viewed as having the technical approval of the IETF. ...


... A standards action is initiated by a recommendation by the IETF Working group responsible for a specification to its Area Director, copied to the IETF Secretariat ...
... IETF Working group responsible for a specification to its Area Director, copied to the IETF Secretariat or, in the case of a specification not associated with a Working Group, a recommendation by an individual to ...
... The IESG will send notice to the IETF of the pending IESG consideration of the document(s) to permit a final review by the ...
... notification shall be via electronic mail to the IETF Announce mailing list. Comments on a Last-Call shall be accepted from anyone, and should be sent as ...
... The Last-Call period shall be no shorter than two weeks except in those cases where the proposed standards action was not initiated by an IETF Working Group, in which case the Last-Call period shall be no shorter than four weeks. If the IESG believes that the community ...
... Working Group in the case of significant controversy in response to a Last-Call for specification not originating from an IETF Working Group. ...
... IESG shall make its final determination of whether or not to approve the standards action, and shall notify the IETF of its decision via electronic mail to the IETF ...
... IETF of its decision via electronic mail to the IETF Announce mailing list. ...
... If a standards action is approved, notification is sent to the RFC Editor and copied to the IETF with instructions to publish the specification as an RFC. The specification shall at that point be removed ...
... A specification shall remain at the Draft Standard level for at least four (4) months, or until at least one IETF meeting has occurred, whichever comes later. ...
... IESG shall decide to maintain the specification at the same maturity level or to move it to Historic status. This decision shall be communicated to the IETF by electronic mail to the IETF ...
... IETF by electronic mail to the IETF Announce mailing list to allow the Internet community an ...
... Disputes are possible at various stages during the IETF process. As much as possible the process is designed so that compromises can be made, and genuine consensus achieved, however there are times when ...
... Internet standards issues that cannot be resolved through the normal processes whereby IETF Working Groups and other Internet Standards Process participants ordinarily reach consensus. ...
... principal agent of the IETF for this purpose, and it is the IESG that is charged with ensuring that the required procedures have been ...
... action is needed. The IESG shall issue a report on its review of the complaint to the IETF. ...
... IAB shall then review the situation and attempt to resolve it in a manner of its own choosing and report to the IETF on the outcome of its review. ...
... acknowledgment advise the petitioner of the expected duration of the Trustees' review of the appeal. The Trustees shall review the situation in a manner of its own choosing and report to the IETF on the outcome of its review. ...


... Many standards groups other than the IETF create and publish standards documents for network protocols ...
... An IETF Working Group may start from an external specification and develop it into an Internet ...
... requirements of section 10, and (2) change control has been conveyed to IETF by the original developer of the specification for the specification or for specifications derived from the original specification. ...


... Internet Standards Process. For purposes of this section, the organizations involved in the development and approval of Internet Standards includes the IETF, the IESG, the IAB, all IETF Working Groups ...
... IETF, the IESG, the IAB, all IETF Working Groups, and the Internet Society Board of Trustees. ...
... For IETF and Working Group meetings announcements shall be made by electronic mail ...
... Working Group meetings announcements shall be made by electronic mail to the IETF Announce mailing list and shall be made sufficiently far in advance of the activity to permit all interested ...
... As a practical matter, the formal record of all Internet Standards Process activities is maintained by the IETF Secretariat, and is the responsibility of the IETF Secretariat except that each IETF Working Group ...
... Internet Standards Process activities is maintained by the IETF Secretariat, and is the responsibility of the IETF Secretariat except that each IETF Working Group is expected to maintain their own email list archive ...
... IETF Secretariat, and is the responsibility of the IETF Secretariat except that each IETF Working Group is expected to maintain their own email list archive and must ...
... Working Group chair is responsible for providing the IETF Secretariat with complete and accurate minutes of all Working Group meetings. Internet-Drafts ...
... removed (for any reason) from the Internet-Drafts directories shall be archived by the IETF Secretariat for the sole purpose of preserving an historical record of Internet standards ...


... Upon the recommendation of the responsible IETF Working Group (or, if no Working Group is constituted, upon the recommendation of an ad hoc ...
... IESG shall make its final determination of whether or not to approve the proposed variance, and shall notify the IETF of its decision via electronic mail to the IETF ...
... IETF of its decision via electronic mail to the IETF Announce mailing list. If the variance is approved it shall be forwarded to the RFC Editor with a request ...


... In the course of standards work, the IETF receives contributions in various forms and from many persons. To best facilitate the dissemination of these contributions, it is necessary to understand ...
... license to the ISOC and the IETF under any copyrights in the contribution. This license includes the right to copy, publish and distribute the ...
... The contributor acknowledges that the ISOC and IETF have no duty to publish or otherwise use or disseminate any contribution. ...
... By ratifying this description of the IETF process the Internet Society warrants that it will not inhibit the traditional open and free access to IETF documents ...
... IETF process the Internet Society warrants that it will not inhibit the traditional open and free access to IETF documents for which license and right have been assigned according to the procedures set forth in this ...
... (C) Where the IESG knows of rights, or claimed rights under (A), the IETF Executive Director shall attempt to obtain from the claimant of such rights, a written assurance that upon approval by the IESG ...
... Working Group proposing the use of the technology with respect to which the proprietary rights are claimed may assist the IETF Executive Director in this effort. The results of this procedure shall not affect advancement of a specification along the standards track, except that the IESG ...
... IESG may defer approval where a delay may facilitate the obtaining of such assurances. The results will, however, be recorded by the IETF Executive Director, and made available. The IESG may also direct that a summary of ...
... (A) Standards track documents shall include the following notice: "The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed ...
... under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation ...
... proprietary rights by implementors or users of this specification can be obtained from the IETF Secretariat." (B) The IETF ...
... IETF Secretariat." (B) The IETF encourages all interested parties to bring to its attention, at the earliest possible time, the existence of any intellectual property rights ...
... following invitation: "The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be ...
... other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director." (C) The following copyright notice and disclaimer shall be included ...
... document shall contain the following notice: "The IETF has been notified of intellectual property rights claimed in regard to some or all of the specification contained ...


... There have been a number of people involved with the development of the documents defining the IETF Standards Process over the years. The process was first described in RFC 1310(-> 1602(-> 2026)) then revised in RFC 1602(-> 2026) ...
... In addition much of the credit for the refinement of the details of the IETF processes belongs to the many members of the various incarnations of the POISED Working Group. ...


... IETF Area ...
... A management division within the IETF. An Area consists of Working Groups related to a general topic such as routing ...
... The manager of an IETF Area. The Area Directors along with the IETF Chair ...
... IETF Area. The Area Directors along with the IETF Chair comprise the Internet Engineering Steering Group (IESG). ...
... group that assists in the management of the IETF standards process. ...
... A group comprised of the IETF Area Directors and the IETF Chair. The IESG ...
... IETF Area Directors and the IETF Chair. The IESG is responsible for the management ...
... for the management, along with the IAB, of the IETF and is the standards approval board for the IETF. ...
... IAB, of the IETF and is the standards approval board for the IETF. ...


... IETF ...



Google
Web
RFC-Ref