Abstract :
Since its inception in 1986, the Internet Engineering Task Force (IETF) has helped drive Internet standards. Its guiding principle of “rough consensus and working code” has produced standards like TCP (Transmission Control Protocol), IP (Internet Protocol), and HTTP (Hypertext Transport Protocol). Companies widely adhere to these standards, yet the IETF has no authority to enforce them. Although initially funded by the National Science Foundation, the IETF has no official backing from the US Government; there is no policy requiring software or hardware to follow IETF-developed standards. So why do approximately 1600 people show up at a typical IETF meeting, and why do even large companies, which could well afford the effort to establish their own de facto standards, develop products in accordance with IETF standards? It all boils down to interoperability
Keywords :
Internet; open systems; standardisation; telecommunication standards; transport protocols; HTTP; Hypertext Transport Protocol; IETF; Internet Engineering Task Force; Internet Protocol; Internet standards; National Science Foundation; TCP/IP; Transmission Control Protocol; authority; interoperability; rough consensus; standards enforcement; working code; Asphalt; Contracts; Diffserv networks; Educational institutions; Internet; Marine technology; Proposals; Space technology; Throughput; Underwater vehicles;