The number of hosts currently connected to the Internet is said to be on the order of several hundred million. Using the Internet, people can now obtain information from around the world by sitting in front of a personal computer. To support the Internet, there are two main communication schemes: Transmission Control Protocol (TCP) for transmitting packets without error between end hosts, and Internet Protocol (IP) for delivering packets from a send host to a receive host via routers within the network. In this regard, the Internet is called a "best-effort network" (in which a network delivers packets between end hosts as quickly as it can) because IP only guarantees connectivity between end hosts in the network.
At the same time, higher processing speeds at end hosts and the development of multimedia, high-speed applications has prompted users to demand various levels of communications quality (referred to as Quality of Service, or QoS). The Integrated Services (IntServ) network was initially proposed as a mechanism for satisfying this demand, and it became the target of standardization activities at the Internet Engineering Task Force (IETF), an Internet standardization body. Though slated to be the platform for future multimedia networks, it was quickly pointed out that IntServ would suffer from problems related to scalability and deployment given the existing network. The Differentiated Services (DiffServ) network was then proposed with the aim of solving the above two problems by giving up a QoS guarantee but by differentiating between connections in a QoS manner. Here too, however, several problems were pointed out with DiffServ architecture, and this approach has not found widespread use as a result.
The following problems are common to the above two types of networks. First, for IntServ, the QoS guarantee means that it must secure network resources at all routers between the send and receive hosts. This means that the transmission path must be decided beforehand, which in turn means that the mechanism itself will collapse if any router or circuit on that path fails during a communication session. This is a problem that also affects DiffServ. Furthermore, as mobile communication technology continues to develop, the mobility of end hosts means that the assumption itself of semi-fixed network resources between end hosts will no longer hold even without the occurrence of equipment failures.
Against the above background, recent years have seen the appearance of Peer-to-Peer (P2P) networks that achieve services through direct communication between end hosts. The P2P format aims to solve some of the key problems of server-based networks such as the World Wide Web including system vulnerability, lack of scalability, and performance limitations due to server bottlenecks. By breaking away from a server-based Web system, the introduction of P2P networks is expected to provide fault tolerance and scalability, to reduce the initial deployment cost and management cost of servers and the network by making intermediary servers unnecessary (disintermediation), and, as a result, to eliminate the need for information-system operators and managers. This elimination of intermediary servers also means that users can join a variety of communities enabling the promotion of independent activities based on autonomy, distribution, and cooperation as appropriate for the information age.
However, on comparing a pure P2P network that floods the entire network with queries to find needed information with a hybrid-type P2P network that improves search efficiency by introducing a server that manages metadata (information that indicates the whereabouts of other information), it was found that scalability in a P2P network has an inverse relationship with fault tolerance and performance, and that a comprehensive solution to all problems has yet to be obtained.
As shown by the above examples, it is not actually that difficult to solve individual problems in a network. There have been many similar problems in the past that can be referenced when designing solutions. The really difficult problem to solve is to:
- Determine the limits of current hardware and software technology and predict future technical limitations;
- Clarify the network service image that is needed now and in the future; and
- Come up with a network design in harmony with all of the above.
This problem is none other than one of constructing appropriate network architecture, which is the goal of our research group.












