From mailman-admin@ietf.org  Sun Feb  1 09:16:42 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14237
	for <p2prg-archive@lists.ietf.org>; Sun, 1 Feb 2004 09:16:42 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AnIOW-0000uJ-F8
	for p2prg-archive@lists.ietf.org; Sun, 01 Feb 2004 09:16:16 -0500
Date: Sun, 01 Feb 2004 09:16:16 -0500
Message-ID: <20040201141616.1364.66792.Mailman@www1.ietf.org>
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@www1.ietf.org
To: p2prg-archive@ietf.org
X-No-Archive: yes
X-Ack: no
Sender: mailman-admin@ietf.org
Errors-To: mailman-admin@ietf.org
X-BeenThere: mailman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, p2prg-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

***************************************************************************


                              Note Well

All statements related to the activities of the IETF and addressed to
the IETF are subject to all provisions of Section 10 of RFC 2026,
which grants to the IETF and its participants certain licenses and
rights in such statements. Such statements include verbal statements
in IETF meetings, as well as written and electronic communications
made at any time or place, which are addressed to

        * the IETF plenary session,
        * any IETF working group or portion thereof,
        * the IESG, or any member thereof on behalf of the IESG,
        * the IAB or any member thereof on behalf of the IAB,
        * any IETF mailing list, including the IETF list itself, any
working
            group or design team list, or any other list functioning
under IETF
            auspices,
        * the RFC Editor or the Internet-Drafts function

Statements made outside of an IETF meeting, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not subject to these provisions.

   
***************************************************************************


If you have questions, problems, comments, etc, send them to
mailman-owner@www1.ietf.org.  Thanks!

Passwords for p2prg-archive@lists.ietf.org:

List                                     Password // URL
----                                     --------  
p2prg@ietf.org                           enimbi    
https://www.ietf.org/mailman/options/p2prg/p2prg-archive%40lists.ietf.org


From exim@www1.ietf.org  Sun Feb  1 20:21:42 2004
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24580
	for <p2prg-archive@odin.ietf.org>; Sun, 1 Feb 2004 20:21:42 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AnSm3-00081k-EN
	for p2prg-archive@odin.ietf.org; Sun, 01 Feb 2004 20:21:15 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i121LFru030852
	for p2prg-archive@odin.ietf.org; Sun, 1 Feb 2004 20:21:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AnSm3-00081X-8v
	for p2prg-web-archive@optimus.ietf.org; Sun, 01 Feb 2004 20:21:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24520
	for <p2prg-web-archive@ietf.org>; Sun, 1 Feb 2004 20:21:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnSm1-0000VQ-00
	for p2prg-web-archive@ietf.org; Sun, 01 Feb 2004 20:21:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AnSl1-0000LW-00
	for p2prg-web-archive@ietf.org; Sun, 01 Feb 2004 20:20:11 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnSjx-00004r-00
	for p2prg-web-archive@ietf.org; Sun, 01 Feb 2004 20:19:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AnSjt-0007W0-If; Sun, 01 Feb 2004 20:19:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AnSjb-0007Uh-Qr
	for p2prg@optimus.ietf.org; Sun, 01 Feb 2004 20:18:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24225
	for <p2prg@irtf.org>; Sun, 1 Feb 2004 20:18:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnSjZ-0007na-00
	for p2prg@irtf.org; Sun, 01 Feb 2004 20:18:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AnShz-0007Mi-00
	for p2prg@irtf.org; Sun, 01 Feb 2004 20:17:07 -0500
Received: from smtp2.att.ne.jp ([165.76.15.138])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnSbh-0005NY-00
	for p2prg@irtf.org; Sun, 01 Feb 2004 20:10:33 -0500
Received: from neurogrid.com (h219-110-056-013.catv01.itscom.jp [219.110.56.13])
	by smtp2.att.ne.jp (Postfix) with ESMTP id 97F18250E7
	for <p2prg@irtf.org>; Mon,  2 Feb 2004 10:10:26 +0900 (JST)
Message-ID: <401DA230.60405@neurogrid.com>
Date: Mon, 02 Feb 2004 10:04:48 +0900
From: Sam Joseph <sam@neurogrid.com>
Reply-To: sam@neurogrid.com
Organization: NeuroGrid http://www.neurogrid.net/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja-JP; rv:1.4) Gecko/20030624
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: p2prg@irtf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [P2Prg] P2PJ Call for Reviewers
Sender: p2prg-admin@ietf.org
Errors-To: p2prg-admin@ietf.org
X-BeenThere: p2prg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/p2prg>,
	<mailto:p2prg-request@ietf.org?subject=unsubscribe>
List-Id: Peer-to-Peer Research Group <p2prg.ietf.org>
List-Post: <mailto:p2prg@ietf.org>
List-Help: <mailto:p2prg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2prg>,
	<mailto:p2prg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

------------------------------------------------------------------
                              CALL FOR REVIEWERS

                                  Peer-to-Peer Journal

                                 (http://p2pjournal.com)
-------------------------------------------------------------------
Apologies if you receive this announcement more than once.

The Peer-to-Peer Journal (P2PJ) is an electronic, refereed journal
devoted to comprehensive coverage of Peer-to-Peer and Parallel computing
topics. It is freely available, with no subscription and is located at
http://www.p2pjournal.com/.

All articles submitted to P2PJ are evaluated by referees who comment
on the article and make recommendations to the Editor. P2PJ is looking
to expand the number of referees and would very much welcome volunteers
from those interested in P2P and with specializations in relevant fields.

When P2PJ receives articles, the editorial board selects referees to
approach according to the overlap between the article itself and the
expertise of the potential reviewers. An invitation email is then sent
to the selected referees, with the anonymised article attached and a
checklist of points to consider. P2PJ hopes to receive reviews
within 10 to 14 days. The authors then receive an anonymised version
of the referees' comments and suggestions for improvement of the article.

While there are no direct benefits available to referees, reviewing
does allow you to see the current state of the art andis of immense
benefit to the peer-to-peer community generally and to the authors
of the submission specifically. A referee would not normally receive
more than three papers a year to review, and most referees are asked
to review only occasionally, when a paper in their particular field
is submitted.

While there are no direct benefits available to referees, reviewing
does allow you to see the current state of the art, is of immense
benefit to the peer-to-peer community generally, and is beneficial
to the authors of the submission specifically.

If you would like to become a referee for P2PJ, please send this
this email to sam@p2pjournal.com after completing the form below.

-----------------------------------------------
Title: (e.g. Dr, Prof.)
First name:
Family Name:

Affiliation/institution:

Email address:

Keywords describing your area of expertise and interest
(please be a specific as possible, e.g. 'distributed hashtables',
not 'p2p'). List up to 5 keywords or phrases, one per line:







Do you have a doctorate (PhD)? If so, in what field:

Number of papers you have published in refereed journals:


Thank you. Your reply will be acknowledged. Invitations to
referee will then arrive when appropriate papers are submitted
to P2PJ. If you need to update your details, please notify
<sam@p2pjournal.com>


Raymond F. Gao, Editor-in-Chief
Daniel Brookshier, Editor
Sam Joseph, Editor




_______________________________________________
P2prg mailing list
P2prg@irtf.org
https://www.ietf.org/mailman/listinfo/p2prg



From exim@www1.ietf.org  Tue Feb 10 21:38:51 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13525
	for <p2prg-archive@odin.ietf.org>; Tue, 10 Feb 2004 21:38:51 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AqkGc-0001iR-8K
	for p2prg-archive@odin.ietf.org; Tue, 10 Feb 2004 21:38:24 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1B2cMDK006591
	for p2prg-archive@odin.ietf.org; Tue, 10 Feb 2004 21:38:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AqkGb-0001iB-UC
	for p2prg-web-archive@optimus.ietf.org; Tue, 10 Feb 2004 21:38:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13515
	for <p2prg-web-archive@ietf.org>; Tue, 10 Feb 2004 21:38:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqkGZ-00027S-00
	for p2prg-web-archive@ietf.org; Tue, 10 Feb 2004 21:38:19 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AqkFd-00022R-00
	for p2prg-web-archive@ietf.org; Tue, 10 Feb 2004 21:37:22 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqkFN-0001x2-00
	for p2prg-web-archive@ietf.org; Tue, 10 Feb 2004 21:37:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AqkFJ-0001Li-LW; Tue, 10 Feb 2004 21:37:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AqkEd-0001J2-G3
	for p2prg@optimus.ietf.org; Tue, 10 Feb 2004 21:36:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13453
	for <p2prg@ietf.org>; Tue, 10 Feb 2004 21:36:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqkEa-0001vp-00
	for p2prg@ietf.org; Tue, 10 Feb 2004 21:36:16 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AqkDe-0001qs-00
	for p2prg@ietf.org; Tue, 10 Feb 2004 21:35:19 -0500
Received: from mordor.cerego.co.jp ([210.158.200.254])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqkD8-0001gT-00
	for p2prg@ietf.org; Tue, 10 Feb 2004 21:34:47 -0500
Received: from CEREGO_EXCHANGE.cerego.co.jp (optional02.cerego.co.jp [192.168.2.1])
	by mordor.cerego.co.jp (Postfix) with ESMTP id 8ABB473C1
	for <p2prg@ietf.org>; Wed, 11 Feb 2004 11:29:17 +0900 (JST)
Received: from neurogrid.com (frodo.cerego.co.jp [192.168.2.3]) by CEREGO_EXCHANGE.cerego.co.jp with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id ZHMQ4W6R; Wed, 11 Feb 2004 11:34:07 +0900
Message-ID: <40299490.2010602@neurogrid.com>
Date: Wed, 11 Feb 2004 11:33:52 +0900
From: Sam Joseph <sam@neurogrid.com>
Reply-To: sam@neurogrid.com
Organization: NeuroGrid http://www.neurogrid.net/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja-JP; rv:1.4) Gecko/20030624
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "'p2prg@ietf.org'" <p2prg@ietf.org>
Subject: Re: [P2Prg] who is going to be at the ietf59 ?
References: <5BE5F1117AEDD5118BFC0000D11EA39CC8C256@blns205e.bln.icn.siemens.de> <6E7E98C4-4C36-11D8-AC36-000A95766260@fastmail.fm>
In-Reply-To: <6E7E98C4-4C36-11D8-AC36-000A95766260@fastmail.fm>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-MailScanner-Information: Verified by MailScanner (Mordor)
X-MailScanner: STATUS-CLEAN
X-MailScanner-SpamCheck: not spam, SpamAssassin (score=-2.1, required 5,
	AWL 0.00, EMAIL_ATTRIBUTION -0.50, IN_REP_TO -0.50,
	QUOTED_EMAIL_TEXT -0.48, REFERENCES -0.50, REPLY_WITH_QUOTES -0.50,
	USER_AGENT_MOZILLA_UA 0.00, X_ACCEPT_LANG -0.10)
Content-Transfer-Encoding: 7bit
Sender: p2prg-admin@ietf.org
Errors-To: p2prg-admin@ietf.org
X-BeenThere: p2prg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/p2prg>,
	<mailto:p2prg-request@ietf.org?subject=unsubscribe>
List-Id: Peer-to-Peer Research Group <p2prg.ietf.org>
List-Post: <mailto:p2prg@ietf.org>
List-Help: <mailto:p2prg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2prg>,
	<mailto:p2prg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi All,

So is there going to be any p2p-rg meeting in Seoul? 
Anybody who is going to be in Seoul let me know and we'll see if we 
can't arrange something if it isn't already.

Thanks in advance.

CHEERS> SAM

Bill Yeager wrote:

> OK by me. I will not be there though ... we do need to begin to prime 
> the RG pump.
>
> Bill
>
> On Jan 21, 2004, at 2:20 AM, Andersen Frank-Uwe wrote:
>
>> hello all,
>> how are chances for a p2p related side-meeting in seoul?
>> regards,
>> frank-uwe
>
>
>
> _______________________________________________
> P2prg mailing list
> P2prg@irtf.org
> https://www.ietf.org/mailman/listinfo/p2prg
>
>




_______________________________________________
P2prg mailing list
P2prg@irtf.org
https://www.ietf.org/mailman/listinfo/p2prg



From exim@www1.ietf.org  Wed Feb 11 06:50:02 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27966
	for <p2prg-archive@odin.ietf.org>; Wed, 11 Feb 2004 06:50:02 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aqss4-0003g0-Ez
	for p2prg-archive@odin.ietf.org; Wed, 11 Feb 2004 06:49:36 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1BBnatf014131
	for p2prg-archive@odin.ietf.org; Wed, 11 Feb 2004 06:49:36 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aqss4-0003fq-7k
	for p2prg-web-archive@optimus.ietf.org; Wed, 11 Feb 2004 06:49:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27934
	for <p2prg-web-archive@ietf.org>; Wed, 11 Feb 2004 06:49:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aqss0-00024W-00
	for p2prg-web-archive@ietf.org; Wed, 11 Feb 2004 06:49:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aqsr5-0001z5-00
	for p2prg-web-archive@ietf.org; Wed, 11 Feb 2004 06:48:36 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqsqY-0001u9-00
	for p2prg-web-archive@ietf.org; Wed, 11 Feb 2004 06:48:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AqsqX-0003ZU-02; Wed, 11 Feb 2004 06:48:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AqsqA-0003ZA-Nq
	for p2prg@optimus.ietf.org; Wed, 11 Feb 2004 06:47:38 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27849
	for <p2prg@ietf.org>; Wed, 11 Feb 2004 06:47:34 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aqsq6-0001tS-00
	for p2prg@ietf.org; Wed, 11 Feb 2004 06:47:34 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AqspE-0001o4-00
	for p2prg@ietf.org; Wed, 11 Feb 2004 06:46:40 -0500
Received: from goliath.siemens.de ([192.35.17.28])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqsoI-0001iM-00
	for p2prg@ietf.org; Wed, 11 Feb 2004 06:45:42 -0500
Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14])
	by goliath.siemens.de (8.11.7/8.11.7) with ESMTP id i1BBjfM20305
	for <p2prg@ietf.org>; Wed, 11 Feb 2004 12:45:41 +0100 (MET)
Received: from moody.mchh.siemens.de (moody.mchh.siemens.de [139.21.205.85])
	by mail1.siemens.de (8.11.7/8.11.7) with ESMTP id i1BBjek21468
	for <p2prg@ietf.org>; Wed, 11 Feb 2004 12:45:40 +0100 (MET)
Received: from mchh275e.mchh.siemens.de (mchh275e.mchh.siemens.de [139.21.200.61])
	by moody.mchh.siemens.de (8.9.3/8.9.1) with ESMTP id MAA28432
	for <p2prg@ietf.org>; Wed, 11 Feb 2004 12:44:47 +0100 (MET)
Received: by mchh275e.mchh.siemens.de with Internet Mail Service (5.5.2657.72)
	id <1M0SAF4S>; Wed, 11 Feb 2004 12:45:38 +0100
Message-ID: <5BE5F1117AEDD5118BFC0000D11EA39CC8C322@blns205e.bln.icn.siemens.de>
From: Andersen Frank-Uwe <frank-uwe.andersen@siemens.com>
To: "'p2prg@ietf.org'" <p2prg@ietf.org>
Subject: AW: [P2Prg] who is going to be at the ietf59 ?
Date: Wed, 11 Feb 2004 12:45:37 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable
Sender: p2prg-admin@ietf.org
Errors-To: p2prg-admin@ietf.org
X-BeenThere: p2prg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/p2prg>,
	<mailto:p2prg-request@ietf.org?subject=unsubscribe>
List-Id: Peer-to-Peer Research Group <p2prg.ietf.org>
List-Post: <mailto:p2prg@ietf.org>
List-Help: <mailto:p2prg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2prg>,
	<mailto:p2prg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

I hope to make it so San Diego (not Seoul).

- frank-uwe


> -----Urspr=FCngliche Nachricht-----
> Von: p2prg-admin@ietf.org [mailto:p2prg-admin@ietf.org] Im=20
> Auftrag von Sam Joseph
> Gesendet: Mittwoch, 11. Februar 2004 03:34
> An: 'p2prg@ietf.org'
> Betreff: Re: [P2Prg] who is going to be at the ietf59 ?
>=20
>=20
> Hi All,
>=20
> So is there going to be any p2p-rg meeting in Seoul?=20
> Anybody who is going to be in Seoul let me know and we'll see if we=20
> can't arrange something if it isn't already.
>=20
> Thanks in advance.
>=20
> CHEERS> SAM
>=20
> Bill Yeager wrote:
>=20
> > OK by me. I will not be there though ... we do need to=20
> begin to prime=20
> > the RG pump.
> >
> > Bill
> >
> > On Jan 21, 2004, at 2:20 AM, Andersen Frank-Uwe wrote:
> >
> >> hello all,
> >> how are chances for a p2p related side-meeting in seoul?
> >> regards,
> >> frank-uwe
> >
> >
> >
> > _______________________________________________
> > P2prg mailing list
> > P2prg@irtf.org
> > https://www.ietf.org/mailman/listinfo/p2prg
> >
> >
>=20
>=20
>=20
>=20
> _______________________________________________
> P2prg mailing list
> P2prg@irtf.org
> https://www.ietf.org/mailman/listinfo/p2prg
>=20

_______________________________________________
P2prg mailing list
P2prg@irtf.org
https://www.ietf.org/mailman/listinfo/p2prg



From exim@www1.ietf.org  Wed Feb 11 16:03:38 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23548
	for <p2prg-archive@odin.ietf.org>; Wed, 11 Feb 2004 16:03:38 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ar1Vj-0005h1-F0
	for p2prg-archive@odin.ietf.org; Wed, 11 Feb 2004 16:03:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1BL37ib021882
	for p2prg-archive@odin.ietf.org; Wed, 11 Feb 2004 16:03:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ar1Vj-0005gr-9o
	for p2prg-web-archive@optimus.ietf.org; Wed, 11 Feb 2004 16:03:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23487
	for <p2prg-web-archive@ietf.org>; Wed, 11 Feb 2004 16:03:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ar1Vh-000564-00
	for p2prg-web-archive@ietf.org; Wed, 11 Feb 2004 16:03:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ar1Uh-0004yI-00
	for p2prg-web-archive@ietf.org; Wed, 11 Feb 2004 16:02:03 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ar1U1-0004rU-00
	for p2prg-web-archive@ietf.org; Wed, 11 Feb 2004 16:01:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ar1Tj-0005LF-VX; Wed, 11 Feb 2004 16:01:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ar1Sq-0005GS-A8
	for p2prg@optimus.ietf.org; Wed, 11 Feb 2004 16:00:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23335
	for <p2prg@ietf.org>; Wed, 11 Feb 2004 16:00:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ar1So-0004io-00
	for p2prg@ietf.org; Wed, 11 Feb 2004 16:00:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ar1S0-0004bc-00
	for p2prg@ietf.org; Wed, 11 Feb 2004 15:59:16 -0500
Received: from mordor.cerego.co.jp ([210.158.200.254])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ar1RI-0004RH-00
	for p2prg@ietf.org; Wed, 11 Feb 2004 15:58:32 -0500
Received: from CEREGO_EXCHANGE.cerego.co.jp (optional02.cerego.co.jp [192.168.2.1])
	by mordor.cerego.co.jp (Postfix) with ESMTP
	id D80B1739F; Thu, 12 Feb 2004 05:53:04 +0900 (JST)
Received: from neurogrid.com (frodo.cerego.co.jp [192.168.2.3]) by CEREGO_EXCHANGE.cerego.co.jp with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id 1XZ561JR; Thu, 12 Feb 2004 05:57:54 +0900
Message-ID: <402A9744.3090005@neurogrid.com>
Date: Thu, 12 Feb 2004 05:57:40 +0900
From: Sam Joseph <sam@neurogrid.com>
Reply-To: sam@neurogrid.com
Organization: NeuroGrid http://www.neurogrid.net/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja-JP; rv:1.4) Gecko/20030624
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: decentralization@yahoogroups.com, p2p-irtf <p2prg@ietf.org>,
        "Peer-to-peer development." <p2p-hackers@zgp.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-MailScanner-Information: Verified by MailScanner (Mordor)
X-MailScanner: STATUS-CLEAN
X-MailScanner-SpamCheck: not spam, SpamAssassin (score=-0.8, required 5,
	AWL 0.00, USER_AGENT_MOZILLA_UA 0.00, X_ACCEPT_LANG -0.10)
Content-Transfer-Encoding: 7bit
Subject: [P2Prg] P2P workshops in Hawaii
Sender: p2prg-admin@ietf.org
Errors-To: p2prg-admin@ietf.org
X-BeenThere: p2prg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/p2prg>,
	<mailto:p2prg-request@ietf.org?subject=unsubscribe>
List-Id: Peer-to-Peer Research Group <p2prg.ietf.org>
List-Post: <mailto:p2prg@ietf.org>
List-Help: <mailto:p2prg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2prg>,
	<mailto:p2prg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi All,

Pardon the cross-posting, but I just found some new P2P workshops in 
Hawaii with abstract deadlines coming up soon.

http://www.neurogrid.net/twiki/bin/view/Main/PeerToPeerConferences

CHEERS> SAM



_______________________________________________
P2prg mailing list
P2prg@irtf.org
https://www.ietf.org/mailman/listinfo/p2prg



From exim@www1.ietf.org  Thu Feb 12 17:03:04 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18812
	for <p2prg-archive@odin.ietf.org>; Thu, 12 Feb 2004 17:03:04 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArOuq-0002uE-84
	for p2prg-archive@odin.ietf.org; Thu, 12 Feb 2004 17:02:36 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1CM2a58011168
	for p2prg-archive@odin.ietf.org; Thu, 12 Feb 2004 17:02:36 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArOup-0002tz-V3
	for p2prg-web-archive@optimus.ietf.org; Thu, 12 Feb 2004 17:02:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18660
	for <p2prg-web-archive@ietf.org>; Thu, 12 Feb 2004 17:02:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArOuk-00029m-00
	for p2prg-web-archive@ietf.org; Thu, 12 Feb 2004 17:02:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1ArOtN-0001tL-00
	for p2prg-web-archive@ietf.org; Thu, 12 Feb 2004 17:01:05 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArOsW-0001jV-00
	for p2prg-web-archive@ietf.org; Thu, 12 Feb 2004 17:00:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArOsO-0002fL-7w; Thu, 12 Feb 2004 17:00:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArOrp-0002e6-Mv
	for p2prg@optimus.ietf.org; Thu, 12 Feb 2004 16:59:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18450
	for <p2prg@ietf.org>; Thu, 12 Feb 2004 16:59:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArOrl-0001h2-00
	for p2prg@ietf.org; Thu, 12 Feb 2004 16:59:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1ArOqs-0001c5-00
	for p2prg@ietf.org; Thu, 12 Feb 2004 16:58:31 -0500
Received: from mordor.cerego.co.jp ([210.158.200.254])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArOq8-0001RX-00
	for p2prg@ietf.org; Thu, 12 Feb 2004 16:57:45 -0500
Received: from CEREGO_EXCHANGE.cerego.co.jp (optional02.cerego.co.jp [192.168.2.1])
	by mordor.cerego.co.jp (Postfix) with ESMTP
	id 2FEC373C1; Fri, 13 Feb 2004 06:52:28 +0900 (JST)
Received: from neurogrid.com (frodo.cerego.co.jp [192.168.2.3]) by CEREGO_EXCHANGE.cerego.co.jp with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id 1XZ561ZM; Fri, 13 Feb 2004 06:57:16 +0900
Message-ID: <402BF6B0.6090103@neurogrid.com>
Date: Fri, 13 Feb 2004 06:57:04 +0900
From: Sam Joseph <sam@neurogrid.com>
Reply-To: sam@neurogrid.com
Organization: NeuroGrid http://www.neurogrid.net/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja-JP; rv:1.4) Gecko/20030624
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: p2p-irtf <p2prg@ietf.org>, p2prg-metadata@cs.umd.edu
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-MailScanner-Information: Verified by MailScanner (Mordor)
X-MailScanner: STATUS-CLEAN
X-MailScanner-SpamCheck: not spam, SpamAssassin (score=-0.8, required 5,
	AWL 0.00, USER_AGENT_MOZILLA_UA 0.00, X_ACCEPT_LANG -0.10)
Content-Transfer-Encoding: 7bit
Subject: [P2Prg] BitTorrent Paper Summary
Sender: p2prg-admin@ietf.org
Errors-To: p2prg-admin@ietf.org
X-BeenThere: p2prg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/p2prg>,
	<mailto:p2prg-request@ietf.org?subject=unsubscribe>
List-Id: Peer-to-Peer Research Group <p2prg.ietf.org>
List-Post: <mailto:p2prg@ietf.org>
List-Help: <mailto:p2prg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2prg>,
	<mailto:p2prg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi All,

So I'm posting this to p2prg as well as p2p-metadata as well, since I 
haven't seen much discussion on either.  To get us going with some 
meta-data and trust topics, I'm posting my summary notes on the 
BitTorrent paper:

http://www.sims.berkeley.edu/research/conferences/p2pecon/papers/s4-cohen.pdf

I would be very interested to hear any comments or feedback.  I think 
BitTorrent is very interesting because it uses special meta-data 
encoding and tit-for-tat choking in order to make sure of fair downloads.

CHEERS> SAM


Incentives Build Robustness in BitTorrent

1. Problems addressed

Downloading files from multiple sources.
Difficult due to:
a) complexity of assignment
b) churn
c) fairness

2. Interface

Absolute simplicity of interface perhaps key to take up of BitTorrent

3. MetaData

Torrent files specify information about a file length, name, hashing 
information, and url of a tracker - all bencoded to reduce size

4. Trackers and peers

Peers get random lists of other peers that are sharing parts of a file 
from trackers.  Updated each 3-5 minutes, and at least 1800 trackers 
currently in existence.  Tracker is simple, runs over http and has 
minimal comms.  Files are broken into chunks with hashes to ensure 
correctness.  All peers continuously download chunks from all peers they 
can.

5.  Various Heuristics used to improve performance

a) random connections
b) pipelining - always have more requests for file pieces lined up
c) try to download the rarest piece of a file first
d) when downloading starts go for random first peice
e) special endgame mode to cancel slow downloads
f) tit for tat choking + optimistic unchoking
g) Snubbing



_______________________________________________
P2prg mailing list
P2prg@irtf.org
https://www.ietf.org/mailman/listinfo/p2prg



From exim@www1.ietf.org  Fri Feb 13 00:38:12 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA09649
	for <p2prg-archive@odin.ietf.org>; Fri, 13 Feb 2004 00:38:11 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArW1K-0007zA-2X
	for p2prg-archive@odin.ietf.org; Fri, 13 Feb 2004 00:37:46 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1D5bkm3030690
	for p2prg-archive@odin.ietf.org; Fri, 13 Feb 2004 00:37:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArW1J-0007yn-Lo
	for p2prg-web-archive@optimus.ietf.org; Fri, 13 Feb 2004 00:37:45 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA09641
	for <p2prg-web-archive@ietf.org>; Fri, 13 Feb 2004 00:37:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArW1D-0000O4-00
	for p2prg-web-archive@ietf.org; Fri, 13 Feb 2004 00:37:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1ArW0L-0000JD-00
	for p2prg-web-archive@ietf.org; Fri, 13 Feb 2004 00:36:46 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArVzb-0000EZ-00
	for p2prg-web-archive@ietf.org; Fri, 13 Feb 2004 00:35:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArVzd-0007by-K5; Fri, 13 Feb 2004 00:36:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArVzP-0007ZR-IC
	for p2prg@optimus.ietf.org; Fri, 13 Feb 2004 00:35:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA09632
	for <p2prg@ietf.org>; Fri, 13 Feb 2004 00:35:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArVzJ-0000D6-00
	for p2prg@ietf.org; Fri, 13 Feb 2004 00:35:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1ArVyS-00007l-00
	for p2prg@ietf.org; Fri, 13 Feb 2004 00:34:49 -0500
Received: from addr-mx02.addr.com ([209.249.147.146])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArVxk-0007gm-00
	for p2prg@ietf.org; Fri, 13 Feb 2004 00:34:04 -0500
Received: from proxy1.addr.com (proxy1.addr.com [209.249.147.28])
	by addr-mx02.addr.com (8.12.8/8.12.2) with ESMTP id i1D5XTiY062675;
	Thu, 12 Feb 2004 21:33:29 -0800 (PST)
Received: from C1812808A (c-24-4-96-9.client.comcast.net [24.4.96.9])
	by proxy1.addr.com (8.12.8/8.12.8/Submit) with SMTP id i1D5XRa9006036;
	Thu, 12 Feb 2004 21:33:29 -0800 (PST)
Reply-To: <osokin@osokin.com>
From: "Serguei Osokine" <osokin@osokin.com>
To: <sam@neurogrid.com>, "p2p-irtf" <p2prg@ietf.org>,
        <p2prg-metadata@cs.umd.edu>
Subject: RE: [P2Prg] BitTorrent Paper Summary
Date: Thu, 12 Feb 2004 21:40:08 -0800
Message-ID: <IJECJCHFLLIPKMNGHDPMGEBMEJAA.osokin@osokin.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
In-Reply-To: <402BF6B0.6090103@neurogrid.com>
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: p2prg-admin@ietf.org
Errors-To: p2prg-admin@ietf.org
X-BeenThere: p2prg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/p2prg>,
	<mailto:p2prg-request@ietf.org?subject=unsubscribe>
List-Id: Peer-to-Peer Research Group <p2prg.ietf.org>
List-Post: <mailto:p2prg@ietf.org>
List-Help: <mailto:p2prg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2prg>,
	<mailto:p2prg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

On Thursday, February 12, 2004 Sam Joseph wrote:
> 3. MetaData
>
> Torrent files specify information about a file
> length, name, hashing information, and url of a
> tracker - all bencoded to reduce size

	Sam, why do you call it metadata? I always assumed that
metadata would be various stuff like performer, album, bitrate,
quality, etc. Okay, so Bram Cohen himself calls .torrent files
'metainfo' - but is it a good term for the contents of that
file? What .torrent has (and btw, I think that it hashes not
only the file itself, but also every separate piece of the
file) - anyway, it seems to be a fairly straightforward
integrity checking mechanism, not unlike, say, TigerTree
hash or Kazaa hash.

	Do you really insist on calling it metadata? Am I missing
something?

	Best wishes -
	S.Osokine.
	12 Feb 2004.


-----Original Message-----
From: p2prg-admin@ietf.org [mailto:p2prg-admin@ietf.org]On Behalf Of Sam
Joseph
Sent: Thursday, February 12, 2004 1:57 PM
To: p2p-irtf; p2prg-metadata@cs.umd.edu
Subject: [P2Prg] BitTorrent Paper Summary


Hi All,

So I'm posting this to p2prg as well as p2p-metadata as well, since I
haven't seen much discussion on either.  To get us going with some
meta-data and trust topics, I'm posting my summary notes on the
BitTorrent paper:

http://www.sims.berkeley.edu/research/conferences/p2pecon/papers/s4-cohen.pd
f

I would be very interested to hear any comments or feedback.  I think
BitTorrent is very interesting because it uses special meta-data
encoding and tit-for-tat choking in order to make sure of fair downloads.

CHEERS> SAM


Incentives Build Robustness in BitTorrent

1. Problems addressed

Downloading files from multiple sources.
Difficult due to:
a) complexity of assignment
b) churn
c) fairness

2. Interface

Absolute simplicity of interface perhaps key to take up of BitTorrent

3. MetaData

Torrent files specify information about a file length, name, hashing
information, and url of a tracker - all bencoded to reduce size

4. Trackers and peers

Peers get random lists of other peers that are sharing parts of a file
from trackers.  Updated each 3-5 minutes, and at least 1800 trackers
currently in existence.  Tracker is simple, runs over http and has
minimal comms.  Files are broken into chunks with hashes to ensure
correctness.  All peers continuously download chunks from all peers they
can.

5.  Various Heuristics used to improve performance

a) random connections
b) pipelining - always have more requests for file pieces lined up
c) try to download the rarest piece of a file first
d) when downloading starts go for random first peice
e) special endgame mode to cancel slow downloads
f) tit for tat choking + optimistic unchoking
g) Snubbing



_______________________________________________
P2prg mailing list
P2prg@irtf.org
https://www.ietf.org/mailman/listinfo/p2prg


_______________________________________________
P2prg mailing list
P2prg@irtf.org
https://www.ietf.org/mailman/listinfo/p2prg



From exim@www1.ietf.org  Fri Feb 13 01:45:19 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA11303
	for <p2prg-archive@odin.ietf.org>; Fri, 13 Feb 2004 01:45:19 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArX4H-00060E-Co
	for p2prg-archive@odin.ietf.org; Fri, 13 Feb 2004 01:44:53 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1D6irAh023068
	for p2prg-archive@odin.ietf.org; Fri, 13 Feb 2004 01:44:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArX4H-0005zz-7v
	for p2prg-web-archive@optimus.ietf.org; Fri, 13 Feb 2004 01:44:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA11220
	for <p2prg-web-archive@ietf.org>; Fri, 13 Feb 2004 01:44:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArX4A-0005oc-00
	for p2prg-web-archive@ietf.org; Fri, 13 Feb 2004 01:44:46 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1ArX3E-0005gw-00
	for p2prg-web-archive@ietf.org; Fri, 13 Feb 2004 01:43:49 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArX2O-0005bb-00
	for p2prg-web-archive@ietf.org; Fri, 13 Feb 2004 01:42:56 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArX2S-0005p1-Vv; Fri, 13 Feb 2004 01:43:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArX2I-0005o2-QY
	for p2prg@optimus.ietf.org; Fri, 13 Feb 2004 01:42:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA11168
	for <p2prg@ietf.org>; Fri, 13 Feb 2004 01:42:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArX2B-0005aC-00
	for p2prg@ietf.org; Fri, 13 Feb 2004 01:42:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1ArX1I-0005VU-00
	for p2prg@ietf.org; Fri, 13 Feb 2004 01:41:48 -0500
Received: from mordor.cerego.co.jp ([210.158.200.254])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArX0V-0005Ks-00
	for p2prg@ietf.org; Fri, 13 Feb 2004 01:41:00 -0500
Received: from CEREGO_EXCHANGE.cerego.co.jp (optional02.cerego.co.jp [192.168.2.1])
	by mordor.cerego.co.jp (Postfix) with ESMTP
	id 19FB773C3; Fri, 13 Feb 2004 15:35:41 +0900 (JST)
Received: from neurogrid.com (frodo.cerego.co.jp [192.168.2.3]) by CEREGO_EXCHANGE.cerego.co.jp with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id 1XZ5610F; Fri, 13 Feb 2004 15:40:29 +0900
Message-ID: <402C7152.1010407@neurogrid.com>
Date: Fri, 13 Feb 2004 15:40:18 +0900
From: Sam Joseph <sam@neurogrid.com>
Reply-To: sam@neurogrid.com
Organization: NeuroGrid http://www.neurogrid.net/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja-JP; rv:1.4) Gecko/20030624
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: osokin@osokin.com
Cc: p2p-irtf <p2prg@ietf.org>, p2prg-metadata@cs.umd.edu
Subject: Re: [P2Prg] BitTorrent Paper Summary
References: <IJECJCHFLLIPKMNGHDPMGEBMEJAA.osokin@osokin.com>
In-Reply-To: <IJECJCHFLLIPKMNGHDPMGEBMEJAA.osokin@osokin.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-MailScanner-Information: Verified by MailScanner (Mordor)
X-MailScanner: STATUS-CLEAN
X-MailScanner-SpamCheck: not spam, SpamAssassin (score=-1.8, required 5,
	AWL 0.00, EMAIL_ATTRIBUTION -0.50, IN_REP_TO -0.50, REFERENCES -0.50,
	REPLY_WITH_QUOTES -0.50, USER_AGENT_MOZILLA_UA 0.00,
	X_ACCEPT_LANG -0.10)
Content-Transfer-Encoding: 7bit
Sender: p2prg-admin@ietf.org
Errors-To: p2prg-admin@ietf.org
X-BeenThere: p2prg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/p2prg>,
	<mailto:p2prg-request@ietf.org?subject=unsubscribe>
List-Id: Peer-to-Peer Research Group <p2prg.ietf.org>
List-Post: <mailto:p2prg@ietf.org>
List-Help: <mailto:p2prg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2prg>,
	<mailto:p2prg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi Serguei,

Serguei Osokine wrote:

>On Thursday, February 12, 2004 Sam Joseph wrote:
>  
>
>>3. MetaData
>>
>>Torrent files specify information about a file
>>length, name, hashing information, and url of a
>>tracker - all bencoded to reduce size
>>    
>>
>
>	Sam, why do you call it metadata?
>
I guess because it is data about data --> meta-data

> I always assumed that
>metadata would be various stuff like performer, album, bitrate,
>quality, etc. 
>
I think that is also meta-data.

>Okay, so Bram Cohen himself calls .torrent files
>'metainfo' - but is it a good term for the contents of that
>file? What .torrent has (and btw, I think that it hashes not
>only the file itself, but also every separate piece of the
>file)
>
I think you're right - I was just summarising from Bram's p2pecon paper.

> - anyway, it seems to be a fairly straightforward
>integrity checking mechanism, not unlike, say, TigerTree
>hash or Kazaa hash.
>
I agree.

>	Do you really insist on calling it metadata? Am I missing
>something?
>
I don't insist on calling it meta-data.  I guess I was just tying it in 
with the ideas in my decentralized meta-data strategies paper:

http://www.neurogrid.net/php/publications.php

in which I say the following:

-------------------------------------------------------------------
Taking an inclusive view of meta-data it seems that we can consider a 
number of possible types:

(1) Document Hash - An id generated from the document contents via some 
hashing algorithm that ideally will be unique to each document
(2) Document Id  - An id assigned arbitrarily to a document according to 
some scheme - different from a hash in that it must be generated by some 
authority
(3) Statistical representation - A representation generated by 
performing a statistical operation on a document, that may involve 
statistics relating to a larger document collection, e.g. TFIDF (see 
section 2.1.1)
(4) Human assigned - Keywords or more complex statements such as RDF 
(see section 2.1.4)

The important differences between the types of meta-data are whether the 
representation is unique among documents, whether it can be 
automatically generated, and the logical complexity of the associations.
-------------------------------------------------------------------

Basically I was just following that thinking.  Perhaps I am muddying the 
water?  But I guess I would want to make a distinction between metadata 
that is semantic annotations, and "structural"? "factual" metadata, that 
can be generated by some process of inspection.

However, even if you wanted to avoid calling data that is derived by 
inspection "meta-data", we still have things like the tracker url.  I 
would have said that that is metadata.  How to organise and co-ordinate 
that data about files is arguably a meta-data issue - but then I would 
be just as happy to use another word - well, I guess I have written a 
lot about meta-data, so to use a different word now might be confusing 
... still I see it all as part of coordination of data about data in p2p 
systems ....

CHEERS> SAM



_______________________________________________
P2prg mailing list
P2prg@irtf.org
https://www.ietf.org/mailman/listinfo/p2prg



From exim@www1.ietf.org  Sat Feb 14 18:54:30 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06260
	for <p2prg-archive@odin.ietf.org>; Sat, 14 Feb 2004 18:54:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1As9bo-0001kB-0p
	for p2prg-archive@odin.ietf.org; Sat, 14 Feb 2004 18:54:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1ENs3CK006699
	for p2prg-archive@odin.ietf.org; Sat, 14 Feb 2004 18:54:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1As9bn-0001jy-SJ
	for p2prg-web-archive@optimus.ietf.org; Sat, 14 Feb 2004 18:54:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06245
	for <p2prg-web-archive@ietf.org>; Sat, 14 Feb 2004 18:53:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1As9bk-0004NE-00
	for p2prg-web-archive@ietf.org; Sat, 14 Feb 2004 18:54:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1As9an-0004KD-00
	for p2prg-web-archive@ietf.org; Sat, 14 Feb 2004 18:53:02 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1As9Zu-0004Hm-00
	for p2prg-web-archive@ietf.org; Sat, 14 Feb 2004 18:52:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1As9Zp-0001TA-Gp; Sat, 14 Feb 2004 18:52:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1As9Yx-0001O7-8w
	for p2prg@optimus.ietf.org; Sat, 14 Feb 2004 18:51:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06216
	for <p2prg@ietf.org>; Sat, 14 Feb 2004 18:51:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1As9Yu-0004EE-00
	for p2prg@ietf.org; Sat, 14 Feb 2004 18:51:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1As9Xw-0004BH-00
	for p2prg@ietf.org; Sat, 14 Feb 2004 18:50:05 -0500
Received: from addr-mx01.addr.com ([209.249.147.145])
	by ietf-mx with esmtp (Exim 4.12)
	id 1As9Xf-00048N-00
	for p2prg@ietf.org; Sat, 14 Feb 2004 18:49:47 -0500
Received: from proxy1.addr.com (proxy1.addr.com [209.249.147.28])
	by addr-mx01.addr.com (8.12.8/8.12.2) with ESMTP id i1ENigcP005499;
	Sat, 14 Feb 2004 15:49:09 -0800 (PST)
Received: from C1812808A (c-24-4-96-9.client.comcast.net [24.4.96.9])
	by proxy1.addr.com (8.12.8/8.12.8/Submit) with SMTP id i1ENTUa9060676;
	Sat, 14 Feb 2004 15:29:31 -0800 (PST)
Reply-To: <osokin@osokin.com>
From: "Serguei Osokine" <osokin@osokin.com>
To: <sam@neurogrid.com>
Cc: "p2p-irtf" <p2prg@ietf.org>, <p2prg-metadata@cs.umd.edu>
Subject: RE: [P2Prg] BitTorrent Paper Summary
Date: Sat, 14 Feb 2004 15:36:11 -0800
Message-ID: <IJECJCHFLLIPKMNGHDPMMEEMEJAA.osokin@osokin.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <402C7152.1010407@neurogrid.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: p2prg-admin@ietf.org
Errors-To: p2prg-admin@ietf.org
X-BeenThere: p2prg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/p2prg>,
	<mailto:p2prg-request@ietf.org?subject=unsubscribe>
List-Id: Peer-to-Peer Research Group <p2prg.ietf.org>
List-Post: <mailto:p2prg@ietf.org>
List-Help: <mailto:p2prg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2prg>,
	<mailto:p2prg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

On Thursday, February 12, 2004 Sam Joseph wrote:
> I guess I was just tying it in with the ideas in my
> decentralized meta-data strategies paper:
>
> http://www.neurogrid.net/php/publications.php
> 
> in which I say the following:
>
> -------------------------------------------------------------------
> Taking an inclusive view of meta-data it seems that we can 
> consider a number of possible types:...

	Fair enough. I was thinking mainly about the 

> (4) Human assigned...

- since... well... that's the hard part, I guess. As opposed
to computing hash, which is easy, fast, and straightforward,
so I tend not to think about it a lot.

	But in yur classification it really is metadata - in fact,
everything that is not in a file itself seems to be metadata.
Okay, that makes sense.

	Best wishes - 
	S.Osokine.
	14 Feb 2004.

-----Original Message-----
From: p2prg-admin@ietf.org [mailto:p2prg-admin@ietf.org]On Behalf Of Sam
Joseph
Sent: Thursday, February 12, 2004 10:40 PM
To: osokin@osokin.com
Cc: p2p-irtf; p2prg-metadata@cs.umd.edu
Subject: Re: [P2Prg] BitTorrent Paper Summary


Hi Serguei,

Serguei Osokine wrote:

>On Thursday, February 12, 2004 Sam Joseph wrote:
>  
>
>>3. MetaData
>>
>>Torrent files specify information about a file
>>length, name, hashing information, and url of a
>>tracker - all bencoded to reduce size
>>    
>>
>
>	Sam, why do you call it metadata?
>
I guess because it is data about data --> meta-data

> I always assumed that
>metadata would be various stuff like performer, album, bitrate,
>quality, etc. 
>
I think that is also meta-data.

>Okay, so Bram Cohen himself calls .torrent files
>'metainfo' - but is it a good term for the contents of that
>file? What .torrent has (and btw, I think that it hashes not
>only the file itself, but also every separate piece of the
>file)
>
I think you're right - I was just summarising from Bram's p2pecon paper.

> - anyway, it seems to be a fairly straightforward
>integrity checking mechanism, not unlike, say, TigerTree
>hash or Kazaa hash.
>
I agree.

>	Do you really insist on calling it metadata? Am I missing
>something?
>
I don't insist on calling it meta-data.  I guess I was just tying it in 
with the ideas in my decentralized meta-data strategies paper:

http://www.neurogrid.net/php/publications.php

in which I say the following:

-------------------------------------------------------------------
Taking an inclusive view of meta-data it seems that we can consider a 
number of possible types:

(1) Document Hash - An id generated from the document contents via some 
hashing algorithm that ideally will be unique to each document
(2) Document Id  - An id assigned arbitrarily to a document according to 
some scheme - different from a hash in that it must be generated by some 
authority
(3) Statistical representation - A representation generated by 
performing a statistical operation on a document, that may involve 
statistics relating to a larger document collection, e.g. TFIDF (see 
section 2.1.1)
(4) Human assigned - Keywords or more complex statements such as RDF 
(see section 2.1.4)

The important differences between the types of meta-data are whether the 
representation is unique among documents, whether it can be 
automatically generated, and the logical complexity of the associations.
-------------------------------------------------------------------

Basically I was just following that thinking.  Perhaps I am muddying the 
water?  But I guess I would want to make a distinction between metadata 
that is semantic annotations, and "structural"? "factual" metadata, that 
can be generated by some process of inspection.

However, even if you wanted to avoid calling data that is derived by 
inspection "meta-data", we still have things like the tracker url.  I 
would have said that that is metadata.  How to organise and co-ordinate 
that data about files is arguably a meta-data issue - but then I would 
be just as happy to use another word - well, I guess I have written a 
lot about meta-data, so to use a different word now might be confusing 
... still I see it all as part of coordination of data about data in p2p 
systems ....

CHEERS> SAM



_______________________________________________
P2prg mailing list
P2prg@irtf.org
https://www.ietf.org/mailman/listinfo/p2prg


_______________________________________________
P2prg mailing list
P2prg@irtf.org
https://www.ietf.org/mailman/listinfo/p2prg



From exim@www1.ietf.org  Mon Feb 16 12:01:25 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05194
	for <p2prg-archive@odin.ietf.org>; Mon, 16 Feb 2004 12:01:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Asm77-0005vO-7J
	for p2prg-archive@odin.ietf.org; Mon, 16 Feb 2004 12:00:57 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1GH0uL5022767
	for p2prg-archive@odin.ietf.org; Mon, 16 Feb 2004 12:00:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Asm73-0005v8-Ac
	for p2prg-web-archive@optimus.ietf.org; Mon, 16 Feb 2004 12:00:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05179
	for <p2prg-web-archive@ietf.org>; Mon, 16 Feb 2004 12:00:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Asm72-0000jL-00
	for p2prg-web-archive@ietf.org; Mon, 16 Feb 2004 12:00:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Asm5x-0000bH-00
	for p2prg-web-archive@ietf.org; Mon, 16 Feb 2004 11:59:46 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Asm5M-0000VO-00
	for p2prg-web-archive@ietf.org; Mon, 16 Feb 2004 11:59:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Asm5H-0005mR-KS; Mon, 16 Feb 2004 11:59:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Asm4p-0005kO-Er
	for p2prg@optimus.ietf.org; Mon, 16 Feb 2004 11:58:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04982
	for <p2prg@ietf.org>; Mon, 16 Feb 2004 11:58:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Asm4o-0000SR-00
	for p2prg@ietf.org; Mon, 16 Feb 2004 11:58:34 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Asm47-0000OB-00
	for p2prg@ietf.org; Mon, 16 Feb 2004 11:57:52 -0500
Received: from [216.65.116.22] (helo=sm1255.hostcentric.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Asm3O-0000D0-00
	for p2prg@ietf.org; Mon, 16 Feb 2004 11:57:06 -0500
Received: (qmail 12819 invoked by uid 107); 16 Feb 2004 16:47:06 -0000
Received: from c-24-118-168-87.mn.client2.attbi.com (HELO bitbucket) (justin@onionnetworks.com@24.118.168.87)
  by 216.65.116.22 with SMTP; 16 Feb 2004 16:47:06 -0000
Subject: RE: [P2Prg] BitTorrent Paper Summary
From: Justin Chapweske <justin@chapweske.com>
To: osokin@osokin.com
Cc: sam@neurogrid.com, p2p-irtf <p2prg@ietf.org>, p2prg-metadata@cs.umd.edu
In-Reply-To: <IJECJCHFLLIPKMNGHDPMGEBMEJAA.osokin@osokin.com>
References: <IJECJCHFLLIPKMNGHDPMGEBMEJAA.osokin@osokin.com>
Content-Type: text/plain
Message-Id: <1076950593.11942.8503.camel@bog>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 
Date: Mon, 16 Feb 2004 10:56:34 -0600
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: p2prg-admin@ietf.org
Errors-To: p2prg-admin@ietf.org
X-BeenThere: p2prg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/p2prg>,
	<mailto:p2prg-request@ietf.org?subject=unsubscribe>
List-Id: Peer-to-Peer Research Group <p2prg.ietf.org>
List-Post: <mailto:p2prg@ietf.org>
List-Help: <mailto:p2prg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2prg>,
	<mailto:p2prg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I see no reason why it isn't valid to refer to the file size,
last-modified, hash, etc., as file metadata.  

As far as encoding goes, we've found that HTTP header fields are a
perfectly capable mechanism for transferring file metadata, and if you
need something with even more structure, then just use RDF.

> 
> 	Sam, why do you call it metadata? I always assumed that
> metadata would be various stuff like performer, album, bitrate,
> quality, etc. Okay, so Bram Cohen himself calls .torrent files
> 'metainfo' - but is it a good term for the contents of that
> file? What .torrent has (and btw, I think that it hashes not
> only the file itself, but also every separate piece of the
> file) - anyway, it seems to be a fairly straightforward
> integrity checking mechanism, not unlike, say, TigerTree
> hash or Kazaa hash.
> 
> 	Do you really insist on calling it metadata? Am I missing
> something?
> 
> 	Best wishes -
> 	S.Osokine.
> 	12 Feb 2004.
> 
> 
> -----Original Message-----
> From: p2prg-admin@ietf.org [mailto:p2prg-admin@ietf.org]On Behalf Of Sam
> Joseph
> Sent: Thursday, February 12, 2004 1:57 PM
> To: p2p-irtf; p2prg-metadata@cs.umd.edu
> Subject: [P2Prg] BitTorrent Paper Summary
> 
> 
> Hi All,
> 
> So I'm posting this to p2prg as well as p2p-metadata as well, since I
> haven't seen much discussion on either.  To get us going with some
> meta-data and trust topics, I'm posting my summary notes on the
> BitTorrent paper:
> 
> http://www.sims.berkeley.edu/research/conferences/p2pecon/papers/s4-cohen.pd
> f
> 
> I would be very interested to hear any comments or feedback.  I think
> BitTorrent is very interesting because it uses special meta-data
> encoding and tit-for-tat choking in order to make sure of fair downloads.
> 
> CHEERS> SAM
> 
> 
> Incentives Build Robustness in BitTorrent
> 
> 1. Problems addressed
> 
> Downloading files from multiple sources.
> Difficult due to:
> a) complexity of assignment
> b) churn
> c) fairness
> 
> 2. Interface
> 
> Absolute simplicity of interface perhaps key to take up of BitTorrent
> 
> 3. MetaData
> 
> Torrent files specify information about a file length, name, hashing
> information, and url of a tracker - all bencoded to reduce size
> 
> 4. Trackers and peers
> 
> Peers get random lists of other peers that are sharing parts of a file
> from trackers.  Updated each 3-5 minutes, and at least 1800 trackers
> currently in existence.  Tracker is simple, runs over http and has
> minimal comms.  Files are broken into chunks with hashes to ensure
> correctness.  All peers continuously download chunks from all peers they
> can.
> 
> 5.  Various Heuristics used to improve performance
> 
> a) random connections
> b) pipelining - always have more requests for file pieces lined up
> c) try to download the rarest piece of a file first
> d) when downloading starts go for random first peice
> e) special endgame mode to cancel slow downloads
> f) tit for tat choking + optimistic unchoking
> g) Snubbing
> 
> 
> 
> _______________________________________________
> P2prg mailing list
> P2prg@irtf.org
> https://www.ietf.org/mailman/listinfo/p2prg
> 
> 
> _______________________________________________
> P2prg mailing list
> P2prg@irtf.org
> https://www.ietf.org/mailman/listinfo/p2prg


_______________________________________________
P2prg mailing list
P2prg@irtf.org
https://www.ietf.org/mailman/listinfo/p2prg



From exim@www1.ietf.org  Mon Feb 16 14:44:23 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14523
	for <p2prg-archive@odin.ietf.org>; Mon, 16 Feb 2004 14:44:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Asoem-0002mY-IF
	for p2prg-archive@odin.ietf.org; Mon, 16 Feb 2004 14:43:56 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1GJhq1b010688
	for p2prg-archive@odin.ietf.org; Mon, 16 Feb 2004 14:43:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Asoel-0002mJ-WB
	for p2prg-web-archive@optimus.ietf.org; Mon, 16 Feb 2004 14:43:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14501
	for <p2prg-web-archive@ietf.org>; Mon, 16 Feb 2004 14:43:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Asoej-0005wR-00
	for p2prg-web-archive@ietf.org; Mon, 16 Feb 2004 14:43:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Asodw-0005qC-00
	for p2prg-web-archive@ietf.org; Mon, 16 Feb 2004 14:43:01 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Asod7-0005jH-00
	for p2prg-web-archive@ietf.org; Mon, 16 Feb 2004 14:42:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Asocz-0002Ut-Gj; Mon, 16 Feb 2004 14:42:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Asoce-0002T4-5h
	for p2prg@optimus.ietf.org; Mon, 16 Feb 2004 14:41:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14316
	for <p2prg@ietf.org>; Mon, 16 Feb 2004 14:41:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Asocb-0005eR-00
	for p2prg@ietf.org; Mon, 16 Feb 2004 14:41:37 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Asobc-0005Z6-00
	for p2prg@ietf.org; Mon, 16 Feb 2004 14:40:37 -0500
Received: from mordred.cs.ucla.edu ([131.179.192.128] helo=cs.ucla.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Asoai-0005RF-00
	for p2prg@ietf.org; Mon, 16 Feb 2004 14:39:40 -0500
Received: from cs.ucla.edu (7m4kc43e6n3yjazx@localhost [127.0.0.1])
	by cs.ucla.edu (8.12.10/8.12.9) with ESMTP id i1GJcvYh059135;
	Mon, 16 Feb 2004 11:38:57 -0800 (PST)
	(envelope-from scottm@cs.ucla.edu)
Message-ID: <40311C51.4050803@cs.ucla.edu>
Date: Mon, 16 Feb 2004 11:38:57 -0800
From: Scott Michel <scottm@cs.ucla.edu>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6b) Gecko/20040206 Thunderbird/0.4
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: osokin@osokin.com
CC: sam@neurogrid.com, p2p-irtf <p2prg@ietf.org>, p2prg-metadata@cs.umd.edu
Subject: Re: [P2Prg] BitTorrent Paper Summary
References: <IJECJCHFLLIPKMNGHDPMGEBMEJAA.osokin@osokin.com>
In-Reply-To: <IJECJCHFLLIPKMNGHDPMGEBMEJAA.osokin@osokin.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: p2prg-admin@ietf.org
Errors-To: p2prg-admin@ietf.org
X-BeenThere: p2prg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/p2prg>,
	<mailto:p2prg-request@ietf.org?subject=unsubscribe>
List-Id: Peer-to-Peer Research Group <p2prg.ietf.org>
List-Post: <mailto:p2prg@ietf.org>
List-Help: <mailto:p2prg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2prg>,
	<mailto:p2prg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Serguei Osokine wrote:

>On Thursday, February 12, 2004 Sam Joseph wrote:
>  
>
>>3. MetaData
>>
>>Torrent files specify information about a file
>>length, name, hashing information, and url of a
>>tracker - all bencoded to reduce size
>>    
>>
>
>	Sam, why do you call it metadata? I always assumed that
>metadata would be various stuff like performer, album, bitrate,
>quality, etc. Okay, so Bram Cohen himself calls .torrent files
>'metainfo' - but is it a good term for the contents of that
>file? What .torrent has (and btw, I think that it hashes not
>only the file itself, but also every separate piece of the
>file) - anyway, it seems to be a fairly straightforward
>integrity checking mechanism, not unlike, say, TigerTree
>hash or Kazaa hash.
>  
>
Filesystem attributes are and will continue to be called metadata. The 
difference here is that the metadata is stored in two different places, 
hence the name change to disambiguate which metadata is which. Even 
worse is when the file content metadata to which you're referring is 
stored in the file itself as opposed to a FS structure.

>	Do you really insist on calling it metadata? Am I missing
>something?
>  
>
Yes, I'm relatively sure that information about a file, irrespective of 
where it is stored (in the FS or inside the file) will always be called 
metadata.


-scooter

_______________________________________________
P2prg mailing list
P2prg@irtf.org
https://www.ietf.org/mailman/listinfo/p2prg



From exim@www1.ietf.org  Thu Feb 19 01:08:25 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15744
	for <p2prg-archive@odin.ietf.org>; Thu, 19 Feb 2004 01:08:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AthLo-0000PC-F6
	for p2prg-archive@odin.ietf.org; Thu, 19 Feb 2004 01:07:56 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1J67uEs001552
	for p2prg-archive@odin.ietf.org; Thu, 19 Feb 2004 01:07:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AthLo-0000Ox-4A
	for p2prg-web-archive@optimus.ietf.org; Thu, 19 Feb 2004 01:07:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15735
	for <p2prg-web-archive@ietf.org>; Thu, 19 Feb 2004 01:07:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AthLl-000586-00
	for p2prg-web-archive@ietf.org; Thu, 19 Feb 2004 01:07:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AthKn-00056H-00
	for p2prg-web-archive@ietf.org; Thu, 19 Feb 2004 01:06:55 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AthK1-00054a-00
	for p2prg-web-archive@ietf.org; Thu, 19 Feb 2004 01:06:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AthJy-0008Uc-8S; Thu, 19 Feb 2004 01:06:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AthJu-0008UP-1k
	for p2prg@optimus.ietf.org; Thu, 19 Feb 2004 01:05:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15708
	for <p2prg@ietf.org>; Thu, 19 Feb 2004 01:05:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AthJr-00053X-00
	for p2prg@ietf.org; Thu, 19 Feb 2004 01:05:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AthIx-00051p-00
	for p2prg@ietf.org; Thu, 19 Feb 2004 01:05:00 -0500
Received: from out1.smtp.messagingengine.com ([66.111.4.25])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AthIS-0004zP-00
	for p2prg@ietf.org; Thu, 19 Feb 2004 01:04:28 -0500
X-Sasl-enc: lHcqwWRl9+Dm0jYFWqSyJA 1077170412
Received: from [10.0.1.3] (adsl-63-202-175-169.dsl.snfc21.pacbell.net [63.202.175.169])
	by mail.messagingengine.com (Postfix) with ESMTP id 762CC583DB7
	for <p2prg@ietf.org>; Thu, 19 Feb 2004 01:00:11 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v609)
Content-Transfer-Encoding: quoted-printable
Message-Id: <E14322E0-62A0-11D8-83D9-000A95766260@fastmail.fm>
Content-Type: text/plain; charset=WINDOWS-1252; format=flowed
To: "'p2prg@ietf.org'" <p2prg@ietf.org>
From: Bill Yeager <byeager@fastmail.fm>
Date: Wed, 18 Feb 2004 22:00:12 -0800
X-Mailer: Apple Mail (2.609)
Content-Transfer-Encoding: quoted-printable
Subject: [P2Prg] HICSS-38 CFP
Sender: p2prg-admin@ietf.org
Errors-To: p2prg-admin@ietf.org
X-BeenThere: p2prg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/p2prg>,
	<mailto:p2prg-request@ietf.org?subject=unsubscribe>
List-Id: Peer-to-Peer Research Group <p2prg.ietf.org>
List-Post: <mailto:p2prg@ietf.org>
List-Help: <mailto:p2prg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2prg>,
	<mailto:p2prg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,LINES_OF_YELLING,
	LINES_OF_YELLING_2 autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

   [Our apologies if you receive multiple postings of this message]


    CALL FOR PAPERS: Peer-to-Peer Infrastructures and Applications
                  in the Software Technology Track
                    at the Thirty-eighth Annual
           HAWAI'I INTERNATIONAL CONFERENCE ON SYSTEM SCIENCES
                     on the Big Island of Hawaii
                         January 3 - 6, 2005

                 Additional detail on the web sites:
                   http://cui.unige.ch/OSG/hicss38/
                     http://www.hicss.hawaii.edu/


The purpose of this one-day mini-track is to provide a forum for=20
researchers
and practitioners to discuss software technology issues related to
peer-to-peer (P2P) computing and its evolving paradigm. P2P is an=20
emerging,
21st century technology whose applications from the onset have=20
exhibited both
its power and diversity. While examples of applications abound, because=20=

of the
youthfulness of P2P these applications more often than not run on
non-interoperable infrastructures. As a consequence others have seen a=20=

need for
infrastructure and protocol standards. The Project JXTA open source=20
community,
and the research branch of the IETF, the Internet Research Task Force=20
(IRTF)
Research Group on P2P are two salient examples. Finally, the research=20
community
has taken it upon itself to put in place a solid theoretical foundation=20=

of P2P
computing by addressing issues like routing, trust, security, content
distribution, P2P platform performance, lookup, search, computational=20
grids
based on P2P platforms, etc.

The above efforts are yielding a common paradigm for Peer-to-Peer=20
computing.
It is a model for programming distributed systems that is characterized=20=

by
an increasing decentralization, autonomy and, if desired, anonymity of=20=

its
Peer components, where they can play the roles of both clients and=20
servers,
thus requiring new approaches and patterns for distributed computing. It
necessitates a natural evolution or mapping of the Internet protocols=20
that
then must also be characterized by the p2p requirements of participating
nodes. While industry as a whole is hard at work trying to impose=20
tomorrow=92s
=93legacy architectures=94 by the means of so called Web Services,=20
Peer-to-Peer
computing goes one step further and postulates that although there will
always be a need for centralization in the client-server sense, the=20
general
model that should prevail is again one where roles are not clear cut but
dynamic. Peers are thus actors that appear and disappear dynamically,=20
hence
pushing back and forth the edges of the network, potentially endorsing=20=

all
possible roles at any point in time. In this context, hard-wired=20
centralized
services are only one among many interaction patterns that can be=20
achieved in
Peer-to-Peer architectures that more closely capture the features of a=20=

real
world, distributed computing eco-system.

Similarly, the Semantic Web initiative by the W3C also builds on this=20
departure
from centralized architectures and places the debate at the level of=20
ontologies
and semantics. We may expect web services to occur and interoperate in
Peer-to-Peer architectures. In this context, the paradigm shift appears=20=

to lie
in the convergence of several technologies such as Peer-to-Peer=20
frameworks,
Mobile Agents, Digital Rights Management / Digital Policy Management,=20
trust
computing, cognitive or knowledge agents and ontologies.

In the above context, contributions of interest will be those that=20
describe novel
business interactions and user coordination models, applications=20
supporting the
peer-to-peer paradigm, and research that both pushes the frontiers of=20
the
applications, infrastructures and protocols as well as verifies their=20
limits with
respect to performance and scalability. Thus we envisage an=20
interdisciplinary
forum that brings together researchers, practitioners from industry,=20
and members
of open source communities to discuss and evaluate the technology=20
aspect as well
as the interplay between technological capabilities and new emerging=20
forms of
commercial electronic interaction. Topics related to the emerging P2P=20
paradigm
include, but are not limited to, the following:

     - P2P system architectures and protocols
     - P2P overlay networks
     - P2P services
     - Security
     - Trust and reputation
     - Mobile objects (Agents)
     - Wireless infrastructures
     - Semantic and discovery services
     - Rights and policy languages
     - Digital rights management and policy management (DRM/DPM)
     - Self-organizing information systems
     - Multi-agent systems
     - Electronic communities and marketplaces
     - Monitoring, metering and auditing
     - Digital asset management and trading


Coordinators:


Primary Contact : Bill Yeager
IRTF Peer-to-Peer Research Group
E-mail: byeager@fastmail.fm


Karl Aberer
EPF Lausanne, Dept. of Communication Systems, Switzerland
E-mail: karl.aberer@epfl.ch

Jean-Henry Morin
University of Geneva - CUI, Switzerland
E-mail: Jean-Henry.Morin@cui.unige.ch

Aris Ouksel
The University of Illinois at Chicago, USA
E-mail: aris@uic.edu


IMPORTANT DEADLINES : New Dates !

March 31, 2004     Abstracts submitted for guidance and indication of
                    appropriate content.
June 15, 2004      Full papers submitted to Minitrack Chairs.
                    Contact minitrack chairs for submission =
instructions.
August 15, 2004    Notice of accepted papers sent to Authors.
October 1, 2004    Accepted manuscripts sent electronically to the
                    publisher. Author(s) must be registered for the
                    conference by this date.


The proceedings will be published by the IEEE Computer Society Press.


PROGRAM COMMITTEE (PRELIMINARY)

Sonia Bergamaschi, University of Modena, Italy
Peter Dadam, University of Ulm, Germany
Shamkant Navathe, Georgia Tech, USA
Oliver Gunther, Humboldt University, Germany
Ouri Wolfson, Univ. Illinois Chicago, USA
Claudio Sartori, University of Bologna, Italy
Tawfik Jelassi, ENPC, France
Peter Scheuermann, Northwestern University, USA
Manfred Hauswirth, EPFL, Switzerland
Heiko Ludwig, IBM T.J. Watson Research Center, USA
Tamer Ozsu, University of Waterloo, Canada
Rachid Guerrraoui, EPFL, Switzerland
Bruno Codenotti, CNR, Italy
Ciaran Bryce, University of Geneva - CUI, Switzerland
Guy Genilloud,  Financial Systems Architects, Switzerland
Yves Pigneur, University of Lausanne - INFORGE, Switzerland
Dimitri Konstantas, University of Geneva - CUI, Switzerland
Vassilis Prevelakis, Drexel University, USA
Yair Babad, University of Illinois at Chicago, USA
Tomas Sander, HP Labs, USA
Esmail Salehi-Sangari, Lulea University of Technology, Sweden
Manolis Koubarakis, Technical University of Crete, Greece
Ling Liu, Georgia Institute of Technology, USA
Rita Chen, Sun Microsystems, USA
Asuman Dogac, Middle East Technical University, Turkey
Bobby Bhattacharjee, University of Maryland, USA
Tsung-Nan Lin, National Taiwan University, Taiwan


INSTRUCTIONS FOR PAPER SUBMISSION:

1. Submit electronically your full paper by June 15, 2004. Full papers
should have an abstract and be 20 - 25 typewritten, double-spaced pages
in length including diagrams.
(NOTE: The final paper will be 10 pages, double-column, single spaced.
The proceedings will be published by the IEEE Computer Society Press.
Authors will be required to follow the general author instructions of
IEEE Computer Society Press: http://computer.org/cspress/instruct.htm )

2. Do NOT submit the manuscript to more than one Minitrack. Papers
should contain original material and not be previously published, or
currently submitted for consideration elsewhere.

3. Each paper must have a title page to include title of the paper,
full name of all authors, and complete addresses including
affiliation(s), telephone number(s), and e-mail address(es).

4. The first page of the manuscript should include only the title and a
300-word abstract of the paper.

Submission Address: byeager@fastmail.fm and morin@cui.unige.ch

Authors are requested to submit the full manuscript electronically in
PDF, Postscript, Word or RTF format by June 15, 2004 to=20
byeager@fastmail.fm
and morin@cui.unige.ch


THE SOFTWARE TECHNOLOGY TRACK AT HICSS-38
     Chair: Gul Agha;
     Email: agha@cs.uiuc.edu;
     WWW  : http://www.hicss.hawaii.edu/Hicss38/fsfcfp.htm

For the latest information; visit the HICSS web site at:
     http://www.hicss.hawaii.edu/

HICSS conferences are devoted to advances in the information, computer,
and system sciences, and encompass developments in both theory and
practice.   Invited papers may be theoretical, conceptual, tutorial or
descriptive in nature.  Submissions undergo a peer referee process and
those selected for presentation will be published in the Conference
Proceedings.  Submissions must not have been previously published.


CONFERENCE ADMINISTRATION:

Ralph Sprague, Conference Chair
Email: sprague@hawaii.edu

Sandra Laney, Conference Administrator
Email: hicss@hawaii.edu

Eileen Dennis, Track Administrator
Email: eidennis@indiana.edu


2005 HICSS-38 CONFERENCE VENUE:

Hilton Waikoloa Village (on the Big Island of Hawaii)
425 Waikoloa Beach Drive
Waikoloa, Hawaii 96738
Tel: 1-808-886-1234
Fax: 1-808-886-2900
http://www.hiltonwaikoloavillage.com/

NOTE:  December 1 is the deadline to guarantee hotel room reservation at
        conference rate.



_______________________________________________
P2prg mailing list
P2prg@irtf.org
https://www.ietf.org/mailman/listinfo/p2prg



From exim@www1.ietf.org  Tue Feb 24 03:56:23 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA07454
	for <p2prg-archive@odin.ietf.org>; Tue, 24 Feb 2004 03:56:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AvYM6-0002ed-EJ
	for p2prg-archive@odin.ietf.org; Tue, 24 Feb 2004 03:55:55 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1O8ts1p010197
	for p2prg-archive@odin.ietf.org; Tue, 24 Feb 2004 03:55:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AvYM5-0002eN-2i
	for p2prg-web-archive@optimus.ietf.org; Tue, 24 Feb 2004 03:55:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA07434
	for <p2prg-web-archive@ietf.org>; Tue, 24 Feb 2004 03:55:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvYM2-0003hm-00
	for p2prg-web-archive@ietf.org; Tue, 24 Feb 2004 03:55:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AvYL7-0003cp-00
	for p2prg-web-archive@ietf.org; Tue, 24 Feb 2004 03:54:54 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvYKL-0003Yk-00
	for p2prg-web-archive@ietf.org; Tue, 24 Feb 2004 03:54:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AvYKH-0002Q7-Af; Tue, 24 Feb 2004 03:54:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AvYK4-0002P6-Pd
	for p2prg@optimus.ietf.org; Tue, 24 Feb 2004 03:53:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA07358
	for <p2prg@ietf.org>; Tue, 24 Feb 2004 03:53:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvYK2-0003XK-00
	for p2prg@ietf.org; Tue, 24 Feb 2004 03:53:46 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AvYJ4-0003T4-00
	for p2prg@ietf.org; Tue, 24 Feb 2004 03:52:47 -0500
Received: from mordor.cerego.co.jp ([210.158.200.254])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvYI8-0003ME-00
	for p2prg@ietf.org; Tue, 24 Feb 2004 03:51:48 -0500
Received: from CEREGO_EXCHANGE.cerego.co.jp (optional02.cerego.co.jp [192.168.2.1])
	by mordor.cerego.co.jp (Postfix) with ESMTP
	id BA4F4734E; Tue, 24 Feb 2004 17:46:11 +0900 (JST)
Received: from neurogrid.com (frodo.cerego.co.jp [192.168.2.3]) by CEREGO_EXCHANGE.cerego.co.jp with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id 1XZ562YK; Tue, 24 Feb 2004 17:50:51 +0900
Message-ID: <403B1074.5080605@neurogrid.com>
Date: Tue, 24 Feb 2004 17:51:00 +0900
From: Sam Joseph <sam@neurogrid.com>
Reply-To: sam@neurogrid.com
Organization: NeuroGrid http://www.neurogrid.net/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja-JP; rv:1.4) Gecko/20030624
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: p2p-irtf <p2prg@ietf.org>,
        "Peer-to-peer development." <p2p-hackers@zgp.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MailScanner-Information: Verified by MailScanner (Mordor)
X-MailScanner: STATUS-CLEAN
X-MailScanner-SpamCheck: not spam, SpamAssassin (score=-0.2, required 5,
	AWL 0.00, SUBJ_ALL_CAPS 1.15, USER_AGENT_MOZILLA_UA 0.00,
	X_ACCEPT_LANG -0.10)
Content-Transfer-Encoding: quoted-printable
Subject: [P2Prg] CFP: AP2PC 2004
Sender: p2prg-admin@ietf.org
Errors-To: p2prg-admin@ietf.org
X-BeenThere: p2prg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/p2prg>,
	<mailto:p2prg-request@ietf.org?subject=unsubscribe>
List-Id: Peer-to-Peer Research Group <p2prg.ietf.org>
List-Post: <mailto:p2prg@ietf.org>
List-Help: <mailto:p2prg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2prg>,
	<mailto:p2prg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

*** our apologies if you receive multiple copies of this e-mail ***

                Preliminary call for papers


              Third International Workshop on
             Agents and Peer-to-Peer Computing
                        (AP2PC 2004)

                 http://p2p.ingce.unibo.it/

                  to be held at AAMAS 2004
          Third International Joint Conference on
          Autonomous Agents and MultiAgent Systems

                     New York City, USA
                     July 19 or 20, 2004


----------
Overview
----------
Peer-to-peer (P2P) computing is attracting enormous media attention, spur=
red by the popularity of file sharing systems such as Napster, Gnutella, =
and Morpheus. The peers are autonomous, or as some call them, first-class=
 citizens. P2P networks are emerging as a new distributed computing parad=
igm for their potential to harness the computing power of the hosts compo=
sing the network and make their under-utilized resources available to oth=
ers. This possibility has generated a lot of interest in many industrial =
organizations which have already launched important projects.

In P2P systems, peer and web services in the role of resources become sha=
red and combined to enable new capabilities greater than the sum of the p=
arts. This means that services can be developed and treated as pools of m=
ethods that can be composed dynamically. The decentralized nature of P2P =
computing makes it also ideal for economic environments that foster knowl=
edge sharing and collaboration as well as cooperative and non-cooperative=
 behaviors in sharing resources. Business models are being developed, whi=
ch rely on incentive mechanisms to supply contributions to the system and=
 methods for controlling free riding. Clearly, the growth and the managem=
ent of P2P networks must be regulated to ensure adequate compensation of =
content and/or service providers. At the same time, there is also a need =
to ensure equitable distribution of content and services.

Although researchers working on distributed computing, MultiAgent Systems=
, databases and networks have been using similar concepts for a long time=
, it is only recently that papers motivated by the current P2P paradigm h=
ave started appearing in high quality conferences and workshops. Research=
 in agent systems in particular appears to be most relevant because, sinc=
e their inception, MultiAgent Systems have always been thought of as netw=
orks of peers.

The MultiAgent paradigm can thus be superimposed on the P2P architecture,=
 where agents embody the description of the task environments, the decisi=
on-support capabilities, the collective behavior, and the interaction pro=
tocols of each peer. The emphasis in this context on decentralization, us=
er autonomy, ease and speed of growth that gives P2P its advantages, also=
 leads to significant potential problems. Most prominent among these prob=
lems are coordination: the ability of an agent to make decisions on its o=
wn actions in the context of activities of other agents, and scalability:=
 the value of the P2P systems lies in how well they scale along several d=
imensions, including complexity, heterogeneity of peers, robustness, traf=
fic redistribution, and so on. It is important to scale up coordination s=
trategies along multiple dimensions to enhance their tractability and via=
bility, and thereby to widen the application domains. These two problems =
are common to many large-scale applications. Without coordination, agents=
 may be wasting their efforts, squander resources and fail to achieve the=
ir objectives in situations requiring collective effort.

This workshop will bring together researchers working on agent systems an=
d P2P computing with the intention of strengthening this connection. Rese=
archers from other related areas such as distributed systems, networks an=
d database systems will also be welcome (and, in our opinion, have a lot =
to contribute).

We seek high-quality and original contributions on the general theme of "=
Agents and P2P Computing". The following is a non-exhaustive list of topi=
cs of special interest:

* Intelligent agent techniques for P2P computing
* P2P computing techniques for multi-agent systems
* The Semantic Web, Semantic Coordination Mechanisms and P2P systems
* Scalability, coordination, robustness and adaptability in P2P systems
* Self-organization and emergent behavior in P2P networks
* E-commerce and P2P computing
* Participation and Contract Incentive Mechanisms in P2P Systems
* Computational Models of Trust and Reputation
* Community of interest building and regulation, and behavioral norms
* Intellectual property rights in P2P systems
* P2P architectures
* Scalable Data Structures for P2P systems
* Services in P2P systems (service definition languages, service discover=
y, filtering and composition etc.)
* Knowledge Discovery and P2P Data Mining Agents
* P2P data management
* Information ecosystems and P2P systems
* Security issues in P2P networks
* Pervasive computing based on P2P architectures (ad-hoc networks, wirele=
ss communication devices and mobile systems)
* Grid computing solutions based on agents and P2P paradigms
* Legal issues in P2P networks


-------
Panel
-------
The theme of the panel will be Conducting Business via P2P. P2P computing=
 has had some visible successes in applications such as file sharing, but=
 many of these applications have had a consumer or hobbyist focus. This p=
anel will discuss emerging "mission-critical" applications of P2P and the=
 challenges that P2P technologies must surmount in order to best support =
such applications. These challenges include security, trust and reputatio=
n, representing business protocols, checking compliance, bootstrapping sy=
stems, and performance. The panel will involve 10 minute presentations by=
 four panelists followed by a discussion session involving the audience.


------------------
Important dates
------------------
Abstract:                       1st April 2004  (see submission
instructions below)
Paper submission:               6th April 2004
Acceptance notification:        1st May 2004
Workshop:                      19 or 20th July 2004
Camera ready for
Post-proceedings:              31st August 2004


---------------
Registration
---------------
Accomodation and workshop registration will be handled by the AAMAS 2004 =
organization along with the main conference registration.


---------------------------
Submission instructions
---------------------------
Unpublished papers should be formatted according to the LNCS/LNAI author =
instructions for proceedings and they should not be longer than 12 pages =
(about 5000 words including figures, tables, references, etc.).

The abstract and then the paper should be submitted electronically HERE a=
ccording to the deadlines mentioned above.=20

In case of problems submit abstract and paper (pdf), according to the dea=
dlines mentioned above, to submission@ingce.unibo.it=20
by specifying in both emails: paper's author(s), title, contact author an=
d at most 5 keywords/topics.



-------------
Publication
-------------
Accepted papers will be distributed to the workshop participants as works=
hop notes. Post-proceedings of the revised papers (namely accepted papers=
 presented at the workshop) will be published by Springer - Lecture Notes=
 in Computer Science series (LNCS)
Here are the volumes of revised and invited papers of preceding editions:=

LNCS volume no. 2530 for AP2PC'2002
LNCS volume no. 2872 for AP2PC'2003 (publication in progress)=20


-------------
Organizers
-------------
Program Co-chairs

Karl Aberer
=C9cole Polytechnique F=E9d=E9rale de Lausanne (EPFL)
CH-1015 Lausanne, Switzerland
Tel. +41-21-693 4679 - Fax +41-21-693 8115
E-mail: karl.aberer@epfl.ch

Sonia Bergamaschi
Dept. of Science Engineering,
University of Modena and Reggio-Emilia, Italy
via Vignolese, 905 - 41100 Modena Italy
Tel. +39 059 2056132 - Fax +39 059 2056126
E-mail: bergamaschi.sonia@unimo.it

Gianluca Moro (main contact)
Dept. of Electronics, Computer Science and Systems,
University of Bologna, Italy
Via Venezia, 52 - I-47023 Cesena (FC)
Tel. +39 0547 339237 - Fax +39 0547 339208
E-mail: gmoro@deis.unibo.it


-------------
Panel Chair
-------------
Munindar P. Singh
Dept. of Computer Science, North Carolina State University, USA
Venture I, Suite 110 / Box 7535 - Raleigh, NC 27695-7535
Tel. +1 919 515.5677 - Fax +1 919 515.7896
E-mail: mpsingh@eos.ncsu.edu


----------------------
Steering Commitee
----------------------
Karl Aberer, EPFL, Lausanne, Switzerland
Sonia Bergamaschi, University of Modena and Reggio-Emilia, Italy
Manolis Koubarakis, Technical University of Crete
Paul Marrow, Intelligent Systems Laboratory, BTexact Technologies, UK
Gianluca Moro, University of Bologna, Cesena, Italy
Aris M. Ouksel, University of Illinois at Chicago, USA
Claudio Sartori, University of Bologna, Italy
Munindar P. Singh, North Carolina State University, USA


----------------------------------
Web Master of Review System
----------------------------------
Sam Joseph
Laboratory for Interactive Learning Technology (LILT), University of
Hawaii
E-mail: srjoseph@hawaii.edu


---------------
Sponsorships
---------------
Khaled Nagi
Computer Science Dept., Alexandria University,
E-mail: khaledn@acm.org


----------------------
Program commitee
----------------------
Karl Aberer, EPFL, Lausanne, Switzerland
Sonia Bergamaschi, University of Modena and Reggio-Emilia, Italy
Jon Bing, Universitat of Oslo, Norway
M. Brian Blake, Georgetown University, USA
Rajkumar Buyya, University of Melbourne, Australia
Ooi Beng Chin, National University of Singapore, Singapore
Paolo Ciancarini, University of Bologna, Italy
Costas Courcoubetis, Athens University of Economics and Business, Greece
Yogesh Deshpande, University of Western Sydney, Australia
Asuman Dogac, Middle East Technical University, Turkey
Boi V. Faltings, EPFL, Lausanne, Switzerland
Maria Gini, University of Minnesota, USA
Dina Q. Goldin, University of Connecticut, USA
Chihab Hanachi, University of Toulouse, France
Mark Klein, Massachusetts Institute of Technology, USA
Matthias Klusch, DFKI, Saarbrucken, Germany
Yannis Labrou, PowerMarket Inc., USA
Tan Kian Lee, National University of Singapore, Singapore
Dejan Milojicic, Hewlett Packard Labs, USA
Alberto Montresor, University of Bologna, Italy
Luc Moreau, University of Southampton, UK
Jean-Henry Morin, University of Geneve, Switzerland
John Mylopoulos, University of Toronto, Canada
Andrea Omicini, University of Bologna, Italy
Maria Orlowska, University of Queensland, Australia
Aris. M. Ouksel, University of Illinois at Chicago, USA
Mike Papazoglou, Tilburg University, Netherlands
Terry R. Payne, University of Southampton, UK
Paolo Petta, Austrian Research Institute for AI, Austria,
Jeremy Pitt, Imperial College, UK
Dimitris Plexousakis, Institute of Computer Science, FORTH, Greece
Martin Purvis, University of Otago, New Zealand
Omer F. Rana, Cardiff University, UK
Katia Sycara, Robotics Institute, Carnegie Mellon University, USA
Douglas S. Reeves, North Carolina State University, USA
Thomas Risse, Fraunhofer IPSI, Darmstadt, Germany
Pierangela Samarati, University of Milan, Italy
Giovanni Sartor, CIRSFID, University of Bologna, Italy,
Christophe Silbertin-Blanc, University of Toulouse, France
Maarten van Steen, Vrije Universiteit, Netherlands
Markus Stumptner, University of South Australia, Australia
Peter Triantafillou, Technical University of Crete, Greece
Anand Tripathi, University of Minnesota, USA
Vijay K. Vaishnavi, Georgia State University, USA
Francisco Valverde-Albacete, Universidad Carlos III de Madrid, Spain
Maurizio Vincini, University of Modena and Reggio-Emilia, Italy
Fang Wang, BTexact Technologies, UK
Gerhard Weiss, Technische Universitaet, Germany
Bin Yu, North Carolina State University, USA
Franco Zambonelli, University of Modena and Reggio-Emilia, Italy






_______________________________________________
P2prg mailing list
P2prg@irtf.org
https://www.ietf.org/mailman/listinfo/p2prg



From exim@www1.ietf.org  Wed Feb 25 04:28:51 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05629
	for <p2prg-archive@odin.ietf.org>; Wed, 25 Feb 2004 04:28:51 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AvvL5-000551-J5
	for p2prg-archive@odin.ietf.org; Wed, 25 Feb 2004 04:28:23 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1P9SNCJ019526
	for p2prg-archive@odin.ietf.org; Wed, 25 Feb 2004 04:28:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AvvL5-00054q-0r
	for p2prg-web-archive@optimus.ietf.org; Wed, 25 Feb 2004 04:28:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05483
	for <p2prg-web-archive@ietf.org>; Wed, 25 Feb 2004 04:28:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvvL2-0006Fr-00
	for p2prg-web-archive@ietf.org; Wed, 25 Feb 2004 04:28:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AvvJC-0005pJ-00
	for p2prg-web-archive@ietf.org; Wed, 25 Feb 2004 04:26:28 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvvHJ-0005O3-00
	for p2prg-web-archive@ietf.org; Wed, 25 Feb 2004 04:24:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AvvH7-0003zs-7s; Wed, 25 Feb 2004 04:24:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AvuVA-000122-41
	for p2prg@optimus.ietf.org; Wed, 25 Feb 2004 03:34:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA03297
	for <p2prg@ietf.org>; Wed, 25 Feb 2004 03:34:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvuV7-00008M-00
	for p2prg@ietf.org; Wed, 25 Feb 2004 03:34:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AvuUE-00003M-00
	for p2prg@ietf.org; Wed, 25 Feb 2004 03:33:46 -0500
Received: from tik6.ethz.ch ([129.132.119.136])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AvuTT-0007lc-00
	for p2prg@ietf.org; Wed, 25 Feb 2004 03:32:59 -0500
Received: from localhost (localhost [127.0.0.1])
	by tik6.ethz.ch (Postfix) with ESMTP id 564436ADFE
	for <p2prg@ietf.org>; Wed, 25 Feb 2004 09:32:59 +0100 (MET)
Received: from kom7 (kom7 [129.132.66.4])
	by tik6.ethz.ch (Postfix) with ESMTP id F1AE36ADE8
	for <p2prg@ietf.org>; Wed, 25 Feb 2004 09:32:58 +0100 (MET)
Date: Wed, 25 Feb 2004 09:32:58 +0100 (MET)
From: Nathalie Weiler <weiler@tik.ee.ethz.ch>
X-X-Sender: weiler@kom7
Reply-To: weiler@tik.ee.ethz.ch
To: p2prg@ietf.org
Message-ID: <Pine.GSO.4.43.0402250932170.24312-100000@kom7>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: by AMaViS new-20020517
Subject: [P2Prg] Call for Papers for P2P2004
Sender: p2prg-admin@ietf.org
Errors-To: p2prg-admin@ietf.org
X-BeenThere: p2prg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/p2prg>,
	<mailto:p2prg-request@ietf.org?subject=unsubscribe>
List-Id: Peer-to-Peer Research Group <p2prg.ietf.org>
List-Post: <mailto:p2prg@ietf.org>
List-Help: <mailto:p2prg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2prg>,
	<mailto:p2prg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60


Dear Recipient,

The call for papers for the Fourth International Peer-to-Peer conference
(P2P2004) is now available. An excerpt is attached below, and the full
version with further information can be found at http://femto.org/p2p2004/

We are looking forward to your submissions and contributions for the
conference, and would like to ask you to forward this call for papers
to any forum or list of people that you would find appropriate.

            Many thanks,

  Nathalie Weiler + Germano Caronni




CALL FOR PAPERS FOR P2P 2004          (see also http://femto.org/p2p2004)
============================

The Fourth International Peer-to-Peer conference (P2P2004) is now seeking
your paper submissions. It is to take place at the Swiss Federal Institute
of Technology in Zurich, from Aug. 25 to Aug 27. 2004.

The Scope
---------
P2P2004 is the fourth Conference in a continuation of annual conferences
concerned with the convergence of overlay network technologies that
empower the leaf-nodes. These technologies include Peer-to-Peer, Grids,
Clusters, and the Web Services that ride over them. These overlay networks
are converging toward a common set of protocols due to their extensive
implementations on the Internet and other shared environments.

These new protocols render the overlay networks functionally independent
of the networks that they ride on. This has opened new security
issues. Not only must we be concerned with the security within the
overlay network, we must be concerned with the threats they may spawn
toward the networks they ride on.

Consistent with our previous conferences we promote a collaboration
in research between academic institutions, government organizations,
and business enterprises that are concerned with the research and
implementation of P2P, Grids, and Clusters.


Topics
------
Any topic that relates to Peer-to-Peer, Grids, and Clusters is open
for consideration. We would like to give special encouragement to
research papers on security technology and policy issues for these
overlay networks. Some of the suggested topics are:

Security in P2P Systems 		Trust and Reputation
Accountability 				Applications
Overlay System Monitoring 		Agents
Overlay Super Computers 		Middleware
Overlay Architectures 			Network Management
Wireless 				Protocols
Collaboration 				Supernodes
Grids 					Clusters
Object Location and Retrieval 		Storage Systems
e-Commerce

We include all presented papers in the proceedings. The IEEE Proceedings
hardcopy will be available at the Conference.

Important Dates
---------------

Paper submission deadline:   2 May 2004
Notification of acceptance:  7 June 2004
Camera ready papers due:    20 June 2004
Conference:                 25-27 August 2004

For more information and submission details, please visit our website
at http://femto.org/p2p2004





_______________________________________________
P2prg mailing list
P2prg@irtf.org
https://www.ietf.org/mailman/listinfo/p2prg



From exim@www1.ietf.org  Fri Feb 27 19:05:15 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05304
	for <p2prg-archive@odin.ietf.org>; Fri, 27 Feb 2004 19:05:15 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AwryL-00075C-L6
	for p2prg-archive@odin.ietf.org; Fri, 27 Feb 2004 19:04:49 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1S04nMO027220
	for p2prg-archive@odin.ietf.org; Fri, 27 Feb 2004 19:04:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AwryL-00074w-Bb
	for p2prg-web-archive@optimus.ietf.org; Fri, 27 Feb 2004 19:04:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05261
	for <p2prg-web-archive@ietf.org>; Fri, 27 Feb 2004 19:04:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwryI-0004DY-00
	for p2prg-web-archive@ietf.org; Fri, 27 Feb 2004 19:04:46 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwrxP-00047W-00
	for p2prg-web-archive@ietf.org; Fri, 27 Feb 2004 19:03:52 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Awrwe-00040w-00
	for p2prg-web-archive@ietf.org; Fri, 27 Feb 2004 19:03:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Awrwa-0006u8-JH; Fri, 27 Feb 2004 19:03:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AwrwH-0006qP-0g
	for p2prg@optimus.ietf.org; Fri, 27 Feb 2004 19:02:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05164
	for <p2prg@ietf.org>; Fri, 27 Feb 2004 19:02:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwrwD-0003ya-00
	for p2prg@ietf.org; Fri, 27 Feb 2004 19:02:37 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AwrvI-0003rE-00
	for p2prg@ietf.org; Fri, 27 Feb 2004 19:01:40 -0500
Received: from proxy.cs.umd.edu ([128.8.128.182] helo=poole.cs.umd.edu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AwruL-0003eE-00
	for p2prg@ietf.org; Fri, 27 Feb 2004 19:00:41 -0500
Received: from poole.cs.umd.edu (localhost.localdomain [127.0.0.1])
	by poole.cs.umd.edu (8.12.8/8.12.8) with ESMTP id i1S04TEL021578;
	Fri, 27 Feb 2004 19:04:29 -0500
Received: (from bobby@localhost)
	by poole.cs.umd.edu (8.12.8/8.12.8/Submit) id i1S04TxF021574;
	Fri, 27 Feb 2004 19:04:29 -0500
From: <bobby@cs.umd.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16447.56076.962934.108402@poole.cs.umd.edu>
Date: Fri, 27 Feb 2004 19:04:28 -0500
To: p2prg@ietf.org
X-Mailer: VM 7.07 under 21.4 (patch 12) "Portable Code" XEmacs Lucid
Reply-To: Bobby Bhattacharjee  <bobby@cs.umd.edu>
cc: byeager@fastmail.fm
Content-Transfer-Encoding: 7bit
Subject: [P2Prg] Subgroup summaries
Sender: p2prg-admin@ietf.org
Errors-To: p2prg-admin@ietf.org
X-BeenThere: p2prg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/p2prg>,
	<mailto:p2prg-request@ietf.org?subject=unsubscribe>
List-Id: Peer-to-Peer Research Group <p2prg.ietf.org>
List-Post: <mailto:p2prg@ietf.org>
List-Help: <mailto:p2prg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2prg>,
	<mailto:p2prg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


[This message is directed explicitly towards the subgroup leaders, but
obviously, everyone is welcome to reply].

We have to send Vern a montly summary of activities for the P2P
research group.  If possible, please email Bill and me a few sentences
about progress within your subgroups.  These summaries are due on the
first of every month, so I understand if this request is too late.

Thanks,
Bill and Bobby

p.s. I already have an extensive report for p2p-mobility (so unless
you want to, you don't need to send us another synopsis).  Thanks.






_______________________________________________
P2prg mailing list
P2prg@irtf.org
https://www.ietf.org/mailman/listinfo/p2prg



