idnits 2.17.1 draft-camarillo-sipping-uri-list-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by 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 : ---------------------------------------------------------------------------- ** There are 3 instances of too long lines in the document, the longest one being 3 characters in excess of 72. == There are 1 instance of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. 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 the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- 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 6, 2004) is 7377 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) ** Obsolete normative reference: RFC 2822 (ref. '3') (Obsoleted by RFC 5322) == Outdated reference: A later version (-05) exists of draft-ietf-simple-xcap-list-usage-01 == Outdated reference: A later version (-12) exists of draft-ietf-simple-xcap-01 == Outdated reference: A later version (-03) exists of draft-camarillo-sipping-exploders-01 Summary: 3 errors (**), 0 flaws (~~), 7 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 SIPPING Working Group G. Camarillo 3 Internet-Draft Ericsson 4 Expires: August 6, 2004 A. Roach 5 dynamicsoft 6 February 6, 2004 8 Providing a Session Initiation Protocol (SIP) Application Server with 9 a List of URIs 10 draft-camarillo-sipping-uri-list-01.txt 12 Status of this Memo 14 This document is an Internet-Draft and is in full conformance with 15 all provisions of Section 10 of RFC2026. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that other 19 groups may also distribute working documents as Internet-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 http:// 27 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 6, 2004. 34 Copyright Notice 36 Copyright (C) The Internet Society (2004). All Rights Reserved. 38 Abstract 40 This document describes how a user agent can provide an application 41 server with a list of URIs. The way the application server uses the 42 URIs in the list is service specific. 44 Table of Contents 46 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 47 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 48 3. URI Parameter vs. Header Field . . . . . . . . . . . . . . . . 3 49 4. The SIP and SIPS URI List Parameter . . . . . . . . . . . . . 4 50 5. Ad-Hoc List' Life Time . . . . . . . . . . . . . . . . . . . . 4 51 6. The Content-ID SIP Header Field . . . . . . . . . . . . . . . 4 52 7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 53 7.1 Ad-Hoc Conference . . . . . . . . . . . . . . . . . . . . . . 5 54 7.2 Presence List . . . . . . . . . . . . . . . . . . . . . . . . 7 55 8. Security Considerations . . . . . . . . . . . . . . . . . . . 7 56 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 57 Normative References . . . . . . . . . . . . . . . . . . . . . 8 58 Informational References . . . . . . . . . . . . . . . . . . . 8 59 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 9 60 Intellectual Property and Copyright Statements . . . . . . . . 10 62 1. Introduction 64 The need for exploders in SIP is described in [7]. Mechanisms to 65 invoke exploders in SIP need to meet the requirements listed there. 67 UAs need to have a means to provide application servers with a set of 68 URIs for certain services. For example, a UA creating a conference 69 needs to provide the conference server with the participants. The 70 same way, a UA requesting presence information from a set of users 71 needs to provide the resource list server with the URIs of the users 72 that belong to the list. 74 These lists are typically configured using out-of-band methods. For 75 instance, a UA can use XCAP [6] to create a list of URIs and to 76 associate this list with a SIP URI. It can, then, send a SIP request 77 (an INVITE or a SUBSCRIBE in our previous examples) to that SIP URI. 79 Still, there is a need to create lists of URIs in an ad-hoc way and 80 send them directly in a SIP message. We define a SIP and SIPS URI 81 paramerer called "list", which carries a URI. This URI is a pointer 82 to a URI list. 84 A UA creating a SIP request that needs to carry a URI list proceeds 85 this way. It places the URI list (e.g., an XCAP resource list [4]) in 86 a body part, and then, it adds a "list" parameter to the Request-URI. 87 This "list" parameter contains a Content-ID URL [2] that points to 88 the body part that carries the URI list. 90 Alternatively, the URI in the "list" parameter can point to an 91 external URI list (e.g., an http URI). In this case, the URI list 92 would not be carried in the SIP request. 94 The way the application server interprets the URI list received in 95 the request is service specific. 97 2. Terminology 99 In this document, the key words "MUST", "MUST NOT", "REQUIRED", 100 "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT 101 RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted as 102 described in BCP 14, RFC 2119 [1] and indicate requirement levels for 103 compliant implementations. 105 3. URI Parameter vs. Header Field 107 We have chosen to transport the pointer to the URI list in a URI 108 parameter rather than in a header field because, this way, the 109 Request-URI fully indentifies the service being invoked and all the 110 recipients of the service. Using a header field instead would imply 111 that the Request-URI did not carry the list of the reciptiens. 113 Network administrators should note that they need to configure 114 proxies to route correctly Request-URIs that contain a "list" 115 parameter and are addressed to their domain. 117 4. The SIP and SIPS URI List Parameter 119 We define the "list" parameter for SIP and SIPS URIs. It MUST contain 120 a URI that points to a URI list. The XCAP resource list format [4] 121 MUST be supported; any other URI list formats MAY be supported. The 122 ABNF of the "list" parameter is: 124 list-param = "list=" absoluteURI 126 The following is an example of a SIP URI with a list parameter 127 pointing to a body part using a Content-ID URL [2]: 129 sip:group@example.com;list=cid:cn35t8jf02@example.com 131 The following is an example of a SIP URI with a list parameter 132 pointing to an external URI: 134 sip:group@example.com;list=http://xcap.example.com/lists/mylist.xml 136 5. Ad-Hoc List' Life Time 138 An application server that receives a request with a URI list (or a 139 pointer to it) creates a so called ad-hoc list, whose lifetime 140 depends on the service provided by the server. 142 Ad-Hoc lists created by requests that do not establish a dialog 143 usually expire immediately. Ad-Hoc lists created by requests that 144 establish a dialog usually expire when the dialog terminates. 146 6. The Content-ID SIP Header Field 148 The Content-ID MIME header field is defined in RFC 2045 [5]. We 149 define here the same header field to be used in SIP messages. Its 150 ABNF is: 152 Content-ID = "Content-ID" HCOLON msg-id 154 RFC 2822 [3] defines msg-id in Section 3.6.4. 156 The Content-ID value is used to uniquely identify a body or a body 157 part. The Content-ID header field MAY appear in any SIP request or 158 response that contains a body. 160 7. Examples 162 This section shows how to use the list parameter to create an ad-hoc 163 conference and to subscribe to the presence information to a set of 164 users. These examples illustrate the usage of the "list" parameter. 165 They do not mandate how the previously mentioned services have to be 166 implemented. 168 7.1 Ad-Hoc Conference 170 Carol creates an ad-hoc conference by sending the INVITE request 171 shown in Figure 1. The list parameter in the Request-URI points to a 172 MIME body that carries the list of participants. 174 INVITE sip:ad-hoc@example.com;list=cid:cn35t8jf02@example.com SIP/2.0 175 Via: SIP/2.0/TCP client.chicago.example.com 176 ;branch=z9hG4bKhjhs8ass83 177 Max-Forwards: 70 178 To: "Ad-Hoc Conferences" 179 From: Carol ;tag=32331 180 Call-ID: d432fa84b4c76e66710 181 CSeq: 1 INVITE 182 Contact: 183 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, 184 SUBSCRIBE, NOTIFY 185 Allow-Events: dialog 186 Accept: application/sdp, message/sipfrag, 187 application/resource-lists+xml 188 Conten-Type: multipart/mixed;boundary="boundary1" 189 Content-Length: 731 191 --boundary1 192 Content-Type: application/sdp 193 Content-Length: 160 195 v=0 196 o=carol 2890844526 2890842807 IN IP4 chicago.example.com 197 s=Example Subject 198 c=IN IP4 192.0.0.1 199 t=0 0 200 m=audio 20000 RTP/AVP 0 201 m=video 20002 RTP/AVP 31 203 --boundary1 204 Content-Type: application/resource-lists+xml 205 Content-Length: 367 206 Content-ID: 208 209 210 211 212 213 214 215 216 217 --boundary1-- 219 Figure 1: INVITE request 221 SIP/2.0 200 OK 222 Via: SIP/2.0/TCP client.chicago.example.com 223 ;branch=z9hG4bKhjhs8ass83;received=192.0.2.4 224 To: "Ad-Hoc Conferences" ;tag=733413 225 From: Carol ;tag=32331 226 Call-ID: d432fa84b4c76e66710 227 CSeq: 1 INVITE 228 Contact: ;isfocus 229 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, 230 SUBSCRIBE, NOTIFY 231 Allow-Events: dialog, conference 232 Accept: application/sdp, application/conference-info+xml, 233 application/resource-lists+xml, message/sipfrag 234 Supported: replaces, join 235 Content-Type: application/sdp 236 Content-Length: 312 238 v=0 239 o=focus431 2890844526 2890842807 IN IP4 ms5.conf.example.com 240 s=Example Subject 241 i=Example Conference Hosted by Example.com 242 u=http://conf.example.com/3402934234 243 e=3402934234@conf-help.example.com 244 p=+1-888-555-1212 245 c=IN IP4 ms5.conf.example.com 246 t=0 0 247 m=audio 49170 RTP/AVP 0 248 m=video 51372 RTP/AVP 31 250 Figure 2: 200 (OK) response 252 The conference server responds with a 200 (OK) that carries the URI 253 for the conference in its Contact header field. If the UA wants to 254 obtain information about the status of the conference, for instance, 255 it will SUBSCRIBE to the conference package using this URI. 257 7.2 Presence List 259 Carol subscribes to the presence information of four of her friends 260 using the list parameter. 262 SUBSCRIBE sip:ad-hoc@example.com;list=cid:cn35t8jf02@example.com SIP/2.0 263 Via: SIP/2.0/TCP client.chicago.example.com 264 ;branch=z9hG4bKhjhs8ass83 265 Max-Forwards: 70 266 To: "Ad-Hoc Presence List" 267 From: Carol ;tag=32331 268 Call-ID: d432fa84b4c76e66710 269 CSeq: 1 INVITE 270 Contact: 271 Require: eventlist 272 Event: presence 273 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, 274 SUBSCRIBE, NOTIFY 275 Allow-Events: presence 276 Accept: application/sdp, message/sipfrag, 277 application/resource-lists+xml, application/rlmi+xml 278 Content-Type: application/resource-lists+xml 279 Content-Length: 367 280 Content-ID: 282 283 284 285 286 287 288 289 290 292 Figure 3: SUBSCRIBE request 294 8. Security Considerations 296 TBD. 298 9. IANA Considerations 300 This document registers the "list" SIP and SIPS URI parameter, which 301 is described in Section 4. This parameter is to be added to the SIP 302 and SIPS URI parameter registry under http://www.iana.org/ TBD. 304 This document registers the Content-ID SIP header field, which is 305 described in Section 6. This header field is to be added to the 306 header field registry under http://www.iana.org/assignments/ 307 sip-parameters. 309 Header Name: Content-ID 311 Compact Form: (none) 313 Normative References 315 [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement 316 Levels", BCP 14, RFC 2119, March 1997. 318 [2] Levinson, E., "Content-ID and Message-ID Uniform Resource 319 Locators", RFC 2392, August 1998. 321 [3] Resnick, P., "Internet Message Format", RFC 2822, April 2001. 323 [4] Rosenberg, J., "An Extensible Markup Language (XML) 324 Configuration Access Protocol (XCAP) Usage for Presence Lists", 325 draft-ietf-simple-xcap-list-usage-01 (work in progress), October 326 2003. 328 Informational References 330 [5] Freed, N. and N. Borenstein, "Multipurpose Internet Mail 331 Extensions (MIME) Part One: Format of Internet Message Bodies", 332 RFC 2045, November 1996. 334 [6] Rosenberg, J., "The Extensible Markup Language (XML) 335 Configuration Access Protocol (XCAP)", draft-ietf-simple-xcap-01 336 (work in progress), October 2003. 338 [7] Camarillo, G., "Requirements for Session Initiation Protocol 339 (SIP) Exploder Invocation", draft-camarillo-sipping-exploders-01 340 (work in progress), November 2003. 342 Authors' Addresses 344 Gonzalo Camarillo 345 Ericsson 346 Hirsalantie 11 347 Jorvas 02420 348 Finland 350 EMail: Gonzalo.Camarillo@ericsson.com 352 Adam Roach 353 dynamicsoft 354 5100 Tennyson Pkwy 355 Suite 1200 356 Plano, TX 75024 357 US 359 EMail: adam@dynamicsoft.com 361 Intellectual Property Statement 363 The IETF takes no position regarding the validity or scope of any 364 intellectual property or other rights that might be claimed to 365 pertain to the implementation or use of the technology described in 366 this document or the extent to which any license under such rights 367 might or might not be available; neither does it represent that it 368 has made any effort to identify any such rights. Information on the 369 IETF's procedures with respect to rights in standards-track and 370 standards-related documentation can be found in BCP-11. Copies of 371 claims of rights made available for publication and any assurances of 372 licenses to be made available, or the result of an attempt made to 373 obtain a general license or permission for the use of such 374 proprietary rights by implementors or users of this specification can 375 be obtained from the IETF Secretariat. 377 The IETF invites any interested party to bring to its attention any 378 copyrights, patents or patent applications, or other proprietary 379 rights which may cover technology that may be required to practice 380 this standard. Please address the information to the IETF Executive 381 Director. 383 Full Copyright Statement 385 Copyright (C) The Internet Society (2004). All Rights Reserved. 387 This document and translations of it may be copied and furnished to 388 others, and derivative works that comment on or otherwise explain it 389 or assist in its implementation may be prepared, copied, published 390 and distributed, in whole or in part, without restriction of any 391 kind, provided that the above copyright notice and this paragraph are 392 included on all such copies and derivative works. However, this 393 document itself may not be modified in any way, such as by removing 394 the copyright notice or references to the Internet Society or other 395 Internet organizations, except as needed for the purpose of 396 developing Internet standards in which case the procedures for 397 copyrights defined in the Internet Standards process must be 398 followed, or as required to translate it into languages other than 399 English. 401 The limited permissions granted above are perpetual and will not be 402 revoked by the Internet Society or its successors or assignees. 404 This document and the information contained herein is provided on an 405 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 406 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 407 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 408 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 409 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 411 Acknowledgment 413 Funding for the RFC Editor function is currently provided by the 414 Internet Society.