RFC 7904: A SIP Usage for REsource LOcation And Discovery (RELOAD)
In plain English — editorial summary, not part of the RFC
This document defines a SIP Usage for REsource LOcation And Discovery (RELOAD). The SIP Usage provides the functionality of a SIP proxy or registrar in a fully distributed system and includes a lookup service for Address of Records (AORs) stored in the overlay. It also defines Globally Routable User Agent URIs (GRUUs) that allow the registrations to map an AOR to a specific node reachable through the overlay. After such initial contact of a Peer, the RELOAD AppAttach method is used to establish a direct connection between nodes through which SIP messages are exchanged.
Document record
- Document ID
- RFC7904
- Published
- October 2016
- Authors
- C. Jennings; B. Lowekamp; E. Rescorla; S. Baset; H. Schulzrinne; T. Schmidt
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8076A Usage for Shared Resources in RELOAD (ShaRe)Current
March 2017
- RFC 7890Concepts and Terminology for Peer-to-Peer SIP (P2PSIP)Current
June 2016
- RFC 7851Peer-to-Peer (P2P) Overlay DiagnosticsCurrent
May 2016
- RFC 7374Service Discovery Usage for REsource LOcation And Discovery (RELOAD)Current
October 2014
- RFC 7363Self-Tuning Distributed Hash Table (DHT) for REsource LOcation And Discovery (RELOAD)Current
September 2014
- RFC 6940REsource LOcation And Discovery (RELOAD) Base ProtocolCurrent
January 2014
- RFC 5693Application-Layer Traffic Optimization (ALTO) Problem StatementCurrent
October 2009
- RFC 5632Comcast's ISP Experiences in a Proactive Network Provider Participation for P2P (P4P) Technical TrialCurrent
September 2009
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?