Subject: [sipcore] Fwd: New Version Notification for draft-sparks-sipcore-refer-clarifications-05.txt

From: Robert Sparks <[email-masked]>
Date: Mon, 27 Oct 2014 09:16:13 -0500

-------- Forwarded Message --------
Subject: 	New Version Notification for 
draft-sparks-sipcore-refer-clarifications-05.txt
Date: 	Mon, 27 Oct 2014 07:13:11 -0700
From: 	[email-masked]
To: 	Adam Roach <[email-masked]>, Adam Roach <[email-masked]>, 
Robert Sparks <[email-masked]>, Robert Sparks <[email-masked]>

A new version of I-D, draft-sparks-sipcore-refer-clarifications-05.txt
has been successfully submitted by Robert Sparks and posted to the
IETF repository.

Name:		draft-sparks-sipcore-refer-clarifications
Revision:	05
Title:		Clarifications for the use of REFER with RFC6665
Document date:	2014-10-27
Group:		Individual Submission
Pages:		5
URL:            http://www.ietf.org/internet-drafts/draft-sparks-sipcore-refer-clarifications-05.txt
Status:         https://datatracker.ietf.org/doc/draft-sparks-sipcore-refer-clarifications/
Htmlized:       http://tools.ietf.org/html/draft-sparks-sipcore-refer-clarifications-05
Diff:           http://www.ietf.org/rfcdiff?url2=draft-sparks-sipcore-refer-clarifications-05

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.

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat