idnits 2.17.1 draft-ietf-sipping-gruu-reg-event-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 15. -- Found old boilerplate from RFC 3978, Section 5.5 on line 480. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 457. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 464. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 470. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([2]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (April 19, 2006) is 6581 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) == Unused Reference: '5' is defined on line 420, but no explicit reference was found in the text == Unused Reference: '7' is defined on line 430, but no explicit reference was found in the text == Outdated reference: A later version (-15) exists of draft-ietf-sip-gruu-06 -- Obsolete informational reference (is this intentional?): RFC 3455 (ref. '6') (Obsoleted by RFC 7315) Summary: 4 errors (**), 0 flaws (~~), 5 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Sipping P. Kyzivat 3 Internet-Draft Cisco Systems, Inc. 4 Expires: October 21, 2006 April 19, 2006 6 Registration Event Package Extension for Session Initiation Protocol 7 (SIP) Globablly Routeable User Agent URIs (GRUUs) 8 draft-ietf-sipping-gruu-reg-event-04 10 Status of this Memo 12 By submitting this Internet-Draft, each author represents that any 13 applicable patent or other IPR claims of which he or she is aware 14 have been or will be disclosed, and any of which he or she becomes 15 aware will be disclosed, in accordance with Section 6 of BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 This Internet-Draft will expire on October 21, 2006. 35 Copyright Notice 37 Copyright (C) The Internet Society (2006). 39 Abstract 41 This draft defines an extension to RFC 3680 [2] for representing the 42 GRUU associated with a Contact. 44 Table of Contents 46 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 47 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 48 3. Description . . . . . . . . . . . . . . . . . . . . . . . . . 3 49 4. Notifier Processing of SUBSCRIBE Requests . . . . . . . . . . 4 50 5. Notifier Generation of NOTIFY Requests . . . . . . . . . . . . 4 51 6. Subscriber Processing of NOTIFY Requests . . . . . . . . . . . 4 52 7. Sample reginfo Document . . . . . . . . . . . . . . . . . . . 4 53 8. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 54 8.1. Example: Welcome Notice . . . . . . . . . . . . . . . . . 5 55 8.2. Example: Implicit Registration . . . . . . . . . . . . . . 6 56 9. XML Schema Definition . . . . . . . . . . . . . . . . . . . . 8 57 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 58 10.1. URN Sub-Namespace Registration . . . . . . . . . . . . . . 9 59 10.2. XML Schema Registration . . . . . . . . . . . . . . . . . 10 60 11. Security Considerations . . . . . . . . . . . . . . . . . . . 10 61 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10 62 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10 63 13.1. Normative References . . . . . . . . . . . . . . . . . . . 10 64 13.2. Informative References . . . . . . . . . . . . . . . . . . 10 65 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 12 66 Intellectual Property and Copyright Statements . . . . . . . . . . 13 68 1. Introduction 70 The addition of GRUU (Globally Routable Unique URI) support to the 71 REGISTER message, defined in [3], introduces another element of state 72 to the registrar. Subscribers to the registration event package [2] 73 will sometimes have need for the new state. 75 For example, the Welcome Notices example in [2] will only operate 76 correctly if the contact address in the reg event notification is 77 reachable by the sender of the welcome notice. When the registering 78 device is using the GRUU extension, it is likely that the registered 79 contact address will not be globally addressable, and the GRUU should 80 be used as the target address for the MESSAGE. 82 Another case where this feature may be helpful is within the 3GPP IP 83 Multimedia Subsystem (IMS). IMS employs a technique where a REGISTER 84 of a contact address to one Address of Record (AOR) causes the 85 implicit registration of the same contact to other associated AORs. 86 If a GRUU is requested and obtained as part of the registration 87 request, then additional GRUUs will also be needed for the implicit 88 registrations. While assigning the additional GRUUs is 89 straightforward, informing the registering UA of them is not. In 90 IMS, UAs typically subscribe to the 'reg' event, and subscriptions to 91 the 'reg' event for an AOR result in notifications containing 92 registration state for all the associated AORs. The proposed 93 extension provides a way to easily deliver the GRUUs for the 94 associated AORs. 96 The reg event package has provision for including extension elements 97 within the element. This document defines a new element 98 that may be used in that context to deliver the GRUU corresponding to 99 the contact. 101 2. Terminology 103 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 104 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 105 document are to be interpreted as described in RFC 2119. [1] 107 3. Description 109 A new element () is defined which contains a GRUU. 111 This optional element is included within the body of a NOTIFY for the 112 "reg" event package when a GRUU is associated with the contact. The 113 contact URI and the GRUU are then both available to the watcher. 115 4. Notifier Processing of SUBSCRIBE Requests 117 Unchanged from RFC 3680 [2]. 119 5. Notifier Generation of NOTIFY Requests 121 A notifier for the "reg" event package [2] SHOULD include the 122 element when a contact has an Instance ID and a GRUU is associated 123 with the combination of the AOR and the Instance ID. When present, 124 the element MUST be be positioned as an instance of the 125 element within the element. 127 6. Subscriber Processing of NOTIFY Requests 129 When a subscriber receives a "reg" event notification [2] with a 130 containing a , it SHOULD use the GRUU in preference 131 to the corresponding when sending SIP requests to the contact. 133 Subscribers that are unaware of this extension will, as required by 134 [2], ignore the element. 136 7. Sample reginfo Document 138 Note: This example and others in the following section are 139 indented for readability by the addition of a fixed amount of 140 whitespace to the beginning of each line. This whitespace is not 141 part of the example. The conventions of [8] are used to describe 142 representation of long message lines. 144 The following is an example registration information document 145 including the new element: 147 148 151 153 156 sip:user@192.0.2.1 157 158 159 "<urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>" 160 161 162 163 sip:user@example.com 164 ;opaque=hha9s8d-999a 165 166 167 168 170 8. Examples 172 Note: In the following examples the SIP messages have been 173 simplified, removing headers that are not pertinent to the example. 175 8.1. Example: Welcome Notice 177 Consider the Welcome Notices example in [2]. When the application 178 server receives a notification of a new registration containing the 179 reginfo shown in Section 7 it should address messages using the 180 contained GRUU as follows: 182 MESSAGE sip:user@example.com;opaque=hha9s8d-999a SIP/2.0 183 To: 184 From: "SIPland Notifier" 185 Content-Type: text/plain 186 Content-Length: ... 188 Welcome to SIPland! 189 Blah, blah, blah. 191 8.2. Example: Implicit Registration 193 In an 3GPP IMS setting, a UA may send a single register message, 194 requesting assignment of a GRUU, as follows: 196 REGISTER sip:example.net SIP/2.0 197 From: ;tag=5ab4 198 To: 199 Contact: 200 ;expires=3600 201 ;+sip.instance="" 202 Supported: path, gruu 203 Content-Length: 0 205 The response reports success of the registration and returns the GRUU 206 assigned for the combination of AOR, Instance ID, and Contact. It 207 also indicates (via the P-Associated-URI header [6]) that there are 208 two other associated AORs that may have been implicitly registered 209 using the same contact. But each of those implicitly registered AORs 210 will have had a unique GRUU assigned, and there is no way defined to 211 report that assignment in the response. 213 SIP/2.0 200 OK 214 From: ;tag=5ab4 215 To: ;tag=373392 216 Path: 217 Service-Route: 218 Contact: 219 ;expires=3600 220 ;+sip.instance="" 221 ;gruu="sip:user_aor_1@example.net;opaque=hha9s8d-999a" 222 P-Associated-URI: , 223 224 Content-Length: 0 226 The UA then subscribes to the 'reg' event package as follows: 228 SUBSCRIBE sip:user_aor_1@example.net SIP/2.0 229 From: ;tag=27182 230 To: 231 Route: 232 Event: reg 233 Expires: 3600 234 Accept: application/reginfo+xml 235 Contact: 236 Content-Length: 0 238 (The successful response to the subscription is not shown.) Once the 239 subscription is established an initial notification is sent giving 240 registration status. In IMS deployments the response includes, in 241 addition to the status for the requested URI, the status for the 242 other associated URIs. 244 NOTIFY sip:user_aor_1@example.net;opaque=hha9s8d-999a SIP/2.0 245 From: ;tag=27182 246 To: ;tag=262281 247 Subscription-State: active;expires=3600 248 Event: reg 249 Content-Type: application/reginfo+xml 250 Contact: 251 Content-Length: (...) 253 254 257 259 261 262 sip:ua.example.com 263 264 265 266 "<urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>" 267 268 269 270 sip:user_aor_1@example.net 271 ;opaque=hha9s8d-999a 272 273 274 275 277 279 280 sip:ua.example.com 281 282 283 284 "<urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>" 285 286 287 288 sip:user_aor_2@example.net 289 ;opaque=hha9s8d-999b 290 291 292 293 297 299 300 sip:ua.example.com 301 302 303 304 "<urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>" 305 306 307 308 sip:+358504821437@example.net;user=phone 309 ;opaque=hha9s8d-999c 310 311 312 313 315 The status indicates that the associated URIs all have the same 316 contact registered. It also includes the unique GRUU that has been 317 assigned to each. The UA may then retain those GRUUs for use when 318 establishing dialogs using the corresponding AORs. 320 9. XML Schema Definition 322 A GRUU document is an XML document that MUST be well-formed and 323 SHOULD be valid. GRUU documents MUST be based on XML 1.0 and MUST be 324 encoded using UTF-8. This specification makes use of XML namespaces 325 for identifying GRUU documents. The namespace URI for elements 326 defined for this purpose is a URN, using the namespace identifier 327 'ietf'. This URN is: 328 urn:ietf:params:xml:ns:gruuinfo 330 BEGIN 331 332 337 338 339 END 341 10. IANA Considerations 343 There are two IANA considerations associated with this specification. 345 10.1. URN Sub-Namespace Registration 347 This section registers a new XML namespace, per the guidelines in 348 [4]. 350 URI: The URI for this namespace is urn:ietf:params:xml:ns:gruuinfo 352 Registrant Contact: IETF, SIPPING working group, , 353 Paul Kyzivat 355 XML: 357 BEGIN 358 359 361 362 363 365 Reg Information GRUU Extension Namespace 366 367 368

Namespace for Reg Information GRUU Extension

369

urn:ietf:params:xml:ns:gruuinfo

370

See RFCXXXX [[NOTE 371 TO RFC-EDITOR/IANA: Please replace XXXX with the RFC Number of 372 this specification]].

373 374 375 END 377 10.2. XML Schema Registration 379 This section registers an XML schema per the procedures in [4]. 381 URI: urn:ietf:params:xml:schema:gruuinfo. 383 Registrant Contact: IETF, SIPPING working group, , 384 Paul Kyzivat 386 The XML for this schema can be found in Section 9. 388 11. Security Considerations 390 Security considerations for the registration event package is 391 discussed in RFC 3680 [2], and those considerations apply here. 393 The addition of GRUU information does not impact security negatively 394 because the GRUU is less sensitive than the contact URI itself. 396 12. Acknowledgements 398 The author would like to thank Jonathan Rosenberg for encouraging 399 this draft. 401 13. References 403 13.1. Normative References 405 [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement 406 Levels", BCP 14, RFC 2119, March 1997. 408 [2] Rosenberg, J., "A Session Initiation Protocol (SIP) Event 409 Package for Registrations", RFC 3680, March 2004. 411 [3] Rosenberg, J., "Obtaining and Using Globally Routable User Agent 412 (UA) URIs (GRUU) in the Session Initiation Protocol (SIP)", 413 draft-ietf-sip-gruu-06 (work in progress), October 2005. 415 [4] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 416 January 2004. 418 13.2. Informative References 420 [5] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., 421 Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP: 423 Session Initiation Protocol", RFC 3261, June 2002. 425 [6] Garcia-Martin, M., Henrikson, E., and D. Mills, "Private Header 426 (P-Header) Extensions to the Session Initiation Protocol (SIP) 427 for the 3rd-Generation Partnership Project (3GPP)", RFC 3455, 428 January 2003. 430 [7] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, "Indicating User 431 Agent Capabilities in the Session Initiation Protocol (SIP)", 432 RFC 3840, August 2004. 434 [8] Sparks, R., "Session Initiation Protocol Torture Test Messages", 435 draft-ietf-sipping-torture-tests-09 (work in progress), 436 November 2005. 438 Author's Address 440 Paul H. Kyzivat 441 Cisco Systems, Inc. 442 1414 Massachusetts Avenue 443 Boxborough, MA 01719 444 USA 446 Email: pkyzivat@cisco.com 448 Intellectual Property Statement 450 The IETF takes no position regarding the validity or scope of any 451 Intellectual Property Rights or other rights that might be claimed to 452 pertain to the implementation or use of the technology described in 453 this document or the extent to which any license under such rights 454 might or might not be available; nor does it represent that it has 455 made any independent effort to identify any such rights. Information 456 on the procedures with respect to rights in RFC documents can be 457 found in BCP 78 and BCP 79. 459 Copies of IPR disclosures made to the IETF Secretariat and any 460 assurances of licenses to be made available, or the result of an 461 attempt made to obtain a general license or permission for the use of 462 such proprietary rights by implementers or users of this 463 specification can be obtained from the IETF on-line IPR repository at 464 http://www.ietf.org/ipr. 466 The IETF invites any interested party to bring to its attention any 467 copyrights, patents or patent applications, or other proprietary 468 rights that may cover technology that may be required to implement 469 this standard. Please address the information to the IETF at 470 ietf-ipr@ietf.org. 472 Disclaimer of Validity 474 This document and the information contained herein are provided on an 475 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 476 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 477 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 478 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 479 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 480 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 482 Copyright Statement 484 Copyright (C) The Internet Society (2006). This document is subject 485 to the rights, licenses and restrictions contained in BCP 78, and 486 except as set forth therein, the authors retain all their rights. 488 Acknowledgment 490 Funding for the RFC Editor function is currently provided by the 491 Internet Society.