draft-ietf-sipping-uri-list-conferencing-03.txt   draft-ietf-sipping-uri-list-conferencing-04.txt 
SIPPING Working Group G. Camarillo SIPPING Working Group G. Camarillo
Internet-Draft Ericsson Internet-Draft Ericsson
Expires: October 10, 2004 A. Johnston Expires: April 24, 2006 A. Johnston
MCI MCI
April 8, 2004 October 21, 2005
Conference Establishment Using Request-Contained Lists in the Session Conference Establishment Using Request-Contained Lists in the Session
Initiation Protocol (SIP) Initiation Protocol (SIP)
draft-ietf-sipping-uri-list-conferencing-03.txt draft-ietf-sipping-uri-list-conferencing-04.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 36 skipping to change at page 1, line 36
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on October 10, 2004. This Internet-Draft will expire on April 24, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). Copyright (C) The Internet Society (2005).
Abstract Abstract
This document describes how to create a conference using SIP URI-list This document describes how to create a conference using SIP URI-list
services. In particular, it describes a mechanism that allows a services. In particular, it describes a mechanism that allows a
client to provide a conference server with the initial list of client to provide a conference server with the initial list of
participants using an INVITE-contained URI-list. participants using an INVITE-contained URI-list.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Providing a Conference Server with a URI-List . . . . . . . 3 3. Providing a Conference Server with a URI-List . . . . . . . . 3
4. URI-List Format . . . . . . . . . . . . . . . . . . . . . . 3 4. URI-List Format . . . . . . . . . . . . . . . . . . . . . . . 3
5. Conference Server Behavior . . . . . . . . . . . . . . . . . 4 5. Conference Server Behavior . . . . . . . . . . . . . . . . . . 4
6. Re-INVITEs . . . . . . . . . . . . . . . . . . . . . . . . . 5 6. Re-INVITEs . . . . . . . . . . . . . . . . . . . . . . . . . . 5
7. Option-tag . . . . . . . . . . . . . . . . . . . . . . . . . 5 7. Option-tag . . . . . . . . . . . . . . . . . . . . . . . . . . 5
8. Example . . . . . . . . . . . . . . . . . . . . . . . . . . 6 8. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
9. Security Considerations . . . . . . . . . . . . . . . . . . 8 9. Security Considerations . . . . . . . . . . . . . . . . . . . 8
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . 8 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
11. Acknowledges . . . . . . . . . . . . . . . . . . . . . . . . 8 11. Acknowledges . . . . . . . . . . . . . . . . . . . . . . . . . 8
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
12.1 Normative References . . . . . . . . . . . . . . . . . . 8 12.1. Normative References . . . . . . . . . . . . . . . . . . 9
12.2 Informational References . . . . . . . . . . . . . . . . 9 12.2. Informational References . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 9 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10
Intellectual Property and Copyright Statements . . . . . . . 10 Intellectual Property and Copyright Statements . . . . . . . . . . 11
1. Introduction 1. Introduction
Section 4.5 of [3] describes how to create a conference using ad-hoc Section 4.5 of [3] describes how to create a conference using ad-hoc
SIP [2] methods. The client sends an INVITE request to a conference SIP [2] methods. The client sends an INVITE request to a conference
factory URI and receives the actual conference URI, which contains factory URI and receives the actual conference URI, which contains
the "isfocus" feature tag, in the Contact header field of a response the "isfocus" feature tag, in the Contact header field of a response
(typically a 200 OK). (typically a 200 OK).
Once the client obtains the conference URI, it can add participants Once the client obtains the conference URI, it can add participants
skipping to change at page 8, line 48 skipping to change at page 9, line 5
This option-tag is used to ensure that a server can process the This option-tag is used to ensure that a server can process the
'recipient-list' body used in an INVITE request. 'recipient-list' body used in an INVITE request.
11. Acknowledges 11. Acknowledges
Cullen Jennings, Hisham Khartabil, and Jonathan Rosenberg provided Cullen Jennings, Hisham Khartabil, and Jonathan Rosenberg provided
useful comments on this document. useful comments on this document.
12. References 12. References
12.1 Normative References 12.1. Normative References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
[2] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., [2] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A.,
Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP: Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP:
Session Initiation Protocol", RFC 3261, June 2002. Session Initiation Protocol", RFC 3261, June 2002.
[3] Johnston, A. and O. Levin, "Session Initiation Protocol Call [3] Johnston, A. and O. Levin, "Session Initiation Protocol Call
Control - Conferencing for User Agents", Control - Conferencing for User Agents",
draft-ietf-sipping-cc-conferencing-06 (work in progress), draft-ietf-sipping-cc-conferencing-07 (work in progress),
November 2004. June 2005.
[4] Camarillo, G. and A. Roach, "Requirements and Framework for [4] Camarillo, G. and A. Roach, "Requirements and Framework for
Session Initiation Protocol (SIP)Uniform Resource Identifier Session Initiation Protocol (SIP)Uniform Resource Identifier
(URI)-List Services", draft-ietf-sipping-uri-services-02 (work (URI)-List Services", draft-ietf-sipping-uri-services-03 (work
in progress), December 2004. in progress), April 2005.
[5] Rosenberg, J., "Extensible Markup Language (XML) Formats for [5] Rosenberg, J., "Extensible Markup Language (XML) Formats for
Representing Resource Lists", Representing Resource Lists",
draft-ietf-simple-xcap-list-usage-05 (work in progress), draft-ietf-simple-xcap-list-usage-05 (work in progress),
February 2005. February 2005.
12.2 Informational References 12.2. Informational References
[6] Rosenberg, J., "A Session Initiation Protocol (SIP) Event [6] Rosenberg, J., "A Session Initiation Protocol (SIP) Event
Package for Conference State", Package for Conference State",
draft-ietf-sipping-conference-package-10 (work in progress), draft-ietf-sipping-conference-package-12 (work in progress),
March 2005. July 2005.
Authors' Addresses Authors' Addresses
Gonzalo Camarillo Gonzalo Camarillo
Ericsson Ericsson
Hirsalantie 11 Hirsalantie 11
Jorvas 02420 Jorvas 02420
Finland Finland
Email: Gonzalo.Camarillo@ericsson.com Email: Gonzalo.Camarillo@ericsson.com
skipping to change at page 10, line 41 skipping to change at page 11, line 41
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject Copyright (C) The Internet Society (2005). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 12 change blocks. 
30 lines changed or deleted 30 lines changed or added

This html diff was produced by rfcdiff 1.27, available from http://www.levkowetz.com/ietf/tools/rfcdiff/