idnits 2.17.1 draft-ietf-sipping-gruu-reg-event-03.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 14. -- Found old boilerplate from RFC 3978, Section 5.5 on line 479. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 456. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 463. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 469. ** 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 (February 23, 2006) is 6637 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 419, but no explicit reference was found in the text == Unused Reference: '7' is defined on line 429, 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: August 27, 2006 February 23, 2006 6 Reg Event Package Extension for GRUUs 7 draft-ietf-sipping-gruu-reg-event-03 9 Status of this Memo 11 By submitting this Internet-Draft, each author represents that any 12 applicable patent or other IPR claims of which he or she is aware 13 have been or will be disclosed, and any of which he or she becomes 14 aware will be disclosed, in accordance with Section 6 of BCP 79. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt. 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 This Internet-Draft will expire on August 27, 2006. 34 Copyright Notice 36 Copyright (C) The Internet Society (2006). 38 Abstract 40 This draft defines an extension to RFC 3680 [2] for representing the 41 GRUU associated with a Contact. 43 Table of Contents 45 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 46 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 47 3. Description . . . . . . . . . . . . . . . . . . . . . . . . . 3 48 4. Notifier Processing of SUBSCRIBE Requests . . . . . . . . . . 4 49 5. Notifier Generation of NOTIFY Requests . . . . . . . . . . . . 4 50 6. Subscriber Processing of NOTIFY Requests . . . . . . . . . . . 4 51 7. Sample reginfo Document . . . . . . . . . . . . . . . . . . . 4 52 8. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 53 8.1. Example: Welcome Notice . . . . . . . . . . . . . . . . . 5 54 8.2. Example: Implicit Registration . . . . . . . . . . . . . . 6 55 9. XML Schema Definition . . . . . . . . . . . . . . . . . . . . 8 56 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 57 10.1. URN Sub-Namespace Registration . . . . . . . . . . . . . . 9 58 10.2. XML Schema Registration . . . . . . . . . . . . . . . . . 10 59 11. Security Considerations . . . . . . . . . . . . . . . . . . . 10 60 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10 61 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10 62 13.1. Normative References . . . . . . . . . . . . . . . . . . . 10 63 13.2. Informative References . . . . . . . . . . . . . . . . . . 10 64 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 12 65 Intellectual Property and Copyright Statements . . . . . . . . . . 13 67 1. Introduction 69 The addition of GRUU (Globally Routable Unique URI) support to the 70 REGISTER message, defined in [3], introduces another element of state 71 to the registrar. Subscribers to the registration event package [2] 72 will sometimes have need for the new state. 74 For example, the Welcome Notices example in [2] will only operate 75 correctly if the contact address in the reg event notification is 76 reachable by the sender of the welcome notice. When the registering 77 device is using the gruu extension, it is likely that the registered 78 contact address will not be globally addressable, and the gruu should 79 be used as the target address for the MESSAGE. 81 Another case where this feature may be helpful is within the 3GPP IP 82 Multimedia Subsystem (IMS). IMS employs a technique where a REGISTER 83 of a contact address to one Address of Record (AOR) causes the 84 implicit registration of the same contact to other associated AORs. 85 If a GRUU is requested and obtained as part of the registration 86 request, then additional GRUUs will also be needed for the implicit 87 registrations. While assigning the additional GRUUs is 88 straightforward, informing the registering UA of them is not. In 89 IMS, UAs typically subscribe to the 'reg' event, and subscriptions to 90 the 'reg' event for an AOR result in notifications containing 91 registration state for all the associated AORs. The proposed 92 extension provides a way to easily deliver the GRUUs for the 93 associated AORs. 95 The reg event package has provision for including extension elements 96 within the element. This document defines a new element 97 that may be used in that context to deliver the GRUU corresponding to 98 the contact. 100 2. Terminology 102 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 103 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 104 document are to be interpreted as described in RFC 2119 [1]. 106 3. Description 108 A new element () is defined which contains a GRUU. 110 This optional element is included within the body of a NOTIFY for the 111 "reg" event package when a GRUU is associated with the contact. The 112 contact URI and the GRUU are then both available to the watcher. 114 4. Notifier Processing of SUBSCRIBE Requests 116 Unchanged from RFC 3680 [2]. 118 5. Notifier Generation of NOTIFY Requests 120 A notifier for the "reg" event package [2] SHOULD include the 121 element when a contact has an Instance ID and a GRUU is associated 122 with the combination of the AOR and the Instance ID. When present, 123 the element MUST be be positioned as an instance of the 124 element within the element. 126 6. Subscriber Processing of NOTIFY Requests 128 When a subscriber receives a "reg" event notification [2] with a 129 containing a , it SHOULD use the gruu in preference 130 to the corresponding when sending SIP requests to the contact. 132 Subscribers that are unaware of this extension will, as required by 133 [2], ignore the element. 135 7. Sample reginfo Document 137 The following is an example registration information document 138 including the new element: 140 141 144 146 149 sip:user@192.0.2.1 150 151 152 "<urn:uuid:f81d4fae-7dec-11d0-a765- 153 00a0c91e6bf6>" 154 155 156 157 sip:user@example.com 158 ;opaque=hha9s8d-999a 159 160 161 162 164 8. Examples 166 Note: In the following examples the SIP messages have been 167 simplified, removing headers that are not pertinent to the example. 168 The conventions of [8] are used to describe representation of long 169 message lines. 171 8.1. Example: Welcome Notice 173 Consider the Welcome Notices example in [2]. When the application 174 server receives a notification of a new registration containing the 175 reginfo shown in Section 7 it should address messages using the 176 contained GRUU as follows: 178 MESSAGE sip:user@example.com;opaque=hha9s8d-999a SIP/2.0 179 To: 180 From: "SIPland Notifier" 181 Content-Type: text/plain 182 Content-Length: ... 184 Welcome to SIPland! 185 Blah, blah, blah. 187 8.2. Example: Implicit Registration 189 In an 3GPP IMS setting, a UA may send a single register message, 190 requesting assignment of a gruu, as follows: 192 REGISTER sip:example.net SIP/2.0 193 From: ;tag=5ab4 194 To: 195 Contact: 196 ;expires=3600 197 ;+sip.instance="" 198 Supported: path, gruu 199 Content-Length: 0 201 The response reports success of the registration and returns the GRUU 202 assigned for the combination of AOR, Instance ID, and Contact. It 203 also indicates (via the P-Associated-URI header [6]) that there are 204 two other associated AORs that may have been implicitly registered 205 using the same contact. But each of those implicitly registered AORs 206 will have had a unique GRUU assigned, and there is no way defined to 207 report that assignment in the response. 209 SIP/2.0 200 OK 210 From: ;tag=5ab4 211 To: ;tag=373392 212 Path: 213 Service-Route: 214 Contact: 215 ;expires=3600 216 ;+sip.instance="" 217 ;gruu="sip:user_aor_1@example.net;opaque=hha9s8d-999a" 218 P-Associated-URI: , 219 220 Content-Length: 0 222 The UA then subscribes to the 'reg' event package as follows: 224 SUBSCRIBE sip:user_aor_1@example.net SIP/2.0 225 From: ;tag=27182 226 To: 227 Route: 228 Event: reg 229 Expires: 3600 230 Accept: application/reginfo+xml 231 Contact: 232 Content-Length: 0 234 (The successful response to the subscription is not shown.) Once the 235 subscription is established an initial notification is sent giving 236 registration status. In IMS deployments the response includes, in 237 addition to the status for the requested URI, the status for the 238 other associated URIs. 240 NOTIFY sip:user_aor_1@example.net;opaque=hha9s8d-999a SIP/2.0 241 From: ;tag=27182 242 To: ;tag=262281 243 Subscription-State: active;expires=3600 244 Event: reg 245 Content-Type: application/reginfo+xml 246 Contact: 247 Content-Length: (...) 249 250 253 255 257 258 sip:ua.example.com 259 260 261 262 "<urn:uuid:f81d4fae-7dec-11d0-a765- 263 00a0c91e6bf6>" 264 265 266 267 sip:user_aor_1@example.net 268 ;opaque=hha9s8d-999a 269 270 271 272 274 276 277 sip:ua.example.com 278 279 280 281 "<urn:uuid:f81d4fae-7dec-11d0- 282 a765-00a0c91e6bf6>" 283 284 285 286 sip:user_aor_2@example.net 287 ;opaque=hha9s8d-999b 288 289 290 291 295 297 298 sip:ua.example.com 299 300 301 302 "<urn:uuid:f81d4fae-7dec-11d0-a765- 303 00a0c91e6bf6>" 304 305 306 307 sip:+358504821437@example.net;user=phone 308 ;opaque=hha9s8d-999c 309 310 311 312 314 The status indicates that the associated URIs all have the same 315 contact registered. It also includes the unique GRUU that has been 316 assigned to each. The UA may then retain those GRUUs for use when 317 establishing dialogs using the corresponding AORs. 319 9. XML Schema Definition 321 A gruu document is an XML document that MUST be well-formed and 322 SHOULD be valid. Gruu documents MUST be based on XML 1.0 and MUST be 323 encoded using UTF-8. This specification makes use of XML namespaces 324 for identifying gruu documents. The namespace URI for elements 325 defined for this purpose is a URN, using the namespace identifier 326 'ietf'. This URN is: 327 urn:ietf:params:xml:ns:gruuinfo 329 BEGIN 330 331 336 337 338 END 340 10. IANA Considerations 342 There are two IANA considerations associated with this specification. 344 10.1. URN Sub-Namespace Registration 346 This section registers a new XML namespace, per the guidelines in 347 [4]. 349 URI: The URI for this namespace is urn:ietf:params:xml:ns:gruuinfo 351 Registrant Contact: IETF, SIPPING working group, , 352 Paul Kyzivat 354 XML: 356 BEGIN 357 358 360 361 362 364 Reg Information GRUU Extension Namespace 365 366 367

Namespace for Reg Information GRUU Extension

368

urn:ietf:params:xml:ns:gruuinfo

369

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

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