230 likes | 362 Views
In this presentation, Enrico Marocco explores the challenges and opportunities of Peer-to-Peer Session Initiation Protocol (P2PSIP) within limited or ephemeral network environments. Highlighting the convergence of mobile communication technologies such as UMTS, GSM, and 802.11, the talk emphasizes the need for distributed fault tolerance and collaborative cyber-communities. Addressing stakeholders such as telcos, vendors, and academics, the session examines the significance of municipal free wireless networks and the potential for self-sustained online communities, while considering implications for security and service provisioning.
E N D
Lucent, 2006, 26th October P2PSIP: Interworking Enrico Marocco Research Engineer enrico.marocco@telecomitalia.it
UMTS 802.16 SIP 802.11 GSM GPRS IMS The World is Converging Mobile
Toothing Communities Ad-Hoc Networks Municipal Free Wireless Networks SIP UMTS 802.16 GSM GPRS 802.11 IMS But Mobile is becoming Ephemeral
Limited or Ephemeral Network Environments • Characterized by physical constraints (e.g. space, time, number...) • Limited diffusion • Limited requirements (e.g. security, equipment...) • Highly specialized (e.g. messaging, gaming, ad-hoc applications...) • Almost isolated (or partially connected) • Collaborative • Self-Sustained Cyber-Communities
“Peer-to-Peer” Distribution of location and routing services for communication Distribution of storage service for file-sharing Technology in Limited or Ephemeral Environments • Unstable links • Cannot rely upon stable servers • Need of distributed fault tolerance (vs. single point of failure) • Missing or unconfigurable naming service • Cannot deploy stable servers • Need of multiple access points for resources (vs. centralization)
Who Cares? • Telcos? • Vendors? • Academics • Open Source • Users! IGNORE?
Cons Scarce security No identity assertion No protection against malicious peers Scarce connectivity Hard to go over locality No Services Peer-to-Peer Limited or Ephemeral Networks Pros • Ease of deployment • Need common devices • Click 'n go • Costless • Need cheap devices • No O&M • Increase of adoption • AUTOCONF, MANET • Just Applications
What can Operators do? • Ignore it • In ephemeral environments service provisioning is not feasible • Internet-like applications are out of core business • Fill the gaps • Provide access-level service for upgrading reachability • Provide “some” services to applications • Impede • Filter P2P traffic whenever is possible • Force the use of IMS
Internet HTTP SMTP POP3 “full” IP A Notable Example Municipal Free Wireless • Mesh of APs on street lamps • Full local connectivity • Cheap – Sustainable • 10-50 Mb/sec • Restricted Internet connection • Must serve Ms of users • Cannot support bandwidth-eager applications
Internet HTTP SMTP POP3 “full” IP Municipal Free Wireless Applications • Exploiting “global” connectivity • Email • Web browsing • Exploiting “local” connectivity • File sharing • VoIP
Municipal Free Wireless - VoIP • Cannot access the home network for call routing • Restricted connectivity • Cannot rely on central servers • Link weakness • Unaccessible configuration • Must rely on resources shared by users
P2PSIP Overlay rome.test.net INVITE bob@rome.test.net REGISTER bob@rome.test.net alice@rome.test.net bob@rome.test.net P2PSIP: How It Works
rome.test.net paris.test.org REGISTER bob@paris.test.org INVITE bob@rome.test.net alice@rome.test.net bob@rome.test.net bob@paris.test.net P2PSIP: What Is Missing ?
rome.test.net paris.test.org REGISTER bob@isp.test.com INVITE bob@isp.test.com alice@rome.test.net bob@isp.test.com P2PSIP: Providing Interworking isp.test.com
Clients Proxies Peers Super Peers Relay Agents P2PSIP: Actors
DNS p2psip.org P2PSIP: Architecture location SIP location location SIP location
Proxy Access to the Internet E.g. peers with DSL access Registered in the DNS with the overlay identifier Semi-stable Open issue: how to register? Client/Peer Must be able to route messages Media Relay Access to the Internet E.g. host with DSL access Must implement a relay mechanism TURN, TEREDO P2PSIP: New Elements
sip:example.com p2psip.org Get Proxy Get Relay INVITE Media sip:bob@example.com sip:alice@p2psip.org P2PSIP: Interworking 1/2 RFC3263 ICE
sip:example.com p2psip.org Get Proxy INVITE Get Relay Media sip:bob@example.com sip:alice@p2psip.org P2PSIP: Interworking 2/2 RFC3263
MAYBE Emergency calls Legal interception P2PSIP: Providing More Than Transport No • QoS YES • Identity • Gateways • Presence service • Conferencing • Voice mail
Do Not Repeat The Same Old Mistakes • Do not understimate • This applies to municipal and building networks, but could also extend to big Internet communities (Skype-like) • Go for a standard P2P solution • Remember the lesson learned from IM&P (ICQ + AIM + MSN + Yahoo!) • Keep it open • IMS is SIP based; let it also be SIP compliant • It is not services vs. applications • Voice is both a service and an application
Some Pointers • Municipal Free Wireless Networks • MuniWireless Web Portal (http://www.muniwireless.com/) • Earthlink Municipal Networks Web Page (http://www.emnwifi.net/) • P2PSIP • P2PSIP Project Page (http://p2psip.org) • Concept and terminology (draft-willis-p2psip-concepts) • SIP-P2PSIP Interworking (draft-marocco-p2psip-interwork) • IMS • ;-)
Thank You! Enrico Marocco enrico.marocco@telecomitalia.it http://sipdht.sourceforge.net