Internet Standard: Difference between revisions

Content deleted Content added
Fix cite date error
m cite repair;
Line 1:
{{short description|Standard published by the Internet Engineering Task Force}}
{{primary sources|date=November 2015}}
An Internet Standard in computer network engineering refers to the normative specification of a technology that is appropriate for the Internet. Internet Standards allow interoperation of hardware and software from different sources which allows the internet to function.<ref>{{Cite journal|last=Leiba|first=Barry|date=January 2008|title=An Introduction to Internet Standards|url=http://ieeexplore.ieee.org/document/4428340/|journal=IEEE Internet Computing|volume=12|issue=1|pages=71–74|doi=10.1109/MIC.2008.2|issn=1089-7801}}</ref> They are the lingua franca of worldwide communications.<ref>{{Cite journal|last=Cath|first=Corinne|last2=Floridi|first2=Luciano|date=April 2017|title=The Design of the Internet’sInternet's Architecture by the Internet Engineering Task Force (IETF) and Human Rights|url=http://link.springer.com/10.1007/s11948-016-9793-y|journal=Science and Engineering Ethics|language=en|volume=23|issue=2|pages=449–468|doi=10.1007/s11948-016-9793-y|issn=1353-3452}}</ref>
 
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).
Line 84:
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 well-documented procedures for creating these standards. Once circulated, those standards are made easily accessible without any cost.
 
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 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.<ref>{{Cite journalIETF |last=Ma|first=D.|last2=Mandelberg|first2=D.|last3=Bruijnzeels|first3=T.|date=August 2018|title=Simplified Local Internet Number Resource Management with the RPKI (SLURM) |urlrfc=http://dx.8416 |doi.org/=10.17487/rfc8416}}</ref> 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.
 
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 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.<ref>{{Cite journal|last=Knieps|first=Günter|date=September 2015|title=ENTREPRENEURIAL TRAFFIC MANAGEMENT AND THE INTERNET ENGINEERING TASK FORCE|url=https://academic.oup.com/jcle/article-lookup/doi/10.1093/joclec/nhv018|journal=Journal of Competition Law and Economics|language=en|volume=11|issue=3|pages=727–745|doi=10.1093/joclec/nhv018|issn=1744-6414}}</ref> 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 descriptions for network processes such as remote network observing. For example, IETF emphasis the enlargement of technical 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.
Line 91:
 
== Internet Engineering Task Force ==
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 process, and publishing and accessing RFCs.<ref>{{Cite book|last=Society.|first=Internet Engineering Task Force. Internet|url=http://worldcat.org/oclc/746928702 |title=IETF journal. |date=2005-|publisher=Internet Society|oclc=746928702}}</ref>
 
=== RFCs ===
Line 97:
* Documents that contain technical specifications and notes for the Internet.
* The acronym RFC came from the phrase "Request For Comments" - this isn't used anymore today and is now simply referred to as RFCs.<ref>{{Cite web|title=RFCs|url=https://www.ietf.org/standards/rfcs/|access-date=2021-12-08|website=IETF|language=en}}</ref>
* The website ''RFC Editor'' is an official archive of internet standards, draft standards, and proposed standards.<ref name="dx.doi.org">{{Cite journalIETF |date=May 2008|title=Internet Official Protocol Standards|urldoi=http://dx.doi.org/10.17487/rfc5000 |rfc=5000}}</ref>
 
=== Internet Drafts ===
 
* Working documents of the IETF and its working groups.<ref>{{Cite journalIETF |last=Farrel|first=A.|date=April 2014|title=Handling of Internet-Drafts by IETF Working Groups|url=http://dx.doi.org/=10.17487/rfc7221 |rfc=7221}}</ref>
* Other groups may distribute working documents as Internet-Drafts
 
=== Intellectual property rights ===
 
* All IETF standards are freely available to view and read, and generally free to implement by anyone without permission or payment.<ref>{{Cite journalIETF |date=March 2005|title=Intellectual Property Rights in IETF Technology|url=http://dx.doi.org/=10.17487/rfc3979 |rfc=3979}}</ref>
 
=== Standards Process ===
 
* The process of creating a standard is straightforward - a specification goes through an extensive review process by the Internet community and revised through experience.<ref>{{Cite journalIETF |last=Hovey|first=R.|last2=Bradner|first2=S.|date=October 1996|title=The Organizations Involved in the IETF Standards Process|url=http://dx.doi.org/=10.17487/rfc2028 |rfc=2028}}</ref>
 
=== Publishing and accessing RFCs ===
Line 118:
 
== Types of Internet Standards ==
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.<ref name=":0">{{Cite journal|last=Nickerson|last2=Muehlen|date=2006|title=The Ecology of Standards Processes: Insights from Internet Standard Making|url=https://www.jstor.org/stable/=10.2307/25148769|journal=MIS Quarterly|volume=30|pages=467|doi=10.2307/25148769}}</ref> A de facto standard becomes a standard through widespread use within the tech community. A de jure standard is formally created by official standard-developing organizations.<ref name=":0" /> These standards undergo the [[Internet Standard#Standardization process|Internet Standards Process]]. Common de jure standards include [[ASCII]], [[SCSI]], and [[Internet protocol suite]].<ref name="dx.doi.org"/>
 
=== Internet Standard Specifications ===
Specifications subject to the Internet Standards Process can be categorized into one of the following: Technical Specification (TS) and Applicability Statement (AS).<ref name=":1">{{Cite journalIETF |last=Bradner|first=S.|date=October 1996|title=The Internet Standards Process -- Revision 3|urldoi=http://dx.doi.org/10.17487/rfc2026 |rfc=2026}}</ref> A Technical Specification is a statement describing all relevant aspects of a protocol, service, procedure, convention, or format.<ref name=":1" /> This 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.<ref name=":1" /> An AS also applies one of the following "requirement levels" to each of the TSs to which it refers:
 
* Required: Implementation of the referenced TS is required to achieve interoperability. For example, Internet systems using the [[Internet protocol suite|Internet Protocol Suite]] are required to implement [[IP address|IP]] and [[Internet Control Message Protocol|ICMP]].<ref name=":1" />
Line 131:
==== Web Standards ====
TCP/ IP Model & associated Internet Standards
[[Web standards]] are a type of internet standard which define aspects of the [[World Wide Web]]. They allow for the building and rendering of websites. The three key standards used by the World Wide Web are [[Hypertext Transfer Protocol]], [[HTML]], and [[URL]].<ref>{{Cite book|last=Comer|first=Douglas|url=https://www.worldcat.org/oclc/870649960 |title=Computer networks and Internets|date=2015|isbn=978-0-13-358793-7|edition=Sixth edition|location=Boston, MassachusettsMA |oclc=870649960}}</ref> Respectively, they specify the content and layout of a web page, what web page identifiers mean, and the transfer of data between a browser and a web server.
 
==== Network Standards ====
Line 145:
== Official Internet Protocol Standards ==
 
* The most recent document that has been published by the IETF is titled ''Registration Data Access Protocol (RDAP) Query Format'' or <nowiki>RFC 9082</nowiki> and is archived on the site ''RFC-Editor.''<ref name="Hollenbeck">{{Cite journalIETF |last=Hollenbeck|first=S.|last2=Newton|first2=A.|date=June 2021|title=Registration Data Access Protocol (RDAP) Query Format|urldoi=http://dx.doi.org/10.17487/rfc9082 |rfc=9082}}</ref> The abstract of the document explains that it "describes uniform patterns to construct HTTP URLs that may be used to retrieve registration information from registries using "RESTful" web access patterns".<ref name="Hollenbeck"/> RDAP allows users to access current registration data and was created to replace the WHOIS protocol.<ref>{{Cite journalIETF |last=Hollenbeck|first=S.|last2=Carney|first2=R.|date=May 2019|title=vCard Format Extensions: ICANN Extensions for the Registration Data Access Protocol (RDAP)|urldoi=http://dx.doi.org/10.17487/rfc8605 |rfc=8605}}</ref>
* Another internet standard protocol was published by the IETF in June 2021 containing information about JSON data structures representing registration information maintained by Regional Internet Registries (RIRs) and Domain Name Registries (DNRs). The abstract goes on to say that those data structures are used to form Registration Data Access Protocol (RDAP) query responses. This document makes <nowiki>RFC 7483</nowiki> obsolete.<ref>{{Cite journalIETF |last=Hollenbeck|first=S.|last2=Newton|first2=A.|date=June 2021|title=JSON Responses for the Registration Data Access Protocol (RDAP)|urldoi=http://dx.doi.org/10.17487/rfc9083 |rfc=9083}}</ref>
 
== Current Internet Standard Issues ==
Even now, the internet is rife with Internet Standard issues. In October 2021, Facebook users, as well as users of its other related apps such as WhatsApp, Messenger, Oculus, and Instagram found themselves without service for 6 hours. The outage extended to internal communications at the companies themselves as they relied on their internal communications platform, Workplace.<ref>{{Cite news|last=Isaac|first=Mike|last2=Frenkel|first2=Sheera|date=2021-10-04|title=Gone in Minutes, Out for Hours: Outage Shakes Facebook|language=en-US|work=The New York Times|url=https://www.nytimes.com/2021/10/04/technology/facebook-down.html |url-access=subscription |access-date=2021-12-08|issn=0362-4331}}</ref> Outside of the company, many businesses and websites were severely affected. Many websites embed scripts for Like buttons or comment sections; they also had increased loading times because they were trying to use something that did not exist. Others rely on Facebook and WhatsApp in order to fulfill orders, communicate with customers, and generally conduct business.    
 
The cause of the loss of service started as regular maintenance. Facebook has multiple facilities and the command was issued in order to see how available the backbone connection between them was. In the end, it accidentally deleted them. Typically, such a flawed command would not have run. However, there was a bug while checking the command.<ref>{{Cite web|title=Facebook explains how its October 4th outage started|url=https://www.engadget.com/facebook-outage-explainer-193155776.html|access-date=2021-12-08|website=Engadget|language=en-US}}</ref> Consequently, in a domino effect of issues, Facebook’sFacebook's DNS servers could not find the data centers. From there, the BGP routing information stopped being advertised to the rest of the internet.<ref name=":3">{{Cite journalreport |last=Sherman|first=Justin|date=1 October 2020|titlechapter=MAPPINGMapping PRIVATEPrivate SECTORSector INFLUENCEInfluence ONon THEthe INTERNETInternet: STARTINGStarting WITHwith INTERNETInternet Protocols PROTOCOLS|urltitle=httpsThe Politics of Internet Security://www. Private Industry and the Future of the Web |publisher=Atlantic Council|jstor.org/stable/=resrep26661.5 |jstor-access=free |pages=4–7}}</ref> It was as if Facebook and other branches were wiped from existence.  
 
== The Future of Internet Standards ==
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 Border Gateway Protocol (BGP) and Domain Name System (DNS).<ref name=":3" />  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.<ref name=":3" />
 
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.<ref name=":4">{{Cite news|last=Newman|first=Lily Hay|title=A Broken Piece of Internet Backbone Might Finally Get Fixed|language=en-US|work=Wired|url=https://www.wired.com/story/bgp-routing-manrs-google-fix/|access-date=2021-12-08|issn=1059-1028}}</ref> Users and companies submit routes and check other users’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.<ref name=":4" /> 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.<ref>{{Cite web|date=2014-10-07|title=DNSSEC: An Introduction|url=http://blog.cloudflare.com/dnssec-an-introduction/|access-date=2021-12-08|website=The Cloudflare Blog|language=en}}</ref>
 
Some companies have taken the initiative to secure internet protocols. It is up to the rest to make it more widespread.