IETF-71 P2PSIP Clients

421 views
357 views

Published on

Published in: Technology, Sports
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
421
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

IETF-71 P2PSIP Clients

  1. 1. P2PSIP Clients <ul><li>draft-pascual-p2psip-clients-01 </li></ul><ul><li>draft-zheng-p2psip-client-protocol-01 </li></ul><ul><li>Marcin Matuszewski [email_address] </li></ul><ul><li>Victor Pascual [email_address] </li></ul><ul><li>Song Yongchao [email_address] </li></ul> Clients .ppt / 2008-03-1 4 / Marcin Matuszewski
  2. 2. Document update <ul><li>draft-pascual-p2psip-clients-01 </li></ul><ul><ul><li>Device do not need to become a peer </li></ul></ul><ul><ul><li>In real-time systems the smaller number of peers the better </li></ul></ul><ul><ul><li>Other applications may benefit from larger number of peers </li></ul></ul><ul><li>How to select devices that should become peers? </li></ul><ul><li>draft-zheng-p2psip-client-protocol-01 </li></ul><ul><ul><li>Service lookup (LookUpServicePeer) </li></ul></ul><ul><ul><li>Candidate associated peers are searched in the same way </li></ul></ul><ul><ul><li>Status notification between the associated client and peer </li></ul></ul><ul><li>Do we need a separate message for service lookup? </li></ul> Clients .ppt / 2008-03-1 4 / Marcin Matuszewski
  3. 3. Why to be a client <ul><ul><li>Battery consumption </li></ul></ul><ul><ul><li>Traffic </li></ul></ul><ul><ul><li>Not adequate resources </li></ul></ul><ul><ul><li>Churn </li></ul></ul><ul><ul><li>Easy implementation </li></ul></ul><ul><ul><li>Policy … </li></ul></ul><ul><ul><li>Being part of DHT requires energy and bandwidth! </li></ul></ul> Clients .ppt / 2008-03-1 4 / Marcin Matuszewski
  4. 4. Three types of nodes (implementation perspective) <ul><li>Pure clients </li></ul><ul><ul><li>Offer PUT/GET/REMOVE/JOIN/LEAVE/NOTIFY/KEEP-ALIVE </li></ul></ul><ul><ul><li>DO NOT implement DHT </li></ul></ul><ul><li>Pure peers </li></ul><ul><ul><li>Implement DHT or unstructured P2P algorithms </li></ul></ul><ul><ul><li>Take part in overlay maintenance </li></ul></ul><ul><ul><li>Route messages </li></ul></ul><ul><ul><li>Store data records </li></ul></ul><ul><li>Client & peer </li></ul><ul><ul><li>Can be a peer or a client </li></ul></ul><ul><ul><li>Can change status if needed </li></ul></ul><ul><ul><ul><li>battery, network connection, uptime </li></ul></ul></ul><ul><ul><li>Device that does not implement a particular DHT joins as a client </li></ul></ul> Clients .ppt / 2008-03-1 4 / Marcin Matuszewski
  5. 5. Peer turning to Client and vice versa Clients .ppt / 2008-03-1 4 / Marcin Matuszewski <ul><ul><li>How can a node indicate that it turns into a client/peer? </li></ul></ul><ul><ul><li>Who should decide if a client can turn into a peer? </li></ul></ul>
  6. 6. Client “connected” to multiple peers <ul><li>Reasons </li></ul><ul><ul><li>Fault tolerance </li></ul></ul><ul><ul><li>Faster response time </li></ul></ul><ul><li>Client may keep connections to all peers </li></ul><ul><ul><li>Traffic, battery consumption is an issue </li></ul></ul><ul><li>Connect, do PUT/GET/REMOVE, and immediately leave </li></ul><ul><li>Client connects to one peer and maintains a list of other peers without necessarily connecting to all of them </li></ul> Clients .ppt / 2008-03-1 4 / Marcin Matuszewski
  7. 7. Notification <ul><li>Info about other peers (e.g. Peer B) </li></ul><ul><li>Peer status notification </li></ul> Clients .ppt / 2008-03-1 4 / Marcin Matuszewski

×