draft-ietf-sipping-cc-framework-05.txt   draft-ietf-sipping-cc-framework-06.txt 
SIPPING WG R. Mahy SIPPING WG R. Mahy
Internet-Draft SIP Edge LLC Internet-Draft Plantronics
Expires: April 4, 2006 B. Campbell Expires: September 6, 2006 B. Campbell
R. Sparks R. Sparks
Estacado Systems Estacado Systems
J. Rosenberg J. Rosenberg
Cisco Systems Cisco Systems
D. Petrie D. Petrie
SIP EZ SIP EZ
A. Johnston A. Johnston
MCI MCI
Oct 2005 March 5, 2006
A Call Control and Multi-party usage framework for the Session A Call Control and Multi-party usage framework for the Session
Initiation Protocol (SIP) Initiation Protocol (SIP)
draft-ietf-sipping-cc-framework-05.txt draft-ietf-sipping-cc-framework-06.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 43 skipping to change at page 1, line 43
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 April 4, 2006. This Internet-Draft will expire on September 6, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2006).
Abstract Abstract
This document defines a framework and requirements for multi-party This document defines a framework and requirements for multi-party
usage of SIP. To enable discussion of multi-party features and usage of SIP. To enable discussion of multi-party features and
applications we define an abstract call model for describing the applications we define an abstract call model for describing the
media relationships required by many of these. The model and actions media relationships required by many of these. The model and actions
described here are specifically chosen to be independent of the SIP described here are specifically chosen to be independent of the SIP
signaling and/or mixing approach chosen to actually setup the media signaling and/or mixing approach chosen to actually setup the media
relationships. In addition to its dialog manipulation aspect, this relationships. In addition to its dialog manipulation aspect, this
framework includes requirements for communicating related information framework includes requirements for communicating related information
skipping to change at page 38, line 11 skipping to change at page 38, line 11
[3] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model with [3] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model with
Session Description Protocol (SDP)", RFC 3264, June 2002. Session Description Protocol (SDP)", RFC 3264, June 2002.
[4] Roach, A., "Session Initiation Protocol (SIP)-Specific Event [4] Roach, A., "Session Initiation Protocol (SIP)-Specific Event
Notification", RFC 3265, June 2002. Notification", RFC 3265, June 2002.
[5] Handley, M. and V. Jacobson, "SDP: Session Description [5] Handley, M. and V. Jacobson, "SDP: Session Description
Protocol", RFC 2327, April 1998. Protocol", RFC 2327, April 1998.
[6] Johnston, A., "Session Initiation Protocol Service Examples", [6] "Session Initiation Protocol Service Examples",
draft-ietf-sipping-service-examples-09 (work in progress), draft-ietf-sipping-service-examples-09 (work in progress),
July 2005. July 2005.
[7] Rosenberg, J., Peterson, J., Schulzrinne, H., and G. Camarillo, [7] Rosenberg, J., Peterson, J., Schulzrinne, H., and G. Camarillo,
"Best Current Practices for Third Party Call Control (3pcc) in "Best Current Practices for Third Party Call Control (3pcc) in
the Session Initiation Protocol (SIP)", BCP 85, RFC 3725, the Session Initiation Protocol (SIP)", BCP 85, RFC 3725,
April 2004. April 2004.
[8] Sparks, R., "The Session Initiation Protocol (SIP) Refer [8] Sparks, R., "The Session Initiation Protocol (SIP) Refer
Method", RFC 3515, April 2003. Method", RFC 3515, April 2003.
[9] Mahy, R., Biggs, B., and R. Dean, "The Session Initiation [9] Mahy, R., Biggs, B., and R. Dean, "The Session Initiation
Protocol (SIP) "Replaces" Header", RFC 3891, September 2004. Protocol (SIP) "Replaces" Header", RFC 3891, September 2004.
[10] Mahy, R. and D. Petrie, "The Session Initiation Protocol (SIP) [10] Mahy, R. and D. Petrie, "The Session Initiation Protocol (SIP)
"Join" Header", RFC 3911, October 2004. "Join" Header", RFC 3911, October 2004.
[11] Rosenberg, J., "An INVITE Inititiated Dialog Event Package for [11] Rosenberg, J., Schulzrinne, H., and R. Mahy, "An INVITE-
the Session Initiation Protocol (SIP)", Initiated Dialog Event Package for the Session Initiation
draft-ietf-sipping-dialog-package-06 (work in progress), Protocol (SIP)", RFC 4235, November 2005.
April 2005.
[12] Rosenberg, J., "A Session Initiation Protocol (SIP) Event [12] Rosenberg, J., "A Session Initiation Protocol (SIP) Event
Package for Conference State", Package for Conference State",
draft-ietf-sipping-conference-package-12 (work in progress), draft-ietf-sipping-conference-package-12 (work in progress),
July 2005. July 2005.
[13] Rosenberg, J., "A Session Initiation Protocol (SIP) Event [13] Rosenberg, J., "A Session Initiation Protocol (SIP) Event
Package for Registrations", RFC 3680, March 2004. Package for Registrations", RFC 3680, March 2004.
[14] Rosenberg, J., "A Presence Event Package for the Session [14] Rosenberg, J., "A Presence Event Package for the Session
skipping to change at page 39, line 8 skipping to change at page 39, line 7
draft-ietf-sipping-conferencing-framework-05 (work in draft-ietf-sipping-conferencing-framework-05 (work in
progress), May 2005. progress), May 2005.
[16] Rosenberg, J., "A Framework for Application Interaction in the [16] Rosenberg, J., "A Framework for Application Interaction in the
Session Initiation Protocol (SIP)", Session Initiation Protocol (SIP)",
draft-ietf-sipping-app-interaction-framework-05 (work in draft-ietf-sipping-app-interaction-framework-05 (work in
progress), July 2005. progress), July 2005.
[17] Camarillo, G., "Framework for Transcoding with the Session [17] Camarillo, G., "Framework for Transcoding with the Session
Initiation Protocol (SIP)", Initiation Protocol (SIP)",
draft-ietf-sipping-transc-framework-02 (work in progress), draft-ietf-sipping-transc-framework-03 (work in progress),
June 2005. November 2005.
[18] Sparks, R., "Session Initiation Protocol Call Control - [18] Sparks, R., "Session Initiation Protocol Call Control -
Transfer", draft-ietf-sipping-cc-transfer-05 (work in Transfer", draft-ietf-sipping-cc-transfer-05 (work in
progress), July 2005. progress), July 2005.
[19] Johnston, A. and O. Levin, "Session Initiation Protocol Call [19] Levin, O., "Session Initiation Protocol Call Control -
Control - Conferencing for User Agents", Conferencing for User Agents",
draft-ietf-sipping-cc-conferencing-07 (work in progress), draft-ietf-sipping-cc-conferencing-07 (work in progress),
June 2005. June 2005.
[20] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, "Indicating [20] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, "Indicating
User Agent Capabilities in the Session Initiation Protocol User Agent Capabilities in the Session Initiation Protocol
(SIP)", RFC 3840, August 2004. (SIP)", RFC 3840, August 2004.
[21] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, "Caller [21] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, "Caller
Preferences for the Session Initiation Protocol (SIP)", Preferences for the Session Initiation Protocol (SIP)",
RFC 3841, August 2004. RFC 3841, August 2004.
8.2 Informational References 8.2 Informational References
[22] Campbell, B. and R. Sparks, "Control of Service Context using [22] Campbell, B. and R. Sparks, "Control of Service Context using
SIP Request-URI", RFC 3087, April 2001. SIP Request-URI", RFC 3087, April 2001.
[23] Mahy, R., "Remote Call Control in SIP using the REFER method [23] Jennings, C. and R. Mahy, "Remote Call Control in SIP using the
and the session-oriented dialog package", REFER method and the session-oriented dialog package",
draft-mahy-sip-remote-cc-01 (work in progress), February 2004. draft-mahy-sip-remote-cc-02 (work in progress), October 2005.
[24] Burger, E., "Basic Network Media Services with SIP", [24] Burger, E., "Basic Network Media Services with SIP",
draft-burger-sipping-netann-11 (work in progress), draft-burger-sipping-netann-11 (work in progress),
February 2005. February 2005.
Authors' Addresses Authors' Addresses
Rohan Mahy Rohan Mahy
SIP Edge LLC Plantronics
345 Encincal Street
Santa Cruz, CA
USA
Email: rohan@ekabal.com Email: rohan@ekabal.com
Ben Campbell Ben Campbell
Estacado Systems Estacado Systems
Email: ben@nostrum.com Email: ben@nostrum.com
Robert Sparks Robert Sparks
Estacado Systems Estacado Systems
skipping to change at page 41, line 41 skipping to change at page 41, 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 (2005). This document is subject Copyright (C) The Internet Society (2006). 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. 
20 lines changed or deleted 22 lines changed or added

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