[ppsp] 答复: PPSP distributed tracker

["Yingjie Gu(yingjie)" <[e-mail]>]

Thanks to Lin  again for doing all the work.

I would apologize, as co-author, I failed to contribute to this version of
updating. 

Here is my comments and hope it can help.

 

 

  _____  

Best Regards
Gu Yingjie

 

发件人: Xiao, Lin (NSN - CN/Beijing) [mailto:[e-mail]] 
发送时间: 2011年10月25日 乐乐14:41
收件人: ext Yingjie Gu(yingjie); [e-mail]
主题: RE: [ppsp] PPSP distributed tracker

 

The updating content in v02 includes :

 

l  The local tracker can keep the content record of  local peers, at the
same time when it forwards the  content update/registration information to
tracker overlay. So, most content requests can be solved locally. 

Y.J. Gu :  How frequently the content record is shared among trackers?  I
guess not real-time sharing, because the content record is updated quite
often.  It could be an implementation choice, but we can give some advise in
the draft. 

l  Delete  the open issues in chapter 5, and decide to use local connection
tracker to manage the status of the ppsp peers locally, as most peer
requests are from local peers according to the algorithm mentioned above. If
the peer status can not be found in local connection tracker, the request is
forwarded to the tracker overlay, as each local tracker always registries
its own address to a node on tracker overly, whose ID has a DHT mapping
with the PPSP peer. As the position of the peer status , which is also the
peer’s connection node address, is always registered to the tracker overlay
according to RELOAD.

Y.J. Gu : Why not share peer status when you share content record? The
reason that we share content record among trackers is to decrease the
response time to a request for some content that is not locally stored. If
the content can be found locally, but the tracker still have to find the
status through the overlay, it doesn’t decrease the response time. The
status shared on tracker overlay might not be accurate, but neither do the
content record. It’s only a way to improve the performance. The peer, who
get an inaccurate information from the tracker, can correct it by
communicating with the peers in peerlist. Even the local connection tracker
can not promise an accurate content record and peer status.

   

l  A data kind for peerStatusIndex is defined.

 

As still some editorial errors, I’ll give a new version soon.

 

 

BR

Xiao Lin 

 

From: ext Yingjie Gu(yingjie) [mailto:[e-mail]] 
Sent: Tuesday, October 25, 2011 11:35 AM
To: Xiao, Lin (NSN - CN/Beijing); [e-mail]
Subject: 答复: [ppsp] PPSP distributed tracker

 

Thanks lin for updating the draft.

Maybe it’s better to give a brief introduction of the updating from -01
version to -02 version.

 

 

  _____  

Best Regards
Gu Yingjie

 

发件人: [e-mail] [mailto:[e-mail]] 代表 Xiao, Lin
(NSN - CN/Beijing)
发送时间: 2011年10月25日 乐乐11:19
收件人: [e-mail]
主题: [ppsp] PPSP distributed tracker

 

Hi All,

 

I’ve updated the distributed tracker draft for a while. Could you please
give your comment on it ? Thanks!

 

http://tools.ietf.org/id/draft-xiao-ppsp-reload-distributed-tracker-02.txt

 

 

Abstract

 

This document defines PPSP tracker usages for REsource LOcation And

Discovery (RELOAD).  Although PPSP assumes a centralized tracker from

peer's point of view, the logical centralized tracker could be realized

by a cluster of geographically distributed trackers. In this draft, we

design distributed trackers system, which are organized by RELOAD. It

provides lookup service for file/channel indexes and Peer Status among

the distributed trackers.

 

 

 

BR

Xiao Lin