Clarifications for the use of REFER with RFC6665
draft-sparks-sipcore-refer-clarifications-05

Document Type Replaced Internet-Draft (individual)
Last updated 2014-10-27
Replaced by draft-ietf-sipcore-refer-clarifications
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf 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
https://www.ietf.org/archive/id/draft-sparks-sipcore-refer-clarifications-05.txt

Abstract

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.

Authors

Robert Sparks (rjsparks@nostrum.com)
Adam Roach (adam@nostrum.com)

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