[p2pi] IRTF - P2P Research Group
stefano previdi <sprevidi@cisco.com> Thu, 13 November 2008 11:03 UTC
Return-Path: <p2pi-bounces@ietf.org>
X-Original-To: p2pi-archive@ietf.org
Delivered-To: ietfarch-p2pi-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 938143A6905; Thu, 13 Nov 2008 03:03:32 -0800 (PST)
X-Original-To: p2pi@core3.amsl.com
Delivered-To: p2pi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 444E93A687E; Thu, 13 Nov 2008 03:03:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level:
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ub07RUq6qx8y; Thu, 13 Nov 2008 03:03:30 -0800 (PST)
Received: from av-tac-bru.cisco.com (odd-brew.cisco.com [144.254.15.119]) by core3.amsl.com (Postfix) with ESMTP id 2C0BC3A6856; Thu, 13 Nov 2008 03:03:29 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost [127.0.0.1]) by av-tac-bru.cisco.com (8.11.7p3+Sun/8.11.7) with ESMTP id mADB3Dk13506; Thu, 13 Nov 2008 12:03:13 +0100 (CET)
Received: from [192.168.0.100] (ams3-vpn-dhcp5378.cisco.com [10.61.85.1]) by strange-brew.cisco.com (8.11.7p3+Sun/8.11.7) with ESMTP id mADB34G13306; Thu, 13 Nov 2008 12:03:06 +0100 (CET)
User-Agent: Microsoft-Entourage/11.4.0.080122
Date: Thu, 13 Nov 2008 12:02:46 +0100
From: stefano previdi <sprevidi@cisco.com>
To: p2prg@irtf.org, p2psip@ietf.org, p2pi@ietf.org, alto@ietf.org, ledbat@ietf.org
Message-ID: <C541C7E6.7CB53%sprevidi@cisco.com>
Thread-Topic: IRTF - P2P Research Group
Thread-Index: AclFf1vLmi5mtLFyEd24OAAX8vOM8g==
Mime-version: 1.0
Cc: Volker Hilt <volkerh@alcatel-lucent.com>, Aaron Falk <falk@bbn.com>
Subject: [p2pi] IRTF - P2P Research Group
X-BeenThere: p2pi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: P2P Infrastructure Discussion <p2pi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/p2pi>, <mailto:p2pi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/p2pi>
List-Post: <mailto:p2pi@ietf.org>
List-Help: <mailto:p2pi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2pi>, <mailto:p2pi-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2pi-bounces@ietf.org
Errors-To: p2pi-bounces@ietf.org
Following the new creation of IETF WGs scoped around issues of peer-to-peer applications (ALTO and LEDBAT) and considering the interest into a forum where research topics related to p2p can be discussed, we started an effort in order to re-activate the IRTF Peer-to-peer Research Group with the proposed (updated) charter below. The p2prg will of course interact with the IETF P2P WGs (P2PSIP, ALTO, LEDBAT). Any comments, feedback and suggestions are welcome. Thanks. s. --------------------------------------------------------------------- IRTF Peer-to-Peer Research Group (P2PRG) ----------------------------------- Chair(s): --------- TBD Mailing Lists: -------------- The email list is p2prg@irtf.org. You need not be a list member to send mail to the list. To subscribe, visit the P2PRG mail page (https://www.ietf.org/mailman/listinfo/p2prg) or send an email to p2prg-request@irtf.org. Website ------- Documents and members only discussion mailing list can be found at the P2Prg web site: http://trac.tools.ietf.org/group/irtf/trac/wiki/PeerToPeerResearchGroup Charter ------- Peer-to-Peer (P2P) is a way of structuring distributed applications such that the individual nodes have symmetric roles. Rather than being divided into clients and servers each with quite distinct roles (such as Web clients vs. Web servers), in P2P applications each node can act as both a client and a server. A key concept for P2P systems is therefore to permit any two peers to communicate with one another in such a way that either ought to be able to initiate the contact. P2P systems in general are highly distributed, highly scalable to large numbers of nodes and users, highly autonomous, and can lend themselves to anonymity. Some historical examples of P2P systems are USENET servers, built on top of NNTP, and inter-domain routing, built on top of BGP. More recent P2P systems are file sharing networks such as Gnutella, BitTorrent, eDonkey/eMule and voice-over-IP applications such as Skype. While P2P systems are deployed and used on a large scale, many research questions in the field of P2P remain open. For example, current P2P systems often form their overlay networks based on application layer information and ignore the structure and policies of the underlying network infrastructure. As a result, peers often connect to peers in a remote network even though an equivalent peer would be available in the local network. This can lead to the inefficient use of network resources and to conflicts between application- and network-level routing. Another problem arises from the fact that many different P2P systems are defined and deployed. It is desirable for users on one system to be able to reach users on other P2P systems without requiring applications to implement the mechanisms and protocols of all systems available. Mechanisms for interconnecting and interoperability between P2P systems are needed. Many P2P systems are based on distributed hash tables (DHTs), which implement a distributed storage for key-value pairs. While DHTs are effective in looking up a specific key, search and information retrieval in DHTs remain challenging problems. Peer nodes in a P2P network perform services for other peers. A challenge is therefore to protect a P2P network against malicious nodes which may try to alter the service or disable it. Finally, it is interesting to evaluate P2P systems that are deployed to better understand the performance of algorithms deployed and the behavior of user. Performance and usage data is an important foundation for the development of new P2P mechanisms and architectures. Mechanisms and tools that collect this information from existing p2p systems are highly desirable. Overall, the field of P2P technologies presents a number of interesting challenges which includes new methods for forming P2P application overlays, interconnecting distinct P2P application overlays, performing routing and peer selection decisions, managing traffic and discovering resources. Other challenges are related to storage, reliability, and information retrieval in P2P systems. Yet another challenging area for P2P is security, privacy, anonymity and trust. Finally, it is challenging to examine P2P systems that are deployed, for example, to measure, monitor and characterize P2P applications. The P2P RG will collaborate with academia and industry on making progress addressing these challenges. The IETF has formed working groups to address specific issues of P2P networking. During the development of standards for P2P networks in these working groups, new research topics may arise that exceed the working group charter and require a separate forum for discussion. The P2P RG will provide such a forum. The IETF has chartered working groups related to the following topics: - Peer-to-Peer SIP signaling (P2PSIP) - Application-Layer Traffic Optimization (ALTO) - Low Extra Delay Background Transport (LEDBAT) Organization ------------ The P2PRG will maintain a list of prioritized topics in order to organize the activity of the research group according to agreed importance and priority. The P2PRG will use an open mailing list (p2prg@irtf.org) as the main communication vehicle for the group. The P2PRG will encourage the organization of the work in smaller design teams focused on specific areas of research. The design teams will use the general mailing list in order to allow the broader community to follow the evolution of their topics. Most of the communication inside the P2PRG will be done through use of mailing lists, however, the group will hold regular physical meetings at least once a year in conjunction with IETF meetings. Additional meetings may be held at IETF or other venues, such as in conjunction with related academic conferences. The P2PRG will produce Informational and Experimental RFCs in order to document the activity of the group and to formalize the outcome of the research topics carried by the group. In addition, such documentation could become input to IETF working groups. Membership ---------- The RG operates in an open fashion (meetings & mailing list). _______________________________________________ p2pi mailing list p2pi@ietf.org https://www.ietf.org/mailman/listinfo/p2pi
- [p2pi] IRTF - P2P Research Group stefano previdi