RFC 5765: Security Issues and Solutions in Peer-to-Peer Systems for Realtime Communications
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC5765
- Published
- February 2010
- Authors
- H. Schulzrinne; E. Marocco; E. Ivov
- Status
- INFORMATIONAL
- Stream
- IRTF
- Area
- —
- Pages
- 28
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7086Host Identity Protocol-Based Overlay Networking Environment (HIP BONE) Instance Specification for REsource LOcation And Discovery (RELOAD)Current
January 2014
- RFC 7933Adaptive Video Streaming over Information-Centric Networking (ICN)Current
August 2016
- RFC 8316Autonomic Networking Use Case for Distributed Detection of Service Level Agreement (SLA) ViolationsCurrent
February 2018
- RFC 8763Deployment Considerations for Information-Centric Networking (ICN)Current
April 2020
- RFC 5694Peer-to-Peer (P2P) Architecture: Definition, Taxonomies, Examples, and ApplicabilityCurrent
November 2009
- RFC 5693Application-Layer Traffic Optimization (ALTO) Problem StatementCurrent
October 2009
- RFC 5859TFTP Server Address Option for DHCPv4Current
June 2010
- RFC 5866Diameter Quality-of-Service ApplicationCurrent
May 2010
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?