RFC 5694 on Peer-to-Peer (P2P) Architecture: Definition, Taxonomies, Examples, and Applicability

rfc-editor@rfc-editor.org Tue, 24 November 2009 00:35 UTC

Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F03DF3A6B0E for <ietf-announce@core3.amsl.com>; Mon, 23 Nov 2009 16:35:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.419
X-Spam-Level:
X-Spam-Status: No, score=-17.419 tagged_above=-999 required=5 tests=[AWL=0.180, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
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 aNiacglNhXoF for <ietf-announce@core3.amsl.com>; Mon, 23 Nov 2009 16:35:26 -0800 (PST)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 33E243A6B03 for <ietf-announce@ietf.org>; Mon, 23 Nov 2009 16:35:26 -0800 (PST)
Received: by bosco.isi.edu (Postfix, from userid 70) id 85117372B7C; Mon, 23 Nov 2009 16:30:15 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5694 on Peer-to-Peer (P2P) Architecture: Definition, Taxonomies, Examples, and Applicability
From: rfc-editor@rfc-editor.org
Message-Id: <20091124003015.85117372B7C@bosco.isi.edu>
Date: Mon, 23 Nov 2009 16:30:15 -0800
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Nov 2009 00:35:27 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5694

        Title:      Peer-to-Peer (P2P) Architecture:
                    Definition, Taxonomies, Examples, and Applicability 
        Author:     G. Camarillo, Ed.,
                    IAB
        Status:     Informational
        Date:       November 2009
        Mailbox:    Gonzalo.Camarillo@ericsson.com, 
                    iab@iab.org
        Pages:      26
        Characters: 68446
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-iab-p2p-archs-03.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5694.txt

In this document, we provide a survey of P2P (Peer-to-Peer) systems.
The survey includes a definition and several taxonomies of P2P
systems.  This survey also includes a description of which types of
applications can be built with P2P technologies and examples of P2P
applications that are currently in use on the Internet.  Finally, we
discuss architectural trade-offs and provide guidelines for deciding
whether or not a P2P architecture would be suitable to meet the
requirements of a given application.  This memo provides information
for the Internet community.

This document is a product of the Internet Architecture Board.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute