Next Generation Peer-to-Peer

1
Next Generation Peer-to-Peer

• Chris Gross
• Mario Hernandez
• Mark Shaver
• Mentor Dr. Gordon Springer

2
Background Introduction

• Internet began as Peer-to-peer (p2p)
• Early application Usenet
• Gnutella is decentralized
• But, easy way for mass infection of viruses

Need security!
3
Background/ Introduction

• Levels of firewall protection
• Gateway
• Router
• Firewall Problems
• False sense security
• Spoofing
• Constantly open ports
• Difficult to Use
• Slow down network traffic
• Firewalls Suck

4
Solution

• P2P has problems sending data through firewall
• Firewalls have problems with p2p

Solution?

• Design P2P with security embedded in the
  application

5
Solution Paradigm Shift

• Current paradigm
• - Assume the network is secure
• - Firewalls needed to provide security
• Better paradigm
• - Design applications with built in security
• - Eliminates need for firewalls
• Tool to help achieve this goal is IPV6

6
Background/Introduction

• IPV4 current standard
• - 32-bit address spacing (scalability)
• - no quality of service
• IPV6
• - 128-bit address spacing
• - quality of service embedded in protocol e.g.
  bandwidth reservation

7
Goals Objectives

• P2p with security capabilities
• Increase p2p performance (search success, network
  speed)
• Eliminate the need for P2ps to circumvent
  firewalls
• Dual stack processing for IPv4 and IPv6

8
Constraints

• Linux OS for the Compaq Tru64
• GNU (GNUs not Unix) development language
• IPv4 and IPv6 compatibility
• Gnutella protocol
• Must be completed by May 1st.

9
Performance Requirements

• Minimal slowdown of network traffic
• High speed p2p connections and downloads
• Mutual authentication of file transfer
• Protect computer from unwanted access

10
Cost/Resource Requirements

• GNU(Gnus Not Unix) IDE for Linux
• CodeWarrior 6.0 130.00
• EBW 122
• Compaq Tru64 with IPv4 and IPv6

11
Components of Approach

• Object Oriented system modeling
• Extend existing p2p applications
• SR6, Mutella, LimeWire
• Mutella Wins

12
Use Case Diagram
13
Testing Methods

• Unit Testing
• Design and test each class individually.
• Simulate several security breeches
• Test p2p connectivity

14
Scheduling (Extremely Tentative)

• We intend to have the final design completed by
  early December.
• System implemented by mid-March
• Complete Testing by April 15th.
• Present project on May 1st.

15
Scheduling Diagram Gantt
16
Alternative Designs (Java)

• Advantages
• Portable
• High built in security
• Disadvantages
• Much slower than C.
• Minimal control over system resources

17
Alternative Designs (Client-Server)

• Advantages
• Reliability
• Speed
• Disadvantages
• Legal issues (Napster)
• Server Maintenance cost

18
Questions or Suggestions?

• ?