< draft-rosenberg-sip-info-litmus-01.txt   draft-rosenberg-sip-info-litmus-02.txt >
SIP J. Rosenberg SIP J. Rosenberg
Internet-Draft Cisco Internet-Draft Cisco
Intended status: Informational July 14, 2008 Intended status: Informational November 3, 2008
Expires: January 15, 2009 Expires: May 7, 2009
Litmus Tests for Usage of the Session Initiation Protocol (SIP) INFO Litmus Tests for Usage of the Session Initiation Protocol (SIP) INFO
Method Method
draft-rosenberg-sip-info-litmus-01 draft-rosenberg-sip-info-litmus-02
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 35 skipping to change at page 1, line 35
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 January 15, 2009. This Internet-Draft will expire on May 7, 2009.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
Abstract Abstract
The Session Initiation Protocol (SIP) Working Group is considering The Session Initiation Protocol (SIP) Working Group is considering
the standardization of a framework for conveying application data the standardization of a framework for conveying application data
through the INFO method. However, the INFO method is just one of through the INFO method. However, the INFO method is just one of
skipping to change at page 3, line 47 skipping to change at page 3, line 47
interaction, and is described in interaction, and is described in
[I-D.ietf-sipping-app-interaction-framework]. [I-D.ietf-sipping-app-interaction-framework].
Media: A user agent can use SIP to set up another media session Media: A user agent can use SIP to set up another media session
whose purpose is to carry the application specific data. This can whose purpose is to carry the application specific data. This can
be done using the TOTE protocol proposed in be done using the TOTE protocol proposed in
[I-D.rosenberg-sip-tote]. [I-D.rosenberg-sip-tote].
INFO Framework: A user agent can send the data in a SIP INFO message INFO Framework: A user agent can send the data in a SIP INFO message
along the existing SIP dialog. This technique is described in along the existing SIP dialog. This technique is described in
[I-D.kaplan-sip-info-events]. [I-D.ietf-sip-info-events].
Each of these mechanisms are different in important ways. The events Each of these mechanisms are different in important ways. The events
framework and the INFO framework utilize the signaling plane, while framework and the INFO framework utilize the signaling plane, while
TOTE utilizes the media plane. The INFO framework always follows the TOTE utilizes the media plane. The INFO framework always follows the
path of an INVITE dialog, while the events framework allows arbitrary path of an INVITE dialog, while the events framework allows arbitrary
connections and can be independent of any dialog. These differences connections and can be independent of any dialog. These differences
result in differing scopes of applicability. As a consequence, there result in differing scopes of applicability. As a consequence, there
cannot be just ONE solution for application signaling. All three are cannot be just ONE solution for application signaling. All three are
needed and serve different purposes. needed and serve different purposes.
skipping to change at page 7, line 24 skipping to change at page 7, line 24
June 2002. June 2002.
[I-D.ietf-sipping-app-interaction-framework] [I-D.ietf-sipping-app-interaction-framework]
Rosenberg, J., "A Framework for Application Interaction in Rosenberg, J., "A Framework for Application Interaction in
the Session Initiation Protocol (SIP)", the 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.
[I-D.rosenberg-sip-tote] [I-D.rosenberg-sip-tote]
Rosenberg, J., "Session Based Trivial Object Transfer and Rosenberg, J., "Session Based Trivial Object Transfer and
Exchange (TOTE)", draft-rosenberg-sip-tote-00 (work in Exchange (TOTE)", draft-rosenberg-sip-tote-01 (work in
progress), February 2008. progress), July 2008.
[I-D.kaplan-sip-info-events] [I-D.ietf-sip-info-events]
Kaplan, H. and C. Holmberg, "The SIP INFO Method and Info Burger, E., Kaplan, H., and C. Holmberg, "Session
Package Framework", draft-kaplan-sip-info-events-01 (work Initiation Protocol (SIP) INFO Method and Package
in progress), February 2008. Framework", draft-ietf-sip-info-events-00 (work in
progress), October 2008.
[I-D.kaplan-sip-info-use-cases] [I-D.kaplan-sip-info-use-cases]
Kaplan, H., "SIP INFO Use Cases", Kaplan, H., "SIP INFO Use Cases",
draft-kaplan-sip-info-use-cases-01 (work in progress), draft-kaplan-sip-info-use-cases-01 (work in progress),
February 2008. February 2008.
[RFC3856] Rosenberg, J., "A Presence Event Package for the Session [RFC3856] Rosenberg, J., "A Presence Event Package for the Session
Initiation Protocol (SIP)", RFC 3856, August 2004. Initiation Protocol (SIP)", RFC 3856, August 2004.
[RFC3680] Rosenberg, J., "A Session Initiation Protocol (SIP) Event [RFC3680] Rosenberg, J., "A Session Initiation Protocol (SIP) Event
Package for Registrations", RFC 3680, March 2004. Package for Registrations", RFC 3680, March 2004.
Author's Address Author's Address
Jonathan Rosenberg Jonathan Rosenberg
Cisco Cisco
Edison, NJ Iselin, NJ
US US
Phone: +1 973 952-5000 Phone: +1 973 952-5000
Email: jdrosen@cisco.com Email: jdrosen@cisco.com
URI: http://www.jdrosen.net URI: http://www.jdrosen.net
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
 End of changes. 7 change blocks. 
12 lines changed or deleted 13 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/