Regarding Henning's comment that DHT lookup seems sufficient for handling service lookups, there have been a number of papers which directly use the DHT for - serving DNS records - locating relay peers in an overlay, including discovery by network position - location telephony feature serving peers in an overlay - locating servers for other service discovery mechanisms like SLP
no modification to the DHT or overlay protocol was needed to support these cases. as long as you can describe a service with a key that all participating peers understand, the DHT should work for service lookup. there are some cases where the service-related resource's availability is dynamic (e.g., relay load for admission control), which could be part of the advertisement. then there is a tradeoff between updating the DHT-stored advertisement when the load changes or leaving it for service invocation time for the invoking peer to find out. John _______________________________________________ P2PSIP mailing list [email protected] https://www.ietf.org/mailman/listinfo/p2psip
