draft-ietf-sipcore-info-events-06.txt   draft-ietf-sipcore-info-events-07.txt 
SIPCORE C. Holmberg SIPCORE C. Holmberg
Internet-Draft Ericsson Internet-Draft Ericsson
Obsoletes: RFC 2976 E. Burger Obsoletes: RFC 2976 E. Burger
(if approved) NeuStar, Inc. (if approved) NeuStar, Inc.
Intended status: Standards Track H. Kaplan Intended status: Standards Track H. Kaplan
Expires: August 2, 2010 Acme Packet Expires: August 5, 2010 Acme Packet
January 29, 2010 February 1, 2010
Session Initiation Protocol (SIP) INFO Method and Package Framework Session Initiation Protocol (SIP) INFO Method and Package Framework
draft-ietf-sipcore-info-events-06 draft-ietf-sipcore-info-events-07
Abstract Abstract
This document defines a method, INFO, for the Session Initiation This document defines a method, INFO, for the Session Initiation
Protocol (SIP) [RFC3261], and an Info Package mechanism. The Protocol (SIP) [RFC3261], and an Info Package mechanism. The
document obsoletes [RFC2976]. For backward compatibility the document obsoletes [RFC2976]. For backward compatibility the
document also specifies a "legacy" mode of usage of the INFO method document also specifies a "legacy" mode of usage of the INFO method
that is compatible with the usage previously defined in [RFC2976], that is compatible with the usage previously defined in [RFC2976],
referred to as "legacy INFO Usage" in this document. referred to as "legacy INFO Usage" in this document.
Conventions Used in this Document Conventions Used in this Document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY" and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
The terminology in this document conforms to the Internet Security
Glossary [RFC4949].
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and 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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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 August 2, 2010. This Internet-Draft will expire on August 5, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with
to this document. Code Components extracted from this document must respect to this document. Code Components extracted from this
include Simplified BSD License text as described in Section 4.e of document must include Simplified BSD License text as described
the Trust Legal Provisions and are provided without warranty as in Section 4.e of the Trust Legal Provisions and are provided
described in the BSD License. without warranty as described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Applicability . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Applicability . . . . . . . . . . . . . . . . . . . . . . . . 5
3. The INFO Method . . . . . . . . . . . . . . . . . . . . . . . 6 3. The INFO Method . . . . . . . . . . . . . . . . . . . . . . . 6
3.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 6 3.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.2. INFO Request . . . . . . . . . . . . . . . . . . . . . . 6 3.2. INFO Request . . . . . . . . . . . . . . . . . . . . . . 6
3.2.1. INFO Request Sender . . . . . . . . . . . . . . . . . 6 3.2.1. INFO Request Sender . . . . . . . . . . . . . . . . . 6
3.2.2. INFO Request Receiver . . . . . . . . . . . . . . . . 7 3.2.2. INFO Request Receiver . . . . . . . . . . . . . . . . 7
skipping to change at page 4, line 31 skipping to change at page 4, line 31
receive INFO requests . . . . . . . . . . . . . . . . . . 25 receive INFO requests . . . . . . . . . . . . . . . . . . 25
12.1.1. Initial INVITE request . . . . . . . . . . . . . . . . 25 12.1.1. Initial INVITE request . . . . . . . . . . . . . . . . 25
12.1.2. Target refresh . . . . . . . . . . . . . . . . . . . . 26 12.1.2. Target refresh . . . . . . . . . . . . . . . . . . . . 26
12.2. INFO request associated with Info Package . . . . . . . . 27 12.2. INFO request associated with Info Package . . . . . . . . 27
12.2.1. Single payload . . . . . . . . . . . . . . . . . . . . 27 12.2.1. Single payload . . . . . . . . . . . . . . . . . . . . 27
12.2.2. Multipart INFO . . . . . . . . . . . . . . . . . . . . 27 12.2.2. Multipart INFO . . . . . . . . . . . . . . . . . . . . 27
13. Security Considerations . . . . . . . . . . . . . . . . . . . 30 13. Security Considerations . . . . . . . . . . . . . . . . . . . 30
14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 31 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 31
14.1. Normative References . . . . . . . . . . . . . . . . . . 31 14.1. Normative References . . . . . . . . . . . . . . . . . . 31
14.2. Informative References . . . . . . . . . . . . . . . . . 31 14.2. Informative References . . . . . . . . . . . . . . . . . 31
Appendix A. Legacy INFO Usage . . . . . . . . . . . . . . . . . . 34 Appendix A. Legacy INFO Usage . . . . . . . . . . . . . . . . . . 33
A.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 34 A.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 33
A.2. ISUP . . . . . . . . . . . . . . . . . . . . . . . . . . 34 A.2. ISUP . . . . . . . . . . . . . . . . . . . . . . . . . . 33
A.3. QSIG . . . . . . . . . . . . . . . . . . . . . . . . . . 34 A.3. QSIG . . . . . . . . . . . . . . . . . . . . . . . . . . 34
A.4. MSCML . . . . . . . . . . . . . . . . . . . . . . . . . . 34 A.4. MSCML . . . . . . . . . . . . . . . . . . . . . . . . . . 34
A.5. MSML . . . . . . . . . . . . . . . . . . . . . . . . . . 34 A.5. MSML . . . . . . . . . . . . . . . . . . . . . . . . . . 34
A.6. Video Fast Update . . . . . . . . . . . . . . . . . . . . 34 A.6. Video Fast Update . . . . . . . . . . . . . . . . . . . . 34
Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 35 Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 34
Appendix C. Change Log . . . . . . . . . . . . . . . . . . . . . 35 Appendix C. Change Log . . . . . . . . . . . . . . . . . . . . . 35
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 38 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 37
1. Introduction 1. Introduction
This document defines a method, INFO, for the Session Initiation This document defines a method, INFO, for the Session Initiation
Protocol (SIP) [RFC3261]. Protocol (SIP) [RFC3261].
The purpose of the INFO message is to carry application level The purpose of the INFO message is to carry application level
information between endpoints, using the SIP dialog signaling path. information between endpoints, using the SIP dialog signaling path.
Note that the INFO method is not used to update characteristics of a Note that the INFO method is not used to update characteristics of a
SIP dialog or session, but to allow the applications which use the SIP dialog or session, but to allow the applications which use the
skipping to change at page 23, line 9 skipping to change at page 23, line 9
security, other than what the underlying SIP protocol provides, it security, other than what the underlying SIP protocol provides, it
MUST be stated in the Info Package specification. MUST be stated in the Info Package specification.
NOTE: In some cases, it may not be sufficient to mandate TLS in order NOTE: In some cases, it may not be sufficient to mandate TLS in order
to secure the Info Package payload, since intermediaries will have to secure the Info Package payload, since intermediaries will have
access to the payload, and beyond the first hop, there is no way to access to the payload, and beyond the first hop, there is no way to
assure subsequent hops will not forwards the payload in clear text. assure subsequent hops will not forwards the payload in clear text.
The best way to ensure secure transport at the application level is The best way to ensure secure transport at the application level is
to have the security at the application level. One way of achieving to have the security at the application level. One way of achieving
this is to use end-to-end security techniques such as S/MIME this is to use end-to-end security techniques such as S/MIME
[RFC3851]. [RFC5751].
10.11. Implementation Details 10.11. Implementation Details
It is strongly RECOMMENDED that the Info Package specification It is strongly RECOMMENDED that the Info Package specification
defines the procedure how implementors shall implement and use the defines the procedure how implementors shall implement and use the
Info Package, or refer to other locations where implementors can find Info Package, or refer to other locations where implementors can find
that information. that information.
NOTE: Sometimes Info Package designer might choose to not reveal the NOTE: Sometimes Info Package designer might choose to not reveal the
details of an Info Package. However, in order to allow multiple details of an Info Package. However, in order to allow multiple
skipping to change at page 32, line 9 skipping to change at page 32, line 9
[RFC2976] Donovan, S., "The SIP INFO Method", RFC 2976, [RFC2976] Donovan, S., "The SIP INFO Method", RFC 2976,
October 2000. October 2000.
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
[RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, [RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768,
August 1980. August 1980.
[RFC4949] Shirey, R., "Internet Security Glossary, Version 2",
RFC 4949, August 2007.
[RFC3080] Rose, M., "The Blocks Extensible Exchange Protocol Core",
RFC 3080, March 2001.
[RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model [RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model
with Session Description Protocol (SDP)", RFC 3264, with Session Description Protocol (SDP)", RFC 3264,
June 2002. June 2002.
[RFC3851] Ramsdell, B., "Secure/Multipurpose Internet Mail
Extensions (S/MIME) Version 3.1 Message Specification",
RFC 3851, July 2004.
[RFC3725] Rosenberg, J., Peterson, J., Schulzrinne, H., and G.
Camarillo, "Best Current Practices for Third Party Call
Control (3pcc) in the Session Initiation Protocol (SIP)",
BCP 85, RFC 3725, April 2004.
[RFC3840] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, [RFC3840] Rosenberg, J., Schulzrinne, H., and P. Kyzivat,
"Indicating User Agent Capabilities in the Session "Indicating User Agent Capabilities in the Session
Initiation Protocol (SIP)", RFC 3840, August 2004. Initiation Protocol (SIP)", RFC 3840, August 2004.
[RFC3841] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, "Caller
Preferences for the Session Initiation Protocol (SIP)",
RFC 3841, August 2004.
[RFC3372] Vemuri, A. and J. Peterson, "Session Initiation Protocol [RFC3372] Vemuri, A. and J. Peterson, "Session Initiation Protocol
for Telephones (SIP-T): Context and Architectures", for Telephones (SIP-T): Context and Architectures",
BCP 63, RFC 3372, September 2002. BCP 63, RFC 3372, September 2002.
[RFC3265] Roach, A., "Session Initiation Protocol (SIP)-Specific [RFC3265] Roach, A., "Session Initiation Protocol (SIP)-Specific
Event Notification", RFC 3265, June 2002. Event Notification", RFC 3265, June 2002.
[RFC3458] Burger, E., Candell, E., Eliot, C., and G. Klyne, "Message [RFC3458] Burger, E., Candell, E., Eliot, C., and G. Klyne, "Message
Context for Internet Mail", RFC 3458, January 2003. Context for Internet Mail", RFC 3458, January 2003.
[RFC3428] Campbell, B., Rosenberg, J., Schulzrinne, H., Huitema, C., [RFC3428] Campbell, B., Rosenberg, J., Schulzrinne, H., Huitema, C.,
and D. Gurle, "Session Initiation Protocol (SIP) Extension and D. Gurle, "Session Initiation Protocol (SIP) Extension
for Instant Messaging", RFC 3428, December 2002. for Instant Messaging", RFC 3428, December 2002.
[RFC4028] Donovan, S. and J. Rosenberg, "Session Timers in the
Session Initiation Protocol (SIP)", RFC 4028, April 2005.
[RFC4145] Yon, D. and G. Camarillo, "TCP-Based Media Transport in
the Session Description Protocol (SDP)", RFC 4145,
September 2005.
[RFC4240] Burger, E., Van Dyke, J., and A. Spitzer, "Basic Network [RFC4240] Burger, E., Van Dyke, J., and A. Spitzer, "Basic Network
Media Services with SIP", RFC 4240, December 2005. Media Services with SIP", RFC 4240, December 2005.
[RFC4730] Burger, E. and M. Dolly, "A Session Initiation Protocol
(SIP) Event Package for Key Press Stimulus (KPML)",
RFC 4730, November 2006.
[RFC4960] Stewart, R., "Stream Control Transmission Protocol", [RFC4960] Stewart, R., "Stream Control Transmission Protocol",
RFC 4960, September 2007. RFC 4960, September 2007.
[RFC4975] Campbell, B., Mahy, R., and C. Jennings, "The Message [RFC4975] Campbell, B., Mahy, R., and C. Jennings, "The Message
Session Relay Protocol (MSRP)", RFC 4975, September 2007. Session Relay Protocol (MSRP)", RFC 4975, September 2007.
[RFC5022] Van Dyke, J., Burger, E., and A. Spitzer, "Media Server [RFC5022] Van Dyke, J., Burger, E., and A. Spitzer, "Media Server
Control Markup Language (MSCML) and Protocol", RFC 5022, Control Markup Language (MSCML) and Protocol", RFC 5022,
September 2007. September 2007.
skipping to change at page 33, line 40 skipping to change at page 33, line 10
Media Control", RFC 5168, March 2008. Media Control", RFC 5168, March 2008.
[I-D.peterson-rai-rfc3427bis] [I-D.peterson-rai-rfc3427bis]
Peterson, J., Jennings, C., and R. Sparks, "Change Process Peterson, J., Jennings, C., and R. Sparks, "Change Process
for the Session Initiation Protocol (SIP) and the Real- for the Session Initiation Protocol (SIP) and the Real-
time Applications and Infrastructure Area", time Applications and Infrastructure Area",
draft-peterson-rai-rfc3427bis-04 (work in progress), draft-peterson-rai-rfc3427bis-04 (work in progress),
October 2009. October 2009.
[W3C.REC-voicexml21-20070619] [W3C.REC-voicexml21-20070619]
Candell, E., Burnett, D., Carter, J., Auburn, R., Lee, A., Burnett, D., Carter, J., Auburn, R., Candell, E.,
McGlashan, S., Lee, A., Porter, B., Oshry, M., Rehor, K., Porter, B., Oshry, M., McGlashan, S., Rehor, K., Bodell,
Bodell, M., Burke, D., and P. Baggia, "Voice Extensible M., Burke, D., and P. Baggia, "Voice Extensible Markup
Markup Language (VoiceXML) 2.1", World Wide Web Consortium Language (VoiceXML) 2.1", World Wide Web Consortium
Recommendation REC-voicexml21-20070619, June 2007, Recommendation REC-voicexml21-20070619, June 2007,
<http://www.w3.org/TR/2007/REC-voicexml21-20070619>. <http://www.w3.org/TR/2007/REC-voicexml21-20070619>.
[I-D.ietf-speechsc-mrcpv2] [I-D.ietf-speechsc-mrcpv2]
Shanmugham, S. and D. Burnett, "Media Resource Control Shanmugham, S. and D. Burnett, "Media Resource Control
Protocol Version 2 (MRCPv2)", Protocol Version 2 (MRCPv2)",
draft-ietf-speechsc-mrcpv2-20 (work in progress), draft-ietf-speechsc-mrcpv2-20 (work in progress),
August 2009. August 2009.
[I-D.saleem-msml] [I-D.saleem-msml]
Saleem, A. and G. Sharratt, "Media Server Markup Language Saleem, A. and G. Sharratt, "Media Server Markup Language
(MSML)", draft-saleem-msml-09 (work in progress), (MSML)", draft-saleem-msml-09 (work in progress),
July 2009. July 2009.
[RFC5751] Ramsdell, B. and S. Turner, "Secure/Multipurpose Internet
Mail Extensions (S/MIME) Version 3.2 Message
Specification", RFC 5751, January 2010.
[Ecma-355] [Ecma-355]
"Standard ECMA-355 Corporate Telecommunication Networks - "Standard ECMA-355 Corporate Telecommunication Networks -
Tunnelling of QSIG over SIP", ECMA http:// Tunnelling of QSIG over SIP", ECMA http://
www.ecma-international.org/publications/standards/ www.ecma-international.org/publications/standards/
Ecma-355.htm, June 2008. Ecma-355.htm, June 2008.
Appendix A. Legacy INFO Usage Appendix A. Legacy INFO Usage
A.1. General A.1. General
 End of changes. 18 change blocks. 
53 lines changed or deleted 25 lines changed or added

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