This document discusses different types of nodes in a peer-to-peer network: pure clients, pure peers, and client-peers. Pure clients only offer basic functions without implementing the distributed hash table (DHT), while pure peers implement the full DHT. Client-peers can act as either a client or peer depending on factors like battery level and network connectivity. The document also considers issues like how nodes transition between client and peer roles and how clients can look up services from multiple peers.

1. P2PSIP Clients draft-pascual-p2psip-clients-01 draft-zheng-p2psip-client-protocol-01 Marcin Matuszewski [email_address] Victor Pascual [email_address] Song Yongchao [email_address] Clients .ppt / 2008-03-1 4 / Marcin Matuszewski

2. Document update draft-pascual-p2psip-clients-01 Device do not need to become a peer In real-time systems the smaller number of peers the better Other applications may benefit from larger number of peers How to select devices that should become peers? draft-zheng-p2psip-client-protocol-01 Service lookup (LookUpServicePeer) Candidate associated peers are searched in the same way Status notification between the associated client and peer Do we need a separate message for service lookup? Clients .ppt / 2008-03-1 4 / Marcin Matuszewski

3. Why to be a client Battery consumption Traffic Not adequate resources Churn Easy implementation Policy … Being part of DHT requires energy and bandwidth! Clients .ppt / 2008-03-1 4 / Marcin Matuszewski

4. Three types of nodes (implementation perspective) Pure clients Offer PUT/GET/REMOVE/JOIN/LEAVE/NOTIFY/KEEP-ALIVE DO NOT implement DHT Pure peers Implement DHT or unstructured P2P algorithms Take part in overlay maintenance Route messages Store data records Client & peer Can be a peer or a client Can change status if needed battery, network connection, uptime Device that does not implement a particular DHT joins as a client Clients .ppt / 2008-03-1 4 / Marcin Matuszewski

5. Peer turning to Client and vice versa Clients .ppt / 2008-03-1 4 / Marcin Matuszewski How can a node indicate that it turns into a client/peer? Who should decide if a client can turn into a peer?

6. Client “connected” to multiple peers Reasons Fault tolerance Faster response time Client may keep connections to all peers Traffic, battery consumption is an issue Connect, do PUT/GET/REMOVE, and immediately leave Client connects to one peer and maintains a list of other peers without necessarily connecting to all of them Clients .ppt / 2008-03-1 4 / Marcin Matuszewski

7. Notification Info about other peers (e.g. Peer B) Peer status notification Clients .ppt / 2008-03-1 4 / Marcin Matuszewski