RFC 5765 on Security Issues and Solutions in Peer-to-Peer Systems for Realtime Communications
rfc-editor@rfc-editor.org Tue, 23 February 2010 01:46 UTC
Return-Path: <wwwrun@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 0DCD83A836C for <ietf-announce@core3.amsl.com>; Mon, 22 Feb 2010 17:46:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level:
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[AWL=0.049, BAYES_00=-2.599, NO_RELAYS=-0.001]
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 6UW9aCOvdafk for <ietf-announce@core3.amsl.com>; Mon, 22 Feb 2010 17:46:26 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 06F2528C4F3 for <ietf-announce@ietf.org>; Mon, 22 Feb 2010 17:45:26 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 11B7E130017; Mon, 22 Feb 2010 17:47:27 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5765 on Security Issues and Solutions in Peer-to-Peer Systems for Realtime Communications
From: rfc-editor@rfc-editor.org
Message-Id: <20100223014727.11B7E130017@rfc-editor.org>
Date: Mon, 22 Feb 2010 17:47:27 -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, 23 Feb 2010 01:46:27 -0000
A new Request for Comments is now available in online RFC libraries. RFC 5765 Title: Security Issues and Solutions in Peer-to-Peer Systems for Realtime Communications Author: H. Schulzrinne, E. Marocco, E. Ivov Status: Informational Date: February 2010 Mailbox: hgs@cs.columbia.edu, enrico.marocco@telecomitalia.it, emcho@sip-communicator.org Pages: 28 Characters: 72134 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-irtf-p2prg-rtc-security-05.txt URL: http://www.rfc-editor.org/rfc/rfc5765.txt Peer-to-peer (P2P) networks have become popular for certain applications and deployments for a variety of reasons, including fault tolerance, economics, and legal issues. It has therefore become reasonable for resource consuming and typically centralized applications like Voice over IP (VoIP) and, in general, realtime communication to adapt and exploit the benefits of P2P. Such a migration needs to address a new set of P2P-specific security problems. This document describes some of the known issues found in common P2P networks, analyzing the relevance of such issues and the applicability of existing solutions when using P2P architectures for realtime communication. This document is a product of the P2P Research Group. This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of the IRTF. 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 Association Management Solutions, LLC