RFC 7878: Session Peering Provisioning (SPP) Protocol over SOAP
In plain English — editorial summary, not part of the RFC
The Session Peering Provisioning Framework (SPPF) specifies the data model and the overall structure to provision Session Establishment Data (SED) into Session Data Registries and SIP Service Provider data stores. To utilize this framework, one needs a substrate protocol. Given that the Simple Object Access Protocol (SOAP) is currently widely used for messaging between elements of such provisioning systems, this document specifies the usage of SOAP (via HTTPS) as the substrate protocol for SPPF. The benefits include leveraging prevalent expertise and a higher probability that existing provisioning systems will be able to easily migrate to using an \%SPPF- based protocol.
Document record
- Document ID
- RFC7878
- Published
- August 2016
- Authors
- K. Cartwright; V. Bhatia; J-F. Mule; A. Mayrhofer
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 83
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7877Session Peering Provisioning Framework (SPPF)Current
August 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 7984Locating Session Initiation Protocol (SIP) Servers in a Dual-Stack IP NetworkCurrent
September 2016
- RFC 7989End-to-End Session Identification in IP-Based Multimedia Communication NetworksCurrent
October 2016
- RFC 8048Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): PresenceCurrent
December 2016
- RFC 7702Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): GroupchatCurrent
December 2015
- RFC 7700Preparation, Enforcement, and Comparison of Internationalized Strings Representing NicknamesObsoleted
December 2015
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?