Request For Comments: Difference between revisions
Dustin Loup (talk | contribs) No edit summary |
Applied modification ruleset: Corrections using AWB-ICW patterns |
||
| (5 intermediate revisions by 4 users not shown) | |||
| Line 4: | Line 4: | ||
The [[IPTO|Information Processing Techniques Office]] (IPTO) funded research on advance computers and network technologies during the 1960s, which led to the development of [[ARPANET]], the first wide area packet switching network, or in simple words, the first Internet.<ref>[http://www.livinginternet.com/i/ii_arpanet.htm ARPANET-The First Internet]</ref> | The [[IPTO|Information Processing Techniques Office]] (IPTO) funded research on advance computers and network technologies during the 1960s, which led to the development of [[ARPANET]], the first wide area packet switching network, or in simple words, the first Internet.<ref>[http://www.livinginternet.com/i/ii_arpanet.htm ARPANET-The First Internet]</ref> | ||
It was in 1968, when the ARPANET research was in full progress wherein researchers and computer scientists met regularly to discuss the progress of their work, technical standards, Internet design and architecture, and many other aspects of computing and networking. The Group called themselves as the [[Network Working Group]]. It was in February | It was in 1968, when the ARPANET research was in full progress wherein researchers and computer scientists met regularly to discuss the progress of their work, technical standards, Internet design and architecture, and many other aspects of computing and networking. The Group called themselves as the [[Network Working Group]]. It was in February 1969 during a meeting in Utah with the BBN when the Network Working Group realized that they needed to start writing down their discussions. | ||
The term "Request For Comments" was first used by [[Steve Crocker]] when he volunteered to organize the notes written by the Network Working Group to give emphasis to their basic ground rule that "anyone can say anything and nothing was official" Crocker wrote the first RFC entitled "Host Software" on April 7, 1969.<ref>[http://www.rfc-editor.org/rfc/rfc1.txt RFC 1:Host Software]</ref> Crocker was part of the UCLA Team along with [[Vinton Cerf]], [[Jon Postel]], [[Bill Naylor]], and [[Mike Wingfield]] responsible for creating the protocols of the ARPANET, which became the foundation of today's Internet.<ref>[http://www.livinginternet.com/i/ii_arpanet.htm www.livinginternet.com]</ref> | The term "Request For Comments" was first used by [[Steve Crocker]] when he volunteered to organize the notes written by the Network Working Group to give emphasis to their basic ground rule that "anyone can say anything and nothing was official" Crocker wrote the first RFC entitled "Host Software" on April 7, 1969.<ref>[http://www.rfc-editor.org/rfc/rfc1.txt RFC 1:Host Software]</ref> Crocker was part of the UCLA Team along with [[Vinton Cerf]], [[Jon Postel]], [[Bill Naylor]], and [[Mike Wingfield]] responsible for creating the protocols of the ARPANET, which became the foundation of today's Internet.<ref>[http://www.livinginternet.com/i/ii_arpanet.htm www.livinginternet.com]</ref> | ||
| Line 11: | Line 11: | ||
==RFC Categories== | ==RFC Categories== | ||
RFCs have different categories, which include:<ref>[http://www.rfc-editor.org/RFCoverview.html RFC Categories]</ref> | |||
*Standard, Draft Standard and Proposed Standard | *Standard, Draft Standard and Proposed Standard | ||
* Best Current Practice | * Best Current Practice | ||
| Line 20: | Line 20: | ||
The RFC Series Editor is responsible for editing, cataloging, and publishing the RFC series of documents regarding computer communications. [[Jon Postel]], was the original Editor of RFC Series. He was the RFC editor for 28 years. [[Joyce Reynolds]] succeeded as RFC Editor in 1998 due to the sudden death of Postel. Reynolds had been working with Postel in editing the RFC's and managing [[IANA]] since 1983.<ref>[http://www.livinginternet.com/i/ia_rfc_invent.htm RFC History]</ref> The sudden death of Postel prompted USC-ISI to make necessary changes in the process of publishing the RFC Series to ensure the continuity of the quality and accessibility of the documents. USC-ISI developed the '''Procedures Manual for the RFC Editor.'''<ref>[http://www.rfc-editor.org/RFCeditor.at.ISI.pdf The RFC Editor Function at ISI]</ref> | The RFC Series Editor is responsible for editing, cataloging, and publishing the RFC series of documents regarding computer communications. [[Jon Postel]], was the original Editor of RFC Series. He was the RFC editor for 28 years. [[Joyce Reynolds]] succeeded as RFC Editor in 1998 due to the sudden death of Postel. Reynolds had been working with Postel in editing the RFC's and managing [[IANA]] since 1983.<ref>[http://www.livinginternet.com/i/ia_rfc_invent.htm RFC History]</ref> The sudden death of Postel prompted USC-ISI to make necessary changes in the process of publishing the RFC Series to ensure the continuity of the quality and accessibility of the documents. USC-ISI developed the '''Procedures Manual for the RFC Editor.'''<ref>[http://www.rfc-editor.org/RFCeditor.at.ISI.pdf The RFC Editor Function at ISI]</ref> | ||
The operations of the RFC Editor were originally funded by the [[DARPA|Defense Advanced research Project Agency]], which lasted until 1988. [[ISOC|The Internet Society]] (ISOC) took over the funding for the RFC Editor in 1988. The RFC Editor was a part of the University of California Information Sciences Institute | The operations of the RFC Editor were originally funded by the [[DARPA|Defense Advanced research Project Agency]], which lasted until 1988. [[ISOC|The Internet Society]] (ISOC) took over the funding for the RFC Editor in 1988. The RFC Editor was a part of the [[University of Southern California – Information Sciences Institute]] from 1977 to 2009. The Association Management Solutions, LLC (AMS). is the current entity that handles the RFC Editor project.<ref>[http://www.rfc-editor.org/RFCeditor.html RFC Editor]</ref> | ||
===Functions of the RFC Series Editor=== | ===Functions of the RFC Series Editor=== | ||
| Line 26: | Line 26: | ||
# Determine the right steps to ensure the continuity of the RFC Series. | # Determine the right steps to ensure the continuity of the RFC Series. | ||
# Exercise executive-level management in implementing policies, processes, and procedures that are created to maintain the quality and consistency of the RFC Series. He or she will also work with the [[RSAG]] whenever necessary, the [[IAB]] and [[IAOC]] | # Exercise executive-level management in implementing policies, processes, and procedures that are created to maintain the quality and consistency of the RFC Series. He or she will also work with the [[RSAG]] whenever necessary, the [[IAB]] and [[IAOC]] to develop new policy and ensure that contractual agreements are met. | ||
# Introduce the proposed changes to the Internet community to make sure that there is enough community participation in reviewing the new policy proposals before the IAB adopts or implements certain policy changes. | # Introduce the proposed changes to the Internet community to make sure that there is enough community participation in reviewing the new policy proposals before the IAB adopts or implements certain policy changes. | ||
# Coordinate with the IAB, IAOC the reviews and functions undertaken by RFC Publisher, RFC Production Center, and Independent Submission Editor to maintain continuity. | # Coordinate with the IAB, IAOC the reviews and functions undertaken by RFC Publisher, RFC Production Center, and Independent Submission Editor to maintain continuity. | ||
| Line 41: | Line 41: | ||
==References== | ==References== | ||
{{reflist}} | {{reflist}} | ||
[[Category:Glossary]] | [[Category:Glossary]] | ||