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.
Overview Engineering work typically begins as an Internet-Draft and may be published as an RFC. Standards-track RFCs are initially published as Proposed Standards and may later advance to Internet Standard when implementation and operational experience requirements are met, as specified by the Internet Standards Process. The definitive list of Internet Standards (and their associated STD and RFC numbers) is maintained by the RFC Editor.
History and the purpose of Internet Standards Internet standards are technical specifications—such as communication protocols and data formats—that allow computers and other networked devices from different vendors to interoperate on the Internet. As networking technology and operational requirements have changed, these standards (and the processes used to develop and maintain them) have likewise evolved. Many foundational Internet protocols originated in research networking work in the 1970s, including early internetworking designs that led to TCP/IP, and were later refined and standardised as the Internet expanded beyond its initial research and government use. TCP/IP A widely cited milestone in the development of the modern Internet was the ARPANET's transition from the earlier Network Control Program (NCP) to the TCP/IP protocol suite on 1 January 1983 (a planned “flag day”cutover). Leiner et al. note that TCP/IP had already been adopted as a U.S. defense standard in 1980, and that the ARPANET’s move to TCP/IP enabled the network to be separated into MILNET for operational military requirements and an ARPANET segment supporting research. TCP/IP is foundational because it specifies interoperable end-to-end communication and internetworking mechanisms—such as packet delivery, addressing, and reliability—that allow independent networks to interconnect and exchange data, and it remains the core protocol suite used for Internet communication. IPsec Internet Protocol Security is a collection of protocols that ensure the integrity of encryption in the connection between multiple devices. The purpose of this protocol is to protect public networks. According to IETF Datatracker the group dedicated to its creation was proposed into existence on 25 November 1992. Half a year later the group was created and not long after in the mid 1993 the first draft was published. HTTP HyperText Transfer Protocol is one of the most commonly used protocols today in the context of the World Wide Web. HTTP is a simple protocol to govern how documents, that are written in HyperText Mark Language(HTML), are exchanged via networks. This protocol is the backbone of the Web allowing for the whole hypertext system to exist practically. It was created by the team of developers spearheaded by Tim Berners-Lee. Berners-Lee is responsible for the proposal of its creation, which he did in 1989. August 6, 1991 is the date he published the first complete version of HTTP on a public forum. This date subsequently is considered by some to be the official birth of the World Wide Web. HTTP has been continually evolving since its creation, becoming more complicated with time and progression of networking technology. By default HTTP is not encrypted so in practice HTTPS is used, which stands for HTTP Secure. TLS/SSL TLS stands for Transport Layer Security which is a standard that enables two different endpoints to interconnect sturdy and privately. TLS came as a replacement for SSL. Secure Sockets Layers was first introduced before the creation of HTTPS and it was created by Netscape. As a matter of fact HTTPS was based on SSL when it first came out. It was apparent that one common way of encrypting data was needed so the IETF specified TLS 1.0 in RFC 2246 in January, 1999. It has been upgraded since. Last version of TLS is 1.3 from RFC 8446 in August 2018. OSI Model The Open Systems Interconnection model began its development in 1977. It was created by the International Organization for Standardization. It was officially published and adopted as a standard for use in 1979. It was then updated several times and the final version. It took a few years for the protocol to be presented in its final form. ISO 7498 was published in 1984. Lastly in 1995 the OSI model was revised again satisfy the urgent needs of uprising development in the field of computer networking. UDP The goal of User Datagram Protocol was to find a way to communicate between two computers as quickly and efficiently as possible. UDP was conceived and realized by David P. Reed in 1980. Essentially the way it works is using compression to send information. Data would be compressed into a datagram and sent point to point. This proved to be a secure way to transmit information and despite the drawback of losing quality of data UDP is still in use.
Standardization process Becoming a standard is a two-step process within the Internet Standards Process: Proposed Standard and Internet Standard. These are called maturity levels and the process is called the Standards Track. If an RFC is part of a proposal that is on the Standards Track, then at the first stage, the standard is proposed and subsequently organizations decide whether to implement this Proposed Standard. After the criteria in RFC 6410 is met (two separate implementations, widespread use, no errata etc.), the RFC can advance to Internet Standard. The Internet Standards Process is defined in several "Best Current Practice" documents, notably BCP 9 (currently RFC 2026 and RFC 6410). There were previously three standard maturity levels: Proposed Standard, Draft Standard and Internet Standard. RFC 6410 reduced this to two maturity levels.
… excerpt ends here. Continue reading the full article.
