idnits 2.17.1 draft-roach-sipcore-6665-clarification-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 27, 2014) is 3462 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group A. B. Roach 3 Internet-Draft Mozilla 4 Updates: 6665 (if approved) October 27, 2014 5 Intended status: Standards Track 6 Expires: April 30, 2015 8 A clarification on the use of Globally Routable User Agent URIs (GRUUs) 9 in the Session Initiation Protocol (SIP) Event Notification Framework 10 draft-roach-sipcore-6665-clarification-00 12 Abstract 14 Experience since the publication of the most recent SIP Events 15 framework has shown that there is room for interpretation around the 16 use of Globally Routable User Agent URIs in that specification. This 17 document clarifies the intended behavior. 19 This document updates RFC 6665. 21 Status of This Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at http://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on April 30, 2015. 38 Copyright Notice 40 Copyright (c) 2014 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (http://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 Table of Contents 55 1. Clarification of GRUU Handling . . . . . . . . . . . . . . . 2 56 2. Security Considerations . . . . . . . . . . . . . . . . . . . 2 57 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 58 4. Normative References . . . . . . . . . . . . . . . . . . . . 3 59 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3 61 1. Clarification of GRUU Handling 63 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 64 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 65 document are to be interpreted as described in [RFC2119]. 67 [RFC6665] section 4.5.1 contains the following normative requirement 68 on implementations: 70 Notifiers MUST implement the Globally Routable User Agent URI 71 (GRUU) extension defined in [RFC5627], and MUST use a GRUU as 72 their local target. This allows subscribers to explicitly target 73 desired devices. 75 The second sentence of this paragraph attempted to set context for 76 the normative statement: the reason GRUUs are required in this 77 context is to allow you to send SUBSCRIBE or REFER requests to a 78 specific user agent, with the target of the subscription request 79 being something like an INVITE dialog on that device. Consequently, 80 the requirement to include a GRUU as a local target applies not just 81 to the local target for SUBSCRIBE-created dialogs, but for *all* 82 dialogs, even those created by INVITE. 84 However, this requirement has been interpreted in a variety of ways 85 by implementors, so a clarification is in order. 87 This document updates [RFC6665] to clarify the actual requirement: 88 "Notifiers MUST implement the Globally Routable User Agent URI (GRUU) 89 extension defined in [RFC5627], and MUST use a GRUU as their local 90 target for all dialog-forming methods and all target-refresh methods. 91 This specifically includes dialogs created by the INVITE method." 93 2. Security Considerations 95 This mechanism does not introduce any security issues beyond those 96 discussed in [RFC6665]. 98 3. IANA Considerations 100 This document requests no actions of IANA. 102 4. Normative References 104 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 105 Requirement Levels", BCP 14, RFC 2119, March 1997. 107 [RFC5627] Rosenberg, J., "Obtaining and Using Globally Routable User 108 Agent URIs (GRUUs) in the Session Initiation Protocol 109 (SIP)", RFC 5627, October 2009. 111 [RFC6665] Roach, A.B., "SIP-Specific Event Notification", RFC 6665, 112 July 2012. 114 Author's Address 116 Adam Roach 117 Mozilla 118 Dallas, TX 119 US 121 Phone: +1 650 903 0800 x863 122 Email: adam@nostrum.com