RFC 6940: REsource LOcation And Discovery (RELOAD) Base Protocol
In plain English — editorial summary, not part of the RFC
This specification defines REsource LOcation And Discovery (RELOAD), a peer-to-peer (P2P) signaling protocol for use on the Internet. A P2P signaling protocol provides its clients with an abstract storage and messaging service between a set of cooperating peers that form the overlay network. RELOAD is designed to support a P2P Session Initiation Protocol (P2PSIP) network, but can be utilized by other applications with similar requirements by defining new usages that specify the Kinds of data that need to be stored for a particular application. RELOAD defines a security model based on a certificate enrollment service that provides unique identities. NAT traversal is a fundamental service of the protocol. RELOAD also allows access from "client" nodes that do not need to route traffic or store data for others.
Document record
- Document ID
- RFC6940
- Published
- January 2014
- Authors
- C. Jennings; B. Lowekamp; E. Rescorla; S. Baset; H. Schulzrinne
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 176
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7363Self-Tuning Distributed Hash Table (DHT) for REsource LOcation And Discovery (RELOAD)Current
September 2014
- RFC 7374Service Discovery Usage for REsource LOcation And Discovery (RELOAD)Current
October 2014
- RFC 7851Peer-to-Peer (P2P) Overlay DiagnosticsCurrent
May 2016
- RFC 7890Concepts and Terminology for Peer-to-Peer SIP (P2PSIP)Current
June 2016
- RFC 7904A SIP Usage for REsource LOcation And Discovery (RELOAD)Current
October 2016
- RFC 7263An Extension to the REsource LOcation And Discovery (RELOAD) Protocol to Support Direct Response RoutingCurrent
June 2014
- RFC 7264An Extension to the REsource LOcation And Discovery (RELOAD) Protocol to Support Relay Peer RoutingCurrent
June 2014
- RFC 8076A Usage for Shared Resources in RELOAD (ShaRe)Current
March 2017
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?