534:
to mature a standard network protocol that is correlated with network statements. Some RFCs are aimed to produce information while others are required to publish
Internet standards. The ultimate form of the RFC converts to the standard and is issued with a numeral. After that, no more comments or variations are acceptable for the concluding form. This process is followed in every area to generate unanimous views about a problem related to the internet and develop internet standards as a solution to different glitches. There are eight common areas on which IETF focus and uses various working groups along with an area director. In the "general" area it works and develops the Internet standards. In "Application" area it concentrates on internet applications such as Web-related protocols. Furthermore, it also works on the development of internet infrastructure in the form of PPP extensions. IETF also establish principles and description standards that encompass the Internet protocol suite (TCP/IP). The Internet Architecture Board (IAB) along with the Internet Research Task Force (IRTF) counterpart the exertion of the IETF using innovative technologies.
530:
works with the World Wide Web
Consortium (W3C) and other standard development organizations. Moreover, it heavily relies on working groups that are constituted and proposed to an Area Director. IETF relies on its working groups for expansion of IETF conditions and strategies with a goal to make the Internet work superior. The working group then operates under the direction of the Area Director and progress an agreement. After the circulation of the proposed charter to the IESG and IAB mailing lists and its approval then it is further forwarded to the public IETF. It is not essential to have the complete agreement of all working groups and adopt the proposal. IETF working groups are only required to recourse to check if the accord is strong.
647:
includes its scope and its intent for use, or "domain of applicability". However, a TSs use within the
Internet is defined by an Applicability Statement. An AS specifies how, and under what circumstances, TSs may be applied to support a particular Internet capability. An AS identifies the ways in which relevant TSs are combined and specifies the parameters or sub-functions of TS protocols. An AS also describes the domains of applicability of TSs, such as Internet routers, terminal server, or datagram-based database servers. An AS also applies one of the following "requirement levels" to each of the TSs to which it refers:
842:
and check other users' routes for safety. If it were more widely adopted, more routes could be added and confirmed. However, RPKI is picking up momentum. As of
December 2020, tech giant Google registered 99% of its routes with RPKI. They are making it easier for businesses to adopt BGP safeguards. DNS also has a security protocol with a low adoption rate: DNS Security Extensions (DNSSEC). Essentially, at every stage of the DNS lookup process, DNSSEC adds a signature to data to show it has not been tampered with.
538:
every one of which is accountable for evolving standards and skills in a specific zone, for example routing or security. People in working groups are volunteers and work in fields such as equipment vendors, network operators and different research institutions. Firstly, it works on getting the common consideration of the necessities that the effort should discourse. Then an IETF Working Group is formed and necessities are ventilated in the influential Birds of a
Feather (BoF) assemblies at IETF conferences.
857:
291:. 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
465:
protocols, message formats, schemas, and languages. An
Internet Standard ensures that hardware and software produced by different vendors can work together. Having a standard makes it much easier to develop software and hardware that link different networks because software and hardware can be developed one layer at a time. Normally, the standards used in data communication are called protocols.
25:
781:
328:. 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.
838:
Border
Gateway Protocol (BGP) and Domain Name System (DNS). This reflects common practices that focus more on innovation than security. Companies have the power to improve these issues. With the Internet in the hands of the industry, users must depend on businesses to protect vulnerabilities present in these standards.
522:(W3C). All organizations are required to use and express the Internet language in order to remain competitive in the current Internet phase. Some basic aims of the Internet Standards Process are; ensure technical excellence; earlier implementation and testing; perfect, succinct as well as easily understood records.
837:
The
Internet has been viewed as an open playground, free for people to use and communities to monitor. However, large companies have shaped and molded it to best fit their needs. The future of internet standards will be no different. Currently, there are widely used but insecure protocols such as the
646:
Specifications subject to the
Internet Standards Process can be categorized into one of the following: Technical Specification (TS) and Applicability Statement (AS). A Technical Specification is a statement describing all relevant aspects of a protocol, service, procedure, convention, or format. This
234:
Internet standard is a set of rules that the devices have to follow when they connect in a network. Since the technology has evolved, the rules of the engagement between computers had to evolve with it. These are the protocols that are in place used today. Most of these were developed long before the
173:
In general, an
Internet Standard is a specification that is stable and well-understood, is technically competent, has multiple, independent, and interoperable implementations with substantial operational experience, enjoys significant public support, and is recognizably useful in some or all parts of
533:
Likewise, the Working Group produce documents in the arrangement of RFCs which are memorandum containing approaches, deeds, examination as well as innovations suitable to the functioning of the Internet and Internet-linked arrangements. In other words, Requests for Comments (RFCs) are primarily used
529:
Till 1993, the United States federal government was supporting the IETF. Now, the Internet Society's Internet Architecture Board (IAB) supervises it. It is a bottom-up organization that has no formal necessities for affiliation and does not have an official membership procedure either. It watchfully
472:
Documents submitted to the IETF editor and accepted as an RFC are not revised; if the document has to be changed, it is submitted again and assigned a new RFC number. When an RFC becomes an Internet Standard (STD), it is assigned an STD number but retains its RFC number. When an Internet Standard is
407:
Proposed Standards are of such quality that implementations can be deployed in the Internet. However, as with all technical specifications, Proposed Standards may be revised if problems are found or better solutions are identified, when experiences with deploying implementations of such technologies
403:
specification is stable, has resolved known design choices, has received significant community review, and appears to enjoy enough community interest to be considered valuable. Usually, neither implementation nor operational experience is required for the designation of a specification as a Proposed
340:
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
271:
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
259:
and the Defense Data Network were the networks to implement the Protocols. These protocols are considered to be the essential part of how the Internet works because they define the rules by which the connections between servers operate. They are still used today by implementing various ways data is
841:
Ways to make BGP and DNS safer already exist but they are not widespread. For example, there is the existing BGP safeguard called Routing Public Key Infrastructure (RPKI). It is a database of routes that are known to be safe and have been cryptographically signed. Users and companies submit routes
537:
The IETF is the standards making organization concentrate on the generation of "standard" stipulations of expertise and their envisioned usage. The IETF concentrates on matters associated with the progress of current Internet and TCP/IP know-how. It is alienated into numerous working groups (WGs),
464:
An Internet Standard is characterized by a high degree of technical maturity and by a generally held belief that the specified protocol or service provides significant benefit to the Internet community. Generally Internet Standards cover interoperability of systems on the Internet through defining
368:
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.),
311:
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
546:
The Internet Engineering Task Force (IETF) is the premier internet standards organization. It follows an open and well-documented processes for setting internet standards. The resources that the IETF offers include RFCs, internet-drafts, IANA functions, intellectual property rights, standards
621:
There are two ways in which an Internet Standard is formed and can be categorized as one of the following: "de jure" standards and "de facto" standards. A de facto standard becomes a standard through widespread use within the tech community. A de jure standard is formally created by official
525:
Creating and improving the Internet Standards is an ongoing effort and Internet Engineering Task Force plays a significant role in this regard. These standards are shaped and available by the Internet Engineering Task Force (IETF). It is the leading Internet standards association that uses
411:
Many Proposed Standards are actually deployed on the Internet and used extensively, as stable protocols. Actual practice has been that full progression through the sequence of standards levels is typically quite rare, and most popular IETF protocols remain at Proposed Standard.
666:
Recommended: Implementation of the referenced TS is not required, but is desirable in the domain of applicability of the AS. Inclusion of the functions, features, and protocols of Recommended TSs in the developments of systems is encouraged. For example, the
468:
All Internet Standards are given a number in the STD series. The series was summarized in its first document, STD 1 (RFC 5000), until 2013, but this practice was retired in RFC 7100. The definitive list of Internet Standards is now maintained by the RFC Editor.
1809:
Sherman, Justin (1 October 2020). "Mapping Private Sector Influence on the Internet: Starting with Internet Protocols". The Politics of Internet Security: Private Industry and the Future of the Web (Report). Atlantic Council. pp. 4–7.
720:
Network standards are a type of internet standard which defines rules for data communication in networking technologies and processes. Internet standards allow for the communication procedure of a device to or from other devices.
144:(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.
473:
updated, its number is unchanged but refers to a different RFC or set of RFCs. For example, in 2007 RFC 3700 was an Internet Standard (STD 1) and in May 2008 it was replaced with RFC 5000. RFC 3700 received
674:
Elective: Implementation of the referenced TS is optional. The TS is only necessary in a specific environment. For example, the DECNET MIB could be seen as valuable in an environment where the
287:, 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
599:
The process of creating a standard is straightforward - a specification goes through an extensive review process by the Internet community and revised through experience.
166:
was an intermediate level, discontinued in 2011. A Draft Standard was an intermediary step that occurred after a Proposed Standard but prior to an Internet Standard.
1792:
325:
1161:
712:. Respectively, they specify the transfer of data between a browser and a web server, the content and layout of a web page, and what web page identifiers mean.
480:
The list of Internet standards was originally published as STD 1 but this practice has been abandoned in favor of an online list maintained by the RFC Editor.
283:
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
1768:
1232:
1103:
215:
445:
219:
526:
well-documented procedures for creating these standards. Once circulated, those standards are made easily accessible without any cost.
824:
660:
211:
is applied to deprecated Standards Track documents or obsolete RFCs that were published before the Standards Track was established.
108:
1190:
791:
559:
The acronym RFC came from the phrase "Request For Comments" - this is not used anymore today and is now simply referred to as RFCs.
46:
39:
589:
All IETF standards are freely available to view and read, and generally free to implement by anyone without permission or payment.
307:
which is a standard that enables two different endpoints to interconnect sturdy and privately. TLS came as a replacement for SSL.
203:, with an additional sequence number, when maturity has reached an acceptable level. Collectively, these stages are known as the
1875:
89:
1336:
1288:
1017:
651:
Required: Implementation of the referenced TS is required to achieve interoperability. For example, Internet systems using the
503:
141:
61:
444:
as soon as the criteria in RFC 6410 are satisfied; or, after two years since RFC 6410 was aproved as BCP (October 2013), the
1132:
396:
RFC 2026 originally characterized Proposed Standards as immature specifications, but this stance was annulled by RFC 7127.
934:
68:
845:
Some companies have taken the initiative to secure internet protocols. It is up to the rest to make it more widespread.
515:
1914:
701:
511:
1153:
1065:
806:
1257:
341:
to be a secure way to transmit information and despite the drawback of losing quality of data UDP is still in use.
75:
1518:
802:
35:
1378:
519:
700:. They allow for the building and rendering of websites. The three key standards used by the World Wide Web are
304:
57:
739:
729:
652:
635:
252:
957:"The Design of the Internet's Architecture by the Internet Engineering Task Force (IETF) and Human Rights"
337:
1679:
Nickerson; Muehlen (2006). "The Ecology of Standards Processes: Insights from Internet Standard Making".
1449:
495:
The draft standard was carefully tested in preparation for riverside to form the future Internet standard
222:(IESG), can approve Standards Track RFCs. The definitive list of Internet Standards is maintained in the
187:(RFC) or a set of RFCs. A specification that is to become a Standard or part of a Standard begins as an
856:
1742:
1659:
1625:
1592:
1558:
1431:
1350:
1302:
1031:
308:
184:
152:
158:
An Internet Standard is characterized by technical maturity and usefulness. The IETF also defines a
1811:
1786:
1696:
992:
926:
1183:"Transport Layer Security (TLS) - MDN Web Docs Glossary: Definitions of Web-related terms | MDN"
1095:
372:
The Internet Standards Process is defined in several "Best Current Practice" documents, notably
724:
In reference to the TCP/IP Model, common standards and protocols in each layer are as follows:
82:
1843:
1774:
1764:
1492:
1469:
1228:
1219:, SpringerBriefs in Computer Science, Cham: Springer International Publishing, pp. 5–17,
1057:
984:
976:
918:
760:
272:
later the group was created and not long after in the mid 1993 the first draft was published.
240:
1835:
1732:
1688:
1649:
1615:
1582:
1548:
1461:
1421:
1398:
1340:
1292:
1220:
1021:
968:
910:
507:
433:
122:
1326:
1278:
871:
862:
288:
376:(currently RFC 2026 and RFC 6410). There were previously three standard maturity levels:
1182:
1212:
697:
188:
148:
1867:
566:
is an official archive of internet standards, draft standards, and proposed standards.
1908:
956:
876:
693:
133:
930:
996:
236:
1085:
RFC 7100 Retirement of the "Internet Official Protocol Standards" Summary Document
1124:
492:
Proposed standards are standards to be implemented and can be changed at any time
349:
Becoming a standard is a two-step process within the Internet Standards Process:
1745:
1726:
1662:
1643:
1628:
1609:
1595:
1576:
1561:
1542:
1434:
1415:
1402:
1353:
1330:
1305:
1282:
1224:
1034:
1011:
753:
251:
The official date for when the first internet went live is January 1, 1983. The
125:
24:
898:
671:
protocol should be implemented by all systems that intend to use remote access.
420:
In October 2011, RFC 6410 merged the second and third maturity levels into one
191:, and is later, usually after several revisions, accepted and published by the
972:
852:
749:
656:
192:
1847:
1816:
1778:
1496:
1473:
1061:
980:
922:
1465:
1450:"Entrepreneurial Traffic Management and the Internet Engineering Task Force"
321:
988:
556:
Documents that contain technical specifications and notes for the Internet.
1417:
Simplified Local Internet Number Resource Management with the RPKI (SLURM)
1049:
1253:
137:
1700:
1510:
914:
733:
256:
1374:
223:
1737:
1692:
1654:
1620:
1587:
1553:
1426:
1345:
1297:
1026:
675:
668:
809:. Statements consisting only of original research should be removed.
627:
373:
292:
268:
1010:
Russell Housley; Dave Crocker; Eric W. Burger (11 October 2011).
239:, going as far back as the 1970s, not long after the creation of
764:
705:
631:
579:
Other groups may distribute working documents as Internet-Drafts
312:
since. Last version of TLS is 1.3 from RFC 8446 in August 2018.
284:
280:
622:
standard-developing organizations. These standards undergo the
609:
Internet-Drafts that successfully completed the review process.
162:
as a less mature but stable and well-reviewed specification. A
774:
743:
709:
18:
1899:
1836:"A Broken Piece of Internet Backbone Might Finally Get Fixed"
428:
retain that classification, absent explicit actions. For old
226:. Previously, STD 1 used to maintain a snapshot of the list.
1487:
Society., Internet Engineering Task Force. Internet (2005).
696:
are a type of internet standard which define aspects of the
488:
The standardization process is divided into three steps:
16:
Standard published by the Internet Engineering Task Force
1645:
The Organizations Involved in the IETF Standards Process
1414:
Ma, D.; Mandelberg, D.; Bruijnzeels, T. (August 2018).
798:
207:, and are defined in RFC 2026 and RFC 6410. The label
140:. Internet Standards are created and published by the
576:
Working documents of the IETF and its working groups.
502:
There are five Internet standards organizations: the
324:
began its development in 1977. It was created by the
436:
are available, which must be aproved by the IESG: A
253:
Transfer Control Protocol/Internet Protocol (TCP/IP)
1013:
Reducing the Standards Track to Two Maturity Levels
257:
ARPANET (Advanced Research Projects Agency Network)
1578:Handling of Internet-Drafts by IETF Working Groups
692:TCP/ IP Model & associated Internet Standards
155:, and may eventually become an Internet Standard.
147:Engineering contributions to the IETF start as an
136:of a technology or methodology applicable to the
388:. RFC 6410 reduced this to two maturity levels.
1611:Intellectual Property Rights in IETF Technology
955:Cath, Corinne; Floridi, Luciano (April 2017).
326:International Organization for Standardization
1537:
1535:
1048:Huitema, C.; Postel, J.; Crocker, S. (1995).
230:History and the purpose of Internet Standards
8:
1728:The Internet Standards Process -- Revision 3
1054:IETF Request for Comments (RFC) Pages - Test
623:
547:process, and publishing and accessing RFCs.
1791:: CS1 maint: location missing publisher (
369:the RFC can advance to Internet Standard.
1815:
1736:
1653:
1619:
1586:
1552:
1425:
1344:
1296:
1025:
825:Learn how and when to remove this message
109:Learn how and when to remove this message
1454:Journal of Competition Law and Economics
612:Submitted to RFC editor for publication.
498:Internet standards are mature standards.
183:An Internet Standard is documented by a
1642:Hovey, R.; Bradner, S. (October 1996).
899:"An Introduction to Internet Standards"
889:
295:is used, which stands for HTTP Secure.
1784:
1375:"Official Internet Protocol Standards"
1332:Characterization of Proposed Standards
1284:Characterization of Proposed Standards
45:Please improve this article by adding
1829:
1827:
1804:
1802:
1720:
1718:
1716:
1714:
1712:
1710:
1674:
1672:
7:
1544:Internet Official Protocol Standards
1279:"Characterization of Specifications"
224:Official Internet Protocol Standards
1327:"IETF Review of Proposed Standards"
626:. Common de jure standards include
484:Organizations of Internet Standards
477:status, and RFC 5000 became STD 1.
220:Internet Engineering Steering Group
322:Open Systems Interconnection model
14:
1448:Knieps, Günter (September 2015).
1096:"A Brief History of the Internet"
1154:"Evolution of HTTP - HTTP | MDN"
1125:"IP Security Protocol (ipsec) -"
855:
779:
771:The future of Internet Standards
642:Internet Standard Specifications
448:can choose to reclassify an old
23:
1878:from the original on 2021-12-06
1761:Computer networks and Internets
1521:from the original on 2021-12-06
1381:from the original on 2018-03-15
1260:from the original on 2021-12-08
1193:from the original on 2021-12-08
1164:from the original on 2023-03-27
1135:from the original on 2019-09-13
1106:from the original on 2002-02-18
1068:from the original on 2018-03-20
937:from the original on 2022-02-09
542:Internet Engineering Task Force
504:Internet Engineering Task Force
199:. Later, an RFC is elevated as
142:Internet Engineering Task Force
1763:(Sixth ed.). Boston, MA.
1254:"What Is UDP | DiverseNet Inc"
1217:Guide to OSI and TCP/IP Models
961:Science and Engineering Ethics
361:and the process is called the
1:
1339:. January 2014. sec. 2.
1291:. January 2014. sec. 3.
897:Leiba, Barry (January 2008).
604:Publishing and accessing RFCs
285:HyperText Mark Language(HTML)
47:secondary or tertiary sources
1725:Bradner, S. (October 1996).
1050:"Not All RFCs are Standards"
584:Intellectual property rights
516:Internet Research Task Force
1225:10.1007/978-3-319-05152-9_2
1211:Alani, Mohammed M. (2014),
805:the claims made and adding
702:Hypertext Transfer Protocol
617:Types of Internet Standards
512:Internet Architecture Board
281:HyperText Transfer Protocol
1931:
655:are required to implement
624:Internet Standards Process
440:may be reclassified as an
269:Internet Protocol Security
260:sent via global networks.
1868:"DNSSEC: An Introduction"
1575:Farrel, A. (April 2014).
973:10.1007/s11948-016-9793-y
520:World Wide Web Consortium
305:Transport Layer Security
195:as an RFC and labeled a
1759:Comer, Douglas (2015).
903:IEEE Internet Computing
653:Internet Protocol Suite
636:Internet protocol suite
345:Standardization process
151:, may be promoted to a
408:at scale is gathered.
338:User Datagram Protocol
176:
34:relies excessively on
1466:10.1093/joclec/nhv018
1187:developer.mozilla.org
1158:developer.mozilla.org
728:The Transport layer:
309:Secure Sockets Layers
218:, represented by the
171:
1491:. Internet Society.
1129:datatracker.ietf.org
185:Request for Comments
169:As put in RFC 2026:
153:Request for Comments
1872:The Cloudflare Blog
357:. These are called
58:"Internet Standard"
1915:Internet Standards
1834:Newman, Lily Hay.
915:10.1109/MIC.2008.2
790:possibly contains
255:went into effect.
241:personal computers
1770:978-0-13-358793-7
1234:978-3-319-05151-2
835:
834:
827:
792:original research
748:Data Link layer:
716:Network Standards
678:protocol is used.
594:Standards Process
460:Internet Standard
454:Proposed Standard
442:Internet Standard
424:. Existing older
422:Internet Standard
401:Proposed Standard
392:Proposed Standard
386:Internet Standard
378:Proposed Standard
355:Internet Standard
351:Proposed Standard
201:Internet Standard
197:Proposed Standard
160:Proposed Standard
130:Internet Standard
119:
118:
111:
93:
1922:
1887:
1886:
1884:
1883:
1864:
1858:
1857:
1855:
1854:
1831:
1822:
1821:
1819:
1806:
1797:
1796:
1790:
1782:
1756:
1750:
1749:
1740:
1738:10.17487/rfc2026
1722:
1705:
1704:
1693:10.2307/25148769
1676:
1667:
1666:
1657:
1655:10.17487/rfc2028
1639:
1633:
1632:
1623:
1621:10.17487/rfc3979
1606:
1600:
1599:
1590:
1588:10.17487/rfc7221
1572:
1566:
1565:
1556:
1554:10.17487/rfc5000
1539:
1530:
1529:
1527:
1526:
1507:
1501:
1500:
1484:
1478:
1477:
1445:
1439:
1438:
1429:
1427:10.17487/rfc8416
1411:
1405:
1396:
1390:
1389:
1387:
1386:
1371:
1365:
1364:
1362:
1360:
1348:
1346:10.17487/RFC7127
1323:
1317:
1316:
1314:
1312:
1300:
1298:10.17487/RFC7127
1275:
1269:
1268:
1266:
1265:
1250:
1244:
1243:
1242:
1241:
1208:
1202:
1201:
1199:
1198:
1179:
1173:
1172:
1170:
1169:
1150:
1144:
1143:
1141:
1140:
1121:
1115:
1114:
1112:
1111:
1092:
1086:
1083:
1077:
1076:
1074:
1073:
1045:
1039:
1038:
1029:
1027:10.17487/RFC6410
1007:
1001:
1000:
952:
946:
945:
943:
942:
894:
865:
860:
859:
830:
823:
819:
816:
810:
807:inline citations
783:
782:
775:
759:Physical layer:
683:Common Standards
508:Internet Society
123:computer network
114:
107:
103:
100:
94:
92:
51:
27:
19:
1930:
1929:
1925:
1924:
1923:
1921:
1920:
1919:
1905:
1904:
1896:
1891:
1890:
1881:
1879:
1866:
1865:
1861:
1852:
1850:
1833:
1832:
1825:
1808:
1807:
1800:
1783:
1771:
1758:
1757:
1753:
1724:
1723:
1708:
1678:
1677:
1670:
1641:
1640:
1636:
1608:
1607:
1603:
1574:
1573:
1569:
1541:
1540:
1533:
1524:
1522:
1509:
1508:
1504:
1486:
1485:
1481:
1447:
1446:
1442:
1413:
1412:
1408:
1397:
1393:
1384:
1382:
1373:
1372:
1368:
1358:
1356:
1325:
1324:
1320:
1310:
1308:
1277:
1276:
1272:
1263:
1261:
1252:
1251:
1247:
1239:
1237:
1235:
1210:
1209:
1205:
1196:
1194:
1181:
1180:
1176:
1167:
1165:
1152:
1151:
1147:
1138:
1136:
1123:
1122:
1118:
1109:
1107:
1094:
1093:
1089:
1084:
1080:
1071:
1069:
1047:
1046:
1042:
1009:
1008:
1004:
954:
953:
949:
940:
938:
896:
895:
891:
886:
881:
872:Standardization
863:Internet portal
861:
854:
851:
831:
820:
814:
811:
796:
784:
780:
773:
738:Network layer:
718:
690:
685:
644:
619:
606:
596:
586:
573:
571:Internet Drafts
553:
544:
486:
462:
430:Draft Standards
426:Draft Standards
418:
394:
363:Standards Track
359:maturity levels
347:
303:TLS stands for
289:Tim Berners-Lee
232:
205:Standards Track
181:
132:is a normative
115:
104:
98:
95:
52:
50:
44:
40:primary sources
28:
17:
12:
11:
5:
1928:
1926:
1918:
1917:
1907:
1906:
1903:
1902:
1895:
1894:External links
1892:
1889:
1888:
1874:. 2014-10-07.
1859:
1823:
1798:
1769:
1751:
1706:
1668:
1634:
1614:. March 2005.
1601:
1567:
1531:
1502:
1479:
1460:(3): 727–745.
1440:
1406:
1391:
1366:
1318:
1270:
1245:
1233:
1203:
1174:
1145:
1116:
1087:
1078:
1040:
1002:
967:(2): 449–468.
947:
888:
887:
885:
882:
880:
879:
874:
868:
867:
866:
850:
847:
833:
832:
787:
785:
778:
772:
769:
768:
767:
757:
746:
736:
717:
714:
698:World Wide Web
689:
686:
684:
681:
680:
679:
672:
664:
643:
640:
618:
615:
614:
613:
610:
605:
602:
601:
600:
595:
592:
591:
590:
585:
582:
581:
580:
577:
572:
569:
568:
567:
560:
557:
552:
549:
543:
540:
500:
499:
496:
493:
485:
482:
461:
458:
450:Draft Standard
438:Draft Standard
417:
416:Draft Standard
414:
393:
390:
382:Draft Standard
346:
343:
231:
228:
189:Internet Draft
180:
177:
164:Draft Standard
149:Internet Draft
117:
116:
31:
29:
22:
15:
13:
10:
9:
6:
4:
3:
2:
1927:
1916:
1913:
1912:
1910:
1901:
1898:
1897:
1893:
1877:
1873:
1869:
1863:
1860:
1849:
1845:
1841:
1837:
1830:
1828:
1824:
1818:
1817:resrep26661.5
1813:
1805:
1803:
1799:
1794:
1788:
1780:
1776:
1772:
1766:
1762:
1755:
1752:
1747:
1744:
1739:
1734:
1730:
1729:
1721:
1719:
1717:
1715:
1713:
1711:
1707:
1702:
1698:
1694:
1690:
1686:
1682:
1681:MIS Quarterly
1675:
1673:
1669:
1664:
1661:
1656:
1651:
1647:
1646:
1638:
1635:
1630:
1627:
1622:
1617:
1613:
1612:
1605:
1602:
1597:
1594:
1589:
1584:
1580:
1579:
1571:
1568:
1563:
1560:
1555:
1550:
1546:
1545:
1538:
1536:
1532:
1520:
1516:
1512:
1506:
1503:
1498:
1494:
1490:
1483:
1480:
1475:
1471:
1467:
1463:
1459:
1455:
1451:
1444:
1441:
1436:
1433:
1428:
1423:
1419:
1418:
1410:
1407:
1404:
1400:
1395:
1392:
1380:
1376:
1370:
1367:
1355:
1352:
1347:
1342:
1338:
1334:
1333:
1328:
1322:
1319:
1307:
1304:
1299:
1294:
1290:
1286:
1285:
1280:
1274:
1271:
1259:
1255:
1249:
1246:
1236:
1230:
1226:
1222:
1218:
1214:
1207:
1204:
1192:
1188:
1184:
1178:
1175:
1163:
1159:
1155:
1149:
1146:
1134:
1130:
1126:
1120:
1117:
1105:
1101:
1097:
1091:
1088:
1082:
1079:
1067:
1063:
1059:
1055:
1051:
1044:
1041:
1036:
1033:
1028:
1023:
1019:
1015:
1014:
1006:
1003:
998:
994:
990:
986:
982:
978:
974:
970:
966:
962:
958:
951:
948:
936:
932:
928:
924:
920:
916:
912:
908:
904:
900:
893:
890:
883:
878:
877:Web standards
875:
873:
870:
869:
864:
858:
853:
848:
846:
843:
839:
829:
826:
818:
808:
804:
800:
794:
793:
788:This article
786:
777:
776:
770:
766:
762:
758:
755:
751:
747:
745:
741:
737:
735:
731:
727:
726:
725:
722:
715:
713:
711:
707:
703:
699:
695:
694:Web standards
688:Web Standards
687:
682:
677:
673:
670:
665:
662:
658:
654:
650:
649:
648:
641:
639:
637:
633:
629:
625:
616:
611:
608:
607:
603:
598:
597:
593:
588:
587:
583:
578:
575:
574:
570:
565:
561:
558:
555:
554:
550:
548:
541:
539:
535:
531:
527:
523:
521:
517:
513:
509:
505:
497:
494:
491:
490:
489:
483:
481:
478:
476:
470:
466:
459:
457:
455:
451:
447:
443:
439:
435:
432:two possible
431:
427:
423:
415:
413:
409:
405:
402:
397:
391:
389:
387:
383:
379:
375:
370:
366:
364:
360:
356:
352:
344:
342:
339:
334:
333:
329:
327:
323:
318:
317:
313:
310:
306:
301:
300:
296:
294:
290:
286:
282:
278:
277:
273:
270:
266:
265:
261:
258:
254:
249:
248:
244:
242:
238:
229:
227:
225:
221:
217:
212:
210:
206:
202:
198:
194:
190:
186:
178:
175:
174:the Internet.
170:
167:
165:
161:
156:
154:
150:
145:
143:
139:
135:
134:specification
131:
127:
124:
113:
110:
102:
99:November 2015
91:
88:
84:
81:
77:
74:
70:
67:
63:
60: –
59:
55:
54:Find sources:
48:
42:
41:
37:
32:This article
30:
26:
21:
20:
1880:. Retrieved
1871:
1862:
1851:. Retrieved
1839:
1760:
1754:
1727:
1684:
1680:
1644:
1637:
1610:
1604:
1577:
1570:
1547:. May 2008.
1543:
1523:. Retrieved
1514:
1505:
1489:IETF journal
1488:
1482:
1457:
1453:
1443:
1416:
1409:
1394:
1383:. Retrieved
1369:
1357:. Retrieved
1331:
1321:
1309:. Retrieved
1283:
1273:
1262:. Retrieved
1248:
1238:, retrieved
1216:
1206:
1195:. Retrieved
1186:
1177:
1166:. Retrieved
1157:
1148:
1137:. Retrieved
1128:
1119:
1108:. Retrieved
1099:
1090:
1081:
1070:. Retrieved
1053:
1043:
1012:
1005:
964:
960:
950:
939:. Retrieved
909:(1): 71–74.
906:
902:
892:
844:
840:
836:
821:
812:
789:
752:for LAN and
723:
719:
691:
645:
620:
563:
562:The website
545:
536:
532:
528:
524:
501:
487:
479:
474:
471:
467:
463:
453:
449:
441:
437:
429:
425:
421:
419:
410:
406:
400:
398:
395:
385:
381:
377:
371:
367:
362:
358:
354:
350:
348:
336:The goal of
335:
331:
330:
319:
315:
314:
302:
298:
297:
279:
275:
274:
267:
263:
262:
250:
246:
245:
237:Internet Age
233:
213:
208:
204:
200:
196:
182:
172:
168:
163:
159:
157:
146:
129:
120:
105:
96:
86:
79:
72:
65:
53:
33:
1687:: 467–488.
1213:"OSI Model"
1100:www.usg.edu
754:Frame Relay
126:engineering
1900:RFC Editor
1882:2021-12-08
1853:2021-12-08
1525:2021-12-08
1385:2018-03-19
1264:2021-12-08
1240:2021-12-08
1197:2021-12-08
1168:2021-12-08
1139:2021-12-08
1110:2021-12-08
1072:2018-03-20
941:2022-02-04
884:References
799:improve it
750:IEEE 802.3
564:RFC Editor
404:Standard.
193:RFC Editor
69:newspapers
36:references
1848:1059-1028
1787:cite book
1779:870649960
1497:746928702
1474:1744-6414
1359:March 11,
1311:March 11,
1062:2070-1721
981:1353-3452
923:1089-7801
803:verifying
316:OSI Model
214:Only the
1909:Category
1876:Archived
1701:25148769
1519:Archived
1379:Archived
1258:Archived
1191:Archived
1162:Archived
1133:Archived
1104:Archived
1066:Archived
989:27255607
935:Archived
931:26168365
849:See also
815:May 2022
518:(IRTF),
510:(ISOC),
506:(IETF),
475:Historic
209:Historic
179:Overview
138:Internet
997:3613408
797:Please
756:for WAN
514:(IAB),
434:actions
299:TLS/SSL
83:scholar
1846:
1814:
1777:
1767:
1699:
1511:"RFCs"
1495:
1472:
1401:
1231:
1060:
995:
987:
979:
929:
921:
708:, and
676:DECNET
669:TELNET
634:, and
247:TCP/IP
85:
78:
71:
64:
56:
1840:Wired
1812:JSTOR
1697:JSTOR
993:S2CID
927:S2CID
628:ASCII
374:BCP 9
293:HTTPS
264:IPsec
128:, an
90:JSTOR
76:books
1844:ISSN
1793:link
1775:OCLC
1765:ISBN
1746:2026
1663:2028
1629:3979
1596:7221
1562:5000
1515:IETF
1493:OCLC
1470:ISSN
1435:8416
1403:7100
1361:2016
1354:7127
1337:IETF
1313:2016
1306:7127
1289:IETF
1229:ISBN
1058:ISSN
1035:6410
1018:IETF
985:PMID
977:ISSN
919:ISSN
765:V.92
763:and
761:8P8C
742:and
732:and
706:HTML
661:ICMP
659:and
632:SCSI
551:RFCs
446:IESG
384:and
353:and
320:The
276:HTTP
216:IETF
62:news
1743:RFC
1733:doi
1689:doi
1660:RFC
1650:doi
1626:RFC
1616:doi
1593:RFC
1583:doi
1559:RFC
1549:doi
1462:doi
1432:RFC
1422:doi
1399:RFC
1351:RFC
1341:doi
1303:RFC
1293:doi
1221:doi
1032:RFC
1022:doi
969:doi
911:doi
801:by
744:IPX
734:SPX
730:TCP
710:URL
452:as
332:UDP
121:In
38:to
1911::
1870:.
1842:.
1838:.
1826:^
1801:^
1789:}}
1785:{{
1773:.
1741:.
1731:.
1709:^
1695:.
1685:30
1683:.
1671:^
1658:.
1648:.
1624:.
1591:.
1581:.
1557:.
1534:^
1517:.
1513:.
1468:.
1458:11
1456:.
1452:.
1430:.
1420:.
1377:.
1349:.
1335:.
1329:.
1301:.
1287:.
1281:.
1256:.
1227:,
1215:,
1189:.
1185:.
1160:.
1156:.
1131:.
1127:.
1102:.
1098:.
1064:.
1056:.
1052:.
1030:.
1020:.
1016:.
991:.
983:.
975:.
965:23
963:.
959:.
933:.
925:.
917:.
907:12
905:.
901:.
740:IP
704:,
657:IP
638:.
630:,
456:.
399:A
380:,
365:.
243:.
49:.
1885:.
1856:.
1820:.
1795:)
1781:.
1748:.
1735::
1703:.
1691::
1665:.
1652::
1631:.
1618::
1598:.
1585::
1564:.
1551::
1528:.
1499:.
1476:.
1464::
1437:.
1424::
1388:.
1363:.
1343::
1315:.
1295::
1267:.
1223::
1200:.
1171:.
1142:.
1113:.
1075:.
1037:.
1024::
999:.
971::
944:.
913::
828:)
822:(
817:)
813:(
795:.
663:.
112:)
106:(
101:)
97:(
87:·
80:·
73:·
66:·
43:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
