On Tue, Feb 10, 2009 at 12:01 PM, Dan York <[email protected]> wrote: > > On Feb 10, 2009, at 1:55 AM, Das, Saumitra wrote: > >> Handling mobile nodes can be done in the framework of the base draft. For >> example, the DHT protocol itself can be different if >> the operating conditions are such that there is a lot of moiblity. There >> are several proposals for DHTs to operate efficiently on highly >> mobile networks such as MANETs. These should be doable under the >> pluggability principle of RELOAD. > > DY> Perhaps this has been discussed a hundred times before and I've missed > it... but doesn't allowing different DHTs to be used in RELOAD introduce an > interop issue? i.e. Phones from Vendor A and Vendor B both nominally > support "P2PSIP" but turn out to not be able to interoperate because their > *implementations* of P2PSIP use different DHT algorithms/protocols?
Here I'd say: "Chord is mandated by default. If any other algorithm is used and you don't support it, act as a client" > DY> So we wind up with actually having multiple different P2PSIP variations: > P2PSIP/DHT1, P2PSIP/DHT2, P2PSIP/DHT3, etc. With the result being that > vendors must either choose a DHT implementation to support or having to > support several of them? (And yes, I realize that Chord is mandated by > default.) It's not clear to me from reading the draft at: > > http://tools.ietf.org/html/draft-ietf-p2psip-base-01#page-25 > > DY> Or later in Section 5 how the "overlay algorithm" is specified or known. > When I do a "JoinReq" as defined in section 5.3 ( > http://tools.ietf.org/html/draft-ietf-p2psip-base-01#section-5.3 ) how do I > know that my P2PSIP implementations DHT algorithm is compatible with the > overlay algorithm of the P2PSIP network I am seeking to join? (Do we need > something almost like an SDP packet here that specifies the DHT algorithms > that a P2PSIP node can support? Or would it try using one DHT and then fall > back to the defined Chord mechanism?) Do you mean something like draft-jiang-p2psip-sep-01, section 6.1.1 http://tools.ietf.org/html/draft-jiang-p2psip-sep-01#section-6.1.1 Cheers, -- Victor Pascual Ávila _______________________________________________ P2PSIP mailing list [email protected] https://www.ietf.org/mailman/listinfo/p2psip
