1 / 12

Standards-Based P2P Communications Systems

Standards-Based P2P Communications Systems. David A. Bryan College of William and Mary April 1, 2005 Advisor: Bruce B. Lowekamp. VoIP/IM. VoIP – Voice over IP (Internet Protocol) IM – Instant Messaging (such as AOL)

laury
Télécharger la présentation

Standards-Based P2P Communications Systems

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Standards-Based P2P Communications Systems David A. Bryan College of William and Mary April 1, 2005 Advisor: Bruce B. Lowekamp

  2. VoIP/IM • VoIP – Voice over IP (Internet Protocol) • IM – Instant Messaging (such as AOL) • Communications systems running over a network – not always the public Internet • Private networks (corporation, research lab) • Remote/ephemeral networks (sensor networks, meetings, battlefields, etc.) • Next generation (3G and later) cellular phones run over IP networks

  3. Traditional Architecture(Client/Server)

  4. Problems with Traditional Architecture Organization B Internet Organization A

  5. Peer-to-Peer (P2P) • Instead of a central server providing services, the members of the network collaborate to provide them as peers • Each node in addition to be a client is responsible for some portion of server work • Classic example is file sharing (Napster and the like)

  6. P2P Architecture

  7. Peer-to-Peer (P2P) Advantages • Scales Well (as new nodes join, they bring more server power) • Highly distributed • Low maintenance • Robust (one node failure doesn’t hurt network) • Can be run internally (with NO outside connections)

  8. Peer-to-Peer (P2P) Problems • Instead of a central server, relying on other possibly “bad” nodes • Other nodes “snooping” • Abuse (for example filesharing) • Denial of Service (DoS) • Node prevents/denies access to other nodes • Sybil attacks • Corrupting information

  9. SOSIMPLE • SIP • IETF (Internet Engineering Task Force) defined a protocol for VoIP, called SIP • Designed for packet networks, useful for any sort of multimedia session establishment • Support for integration with email/web services • SIMPLE is a set of extensions to SIP to support instant messaging • SOSIMPLE : Self-Organized SIMPLE

  10. Why SIP? • Widely used today for VoIP and IM • Vonage, Microsoft MSN • Large investment • $$$ (phones, gateways) • Effort (applications, stacks) • Reuse/cheap COTS devices • SIP is extensible – we can extend for P2P • Used SIP’s REGISTRATION support

  11. Research • Defining a protocol for P2P SIP • Completed this work, presented it to the IETF for standardization • Implementation • Currently finishing up a working version as a proof-of-concept • Security Concepts • Scalability and Routing • Simulations • Social Routing

  12. Questions? • Email : bryan@cs.wm.edu • Web : • http://www.cs.wm.edu/~bryan • http://www.p2psip.org • Documents (available at above sites) • IETF draft describing protocol • White papers/publications describing our approach and research

More Related