A bootstrapping node, also known as a rendezvous host,[1] is a node in an overlay network that provides initial configuration information to newly joining nodes so that they may successfully join the overlay network.[2][3] Bootstrapping nodes are predominantly found in decentralized peer-to-peer (P2P) networks because of the dynamically changing identities and configurations of member nodes in these networks.
Overview
editWhen attempting to join a P2P network, specific discovery or membership protocols (or other configuration information) may be required, and, if a newly joining node is unaware of these protocols, the newly established joining node will not be able to communicate with other nodes and ultimately join the network.[3] Furthermore, these protocols and configuration requirements may dynamically change as the infrastructure and membership of the P2P network evolves.[1] Therefore, there is a need to be able to dynamically inform a newly joining node of the required protocols and configurations.[2]
Identifying a bootstrapping node
editSeveral methods may be used by a joining node to identify bootstrapping nodes:
- A joining node may have been pre-configured with the static addresses of the bootstrapping nodes.[2] In such a case, the bootstrapping node addresses cannot change, and therefore should be fault-tolerant members of the network, which are not able to leave the network.
- Alternatively, the bootstrap node can be identified via a DNS service, where a domain name resolves to one of the bootstrapping nodes' addresses.[1][4] This allows the bootstrapping nodes' addresses to change as needed.
Configuration information provided
editThe objective of the bootstrapping node is to provide newly joining nodes with sufficient configuration information so that the new node may then successfully join the network and access resources, such as shared content.[1] Discovery protocol information can instruct the new node how to discover peers on the network.[1] Membership protocol information can instruct the new node how to request-to-join and subsequently join peer groups on the network.[2] Other configuration information, such as overlay network dependent instructions, may be provided.[1][4] An example of overlay dependent instructions is instructing a new node how to obtain a zone of a CAN.[4] Further configuration information may be designed for P2P network admission control, used when joining a network that supports trust management, and include such things as encryption/signature protocols or admission policies.[3]
Networks that use bootstrapping nodes
editReferences
edit- ^ a b c d e f Francis, Paul (2000-04-02). "Yoid: Extending the Internet Multicast Architecture" (PDF). www.aciri.org. Retrieved 2008-12-24.
{{cite journal}}: Cite journal requires|journal=(help) - ^ a b c d Traversat; et al. (2006-06-20). "US Patent 7,065,579". Retrieved 2008-12-23.
- ^ a b c Saxena; et al. (2003). "Admission Control in Peer-to-Peer: Design and Performance Evaluation" (PDF). In ACM Workshop on Security of Ad Hoc and Sensor Networks (SASN) 2003. Retrieved 2008-12-24.
{{cite journal}}: Cite journal requires|journal=(help) - ^ a b c Ratnasamy; et al. (2001). "A Scalable Content-Addressable Network" (PDF). In Proceedings of ACM SIGCOMM 2001. Archived from the original (PDF) on 2008-08-07. Retrieved 2008-12-23.
{{cite journal}}: Cite journal requires|journal=(help)