RFC 7614: Explicit Subscriptions for the REFER Method
In plain English — editorial summary, not part of the RFC
The Session Initiation Protocol (SIP) REFER request, as defined by RFC 3515, triggers an implicit SIP-Specific Event Notification framework subscription. Conflating the start of the subscription with handling the REFER request makes negotiating SUBSCRIBE extensions impossible and complicates avoiding SIP dialog sharing. This document defines extensions to REFER that remove the implicit subscription and, if desired, replace it with an explicit one.
Document record
- Document ID
- RFC7614
- Published
- August 2015
- Authors
- R. Sparks
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7573Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): One-to-One Text Chat SessionsCurrent
June 2015
- RFC 7572Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Instant MessagingCurrent
June 2015
- RFC 7700Preparation, Enforcement, and Comparison of Internationalized Strings Representing NicknamesObsoleted
December 2015
- RFC 7702Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): GroupchatCurrent
December 2015
- RFC 7375Secure Telephone Identity Threat ModelCurrent
October 2014
- RFC 7877Session Peering Provisioning Framework (SPPF)Current
August 2016
- RFC 7878Session Peering Provisioning (SPP) Protocol over SOAPCurrent
August 2016
- RFC 7345UDP Transport Layer (UDPTL) over Datagram Transport Layer Security (DTLS)Updated
August 2014
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?