RFC 7890: Concepts and Terminology for Peer-to-Peer SIP (P2PSIP)
In plain English — editorial summary, not part of the RFC
This document defines concepts and terminology for using the Session Initiation Protocol in a peer-to-peer environment where the traditional proxy-registrar and message-routing functions are replaced by a distributed mechanism. These mechanisms may be implemented using a Distributed Hash Table or other distributed data mechanism with similar external properties. This document includes a high-level view of the functional relationships between the network elements defined herein, a conceptual model of operations, and an outline of the related problems addressed by the P2PSIP working group, the REsource LOcation And Discovery (RELOAD) protocol, and the SIP usage document defined by the working group.
Document record
- Document ID
- RFC7890
- Published
- June 2016
- Authors
- D. Bryan; P. Matthews; E. Shim; D. Willis; S. Dawkins
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- art
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7904A SIP Usage for REsource LOcation And Discovery (RELOAD)Current
October 2016
- RFC 8076A Usage for Shared Resources in RELOAD (ShaRe)Current
March 2017
- RFC 7374Service Discovery Usage for REsource LOcation And Discovery (RELOAD)Current
October 2014
- RFC 6940REsource LOcation And Discovery (RELOAD) Base ProtocolCurrent
January 2014
- RFC 7878Session Peering Provisioning (SPP) Protocol over SOAPCurrent
August 2016
- RFC 7877Session Peering Provisioning Framework (SPPF)Current
August 2016
- RFC 7851Peer-to-Peer (P2P) Overlay DiagnosticsCurrent
May 2016
- RFC 7984Locating Session Initiation Protocol (SIP) Servers in a Dual-Stack IP NetworkCurrent
September 2016
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?