Concepts and Terminology for Peer-to-Peer SIP (P2PSIP) (RFC7890)
Original Publication Date: 2016-Jun-01
Included in the Prior Art Database: 2016-Jun-29
Internet Society Requests For Comment (RFCs)
D. Bryan: AUTHOR [+5]
One of the fundamental problems in multimedia communication between Internet nodes is the rendezvous problem, or discovering the host at which a given user can be reached. In the Session Initiation Protocol (SIP) [RFC3261], this problem is expressed as the problem of mapping an Address of Record (AoR) for a user into one or more Contact URIs [RFC3986]. The AoR is a name for the user that is independent of the host or hosts where the user can be contacted, while a Contact URI indicates the host where the user can be contacted.
Internet Engineering Task Force (IETF) D. Bryan Request for Comments: 7890 Cogent Force, LLC Category: Informational P. Matthews ISSN: 2070-1721 Nokia E. Shim Samsung Electronics Co., Ltd. D. Willis Softarmor Systems S. Dawkins Huawei (USA) June 2016
Concepts and Terminology for Peer-to-Peer SIP (P2PSIP)
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.
Status of This Memo
This document is not an Internet Standards Track specification; it is published for informational purposes.
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 7841.
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7890.
Bryan, et al. Informational ...