At Thu, 06 Mar 2008 13:53:18 +0800, Song Yongchao wrote: > > >> >-----Original Message----- > >> >It seems UPDATE and ROUTE-QUERY are some of the main reasons why the > >> >client protocol differs from the peer protocol in P2PP. Are there any > >> >other? > >> > > >> >Am I missing something? > >> > > >> First, when a client has multiple associated peers. I think the client > >> should get the status of its associated peers for the choice of sending > >> requests and avoid sending requests to a congested/busy associated peer. > In > >> SEP client protocol, a Notify message is used for the notification. I > think > >> this must be merged for client protocol. > > > >As with the ordinary peer protocol, I think this should be done with > >UPDATE at the DHT layer. > > I don't think Client has the "DHT layer".
It does in RELOAD. > >> Second, a client must know the departure of its associated peer. Does the > >> peer also send Leave message to its associated clients? My answer is YES. > If > >> people agree, we should clarify it in the merged client Protocol. > > > >Section 7.3.2 already implies this: > > > > The LEAVE_Q message is used to indicate that a peer is exiting the > > overlay. The peer SHOULD send this message to each peer with which > > it is directly connected prior to exiting the overlay. > > > >"peer" in this case (in fact, throughout RELOAD) refers to both > >client peers and non-client peers. However, I agree that this > >could be clearer. > > We need a clear rather than an obscure draft for the implementation. Well, I didn't say it was obscure; I just said it could be clearer. We'll clarify in the next revision. > I think the roles and responsibilities are different for clients and peers. > If a peer is not willing to be acting as an associated peer, he can also > discard messages received from the client. Again, in RELOAD the difference between a client and a peer is very small. A peer which refuses to route messages, whether for a client or another peer, is misbehaving. -Ekr _______________________________________________ P2PSIP mailing list [email protected] https://www.ietf.org/mailman/listinfo/p2psip
