ARPAnet (Advanced Research Projects Agency Network)
ARPANET (Advanced Research Projects Agency Network) is a computer network made by ARPA (Advanced Research Project Agency) of the America Department of Defense in 1969.
ARPANET functioned as a means of trial latest computer network technology of his day, such as packet switching technology and into the beginning of the establishment of the current Internet.
Network Control Protocol (NCP) is the first standard network protocols on the ARPANET. NCP perfected and launched in December 1990 by the Network Working Group (NWG) led by Steve Crocker, who is also the inventor of Request for Comments.
ARPANET functioned as a means of trial latest computer network technology of his day, such as packet switching technology and into the beginning of the establishment of the current Internet.
Network Control Protocol (NCP) is the first standard network protocols on the ARPANET. NCP perfected and launched in December 1990 by the Network Working Group (NWG) led by Steve Crocker, who is also the inventor of Request for Comments.
ARPANET History
In 1957 the U.S. Department of Defense (DoD - Department of Defense) formed ARPA (Advanced Research Projects Agency) in response to the launch of the Soviet Sputnik. ARPA charge of improving technological capabilities that can be utilized by the military. ARPA actually do not have expert knowledge or laboratory. Owned only a small office and budget (for standard Pentagon) alone. ARPA carry out their duties to provide assistance and perform contracts with universities and companies that have ideas that are considered promising for its operations.
In the mid 1960s, the height of the Cold War, DoD would like to have a command and control network that can defend itself in the event of nuclear war. Traditional telephone networks are considered unsafe. Because if one path is lost, then this may result in the cessation of all conversations that use the network or even the only use part of the network suddenly. To resolve this issue change the direction of DoD research, ARPA.
In cooperation with several universities, ARPA decided that the required DoD network is packet-switching form consisting of a subnet and host computers. In December 1968, the ARPA gave the contract to BBN, a consulting firm in Cambridge, Massachusetts to build the network and make the supporting software.
Although there are flaws in the software problems, in December 1969 successfully launched an experimental network connecting the four vertices are UCLA, UCSB, SRI and Utah University. The fourth node does have various contracts with ARPA, and each node has a host computer that is completely different and incompatible with each other. ARPANET network is growing rapidly soon covers the whole of the U.S. in its first three years.
In addition to helping the growth of the ARPANET is still premature, ARPA also funded research satellite network and mobile packet radio networks. These experiments also showed that the ARPANET protocols that have been there do not suitable to operate on multiple networks. These observations are encouraging more and more research on protocols, culminating in the discovery of the model and the TCP / IP protocol. TCP / IP is specifically designed to handle communication through the internetwork, something that is becoming increasingly important as more networks and LANs that are connected to the ARPANET.
To encourage the use of these new protocols, ARPA entered into several contracts with BBN and the University of California at Berkeley to integrate these protocols into Berkeley UNIX. Researchers at Berkeley developed a program interface (interface) to the network (socket) that makes it easy and write some utility programs, applications and network management to make the system easier to operate.
In 1983, the ARPANET has a large network and it can be considered stable and successful. Until this situation, ARPA network management handed over to the Defense Communications Agency (DCA) to run the ARPANET as an operational network. DCA first thing to do is separate the military network into separate subnets, MILNET, gateway-gateway which has a very strict distinction between MILNET with the rest of the subnet other research.
During the 1980s, additional networks, especially LANs, the more that is connected to the ARPANET. In line with the increased breadth of the network, host-even more expensive. Because the DNS (Domain Naming System) was formed to organize machines into domain-specific and domain mapping host names into IP addresses. Since then, the DNS be generalized systems and distributed databases to store a variety of information related to naming.
In 1990, ARPANET had been composed by the new networks, which is actually born by the ARPANET. After the ARPANET ceased operations and dismantled. Until now, MILNET still operating.
In the mid 1960s, the height of the Cold War, DoD would like to have a command and control network that can defend itself in the event of nuclear war. Traditional telephone networks are considered unsafe. Because if one path is lost, then this may result in the cessation of all conversations that use the network or even the only use part of the network suddenly. To resolve this issue change the direction of DoD research, ARPA.
In cooperation with several universities, ARPA decided that the required DoD network is packet-switching form consisting of a subnet and host computers. In December 1968, the ARPA gave the contract to BBN, a consulting firm in Cambridge, Massachusetts to build the network and make the supporting software.
Although there are flaws in the software problems, in December 1969 successfully launched an experimental network connecting the four vertices are UCLA, UCSB, SRI and Utah University. The fourth node does have various contracts with ARPA, and each node has a host computer that is completely different and incompatible with each other. ARPANET network is growing rapidly soon covers the whole of the U.S. in its first three years.
In addition to helping the growth of the ARPANET is still premature, ARPA also funded research satellite network and mobile packet radio networks. These experiments also showed that the ARPANET protocols that have been there do not suitable to operate on multiple networks. These observations are encouraging more and more research on protocols, culminating in the discovery of the model and the TCP / IP protocol. TCP / IP is specifically designed to handle communication through the internetwork, something that is becoming increasingly important as more networks and LANs that are connected to the ARPANET.
To encourage the use of these new protocols, ARPA entered into several contracts with BBN and the University of California at Berkeley to integrate these protocols into Berkeley UNIX. Researchers at Berkeley developed a program interface (interface) to the network (socket) that makes it easy and write some utility programs, applications and network management to make the system easier to operate.
In 1983, the ARPANET has a large network and it can be considered stable and successful. Until this situation, ARPA network management handed over to the Defense Communications Agency (DCA) to run the ARPANET as an operational network. DCA first thing to do is separate the military network into separate subnets, MILNET, gateway-gateway which has a very strict distinction between MILNET with the rest of the subnet other research.
During the 1980s, additional networks, especially LANs, the more that is connected to the ARPANET. In line with the increased breadth of the network, host-even more expensive. Because the DNS (Domain Naming System) was formed to organize machines into domain-specific and domain mapping host names into IP addresses. Since then, the DNS be generalized systems and distributed databases to store a variety of information related to naming.
In 1990, ARPANET had been composed by the new networks, which is actually born by the ARPANET. After the ARPANET ceased operations and dismantled. Until now, MILNET still operating.
ARPAnet History
Softwere And Protocol
The starting point for host-to-host communication on the ARPANET in 1969 was the 1822 protocol, which defined the transmission of messages to an IMP. The message format was designed to work unambiguously with a broad
range of computer architectures. An 1822 message essentially consisted
of a message type, a numeric host address, and a data field. To send a
data message to another host, the transmitting host formatted a data
message containing the destination host's address and the data message
being sent, and then transmitted the message through the 1822 hardware
interface. The IMP then delivered the message to its destination
address, either by delivering it to a locally connected host, or by
delivering it to another IMP. When the message was ultimately delivered
to the destination host, the receiving IMP would transmit a Ready for Next Message (RFNM) acknowledgement to the sending, host IMP.
Unlike modern Internet datagrams, the ARPANET was designed to
reliably transmit 1822 messages, and to inform the host computer when it
loses a message; the contemporary IP is unreliable, whereas the TCP
is reliable. Nonetheless, the 1822 protocol proved inadequate for
handling multiple connections among different applications residing in a
host computer. This problem was addressed with the Network Control Program
(NCP), which provided a standard method to establish reliable,
flow-controlled, bidirectional communications links among different
processes in different host computers. The NCP interface allowed application software to connect across the ARPANET by implementing higher-level communication protocols, an early example of the protocol layering concept incorporated to the OSI model.
In 1983, TCP/IP protocols replaced NCP as the ARPANET's principal protocol, and the ARPANET then became one component of the early Internet.
Network applications
NCP provided a standard set of network services that could be shared
by several applications running on a single host computer. This led to
the evolution of application protocols that operated, more or
less, independently of the underlying network service. When the ARPANET
migrated to the Internet protocols in 1983, the major application
protocols migrated with it.
- E-mail: In 1971, Ray Tomlinson, of BBN sent the first network e-mail (RFC 524, RFC 561). By 1973, e-mail constituted 75 percent of ARPANET traffic.
- File transfer: By 1973, the File Transfer Protocol (FTP) specification had been defined (RFC 354) and implemented, enabling file transfers over the ARPANET.
Voice traffic: The Network Voice Protocol (NVP) specifications were defined in 1977 (RFC 741), then implemented, but, because of technical shortcomings, conference calls over the ARPANET never worked well; the contemporary Voice over Internet Protocol (packet voice) was decades away.
WARNING:
BalasHapusNO BUDGET
NO INVEST
BAASKE LABORATORIES GROUP
IN GRÜNDUNG
ALL FINITE ALGORITHMS - UNLIMITED
PARADOXA RESEARCH