Subject: [P2PSIP] FW: some comments on P2PP protocol

From: JiangXingFeng <[email-masked]>
Date: Tue, 17 Jul 2007 18:59:51 +0800

Sorry, forget to copy the P2PSIP community. 

--
Jiang XingFeng

> -----Original Message-----
> From: JiangXingFeng [mailto:[email-masked]]
> Sent: Tuesday, July 17, 2007 6:59 PM
> To: 'Salman Abdul Baset'; [email-masked]'
> Subject: some comments on P2PP protocol
> 
> Hi,
> Some comments on draft-baset-p2psip-p2pp-00 are followed.
> 
> 1. In section 4.1, the draft says that Client and peers communicate using
the same
> protocol as peers do, i.e., there is no distinct protocol for
client-to-peer and
> peer-to-peer communication.
> 
> Does it mean that Publish, lookupObject, RemoveObject could be used by
clients in
> the same way as the peer uses them? If it does, how do clients fill the
peer-info field
> in these messages? After all, clients have no peer ID which peers have.
> 
> 2. In section 5.2.1, it seems that peer will add copy of its routing table
and neighbor
> table in both directions, not only during forwarding request, but also
during
> forwarding response. It will add the copy two times and it is enough to do
the
> operation in either direction.
> 
> 3. In the draft, when a peer receives a request, it will look up the
routing table and
> find out whether it could give the definitive answer for this request.
What does the
> definitive answer mean? Does it mean that P2PP protocol will check whether
the
> peer is the destination peer, then look up in the resource table to get a
resource
> object keyed by the resource ID? Most of the P2P systems give the
definitive
> answer according to the above rule.
> 
> But if there are some caches of the resource in the overlay, maybe it
could be
> incorporated into the resource table and it could be used to answer the
request. But
> this method may destroy the DHT rule, i,e, peers which are not the
resource's root
> could give the response. What about your opinions?
> 
> 4. As for Peer-info, how about adding a field to identify which add-on
services the
> peer supports? In P2PSIP, peers must support routing and storage service.
But
> maybe some peers may have additional services, for example, STUN or TURN,
> which could be used by the other peers. By carrying the service which the
peer
> supports may facilitate the discovery of these services in the overlay?
Comments?
> Regards
> --
> Jiang XingFeng

_______________________________________________
P2PSIP mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/p2psip