draft-ietf-sipcore-refer-clarifications-01.txt   draft-ietf-sipcore-refer-clarifications-02.txt 
Network Working Group R. Sparks Network Working Group R. Sparks
Internet-Draft Oracle Internet-Draft Oracle
Updates: 3515 (if approved) A. Roach Updates: 3515 (if approved) A. Roach
Intended status: Standards Track Mozilla Intended status: Standards Track Mozilla
Expires: July 25, 2015 January 21, 2015 Expires: August 3, 2015 January 30, 2015
Clarifications for the use of REFER with RFC6665 Clarifications for the use of REFER with RFC6665
draft-ietf-sipcore-refer-clarifications-01 draft-ietf-sipcore-refer-clarifications-02
Abstract Abstract
The SIP REFER method relies on the SIP-Specific Event Notification The SIP REFER method relies on the SIP-Specific Event Notification
Framework. That framework was revised by RFC6665. This document Framework. That framework was revised by RFC6665. This document
highlights the implications of the requirement changes in RFC6665, highlights the implications of the requirement changes in RFC6665,
and updates the definition of the REFER method, RFC3515, to clarify and updates the definition of the REFER method, RFC3515, to clarify
and disambiguate the impact of those changes. and disambiguate the impact of those changes.
Status of This Memo Status of This Memo
skipping to change at page 1, line 35 skipping to change at page 1, line 35
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 25, 2015. This Internet-Draft will expire on August 3, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 17 skipping to change at page 3, line 17
3. Use of GRUU is mandatory 3. Use of GRUU is mandatory
Section 4.5.1 of [RFC6665] makes GRUU [RFC5627] mandatory for Section 4.5.1 of [RFC6665] makes GRUU [RFC5627] mandatory for
notifiers to implement and use as the local target in the notifiers to implement and use as the local target in the
subscription created by the REFER request. subscription created by the REFER request.
A user agent accepting a REFER that creates a subscription MUST A user agent accepting a REFER that creates a subscription MUST
populate its Contact header field with a GRUU. populate its Contact header field with a GRUU.
A UA that will accept a REFER request needs to include a GRUU in the A UA that might possibly become a notifier (e.g. by accepting a REFER
Contact header field of all dialog-forming and target-refresh methods request that creates a subscription) needs to include a GRUU in the
Contact header field of dialog-forming and target-refresh methods
(such as INVITE) [I-D.roach-sipcore-6665-clarification]. This (such as INVITE) [I-D.roach-sipcore-6665-clarification]. This
ensures that out-of-dialog REFER requests corresponding to any ensures that out-of-dialog REFER requests corresponding to any
resulting INVITE dialogs arrive at this UA. Future extensions (such resulting INVITE dialogs arrive at this UA. Future extensions (such
as [I-D.ietf-sipcore-refer-explicit-subscription]) might relax this as [I-D.ietf-sipcore-refer-explicit-subscription]) might relax this
requirement by defining a REFER request that cannot create an requirement by defining a REFER request that cannot create an
implicit subscription, thus not causing the accepting UA to become an implicit subscription, thus not causing the accepting UA to become an
RFC6665 notifier in the context of this dialog. RFC6665 notifier in the context of this dialog.
4. Dialog reuse is prohibited 4. Dialog reuse is prohibited
skipping to change at page 4, line 42 skipping to change at page 4, line 42
Christer Holmberg provided the formulation for the final paragraph of Christer Holmberg provided the formulation for the final paragraph of
the introduction. Christer Holmberg and Ivo Sedlacek provided the introduction. Christer Holmberg and Ivo Sedlacek provided
detailed comments during working group discussion of the document. detailed comments during working group discussion of the document.
8. Changelog 8. Changelog
RFC Editor - please remove this section when formatting this document RFC Editor - please remove this section when formatting this document
as an RFC as an RFC
-00 to -01 -02 to -01
Tweaked the third paragraph of section 3 per list discussion.
(Note the subject line of that discussion said -explicit-
subscription)
-00 to -01
Added the 3rd paragraph to the introduction per extensive list Added the 3rd paragraph to the introduction per extensive list
discussion discussion
draft-sparks-sipcore-refer-clarifications-05 to draft-ietf- draft-sparks-sipcore-refer-clarifications-05 to draft-ietf-
sipcore-refer-clarifications-00 sipcore-refer-clarifications-00
Attempted to improve the accuracy of the Abstract and Attempted to improve the accuracy of the Abstract and
Introduction without diluting the essential point of the Introduction without diluting the essential point of the
document. document.
Added an informative reference to RFC5057. Added an informative reference to RFC5057.
Adjusted text to more reflect what RFC6665 (as clarified by Adjusted text to more reflect what RFC6665 (as clarified by
draft-roach-sipcore-6665-clarification) actually requires, and draft-roach-sipcore-6665-clarification) actually requires, and
added a normative reference to that clarification draft. added a normative reference to that clarification draft.
Specifically, the requirement for the _sender_ of a REFER to Specifically, the requirement for the _sender_ of a REFER to
 End of changes. 7 change blocks. 
6 lines changed or deleted 13 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/