Service Discovery FURPS
Functionality
- Libp2p Kad-DHT nodes can advertise their own addresses and capabilities in a signed record
- Libp2p Kad-DHT nodes can discover and validate the signed records of random, advertised peers
- Libp2p Kad-DHT nodes can filter discovered records for specific capabilities
- Libp2p nodes can use a general service discovery API to discover peers with specific capabilities
- The service discovery protocol adapts DISC-NG for Kad-DHT to ensure efficient service discovery
- Client nodes can discover addresses of peers with specific capabilities without participating in the Kad-DHT
- Service discovery correctly discovers all advertised peers in a topology of several thousand nodes
- Service discovery correctly discovers peers advertising a sparse service in a topology of several thousand nodes
Usability
- The service discovery protocol is published in a specification
- A PoC implementation accompanies the published protocol
- The PoC implementation contains instructions to allow open dogfooding
- A forum post introduces the new protocol, explains privacy tradeoffs, and links to spec and PoC implementation
- A Kad-DHT discovery protocol is published in a specification
- The Kad-DHT discovery API is available in Nim
- The reference Kad-DHT discovery implementation is completed in Nim over the nim-libp2p Kad-DHT implementation
- The reference service discovery implementation is completed in Nim over the nim-libp2p Kad-DHT implementation
- Service discovery is integrated in Logos Delivery to discover libp2p mix nodes
- The service discovery module is available as a Logos Core module
- The service discovery API is published in a specification
- An extensible peer record library allows application modules to create and maintain discoverable records
- Service discovery is integrated into
chat2mixapplication for dogfooding - Service discovery is built into Logos Delivery as a separate Logos core module
- Service discovery can be configured in Logos Delivery as alternative ambient peer discovery to discv5
- A research post introducing the service discovery protocol and its implementation, including DST performance results, is published on the Logos research blog
- An analysis enumerating privacy-leaking actions in the service discovery protocol is published
- A survey of anonymisation techniques applicable to DHT-based service discovery, including the Octopus protocol and mix-based approaches, is published
- A roadmap for introducing anonymity properties into service discovery, including dependencies on the libp2p mix protocol, is published
Reliability
Performance
- The service discovery module provides comparable performance to discv5 when all nodes support the same service
- The service discovery module performs better than discv5 to find a sparse service
- Service discovery integrated in Logos Delivery provides comparable performance to discv5 when all nodes support the same service
- Service discovery integrated in Logos Delivery performs better than discv5 to find a sparse service
Supportability
- Service discovery can be functionally validated in large-scale standalone DST simulations
- The service discovery module can be benchmarked in large-scale standalone DST simulations
- Logos Delivery with integrated service discovery can be validated and benchmarked in large-scale DST simulations
Miscellaneous dependencies:
- Dependency on nim-libp2p implementation of Kad-DHT
- Dependency on DST for benchmarking and iterative improvement
Functionality
XX. Service discovery does not reveal to DHT intermediary nodes the full service lookup intent of a querying node XX. Service discovery protects a querying node’s network identity from correlation with their service lookup patterns by a passive network observer XX. A node’s advertisements of multiple services are not linkable to each other by passive DHT observers XX. Service discovery request routing can be anonymised through an anonymous transport layer such as the libp2p mix protocol