From: Roni Even [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 13, 2008 6:35 AM
To: 'Song Haibin'; Das, Saumitra; [EMAIL PROTECTED]
Cc: ietf@ietf.org
Subject: RE: [P2PSIP] How to describe the processing power
Song Haibin,
Your response It is also useful in selecting peer for a neighbor table
ntpdate may not be setup to
work often enough.
Thanks
Saumitra
From: Roni Even [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 13, 2008 6:24 AM
To: Das, Saumitra; [EMAIL PROTECTED]
Cc: ietf@ietf.org
Subject: RE: [P2PSIP] P2PSIP diagnostics: PING discussion
Hi,
I am not sure what you mean NTP
Yes, there are other metrics from comon related to memory usage, bandwidth use
which may also be useful.
Thanks
Saumitra
From: Song Haibin [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 12, 2008 7:07 PM
To: Das, Saumitra; [EMAIL PROTECTED]
Cc: ietf@ietf.org
Subject: RE: [P2PSIP] How
Hi,
I propose that we should allow some flexibility in the discovery process by
decoupling the enrollment server from the overlay configuration document.
Currently, section 11.2 specifies that this overlay configuration file is
obtained from an enrollment server. A more flexible mechanism
Dear Song,
Processing power would be more informational in terms of CPU load. A good
example of what would be useful would be to look at the comon monitoring tool
(http://summer.cs.princeton.edu/status/) for the planetlab testbed. It uses the
following metrics for selecting nodes based on
Hi Song,
Even in the planetlab testbed, the following paper at PAM 2008 (
http://pam2008.cs.wpi.edu/slides/pathak.ppt ) shows that more than 40% of nodes
have more than 20ms NTP error. In a general overlay we are likely to find a
larger fraction of nodes with error in their NTP time (since
Citing one of the responses from Vijay on Oct 13 For instance, it is not ALTO
that gets to decide which peer is hosting which content and what the
contributions of that peer to the overlay are. However, it is ALTO's job to
provide information to a querying peer allowing it to determine wisely
