Notifying of move discussion on Talk:Request for Comments
|
m Make capitalization consistent throughout page. Note before this edit, some "Comments" were capitalized, but some were lower case. Remove unnecessary category sortkey.
|
||
Line 4:
{{Selfref|For the Wikipedia process, see [[Wikipedia:Requests for comment]].}}
In information and communications technology, a '''Request for
An RFC is authored by engineers and [[computer scientist]]s in the form of a [[memorandum]] describing methods, behaviors, research, or innovations applicable to the working of the Internet and Internet-connected systems. It is submitted either for [[peer review]] or to convey new concepts, information, or (occasionally) engineering humor.<ref name=":0">{{cite IETF |title=A Standard for the Transmission of IP Datagrams on Avian Carriers |rfc=1149 |last=Waitzman |first=David |date=April 1, 1990 |publisher=[[Internet Engineering Task Force|IETF]] |accessdate=March 29, 2017 }}</ref> The IETF adopts some of the proposals published as RFCs as [[Internet Standard]]s. However, many RFCs are informational or experimental in nature and are not standards.<ref>{{cite IETF |title=Not All RFCs are Standards |rfc=1796 |last1=Huitema |first1=Christian |authorlink1=Christian Huitema |last2=Postel |first2=Jon |authorlink2=Jon Postel |last3=Crocker |first3=Steve |authorlink3=Steve Crocker |date=April 1995 |publisher=[[Internet Engineering Task Force|IETF]] |accessdate=May 15, 2018 }}</ref> Request for
Requests for Comments are produced in a non-reflowable document format, but work is under way to change the format to a reflowable one, so that documents can be viewed in devices with restricted size.<ref>[https://www.rfc-editor.org/rse/format-faq/ RFC Format Change FAQ]</ref>
Line 160:
{{Authority control}}
[[Category:Request for Comments| ]]
[[Category:Computer-related introductions in 1969]]
|