Request for Comments in the context of List of HTTP status codes


Request for Comments in the context of List of HTTP status codes

Request for Comments Study page number 1 of 1

Play TriviaQuestions Online!

or

Skip to study material about Request for Comments in the context of "List of HTTP status codes"


⭐ Core Definition: Request for Comments

A Request for Comments (RFC) is a publication in a series from the principal technical development and standards-setting bodies for the Internet, most prominently the Internet Engineering Task Force (IETF). An RFC is authored by individuals or groups of engineers and computer scientists 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.

The IETF adopts some of the proposals published as RFCs as Internet Standards. However, many RFCs are informational or experimental in nature and are not standards. The RFC system was invented by Steve Crocker in 1969 to help record unofficial notes on the development of ARPANET. RFCs have since become official documents of Internet specifications, communications protocols, procedures, and events. According to Crocker, the documents "shape the Internet's inner workings and have played a significant role in its success," but are not widely known outside the community.

↓ Menu
HINT:

👉 Request for Comments in the context of List of HTTP status codes

This article lists standard and notable non-standard HTTP response status codes. Standardized codes are defined by IETF as documented in Request for Comments (RFC) publications and maintained by the IANA. Other, non-standard values are used by various servers. The descriptive text after the numeric code – the reason phrase – is shown here with typical value, but in practice, can be different or omitted.

↓ Explore More Topics
In this Dossier

Request for Comments in the context of PNG

Portable Network Graphics (PNG, officially pronounced /pÉŠÅ‹/ PING, colloquially pronounced /ˌpiːɛnˈdʒiː/ PEE-en-JEE) is a raster-graphics file format that supports lossless data compression. PNG was developed as an improved, non-patented replacement for Graphics Interchange Format (GIF).

PNG supports palette-based images (with palettes of 24-bit RGB or 32-bit RGBA colors), grayscale images (with or without an alpha channel for transparency), and full-color non-palette-based RGB or RGBA images. The PNG working group designed the format for transferring images on the Internet, not for professional-quality print graphics; therefore, non-RGB color spaces such as CMYK are not supported. A PNG file contains a single image in an extensible structure of chunks, encoding the basic pixels and other information such as textual comments and integrity checks documented in RFC 2083.

View the full Wikipedia page for PNG
↑ Return to Menu

Request for Comments in the context of Internet standard

In computer network engineering, an Internet Standard is a normative specification of a technology or methodology applicable to the Internet. Internet Standards are created and published by the Internet Engineering Task Force (IETF). They allow interoperation of hardware and software from different sources which allows internets to function. As the Internet became global, Internet Standards became the lingua franca of worldwide communications.

Engineering contributions to the IETF start as an Internet Draft, may be promoted to a Request for Comments, and may eventually become an Internet Standard.

View the full Wikipedia page for Internet standard
↑ Return to Menu

Request for Comments in the context of Internet Standard

Internet Standard (often abbreviated STD) is the highest maturity level in the Internet Engineering Task Force (IETF) standards track for Internet protocol specifications. Internet Standards are published as one or more Request for Comments (RFC) documents and are additionally assigned an STD number that identifies the standard as a whole (as distinct from the RFC document number).

The Internet Standards Process is defined in a series of IETF Best Current Practice documents, including RFC 2026 and RFC 6410. Not all RFCs are Internet Standards; RFCs may also be informational, experimental, or otherwise outside the standards track.

View the full Wikipedia page for Internet Standard
↑ Return to Menu

Request for Comments in the context of Steve Crocker

Stephen D. Crocker (born October 15, 1944) is an American Internet pioneer. In 1969, he created the ARPA "Network Working Group" and the Request for Comments series. He served as chair of the board of the Internet Corporation for Assigned Names and Numbers (ICANN) from 2011 through 2017.

View the full Wikipedia page for Steve Crocker
↑ Return to Menu

Request for Comments in the context of Mailto

mailto is a Uniform Resource Identifier (URI) scheme for email addresses. It is used to produce hyperlinks on websites that allow users to send an email to a specific address directly from an HTML document, without having to copy and enter it into an email client.

It was originally defined by Request for Comments (RFC) 1738 in December 1994, expanded by RFC 2368 in July 1998, and refined by RFC 6068 in October 2010.

View the full Wikipedia page for Mailto
↑ Return to Menu