Peer-to-peer

From Citizendium, the Citizens' Compendium
Jump to: navigation, search
This article is developing and not approved.
Main Article
Talk
Definition [?]
Related Articles  [?]
Bibliography  [?]
External Links  [?]
Citable Version  [?]
 
This editable Main Article is under development and not meant to be cited; by editing it you can help to improve it towards a future approved, citable version. These unapproved articles are subject to a disclaimer.

A peer-to-peer (P2P) network is a type of distributed system for which clients and servers are not distinguished from each other. All computers in the shared network, usually the public Internet are considered peers and can act as both clients and servers. Computers act as clients when requesting services from their peers and as servers when providing services. This is an actively emerging technology where research and deployment are closely coupled.[1]

In looking at peer-to-peer applications, the difference among the mechanisms of transfer, the operational aspects of providing service, and the ownership of data all need to be considered. Some objections, ostensibly to P2P, are actually objections to sharing data (e.g., music) where the owner charges for access to material. In other cases, a network operator has had uncontrolled P2P, often with multiple exchanges for the same data, overwhelm network capacity.

P2P has gained an unfortunate association with unauthorized dissemination of intellectual property, using a term deliberately more neutral and general than "piracy". Intellectual property can be sent without P2P, and P2P can and is used for many internal operations among unquestionably legal users.

As mentioned, the issues are sometimes more related to traffic volume than property rights. See legal and economic issues below.

Advantages

As opposed to traditional client-server systems in which the server can create a bottleneck, peer-to-peer systems are more versatile in satisfying service requests as all nodes in such a system can act as servers.

Assuming content is replicated, there is no single point of failure. This is especially attractive in military networks where nodes may be destroyed, such as Cooperative Engagement Capability. Such military P2P applications run over secure networks that still support the needed any-to-any topology.

It lends itself to support of federated databases. This may be necessary for such applications as national health care information exchange, but with obvious security concerns.

When the specific application involves not just passive information sharing, but transactional data exchange, P2P with adequate security may be a viable approach. [2]

Disadvantages

When all content is distributed, there are more opportunities for security compromise, such as alteration of content.

Unless designed and administered carefully, unlimited P2P traffic can generate a great amount of traffic. While issues here involve both the technology (i.e., many independent flows) and typical content (e.g., entertainment), the traffic load may be much greater than the load for which the network was designed. Especially in university networks, P2P traffic has sufficiently overloaded the network such that educational and research activities cannot get adequate bandwidth.

Some service providers have, variously, completely blocked, or rate-limited, P2P traffic. Unquestionably, this can cause resentment. Much depends on the language of the service contract: is there a specific or implied limit on bandwidth use?

Especially when the service provider, such as a cable television operator, also is a content provider, there can be a perceived conflict of interest. Under the principle of net neutrality, a connectivity provider cannot give preferential or degraded service to their own content, or to a competitor. At the same time, a connectivity provider has an implied responsibility to deliver minimal service, which it cannot do with overloaded facilities. There is a real cost to increasing capacity, which might not have been part of the original pricing model that did not consider P2P.

Principles of operation

To request or provide services in a peer-to-peer network, all nodes must first join the network. Once a node is part of the network, service requests can be performed in two common ways.

  • On joining a network, all nodes register the services they provide with a centralized lookup service. When a node, acting as a client, desires a service, it contacts the centralized lookup service to find out which node provides this service. After obtaining this information, the client node continues all communication with its servicing (server) peer
  • When a node desires a service, it broadcasts this request to all other nodes on the network. Any nodes that provide this service then respond to the requesting node. A discovery protocol is required to support this approach.

Legal and economic issues

In the U.S., the Higher Education Act, largely due to pressure by the recording and film industries, requires colleges and universities to monitor and police illegal file sharing. The institutions are “required to consider the use of technology-based deterrents” (e.g., such as traffic monitoring, quotas, and bandwidth shaping) which are not general solutions, may lead to a "technology" war much like spam/anti-spam, and imposes operational cost on the network opreators. [3] The Campus Computing Project, which shares information about educational networks and their operation, did a survey of the impact and cost of P2P. Kenneth C. Green, who ran the P2P survey, said the costs of enforcement could run into hundreds of thousands of dollars (USD) annually. Green has been a critic of the entertainment industry's concerns and enforcement. [4]

Nevertheless, academic organizations also have reported that student downloading of entertainment has a significant impact on the bandwidth needed for their research and education missions. Service providers have discussed pricing alternatives for high-bandwidth users. [5]

This U.S. law also mandates that educational institutions inform their students about the legalities of sharing copyrighted works and to offer — but not mandate — legal alternatives to illegal information sharing networks (e.g., Ruckus and Napster).

References

  1. J. Risson, T. Moors (September 2007), Survey of Research towards Robust Peer-to-Peer Networks: Search Methods, RFC4981
  2. D. Moberg, R. Drummond. (July 2005), MIME-Based Secure Peer-to-Peer Business Data Interchange Using HTTP, Applicability Statement 2 (AS2), RFC4130
  3. "The Costs of Policing Campus Networks", Inside Higher Ed, October 20, 2008
  4. Green, Kenneth C. (November 15, 2007), "Swiftboating Higher Education on P2P", Inside Higher Ed
  5. Nieminen, Klaus (2004), Antila, Johanna, ed., Current Topics in IP Networks, Department of Electrical and Communications Engineering, Helsinki University of Technology, pp. 95-105