TCP/IP is not a single protocol, nor is it, as its name might suggest, a pair of protocols. TCP/IP is actually a suite of protocols. In other words, it's a large group of protocols that work together. The TCP/IP designers' original intent was to create a protocol that could traverse various heterogeneous network environments while having the ability to take multiple routes to a final destination. This flexibility was crucial. TCP/IP, originally called NCP (Network Control Protocol), was a product of an experimental project commissioned by the Department of Defense of ARPANet (Advanced Research Project Agency Network) as an experimental protocol that traveled over packet-switched networks. The goal was to ensure that if a single part of the network became damaged or unreachable, transmission of critical data would continue to reach its destination on the network through alternate routes.
Despite its roots in the defense community, the development and evolution of TCP/IP cannot be attributed to any one group of individuals. TCP/IP is nonproprietary, and it's the accepted communications protocol on the Internet. Like other matters related to the Internet, TCP/IP standards are publicly available and published as RFCs (Requests For Comments) that are maintained by the Internet Architecture Board (IAB).The IAB allows any individual or company to submit or evaluate an RFC. RFCs can contain a variety of information; one use of RFCs is to publish proposals or new ideas for standards that might add to or change the functionality of the TCP/IP protocol suite in some way. RFCs are posted to the Internet for public review and are reviewed by IETF (Internet Engineering Task Force), a division of the IAB. After an appropriate amount of discussion and scrutiny, a newly proposed draft can be made into a standard that will then be adopted by the entire Internet development community. Because TCP/IP is based on open, nonproprietary standards, it has been scrutinized and revised by numerous people from all over the world, and has thus been continuously developed and improved since its inception.
TCP/IP is based on the idea of an open system (nonproprietary) model. With regard to system architecture, TCP/IP's functionality maps loosely to the OSI (Open Systems Interconnection) Reference Model, a basic system architectural reference designed for programmers to provide a common framework and design for network protocols. By using the OSI Model, protocol designers can ensure that the protocols they design meet at least the basic levels of functionality and that there is some degree of standardization between their implementation of a protocol and someone else's. Microsoft's TCP/IP is compliant with RFC-published TCP/IP standards. However, the Microsoft implementation includes support for a number of features not found in other versions of TCP/IP. (www.articlebase.com)
Despite its roots in the defense community, the development and evolution of TCP/IP cannot be attributed to any one group of individuals. TCP/IP is nonproprietary, and it's the accepted communications protocol on the Internet. Like other matters related to the Internet, TCP/IP standards are publicly available and published as RFCs (Requests For Comments) that are maintained by the Internet Architecture Board (IAB).The IAB allows any individual or company to submit or evaluate an RFC. RFCs can contain a variety of information; one use of RFCs is to publish proposals or new ideas for standards that might add to or change the functionality of the TCP/IP protocol suite in some way. RFCs are posted to the Internet for public review and are reviewed by IETF (Internet Engineering Task Force), a division of the IAB. After an appropriate amount of discussion and scrutiny, a newly proposed draft can be made into a standard that will then be adopted by the entire Internet development community. Because TCP/IP is based on open, nonproprietary standards, it has been scrutinized and revised by numerous people from all over the world, and has thus been continuously developed and improved since its inception.
TCP/IP is based on the idea of an open system (nonproprietary) model. With regard to system architecture, TCP/IP's functionality maps loosely to the OSI (Open Systems Interconnection) Reference Model, a basic system architectural reference designed for programmers to provide a common framework and design for network protocols. By using the OSI Model, protocol designers can ensure that the protocols they design meet at least the basic levels of functionality and that there is some degree of standardization between their implementation of a protocol and someone else's. Microsoft's TCP/IP is compliant with RFC-published TCP/IP standards. However, the Microsoft implementation includes support for a number of features not found in other versions of TCP/IP. (www.articlebase.com)
No comments:
Post a Comment