> An example of a "pervasively supported mechanism" is the SEP > technique > of having the receiver respond not just with whether it has the > resource, but whether it knows where to find the resource (from > exchanges with its neighbors.) Since that would seem to be > independent > of any particular usage, it is a mechanism which, if you want it > at all, > you want supported by every node (i.e. pervasive.) > I can imagine other techniques.
That's right. The method proposed by SEP could work in both structured and unstructured overlay. What it requires node to do is to check its routing state whether there are peers providing the desired service while processing service searching message, in SEP, it is LookupServicePeer message. > > PS: The reason I was asking about whether it is a single service > (TURN) > or multiple is that if we are going to end up with multiple > "usages" > which are essentially identical, it would be nice not to need to > redefine things for each service. As written Reload requires that > the > usage be redefined each time just to discover another underlying > service. SEP tries to propose a general method to search service. _______________________________________________ P2PSIP mailing list [email protected] https://www.ietf.org/mailman/listinfo/p2psip
