Clarifications for the use of REFER with RFC6665

Document Type Replaced Internet-Draft (individual)
Authors Robert Sparks  , Adam Roach 
Last updated 2014-10-27
Replaced by RFC 7647
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-sipcore-refer-clarifications
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


An accepted SIP REFER method creates an implicit subscription using the SIP-Specific Event Notification Framework. That framework was revised by RFC6665. This document highlights the implications of the requirement changes in RFC6665, and updates the definition of the REFER method, RFC3515, to clarify and disambiguate the impact of those changes.


Robert Sparks (
Adam Roach (

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)